2026-07-31

PDF too large to email? How to split it into files that fit — without uploading anywhere

"PDF too large to email" shouldn't still be a real problem in 2026, and yet it is, because email providers still enforce small, hard caps on attachments. Gmail's own Help documentation puts the ceiling for a personal account at 25 MB, full stop — go over that and Gmail quietly strips the file out of the message and swaps in a Google Drive link instead, whether you meant for that to happen or not. Outlook.com's own sending-limits support page states the identical number for personal accounts: 25 MB. Work email is often tighter, not looser: Microsoft's own guidance on reducing attachment size notes that a typical Exchange (business) account defaults to just 10 MB, covering the message and its attachments together. A scanned exhibit bundle, a signed multi-page contract, or a stack of assembled reports can clear any of those ceilings without anyone doing anything unusual — and "just compress it," the fix people reach for first, isn't something every free tool can actually do. Splitting the file into pieces that each fit under the limit is a different fix for a specific version of this problem — worth understanding exactly what it can and can't do before you start.

Splitting isn't compressing, and the difference decides whether it'll actually help

Splitting a PDF doesn't shrink anything — it redistributes the same total bytes across more files. A 22 MB, 40-page PDF split into two 20-page halves comes out to roughly two ~11 MB files (splitting overhead aside), not two lighter documents. That's genuinely useful when the rule you're up against is "no single attachment over 25 MB," since the combined size of the pieces staying the same is fine — only the size of any one file matters. It stops helping the moment the real problem isn't page count but pixel count: a document with even one very high-resolution scanned page can have that single page weigh more than the limit on its own, and splitting the other pages away from it does nothing to change what that one page weighs. NearPDF doesn't have a page-resize or image-compression tool — its toolset stops at merge, split, organize, delete, rotate, watermark, page numbers, and PDF-to-JPG conversion — so if one oversized page is the actual bottleneck, splitting genuinely won't fix it, and the honest next step is re-scanning that page at a lower resolution before you start, not expecting a split tool to solve a compression problem.

NearPDF's split tool answers one specific question: "every page, as its own file"

NearPDF's own description of its split tool is exact about what it does: "Extract every page as its own PDF." That's the whole mechanism — it produces one PDF per page, delivered together as a zip, no exceptions and no "N pages per output file" setting. That's the right tool when you need every page individually addressable — pulling a single page out to send on its own, or turning a whole document into standalone single-page files. It's the wrong tool if what you actually want is one file containing pages 1 through 20 and a second file containing pages 21 through 40, because split doesn't produce ranges at all — every output is exactly one page, always.

For a page range instead, delete the pages you don't want and save

NearPDF's delete tool doesn't have a "keep pages 1–20" shortcut either — there's no range field, no multi-select, no "select all then invert" control. What it has is a plain per-page ✕ button on each page in the workspace grid. That's exactly enough if you're willing to work backward: add the file, click ✕ on every page outside the range you want to keep, and save — the result is one file containing only that range. To get a second file covering the rest, load the same source file into the delete tool again and remove the opposite set of pages. For a two-way split of a 40-page document, that's two passes of roughly twenty clicks each — tedious if you're carving a hundred-page file into many small pieces, but entirely realistic for the common case: one big file split into two or three pieces, each clearing a specific size limit.

A practical workflow

A realistic sequence, entirely inside NearPDF, with nothing uploaded anywhere: merge exhibits or attachments together first if they started as separate files; decide how many pieces you actually need based on the limit you're working against (a 25 MB Gmail or Outlook.com cap is usually workable as two or three pieces; a 10 MB business-account cap may take more); then either run split for one file per page, or use delete twice per split to carve out the specific ranges you want. Rotate any page a scanner delivered sideways — the same per-page rotate control described in NearPDF's rotation post — before you save, since fixing rotation after export means redoing the split. Save each resulting file with a name that makes the range obvious — "contract-pages-1-20.pdf" beats "contract (3).pdf" — so whoever gets the second half of an email chain knows what they're opening without renumbering it themselves.

The honest limits, restated

None of this makes a file's total data smaller — splitting only ever produces more files that add up to the same size as the one you started with, and the pieces you can make are limited to "every page" or "whatever range you're willing to click through by hand," not arbitrary named chunks in one click. If the real bottleneck is a single oversized page rather than a document with too many pages, no amount of splitting gets that page under a limit — that's a resolution problem, fixed by re-scanning or re-exporting the source at lower quality, not something a page-splitting tool can retroactively repair. For the much more common case — a multi-page document that's simply too big as one file for an inbox with a real cap — carving it into two or three pieces you control, entirely on your own device, gets you there without uploading anything to find out whether it worked.