Guide
A no-upload split flow usually means the PDF is read and rearranged in your browser instead of being sent to an application server for the core job. That can be useful, but it is still worth understanding the limits.
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.
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.
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.
Use Split 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, Remove PDF Pages may fit better.
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.
Open Split PDF for the actual task, read Are no-upload PDF tools safer? for the broader privacy question, and compare Split PDF vs Remove Pages if you are deciding between extraction and trimming.