Run a PDF/A-2b-oriented preflight check
Inspect common archival risks on your device and turn the report into a focused correction checklist.
Open PickPDF 
Add to ChromeQuick answer
Run a PDF/A-2b-oriented preflight check
To preflight a PDF in PickPDF, run the PDF/A-2b-oriented check and review findings for encryption, fonts, transparency, JavaScript, attachments, XFA, metadata, OutputIntent, and annotations. The report screens for common issues but does not certify conformance. Use an approved validator when a repository requires formal PDF/A certification.
Step by step
How to use this tool in PickPDF
Run preflight on the delivery candidate
Use the file you plan to archive, after editing and page organization but before final submission.
Review each reported category
Check encryption, fonts, transparency, scripts, attachments, XFA, metadata, OutputIntent, and annotations.
Correct the source or PDF
Fix issues in the source document where possible. Remove unsupported content only when the archive requirements call for it.
Validate with the receiving standard
Run the corrected file through the validator or repository process required by the organization.
Current capabilities
What the current PickPDF build supports
- PDF/A-2b-oriented screening
- Encryption and font checks
- Transparency and JavaScript findings
- Attachment and XFA findings
- Metadata and OutputIntent review
- Annotation reporting
Preflight finds risks before archival submission
PDF/A aims to preserve a stable visual document without dependencies that may disappear. Fonts, colour information, metadata, encryption, interactive content, and external dependencies can affect conformance. A preflight report identifies categories that need investigation.
The correct response depends on the archive profile and receiving system. Removing an attachment or script can change the record. Work from an unchanged source and document the corrections required by the retention policy.
A screening report is not a conformance certificate
PickPDF checks a PDF/A-2b-oriented baseline and reports common findings. Formal validation can require a standards-focused engine, profile rules, and repository-specific acceptance tests. A clean PickPDF report should not be described as certification.
Use the report to reduce avoidable failures before the formal validator. Retain the validator result with the archival package when the records process requires proof of conformance.
Metadata and visible pages both need review
Archival work covers more than page appearance. Document title, author, language, dates, identifiers, and colour profile can matter. The visible pages still need a human check for missing text, substituted fonts, and altered transparency.
PickPDF runs the screening on the device. The report can expose document properties and file details, so store it with the same care as the PDF.
Common questions
Questions about run a pdf/a-2b-oriented preflight check
Does PickPDF certify PDF/A-2b compliance?
No. It performs a PDF/A-2b-oriented screening check. Use the validator required by the archive or receiving organization for certification.
Why does PDF/A restrict encryption?
An archive must be able to open and render the document in the future. Encryption can prevent that access without keys or passwords.
Should I delete every item reported by preflight?
No. Review the archive requirements and record meaning first. Removing content can change the document.