JPG or PNG for exported PDF pages

Use PNG when exact rendered pixels and crisp diagram edges matter. Use JPG when photographic content and a smaller delivery image justify lossy encoding. Compare the actual outputs before choosing.

The distinction that matters

JPEG encodes images with a quality-size tradeoff. Text edges, thin rules, and high-contrast diagrams can show ringing or block artifacts when aggressively encoded. A photograph may tolerate the same setting more comfortably because its detail has different visual characteristics. A quality slider is not a universal measure of readability.

PNG uses lossless compression for the pixels supplied to it. That means the PNG encoding does not add JPEG-style losses, but the pixels may already contain limitations from the source scan and the rendering step. Lossless output does not make a blurry input sharp. It also does not preserve the PDF's vector objects as vectors.

Keep rendering scale constant when comparing formats. Otherwise you are changing both pixel dimensions and encoding, and cannot tell which caused the difference. Use a representative page that includes the smallest important text or the most demanding image detail. Inspect the same region in each output and compare stored bytes.

For multiple pages, the archive is a delivery convenience. The ZIP can group files without rebuilding a PDF's navigation or form behavior. Name and check the page images in sequence before handing them to someone who needs to reconstruct their order. If the recipient needs a searchable, accessible document, the PDF may remain the better delivery format.

A worked example

In a hypothetical test, render the same mixed text-and-photo page at scale 2 into PNG and JPG. Hold the scale fixed, choose a JPG quality setting, and record the downloaded byte counts. Inspect fine text and smooth photo gradients separately. If JPG makes a reference number ambiguous, the byte saving does not meet the document's requirement. The example deliberately supplies no invented compression percentage; your page determines the result.

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.

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.