No-upload splitting usually means browser-side processing
In a browser-side split workflow, the file is opened and page selections are applied by JavaScript on your device. The provider does not need the selected PDF on its server for the core split task.
What this can help protect
This approach can keep the PDF contents, page thumbnails, and selected ranges off the provider's application backend for that operation. That is useful for internal documents, drafts, invoices, and routine office files.
What still depends on your environment
A large file can still stress your browser memory, and an older device can still feel slow. No-upload does not mean no limits. It means the core file operation happens locally.
When split is the right local workflow
Use 拆分 PDF when you want pages 3-7 as a new file, one appendix from a report, or a few selected sheets from a scan. If you are deleting only a couple of pages from a mostly finished document, 删除 PDF 页面 may fit better.
What no-upload does not automatically guarantee
A site can still have normal analytics, hosting logs, or cookie storage at the page level. That is why tool-level wording and the site privacy page both matter.
Related tools and guides
Open 拆分 PDF for the actual task, read 不上传 PDF 工具真的更安全吗 for the broader privacy question, and compare PDF 拆分与删除页面的区别 if you are deciding between extraction and trimming.