What this tool does
It reads the source PDF and creates new PDFs from selected pages, ranges, or per-page mode.
Split PDF pages by range or extract individual pages locally in your browser. The core workflow runs in your browser with no upload step to Plain Tools.
Upload your file, choose options, and download the processed output in the result area.
Result section
When processing finishes, a download action appears below. If output quality is not ideal, adjust options and run again.
Privacy and trust
Processed locally in your browser. Files never leave your device.
Best-effort split. Invalid page ranges or damaged PDFs may fail.
Split PDF extracts selected pages or ranges from one source PDF. Processing stays local in your browser.
It reads the source PDF and creates new PDFs from selected pages, ranges, or per-page mode.
One PDF and a page selection such as 1,3,5-7.
A single extracted PDF or multiple PDFs (often as ZIP).
Page extraction and export run locally on-device.
Invalid ranges or pages outside document length are rejected.
Split PDF is designed for people who want a practical browser-first workflow instead of uploading files to a third-party service just to complete a routine task. Split PDF runs in your browser for local, private document handling. Process files directly on your device without a server-side upload step for core workflows. Split PDF pages by range or extract individual pages locally in your browser. Private, fast, and no upload required.
Page extraction and export run locally on-device. That matters when you are handling work files, drafts, forms, exported data, or other material that should stay under your control until you decide to share the result. It also removes the usual upload delay, which keeps the workflow lighter and easier to repeat when you need to adjust settings and try again.
In most cases, people use Split PDF to prepare documents quickly before sharing or archiving. handle privacy-sensitive files without third-party upload workflows. Before you publish, archive, or forward the output, do a quick review of the result because invalid ranges or pages outside document length are rejected.
Local browser workflows reduce exposure for private files because the main processing path runs on your device instead of starting with an upload to a third-party service. That is useful when the document, image, text, or encoded payload contains work material, customer data, or anything you would rather review locally before sharing.
Browser-based tools are also direct. You open the file, run the operation, and download the result without waiting for remote queues or account-gated limits. You can review Plain.tools privacy claims in Verify Claims.
This page also includes answers to 3 common questions and links to 3 related workflows, so you can validate the process first and move to the next step without leaving the tool cluster.
Known limitations
Best-effort split. Invalid page ranges or damaged PDFs may fail. For complex files, run a quick output check before sharing or archiving.
Use values such as 1,3,5-7. Invalid or out-of-range pages are rejected before export.
Yes. Page extraction keeps the source page visuals because it copies pages rather than re-rendering.
Yes. Per-page mode creates one output per page, typically packaged as ZIP for convenience.
These routes answer common modifier searches such as offline, no-upload, mobile, large-file, and sharing-specific workflows while reusing the same core tool.
Prefer a page tailored to a specific query? These routes use the same underlying tool workflow.
If you want a step-by-step explanation before using the live workspace, start with the matching guide and then come back to this tool.
Learning CentreContinue with related tools, comparisons, and practical guides.
Drop a PDF here, or click to browse
Single file input. Local-only processing.
Click or drop files to continue
No PDF selected yet.
Extracts selected pages into one new PDF.