Byte-Accurate PDF Parting · Local Browser Engine

Split PDF by Exact File Size (MB) or Page Range

Break oversized PDFs into clean parts strictly under 2 MB, 4 MB, 5 MB, or 10 MB for immigration portals, court e-filing, and corporate gateways—without blurry over-compression or server uploads.

✓ File contents stay in your browser

✓ Strips unreferenced objects per part

✓ Individual PDFs + 1-click ZIP export

📏

Split by Max File Size

Strict MB Cap · Auto Page Grouping

Packs as many sequential pages as possible into each part while keeping every output PDF under your exact decimal MB limit.

Max per part:

Apply size limit & open splitter →

Click to choose PDF or drag & drop here

Opens directly in the byte-accurate PDF splitter

📑

Split by Page Count or Ranges

Every N Pages · Custom Intervals

Extract specific chapters (e.g. 1-3, 4-8, 9-) or burst a multi-record packet into single-page or fixed-page PDFs.

Split rule:

Open page range splitter →

Click to choose PDF or drag & drop here

Supports encrypted PDFs when you enter the open password

Portal Size Caps & Why Byte-Based PDF Splitting Matters

Most free cloud PDF splitters only split by page numbers—or lock "split by MB" behind a monthly subscription while requiring you to upload sensitive documents. NeatCompress measures real output bytes locally in your browser.

Submission Portal / Use Case	Typical Single-File Cap	Recommended Workflow	Why Local Browser Processing Helps
Visa & Immigration (IRCC, UKVI, Visa Centers)	2 MB – 4 MB per upload slot	Compress once → Split at ≤ 2 MB or ≤ 4 MB	Passports, bank statements, and civil records never leave your laptop
USCIS / Administrative E-Filing	6 MB – 12 MB per exhibit	Split by Max Size (≤ 5 MB or ≤ 10 MB)	Keeps 200+ DPI text crisp for OCR instead of over-compressing scans
Court Exhibits & Legal Discovery	10 MB – 25 MB per filing	Split at ≤ 10 MB or custom exhibit page ranges	Preserves original vector text, bookmarks, and legible signatures
Accounting & Invoice Batches	1 record per PDF	Split Every 1 Page + Download ZIP	Zero upload/download roundtrip for dozens of pages

How orphan-object stripping keeps split parts small

Naive PDF splitters copy the entire document resource dictionary—including embedded fonts and full-document XObject images—into every single output chunk, causing a 10 MB PDF split in half to produce two 8 MB files. NeatCompress rebuilds each chunk cleanly and strips unreferenced page resources so each part reflects only the pages inside it.

When to compress first vs. split right away

Compress first (1MB / 2MB PDF Compressor) if your document contains uncompressed phone photos and needs to fit into a single-file upload slot.
Split directly by MB if your PDF is already compressed or has 40+ scanned pages where further downsampling would blur small print, stamps, or barcodes.

Frequently Asked Questions

How do I split a PDF into parts under a specific MB limit?

Choose your maximum part size (such as 2 MB, 4 MB, 5 MB, or 10 MB) on the first card and select your PDF. NeatCompress measures real serialized byte sizes in a local Web Worker and groups consecutive pages so each output PDF stays strictly below your chosen MB ceiling, then bundles all parts into a one-click ZIP download.

Why split a PDF by size instead of compressing it further?

Multi-page scanned documents (like 80-page bank statements, tax returns, or medical records) eventually become unreadable if compressed down to 2 MB. Portal rules for immigration (USCIS, IRCC, UKVI), court e-filing, and university applications explicitly allow multi-part uploads (Part 1, Part 2) as long as each file is legible and under the size cap.

What happens if a single page in my PDF is already larger than my MB limit?

If an individual high-DPI scanned page exceeds your target cap on its own, the splitter isolates that page and clearly flags it as over the limit. You can compress the PDF first in Smart or Raster mode to bring individual page sizes down, then split into clean multi-page parts.

Are my confidential tax, legal or visa PDFs uploaded to a server?

No. Document parsing, orphan object cleanup, and byte-accurate splitting run locally inside your browser via WebAssembly and Web Workers. Your PDF contents never touch an external server.