PDF Split
How to use this PDF split tool
- Select a PDF — the page count appears automatically.
- Enter a from/to page range and click "Extract Range", or click "Split Every Page".
- Your file(s) download automatically.
What does "split every page" do?
It downloads one PDF file per page in your document. For a range extraction, you get a single PDF containing only the pages you specify.
Why do multiple downloads happen with "Split Every Page"?
Each page becomes its own PDF file, so a 10-page document produces 10 separate downloads — your browser may ask permission to allow multiple downloads at once.
Can I extract non-consecutive pages?
Range extraction currently supports a single continuous range. For non-consecutive pages, run the extraction multiple times with different ranges.
What happens to page content when splitting
Splitting works the same way merging does, just in reverse: the tool reads the source PDF's internal page objects — text, vector graphics, embedded images, fonts — and copies the ones you selected into a new, independent PDF file, without rasterizing or re-encoding anything. This is why a split PDF has exactly the same visual quality as the original: extracted text stays selectable and searchable, images keep their original resolution, and vector graphics remain sharp, since the operation is really about reorganizing which page objects belong to which file, not redrawing content.
Why your browser might block or ask about multiple downloads
Splitting a multi-page document into individual files means this tool triggers one file download per page, all within a few moments of each other — and most browsers have a built-in safeguard against a website silently triggering many downloads at once, since that pattern is also how malicious sites sometimes try to flood a device with unwanted files. The first time you use "Split Every Page" on a document with several pages, your browser will likely show a permission prompt asking whether to allow multiple downloads from this site; allowing it lets the rest of the pages download normally, and the browser typically remembers that choice for the site going forward.
Range extraction vs. splitting every page
These two modes serve different practical needs. Range extraction is the right tool when you know exactly which contiguous section you need — pulling out a specific chapter, a signed page from a longer contract, or a particular exhibit from a larger filing — and produces one clean file containing just that range. Splitting every page is built for a different workflow: turning a scanned batch of documents (where every page happens to be a separate, unrelated item) back into individual files, or feeding pages one at a time into another tool that only accepts single-page inputs. Reaching for the wrong mode usually just means an extra step, not a real problem — extracting a range one page at a time works too, just less conveniently.
What doesn't carry over when you split a document
Anything that depends on the document's overall structure can behave unexpectedly once pages are pulled out of their original context. Bookmarks or a table of contents that reference specific pages will point to the wrong location, or nowhere at all, in a file that no longer contains those original page numbers. Page numbering baked directly into the page content itself (a header reading "Page 5 of 20", for instance) stays exactly as printed, since it's just part of the page's visual content — it won't recalculate to reflect the new, smaller document. Internal links between pages within the original document also won't resolve correctly if the page they pointed to wasn't included in the extracted range.
Limitations of this tool
Range extraction currently supports one single, continuous range per operation — extracting pages 3-5 and 9-11 from the same document in one pass isn't supported; you'd run the extraction twice with different ranges instead. This tool also doesn't merge extracted pieces back together (this site's PDF merge tool handles that direction), doesn't support rotating or deleting individual pages independent of a range, and works entirely in your browser's memory, so extremely large source documents (many hundreds of pages or a very large file size) may be slower to process, limited by your device's available memory.