Records teams
Check an incoming archive file
Verify the PDF/A level required by your organization before accepting a record.
A useful PDF task, made simple
PDF/A Validator.
Check your PDF for archival compliance. Get a clear result and a report of what needs attention.
Advertisements
Ad placeholderResponsive · up to 1933 × 500Responsive · up to 1933 × 250468 × 60Up to 320 × 100Up to 300 × 50
Check all pages and document-wide PDF/A requirements.
100%
Your validation report is ready.
Review the findings and download your report. Your PDF stays unchanged.
Advertisements
Ad placeholder336 × 280468 × 60Responsive · flexible width × 250Up to 300 × 50
Your PDF is uploaded for validation. The original file is not rewritten.
PDF
How to validate a PDF/A file
- 01
Open your PDF
Choose one unlocked PDF or try the validated sample.
- 02
Check the required standard
Detect the declared standard or choose a PDF/A level, then select Validate PDF/A.
- 03
Read and save the report
Review the result, expand failed rules if needed, and download TXT or JSON.
PDF/A Validator – check your file before archiving
A PDF/A validator checks whether a PDF satisfies an archival conformance profile. Upload your original file, choose the standard, and review a clear result with downloadable findings.
QUICK VIDEO TUTORIAL
How to check whether a PDF meets PDF/A requirements
Check the archival profile before accepting a file.
English narration
Watch the video
Practical ways to use this tool
Researchers and students
Review a thesis or report
Check an exported document against the level requested by a repository.
Document producers
Diagnose export problems
Use failed rule references to review fonts, color profiles and metadata.
Features and controls
Choose the PDF/A standard your archive needs
Detect a declared standard automatically, or select a specific PDF/A level.
How standard selection works
Detect from document reads the PDF/A declaration inside the file, then validates against that profile. If the declaration is missing or unrecognized, the tool checks PDF/A-2b and clearly states this fallback in the result. It does not try every level until one passes.
Choose a standard lets you test PDF/A-1a or 1b; PDF/A-2a, 2b or 2u; PDF/A-3a, 3b or 3u; and PDF/A-4, 4e or 4f. Match the receiving archive’s requirement. A result for one profile is not a result for all profiles.
Validate the original PDF, without changing it
The report describes your uploaded file, not a converted or repaired copy.
What stays unchanged
The server checks the exact uploaded bytes. Validation does not flatten pages, rasterize text, remove attachments, change metadata or resave the PDF. This matters because rewriting a file before checking it could change its conformance.
The source stays in private quarantine during checking and is not published as a downloadable PDF. The report records its SHA-256 identifier, page count and check time. Opening a preview or downloading a report does not modify your original.
Understand failed rules and repeated checks
Findings are grouped into useful categories with expandable technical details.
Read the findings
The result shows pages checked, rules passed and rules failed. A single rule may fail for many objects; failed checks are not a count of pages. Expand Fonts, Colors, Metadata or another reported category to see the rule references and number of occurrences.
Category headings and practical guidance are available in English and Arabic. Exact technical rule descriptions are shown in their original English. You can use these references when reviewing the source application’s export settings. A validation error caused by an unreadable file is shown as an error, never as a pass.
Save a readable or structured validation report
Download TXT for reading or JSON for a structured record of the result.
What the report contains
The report includes the checked standard, declared standard where recognized, pass/fail status, counts, failed rules, timestamp and file identifier. TXT uses the selected interface language for headings; technical rule descriptions remain in English. JSON keeps stable field names.
Use Back to check the same file against another standard, or Start over for another document. If you need conversion, open PDF to PDF/A to create a new archival copy, then validate that output. Validation itself does not repair failures.
Check Arabic PDFs, scans and document-wide resources
Validation examines the whole PDF, including its fonts, color information and structure.
Supported files and scope
Open one unencrypted PDF up to 50 MB and 750 pages. The current preview page does not limit validation: the entire document is checked when you select Validate PDF/A. Invalid or encrypted input is rejected.
Arabic and multilingual PDFs can be checked without translating or reflowing their text. Scanned PDFs can also be checked, but a pass does not mean their images contain searchable text. Profile-specific text or tagging requirements still apply. A PDF/A pass is not a digital-signature check, a complete accessibility certification or a legal retention guarantee.
Supported files & processing
- Input
- Output
- TXT / JSON
Open one PDF up to 50 MB and 750 pages. Additional output, memory and processing limits can apply to complex documents.
Processing uses our servers. Source files, temporary files and results are deleted from our servers within 30 minutes after processing finishes. We do not share document contents with third parties or use them to train AI models.
Advertisements
Ad placeholderResponsive · up to 1933 × 500Responsive · up to 1933 × 250468 × 60Up to 320 × 100Up to 300 × 50
FAQ
A few useful answers
Know what to expect before you start.
Secure processingHow do I check if a PDF is PDF/A compliant?
Open the file, keep Detect from document or choose the required level, then select Validate PDF/A. The tool examines the entire original PDF and reports whether it meets that profile.
Which PDF/A levels can I validate?
PDF/A-1a and 1b; PDF/A-2a, 2b and 2u; PDF/A-3a, 3b and 3u; and PDF/A-4, 4e and 4f. Choose the level requested by the receiving archive.
What happens if the file has no PDF/A declaration?
Automatic mode checks against PDF/A-2b and labels this fallback in the result. It does not assume the PDF is compliant. You can choose a different level manually.
Does validation change or convert my PDF?
No. It checks the exact uploaded bytes, including metadata and document objects, without rewriting them. Use PDF to PDF/A if you need to create an archival copy, then validate that copy.
What does a failed rule mean?
A requirement of the selected profile was not met. A rule may fail many times, so failed checks are not a count of affected pages. Expand the categories to see rule references and their original English technical descriptions.
Can I save the results?
Yes. Download a readable TXT report or a structured JSON report. Both include the selected standard, result, rule counts, timestamp and SHA-256 identifier of the checked file.
Can I validate Arabic documents?
Yes. Validation checks PDF structure and embedded resources rather than translating text. The interface and report headings are available in Arabic. Technical rule descriptions remain in their original English.
Does a pass certify the document for every purpose?
No. It applies only to the checked file and selected PDF/A profile. It does not verify a digital signature, certify full accessibility, check factual content or guarantee acceptance by every archive.
