When this tool is useful
Finding obvious readiness gaps before sending a document to a dedicated validator and an archive with a specified PDF/A part and conformance level.
How local processing works
The report checks XMP pdfaid part and conformance declarations, Catalog OutputIntents presence, referenced font-file evidence, Catalog EmbeddedFiles, selected automatic-action locations, and whether the parser opened the file without an encryption password.
How to use it
- Prepare a safe working copy: Keep every source unchanged and review the supported input, controls, and limits before processing. Finding obvious readiness gaps before sending a document to a dedicated validator and an archive with a specified PDF/A part and conformance level.
- Process locally: Run the documented operation in this browser and stop if an unsupported structure is reported. The report checks XMP pdfaid part and conformance declarations, Catalog OutputIntents presence, referenced font-file evidence, Catalog EmbeddedFiles, selected automatic-action locations, and whether the parser opened the file without an encryption password.
- Download and verify: Run the exact saved source through a recognized PDF/A validator configured for the intended part, review every failure, and test the archive's own acceptance and rendering workflow.
Important limitations
This preflight is not PDF/A validation, certification, conversion, or proof of archival suitability. Color spaces, transparency, glyph coverage, ICC correctness, content operators, optional content, rendering equivalence, and many part-specific rules are not fully checked.
Verify the downloaded result
Run the exact saved source through a recognized PDF/A validator configured for the intended part, review every failure, and test the archive's own acceptance and rendering workflow.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
When is this tool useful?
Finding obvious readiness gaps before sending a document to a dedicated validator and an archive with a specified PDF/A part and conformance level.
What does the browser actually do?
The report checks XMP pdfaid part and conformance declarations, Catalog OutputIntents presence, referenced font-file evidence, Catalog EmbeddedFiles, selected automatic-action locations, and whether the parser opened the file without an encryption password.
Which limits must I understand?
This preflight is not PDF/A validation, certification, conversion, or proof of archival suitability. Color spaces, transparency, glyph coverage, ICC correctness, content operators, optional content, rendering equivalence, and many part-specific rules are not fully checked.
How should I verify the result?
Run the exact saved source through a recognized PDF/A validator configured for the intended part, review every failure, and test the archive's own acceptance and rendering workflow.