PDF versions and the ISO standards

A PDF version describes a set of format capabilities, not a guarantee that every document feature will work in every reader. The PDF Association maps PDF 1.7 to ISO 32000-1:2008 and PDF 2.0 to ISO 32000-2:2020.

The distinction that matters

A version label is useful when choosing compatibility settings, but the actual objects in a document still matter. A file can use ordinary text and images, or more specialized features such as forms, annotations, and particular encryption handlers. A reader may support common pages while behaving differently on the specialized parts. A successful first-page preview is therefore a limited compatibility check.

The standards families also describe different goals. Core PDF specifies the general format. PDF/A addresses long-term preservation, PDF/UA addresses accessibility, and PDF/X addresses print exchange. These are not simply newer versions of the same promise. A document can require more than one kind of conformance, and the target should be stated precisely.

For everyday work, do not choose a version solely because its number is larger. Choose the output required by the recipient and the software that will use it. If an older system rejects the file, use a suitable compatibility conversion and test the features that matter. Renaming a file or changing a metadata string is not a real standards conversion.

A worked example

Consider an illustrative report that opens in a modern reader but fails in a receiving system. The first test is a copy with the required compatibility setting exported from the source application. Compare the text, links, forms, and any signatures before accepting it. If the receiving system specifically asks for an archival conformance target, a generic older-version export is not enough. The target and validation method need to match that request.

Check more than the visible page

A PDF can carry a visual page and a separate structure for interaction and interpretation. Links, bookmarks, form widgets, tags, and document metadata do not all live in the same place as the text and images you see. An operation that copies or redraws page content can produce a convincing picture while leaving some of those other features behind.

Decide which features are part of the acceptance test. If readers need to follow a contents page, try its links. If a form must remain editable, change a value in a copy and save it. If assistive technology is part of the workflow, inspect reading order and structure rather than relying on visual appearance. A successful visual comparison does not establish accessibility conformance.

Page assembly deserves particular care because document-level information can depend on the original sequence. A bookmark can target an old page location, a printed cross-reference can become misleading, and a tagged reading order may no longer describe the merged packet. Keep a source document available and test the elements that readers actually use.

When a conversion intentionally removes interactivity, describe that choice to the recipient. An image export is useful for a slide or a visual reference, but it is a poor replacement for a form that needs further editing. The right output is defined by its purpose. Do not preserve a feature merely for its own sake, but do not discard one without recognizing what the next person needs to do.

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.

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.

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.