Split a PDF into individual page files
Splitting a PDF is the inverse of merging: you select a subset of pages from a source document and build a new document containing only those pages, with cross-references rebuilt and unused objects garbage-collected. Three modes cover most use cases. Custom ranges let you extract arbitrary selections using notation like "1-5, 8, 12-15"useful when you need to pull one chapter from a 300-page book. Fixed intervals split every N pages, which is how you take a 200-page scanned batch and break it into 50 four-page documents. Individual page mode produces one output file per source page, useful when every page is a separate standalone document (invoices scanned in batch, for example). Because the splitter operates on the PDF object model rather than re-rendering, extracted pages are pixel-identical to the original. A page with 300 DPI embedded images stays 300 DPI. A page with vector text stays vector. Splitting a 50 MB document to extract 5 pages typically produces an output in the single-digit megabytes, not exactly 10% of the source, because shared resources like fonts are embedded fresh in the output, but close to proportional with the page count.
Initializing in your browser…
Extract embedded images (photos, logos) from PDF
Extract all text content from a PDF document
Add your signature to PDF documents. Draw, type, or upload your signature, then position it anywhere on the page. Perfect for contracts, agreements, and official documents.
A 60-page report needs section 3 (pages 18–27) sent on its own.
Input
report.pdf · extract pages 18–27
Output
report_p18-27.pdf, 10 pages, fonts and layout unchanged
Selected page ranges are pulled into a new PDF without re-rendering, so text stays selectable and vector graphics stay sharp. You can split by range, fixed size, or one file per page.
Splitting a PDF is the inverse of merging: you select a subset of pages from a source document and build a new document containing only those pages, with cross-references rebuilt and unused objects garbage-collected. Three modes cover most use cases. Custom ranges let you extract arbitrary selections using notation like "1-5, 8, 12-15"useful when you need to pull one chapter from a 300-page book. Fixed intervals split every N pages, which is how you take a 200-page scanned batch and break it into 50 four-page documents. Individual page mode produces one output file per source page, useful when every page is a separate standalone document (invoices scanned in batch, for example). Because the splitter operates on the PDF object model rather than re-rendering, extracted pages are pixel-identical to the original. A page with 300 DPI embedded images stays 300 DPI. A page with vector text stays vector. Splitting a 50 MB document to extract 5 pages typically produces an output in the single-digit megabytes, not exactly 10% of the source, because shared resources like fonts are embedded fresh in the output, but close to proportional with the page count.
Pull out a specific chapter or section to send to a colleague without sharing the entire document.
Extract only the pages you need so the resulting file is smaller and easier to email.
Break a large scan into individual documents for filing or categorization.
The splitter parses the source PDF's cross-reference table to enumerate page objects, then for each extraction it builds a new document whose /Pages tree references only the requested pages. Objects reachable from those pages, fonts, images, color profiles, pattern dictionaries, are copied into the output. Objects not reachable (pages not selected, form fields on excluded pages, thumbnails for excluded pages) are omitted, which is where the file-size reduction comes from. The output is a standalone, valid PDF that does not depend on the source file being present.
One behavior worth understanding: PDFs can contain objects that span pages. Form fields attached at the document root, JavaScript actions tied to document open/close, and bookmarks pointing into the body of the document are all examples. The splitter takes a reasonable-default approach: form fields and JavaScript actions are preserved on the output, bookmarks are rewritten to reference only the extracted pages (bookmarks pointing to excluded pages are dropped), and document-level metadata like title and author is copied as-is. If the source has a strict attachment to the original page set, for example, a multi-page form where field values depend on pages outside the extracted range, those fields will appear blank in the output.
The most common real-world use of splitting is sharing a subset of a larger document without leaking the rest. A common pattern: you need to send a contractor pages 47-58 of a spec document but not the whole thing. Range-mode extraction of "47-58" produces an exactly-twelve-page output with just those pages, retaining original resolution and formatting. The PDF title metadata remains from the source; if you want the output title to reflect the excerpt, edit the metadata before sending. For sensitive documents, also consider running the output through a metadata stripper to remove author names and editing history.
Yes. Select the "individual pages" option and each page will be saved as its own PDF.
No. Pages are extracted as-is without any re-encoding or quality loss.
Enter comma-separated values like "1-3, 7, 10-12" in the page range field.
PDF parsing and editing happen in your browser. Documents, and everything inside them, are never uploaded or stored remotely.