Scanning resolution: pixels with a purpose

Choose scanning resolution for the detail you must preserve and the purpose of the copy. More pixels can capture finer information, but they also increase processing and storage demands.

The distinction that matters

NARA's guidance for permanent federal paper records specifies a minimum of 300 pixels per inch for modern textual records and 400 pixels per inch for photographic prints or paper with fine details. Those are requirements for that described records context, not a universal rule for every receipt or casual attachment. The useful lesson is to connect resolution to the source and preservation purpose.

Scanning at higher resolution does not repair poor focus, motion blur, clipped highlights, or missing page edges. Capture quality and pixel density are separate issues. Before scanning a long packet, check a sample for complete edges, legible faint marks, straight alignment, and consistent illumination. Rescanning early is easier than discovering later that a critical note is missing.

A delivery copy can be smaller than a preservation master. Keep those roles separate. If a portal needs a compact document, derive a readable copy from the master rather than replacing the master with the smallest accepted file. Color should also be retained when it carries meaning, such as highlights, stamps, or annotations that distinguish categories.

A worked example

For an illustrative US Letter scan at 300 ppi, multiply 8.5 inches by 300 to get 2,550 pixels across, and 11 inches by 300 to get 3,300 pixels high. The image contains 8,415,000 pixels. At 600 ppi, both dimensions double, so the pixel count becomes four times as large. These are computed dimensions, not a prediction of the compressed JPEG or PDF file size.

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.

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.

Treat file size and working memory separately

The size stored on disk is only one part of a browser-processing job. Compressed images must be decoded before they can be drawn, page objects need to be interpreted, and the result may exist in memory alongside the original. A file that looks modest in a file manager can therefore be demanding to render, especially on a phone or a device with other busy applications.

Start with a small representative batch. A sample should resemble the difficult content in the full job: a detailed scan is more informative than a blank page when testing an image-heavy packet. If the sample works, increase the work carefully. A universal browser file-size promise would hide differences in memory, operating system, page complexity, and background load.

Keep the active tab open while processing. If you switch away, a mobile browser may suspend work or discard the tab under pressure. Save the output before refreshing. Closing the tab clears the local workspace, which supports privacy but also means it is not a durable storage system. A downloaded copy is the useful checkpoint.

When a job fails, reduce the variable most likely to be responsible. Lower a rendering scale for a very large page, split a long packet into smaller groups, or choose an installed application suited to a demanding workflow. An error does not automatically mean the PDF is corrupt. It can reflect a capability or resource boundary that is specific to the device and operation.

Preserve context, not only a file extension

An archive needs more than a document that opens today. The file should retain the information necessary to interpret it, and the organization should know where it came from, which version it represents, and what transformations were applied. A readable PDF is useful, but its extension alone does not establish a preservation policy or standards conformance.

Keep the source and record the purpose of any derivative. A small reading copy can be appropriate for sharing while a higher-quality master remains the preservation reference. Do not discard an original scan simply because a compressed output looks similar at normal zoom. Fine annotations, marginal notes, and tonal differences can carry information that becomes important later.

If a standard is required, identify the exact family and conformance target. PDF/A concerns long-term preservation, PDF/UA concerns accessibility, and PDF/X concerns print exchange. They are not interchangeable badges. A conversion should be followed by a validator appropriate to the target, and a later edit can require validation again.

Plan for retrieval as well as storage. Use meaningful filenames, stable descriptions, and controlled locations so someone can find the right document later. Metadata can help, but it should agree with the visible content and organizational records. Pagestays can change ordinary document information and create useful derivatives; it does not certify an archival collection or replace a records-management process.

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.