Splitting a PDF by a file-size target

Splitting by size requires measuring saved output files. Dividing the original byte count by its page count cannot reliably predict the size of each result.

The distinction that matters

PDF pages can share fonts, images, and other resources. A page copied into a separate file may need its own copy of resources that were shared in the source. Other pages can have very different image weight. An average byte count per page therefore hides both content differences and packaging overhead.

Pagestays builds candidate page groups and measures the actual saved bytes against the selected target. When adding a page would exceed that target, it begins another output. If a single page exceeds the target on its own, it reports that the requested split cannot be satisfied. It does not claim success by silently producing an oversized part.

The target is a product input expressed in KiB, using 1,024 bytes per KiB. A destination may publish its rule in decimal MB, binary units, or a whole-message allowance. Convert deliberately and leave suitable room when the destination counts more than the uploaded PDF. The email-limit data page distinguishes these scopes.

A split also needs a useful reading sequence. Name the parts clearly and keep related pages together when possible. If a section must not be separated, use range splitting instead and then measure the result. A technically compliant set of files can still be inconvenient if a table and its explanatory note land in different submissions.

A worked example

Suppose a hypothetical portal accepts separate files and you choose a target of 1,000 KiB. The tool compares each saved part with 1,000 × 1,024 = 1,024,000 bytes. If an individual image-heavy page saves above that target, splitting alone cannot solve it. Reduce eligible image weight, choose another accepted format, or use the recipient's alternative route, while preserving readable detail.

Make the calculation reproducible

A useful measurement has an input, a unit, and a method. Record those before comparing outputs. For a physical page, distinguish millimeters, inches, PDF points, and pixels. For a file, distinguish the stored byte count from an application label that may round or use a different unit convention. Two displays can show different-looking numbers for the same underlying object.

Carry the unrounded value through intermediate calculations and round only the figure you display. Repeated rounding can accumulate an avoidable difference, particularly when dimensions are converted from millimeters to inches and then to page units. The size pages on Pagestays use a sourced base dimension and compute the other units, rather than treating a rounded inch description as exact.

Write assumptions next to the example. If an example uses a chosen image width, a hypothetical attachment size, or a user-selected margin, say that it is an input to the calculation. It is not a measured industry average or a guaranteed result. The reader should be able to substitute their own input and understand what changes.

Finally, verify the artifact itself. A correct formula in a settings panel does not prove that the saved file has the intended page dimensions. Reopen the PDF and inspect its page properties, or check exported image dimensions with an image viewer. When a recipient imposes a limit, use their current rule and leave room for any additional packaging or message content the rule includes.

Inspect the detail that carries meaning

Image quality should be judged at the place where information is easiest to lose. A large heading can remain readable even after small account references, decimal points, map labels, or faint handwritten marks have become ambiguous. Pick a difficult region before exporting and return to that same region in the result. This gives you a consistent comparison as you change settings.

Look at both a normal reading view and a closer view. The normal view tells you whether the document is usable at its intended size. The closer view helps distinguish blur, block artifacts, missing strokes, and color changes. Neither view alone is sufficient: extreme zoom can exaggerate harmless pixel structure, while fit-to-page can hide damaged fine print.

Compare against the original, not against a remembered impression. If possible, put both copies side by side and examine the same content. Do not repeatedly recompress the last output while searching for a setting; go back to the original for each trial. Otherwise you are changing both the setting and the source quality, which makes the result harder to interpret.

A good delivery copy is not always the smallest possible file. Choose the smallest version that preserves the required information and works in the receiving system. If no setting achieves both goals, change the workflow: remove genuinely unnecessary pages, use an approved link, or ask the recipient for a different submission route. Destroying detail to satisfy a size field can make the document unusable.

Separate processing from storage and delivery

Local processing describes where a document operation happens. It does not describe every later place the file can go. A browser can save its result into a folder synchronized by a separate storage service. An email client can upload an attachment when you send it. A shared workstation can retain downloaded files after the editing tab has closed.

Choose the storage location deliberately. If a task requires a local copy, check the destination used by the browser and whether that folder is synchronized. If the file is meant to be shared, decide whether an attachment or an access-controlled link is appropriate. Those choices should follow the recipient's needs and any applicable organizational rules, not the editor's marketing language.

A hosted link is a separate workflow with its own questions. Confirm who can open it, whether forwarding the link grants access, whether it expires, and whether the recipient can retain a copy. A smaller message containing a link may solve an attachment limit while creating an access problem for the person receiving it.

For Pagestays, document contents and file names stay in the processing tab. The site still downloads code and supporting assets to run the tools. The optional email waitlist is a separate request and does not include a PDF. Keep these distinctions precise: local editing is a meaningful property, but it is not a promise about your browser extensions, your operating system, or a storage provider you choose afterward.

Keep a source and a delivery copy

The original and the deliverable have different jobs. The original is a reference you can return to when a setting turns out to be wrong. The deliverable is the copy prepared for a particular recipient, format, or size constraint. Giving them different names prevents a successful-looking conversion from becoming an accidental overwrite of your only useful source.

Start by opening the original and identifying the features that matter. A plain scan may need only readable pixels, while an application form may need editable fields and a report may need working links. Write the required properties down before choosing a transformation. This makes the final inspection a comparison against a requirement rather than a general impression that the document looks fine.

After saving, close the preview of the edited result and open the downloaded file. That small separation matters: a tool can display an intermediate state that is not identical to the file it exported. Check the filename and destination so you know which copy you are inspecting. If the result is intended for someone else, use the viewer or delivery channel they are likely to use when practical.

Keep useful intermediate copies when a job involves several operations. If a merge is correct but a later image conversion is too soft, restart from the merged PDF rather than reconstructing the whole sequence. Do not treat a smaller byte count, a completed progress bar, or a successful download as proof that all document features survived.

Put the distinction to work

Open the related local tool when its supported operation matches your task. Read the limits beside the controls, make a separate output, and check it against the requirements described above. For a sequence of PDF operations, the workspace lets you carry a PDF result into the next edit.