Extract Pages from a PDF (Create a New PDF from Selected Pages)

Affiliate disclosure: This page contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you.

You export a PDF for a form, only to discover the scanner settings produced a 25MB monster for three pages. In practice, the fastest wins come from fixing the source first, then doing one clean optimisation pass (not five repeated re-saves).

In this PDF guide—Extract Pages from a PDF (Create a New PDF from Selected Pages)—you’ll learn what makes files large, which changes deliver the biggest savings, and how to keep the result readable and portal-friendly. This is written for people who want results without guesswork.

When you’re ready, use Extract Pages (and the related tools listed below). The approach is: clean first → optimise once → verify.

Extract only what you need (and shrink size instantly)

Extracting specific pages is one of the cleanest ways to reduce file size and create submission-ready bundles.

Workflow

Select the exact page range.
Extract using Extract Pages.
If you’re building a pack, merge extracted parts in order using Merge PDF.

💡 Helpful gear for this task: Extracted PDF sets are easier to manage when stored separately — a multipack of USB drives means you can keep one set per project without any mix-ups.

🛒 Search on Amazon — USB Flash Drive Multi-Pack Opens Amazon search · Affiliate link · No extra cost to you

Quick tool path:

A 60‑second action plan

Remove pages you don’t need (blank pages, duplicates).
Fix order/rotation so the document is reviewable.
Run one clean optimisation pass (don’t repeat it five times).
Verify at 100% zoom and test on mobile.

Most “stuck” cases are solved by the first two steps. Once the file is structurally clean, optimisation becomes predictable.

Quality check before you hit “Submit”

Don’t trust the thumbnail preview—open the file properly and verify the details.

Open at 100% zoom and check the smallest text (names, dates, serial numbers).
Scroll every page for rotation, missing pages, and blank pages created by exports.
Confirm file size against the true limit (some portals count after upload).
Test on mobile if the recipient opens it on a phone.
Do a test upload if possible; validators can reject encryption or unusual PDF structures.

Troubleshooting by error message

Use the error text as a clue. The fix for “too large” is different from “can’t be processed.”

“File too large”: Reduce size by removing pages, resizing images, or splitting. Start with Split PDF if the limit is strict.
“File can’t be processed / invalid”: Re-export a clean copy and avoid encryption. A single clean pass via PDF tools often resolves validator errors.
“Upload failed” (but size is ok): try smaller parts or a lighter file (timeouts are common).
“Security settings / password protected”: portals often reject encrypted files—use an unencrypted export.

Real-world examples (what “good” looks like)

As a sanity check, compare your output to typical ranges for similar documents.

1–3 page form: commonly under 500KB–2MB (depends on scans/photos).
10–20 page text report: often 1–5MB when exported cleanly and images optimised.
Scanned pages: biggest wins come from grayscale + sensible DPI (~150–200).

On mobile: what changes

Mobile uploads fail more often due to timeouts. If a portal keeps failing, try smaller parts or a lighter file and upload over stable Wi‑Fi.

Common mistakes

Using PNG for photos when JPG would be much smaller.
Pasting huge screenshots/photos (4000–8000px) when 1500–2500px is enough.
Compressing five times in a row instead of doing one clean export.
Uploading the wrong format (PNG instead of JPG; PPTX instead of PDF).
Exporting via “Print to PDF” (often flattens text into images).
Leaving comments/annotations when the portal expects a clean file.
Embedding videos in slides when a link would do.

FAQ

How do I get even smaller without blur?

Prefer splitting, grayscale for scans, and resizing images before export. Extreme compression is what creates blur.

Is it safe for private documents?

Prefer tools that process locally in the browser and keep a clean local copy. For highly sensitive files, avoid unknown uploaders.

What should I do on mobile?

Do the final check on the same device you’ll submit from. Mobile viewers can reveal issues (blurry text, missing fonts) you won’t notice on desktop.

Why did the file get bigger after editing?

Some editors add incremental-save history and duplicated resources. A clean export + one optimisation pass usually fixes it.

Will this change layout?

If you keep the file in the same format (PDF stays PDF) and avoid printing-to-PDF, layout should remain stable. Always verify at 100% zoom.

Related guides you can use next

Final takeaways

For most submissions, the winning pattern is consistent: clean first → optimise once → verify. That keeps quality high and reduces portal errors.

Next step: run Extract Pages and use the checklist above before you upload or send.