Preparing PDFs for upload portals

Use the destination's published requirements for your exact document type. Page limits, file-size limits, accepted formats, and required contents are separate rules; satisfying one does not satisfy the others.

The distinction that matters

The US Office of Personnel Management's applicant guidance describes the federal 2-page resume limit effective September 27, 2025. That is a scoped resume requirement, not a universal limit for all government uploads or every supporting attachment. Follow the current vacancy announcement and the receiving system's instructions for each document category.

Do not transfer a familiar limit from one portal to another. An upload interface can impose a byte cap while the application instructions impose a page limit and content requirements. An accepted upload only confirms that the file passed that stage of the system; it does not prove the document is complete, readable, or responsive to the application.

Prepare a delivery copy from the original. Remove genuinely unnecessary pages, preserve required evidence, and check that the chosen format is accepted. If the document must be shortened, edit the source content when possible. Cropping margins or rasterizing text is not a sound substitute for meeting substantive instructions.

After upload, use any available preview or download function to inspect the stored copy. Confirm page count, orientation, readable text, and the intended filename. Keep the submission receipt or confirmation according to your own workflow. Pagestays prepares files locally and does not submit applications or verify a portal's acceptance.

A worked example

For a hypothetical application covered by the cited federal resume rule, begin with a 3-page draft and revise the source to meet the 2-page requirement while retaining relevant qualifications. Export and inspect the final PDF. Do not merely delete the last page if it removes required information. Treat supporting documents separately under the vacancy’s instructions rather than assuming the resume rule applies to every attachment.

Choose the operation that changes the right thing

A document problem is easier to solve when it is stated as a required change rather than a tool name. A file can be too large because it contains unnecessary pages, oversized images, embedded material, or inefficient encoding. A page can look wrong because of its rotation, crop boundary, physical dimensions, or print scaling. Each cause points to a different operation.

Inspect the input before trying several transformations. Select text to see whether a text layer exists. Look at page properties when geometry matters. Open the form controls when the recipient expects structured values. This short diagnosis avoids an unnecessary image conversion that might make the page look acceptable while removing features you still need.

Apply the least disruptive operation that meets the requirement. If only the order is wrong, rearrange pages rather than rendering the whole document into images. If only an appendix is needed, extract it rather than compressing an entire report. If a scanned image is the source of excessive size, test an image-focused change and inspect the detail afterward.

When chaining tools, treat each stage as a new input with its own properties. In Pagestays, select Use result for next edit to make a PDF output the working document. Keep an intermediate download when it represents useful progress. If a later step fails, that checkpoint makes it easier to isolate the problem and restart without repeating successful work.

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.

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.

Return to the source when the PDF is the wrong layer

A PDF is often the final delivery artifact of a document authored elsewhere. A word processor, layout application, spreadsheet, or scanning system may hold a richer source that is easier to correct. If the problem is a paragraph, a table layout, an incorrect heading, or a bad export setting, editing that source can produce a cleaner result than patching the final PDF.

Check whether the source still exists and whether you are authorized to change it. Re-exporting can preserve relationships that are difficult to reconstruct from page drawing instructions. It also gives you an opportunity to correct accessible structure, image sizing, and document metadata before they become part of the delivery file.

Do not assume that converting a PDF back into an office format restores the original document. Reconstruction can infer text boxes, table cells, and paragraphs from visual placement. That may be useful, but it is a new interpretation that needs review. A complex layout or scan can behave differently from a simple native-text report.

When the source is unavailable, choose a PDF operation that matches the limited change needed. Page utilities are well suited to assembly, extraction, orientation, and adding simple marks. Existing-text editing, redaction, OCR, and standards remediation may require specialized software. Keeping this distinction clear saves time and helps prevent a simple task from turning into an accidental redesign of the document.

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.