A 300 MB scan set will never survive an email server: Gmail caps attachments at 25 MB, Outlook at 20 MB, and corporate servers often enforce 10 MB — before the ~37% base64 inflation email encoding adds on top.
The fix is not another cloud link. Split the file into email-size chunks, send them as ordinary attachments across one or several emails, and have the recipient rejoin them into a byte-identical copy.
Try it now: 📦 Large File Split & Join · ✂ Split PDF · 🗜 Compress PDF
Pick a chunk size the server cannot refuse
Size chunks for the strictest server in the chain, not yours: 20 MB slides under Gmail and Yahoo, while 9 MB clears almost every corporate Exchange default. Smaller chunks also resume painlessly — one failed 9 MB attachment re-sends in seconds, a failed 2 GB upload restarts from zero.
As a rule of thumb, divide the portal or mailbox limit by 1.4 to cover encoding overhead, then round down. A 25 MB Gmail ceiling becomes ~17 MB safe chunks; a 10 MB office server becomes ~7 MB.
Split, send, and rejoin without losing a byte
Binary chunks are transport copies, not mini-PDFs — nobody can open a single .part file, and that is expected. Numbering keeps order unambiguous: big.pdf.part001 through big.pdf.partNNN rejoin in exactly that sequence.
Rejoining concatenates bytes, so one missing or renamed part corrupts the result. Always count parts before rejoining (a 10-part set needs all ten), and verify the rejoined size equals the sum of the chunks.
Check the giant file before moving gigabytes
Moving gigabytes to discover a truncated trailer wastes an afternoon. Inspect the header (%PDF version) and trailer (startxref plus %%EOF markers) with a no-load check first — it reads kilobytes, not gigabytes.
A healthy trailer means the file will survive the trip; a missing one means repair or re-export before you split, because no transport method fixes corruption.
Steps
- Open Large File Split & Join directly and upload the giant file
- Choose Split mode and set MB per chunk for the strictest recipient server
- Download the .part files and attach them across one or several emails
- On the receiving end, upload all parts in numeric order with Join mode
- Download the rejoined file and confirm its size matches the original
Pro tips
- Name the email subject with part counts ('Plans 3/10') so nothing goes missing.
- Keep one local copy of the original until the recipient confirms the rejoin.
Frequently asked questions
Why does a 24 MB PDF bounce on a 25 MB limit?
Email encoding inflates attachments by roughly 37% in transit, so a 24 MB file travels as ~33 MB. Aim for two-thirds of the stated limit to be safe.
Can the recipient open a single chunk?
No. Chunks are raw byte slices for transport, not valid PDFs. They must all be rejoined in order first — then the result opens normally.
What if one email with chunks gets lost?
Resend just the missing part numbers. Join mode only needs the complete ordered set at the end; arrival order across emails does not matter.
Is there a maximum file size for splitting?
Splitting streams without loading, so files up to 6 GB work on desktops. Shrinking (compression) is different — it must decode pages and caps around 1 GB.