Skip to content

Extract PDF pages

Save chosen pages as a new PDF.

Drop a PDF here

Only your browser reads them.

How to use Extract pages

  1. Load your PDF. Drop a file onto the upload zone or click Choose a file to render local page thumbnails.
  2. Pick pages to keep. Click individual page previews in the grid, or use Select all and Clear to adjust your selection.
  3. Choose Save as mode. Select One PDF for a single combined document, or A PDF for each page for separate files.
  4. Click Extract pages. Save the generated file to your device, or hand it off to Merge with another or Organize pages.

Your files are processed on this device and never uploaded. They stay private, and there's nothing to delete afterwards.

How does browser page extraction copy PDF pages without quality loss?

Browser extraction builds a new PDF document in memory by copying only the selected page nodes and their referenced fonts, images, and color spaces, leaving 0 bytes uploaded to any server. Because the worker transfers raw PDF object streams rather than rendering pages to bitmaps, selectable text, vector line art, and embedded photos keep their original fidelity.

Traversing the ISO 32000 page tree inside a Web Worker

Under the PDF Association ISO 32000-2 Specification, a PDF does not store pages as a flat image sequence. Instead, the document catalog points to a hierarchical /Pages tree whose leaf nodes are individual /Page dictionaries referencing content streams and shared resources.

When you drop a PDF, the interface renders lightweight local previews and stores their object URLs in memory until extraction finishes or you click Change file, at which point every preview URL is revoked. If your goal is to strip a few unwanted sheets while keeping most of a packet intact, you can also remove unwanted pages from a document using the same visual grid.

Preserving vector text, embedded fonts, and original images

In One PDF mode, the worker calls copyPages() with your chosen 0-based page indices, inserts them into a fresh document, sets the producer metadata, and writes <stem>-extract.pdf. Every hyperlink annotation, vector curve, and embedded font subset belonging to those pages travels along cleanly so you can save pages from a PDF without losing text searchability.

This structural copy avoids the file bloat and blurry typography caused by tools that screenshot pages into JPEGs before rebuilding a PDF. Note that password-protected PDF files must be unlocked before their page tree can be read locally.

Choosing between One PDF and A PDF for each page

Visual page picking handles both quick excerpts and multi-file bursting from one interface. Depending on how you plan to distribute the output, the Save as radio group switches between two distinct worker pipelines.

Selecting non-consecutive thumbnails with Select all and Clear

After the thumbnail grid loads, click any page card to toggle it on or off while watching the Pages to keep counter in the sidebar. The Select all and Clear controls let you invert large selections quickly without clicking dozens of thumbnails one by one.

At least 1 page must remain selected before the Extract pages button activates, preventing empty zero-page documents. Heavy binary parsing runs off the main thread via the MDN Web Workers API Documentation, keeping thumbnail scrolling responsive even on multi-hundred-page manuals.

Single-pass export naming for individual page files

When you choose A PDF for each page, the worker calls extractSeparatePages() and parses the source PDF only once. It loops through your selected page indices, creates a standalone single-page PDF for each entry, and names it <stem>-page-<N>.pdf using 1-based page numbers.

If you are pulling pages apart primarily to stay under strict attachment caps, you can also divide oversized files under email limits by targeting a megabyte threshold instead of clicking individual pages.

Comparing Extract PDF pages with splitting and deletion workflows

Picking the right page-management tool depends on whether you know the exact pages visually, need fixed numerical ranges, or want to break a file along structural boundaries.

Workflow tool Selection method Output behavior Best use case
Extract PDF pages Click visual thumbnails One combined PDF or one PDF per page Pulling specific non-consecutive pages
Split PDF Type numerical page ranges Multiple PDFs per range Dividing manuals into fixed chapter ranges
Delete PDF pages Click pages to discard One PDF with remaining pages Dropping cover sheets or blank scans
Split by bookmarks Reads PDF outline tree One PDF per top-level bookmark Exporting chapters from long reports
Split by file size Target megabyte limit Sequential chunks under size cap Fitting attachments into email gateways

Every extracted file preserves native stream structures as described in the Library of Congress PDF 2.0 Format Description. When you already know the exact page numbers (such as pages 1-10 and 11-25) without needing visual previews, use our range tool to split documents into page-range chunks faster.

Organizing extracted pages and downstream document workflows

Extracting a subset of pages is often the first step before combining exhibits, reordering appendices, or archiving individual receipts. Because the result panel keeps your output in browser memory, you can chain the next operation immediately.

Pulling out chapters or invoices from large packets

Legal packets, scanned invoice batches, and financial statements frequently bundle unrelated sections into one large file. Clicking only the relevant thumbnails isolates client-ready excerpts right away while leaving confidential pages behind on your device. Because page extraction builds a fresh document, document-level outline bookmarks are not carried over automatically.

Tip: If you are extracting chapters from a structured manual or report that already has a clickable table of contents, check whether outline bookmarks exist first so you do not have to scroll through hundreds of thumbnails.

For book-length PDFs with embedded outline trees, a bookmark-driven PDF chapter splitter separates every section automatically in one click.

Merging and reordering extracted files in your browser

Every output file conforms to the IETF RFC 8118 PDF Media Type (application/pdf), ensuring reliable opening across desktop, mobile, and print workflows. From the completion panel, click Merge with another to append your extracted pages to another document, or choose Organize pages to reorder and rotate them before sharing.

Questions

What is the difference between Extract PDF pages and Split PDF?

Extract PDF pages lets you click specific visual thumbnails and pull just those pages into a new file or individual page files. Split PDF is built for dividing an entire document into consecutive range chunks.

Does extracting pages reduce PDF text or image quality?

No. The tool copies the underlying PDF page objects, vector drawing streams, fonts, and embedded images directly without re-encoding or rasterizing them to pixels, so text searchability remains completely intact.

Can I save every selected page as its own separate PDF?

Yes. Switch the Save as option to A PDF for each page. The worker parses your source PDF once and outputs an individual PDF file for every selected page.

Are non-consecutive pages supported when extracting?

Yes. You can click any combination of pages across the document, such as pages 2, 5, and 14, and export them together in order or as separate single-page PDFs.

How are extracted individual PDFs named?

In One PDF mode, the output is named with an -extract.pdf suffix. When exporting A PDF for each page, each file uses the original filename stem followed by -page-N.pdf using 1-based page numbers.

Is the original source PDF modified when I extract pages?

No. Your original file is read into browser memory as a read-only byte array and never overwritten. The extracted output is saved as a brand-new PDF document.

Updated