Initializing secure environment…
Initializing secure environment…
Break a document that is too big for a form or a mail server into parts that each fit. Set the ceiling in kilobytes or megabytes and the splitter measures the finished parts, not a guess based on page count. A part is closed as soon as adding the next page would cross your limit, so the result respects the cap exactly. Nothing is uploaded, there is no watermark, and no sign-up — which matters when the file is a payslip or a medical record.
To split a PDF by size, set a maximum part size in KB or MB and the tool cuts the document where each page would push it over the limit. Every part is measured after cutting, so each one genuinely stays under your cap.
Set 10 MB and the tool closes each part at the last page that fits. A parts-per-page count readout tells you what to expect before you start, so you can sanity-check the number against the page count and catch a mistyped limit immediately.
Three common reasons: the form counts the whole session rather than the file, the form has a page limit as well as a size limit, or the form rejects documents with an owner password set. Split by size and page count together, and flatten the parts to remove encryption and metadata.
If the document is 3 MB and mostly photographs, compression alone will get it under the cap and you keep one file. If it is 30 MB of scans, no honest compressor will reach 2 MB without destroying the pages, and splitting is the correct answer instead.
Parts are named with their page range, so 001-24, 025-48 and so on. That is enough for a human and enough for a script — and it survives the round trip through an email client that renames attachments to attachment-1.pdf.
It adds pages in order and closes the current part at the last page that still fits under your limit. That keeps every part under the cap, and it keeps pages in their original order. It cannot re-compress content, so a single page larger than your limit will produce a part that is still too big — the tool says so rather than pretending.
Then no split can get that page under the limit without altering it. Compress the PDF first, which re-encodes the images inside that page, then split the smaller file. The tool will point at the oversized page instead of silently emitting a part that fails the form.
Before. Splitting never changes content, so a part measured at 9.8 MB is exactly 9.8 MB on disk. If you want them smaller, run the compress tool on the parts afterwards.
Text is fully preserved because pages are copied rather than re-rendered. Bookmarks inside a part are kept and re-pointed; a bookmark that pointed past the cut is dropped.
Yes, and combining the two is often what a portal actually wants. Set a size ceiling and a maximum page count, and the splitter respects both.
It can, if you set a very small limit. The part count and the smallest resulting part are both shown before you download, so an obviously wrong limit is visible rather than discovered when you open forty files.
No, and the two solve different problems. Compression makes each page smaller; splitting makes more files. Most upload failures are a size problem, so try compression first and split only when the file is still too big even compressed.
Free, no sign-up, no watermark, and nothing is uploaded — the file is only read and rewritten inside this tab. That is what makes it usable on a machine with no internet access.
More essential pdf tools — all free, no upload.