[{"data":1,"prerenderedAt":6},["ShallowReactive",2],{"guide-en-convert-pdf-to-pdfa-for-archiving":3},{"markdown":4,"language":5},"# How to Convert PDF to PDF\u002FA for Archiving\n\nPDF\u002FA is an archival profile with constraints intended to support long-term reproduction. A normal PDF is not automatically PDF\u002FA, and changing its extension does not make it compliant. Confirm the receiving archive's required profile before converting.\n\n## Prepare the Source\n\nKeep the original and record the archive's requirements for the PDF\u002FA level, metadata, attachments, and delivery naming. Check fonts, page appearance, encryption, multimedia, and signatures that may be affected by conversion.\n\nConversion can change unsupported features. It does not automatically make a scan searchable or prove that the document is accessible. If search is required, perform and verify OCR separately before making the archival copy.\n\n## Create an Archival Copy\n\n1. Open [PDF to PDF\u002FA](\u002Fpdf-to-pdfa) and check the profile and options available in the workspace.\n2. Confirm that the supported profile matches the recipient's requirement. Use a compatible alternative if a different level is needed.\n3. Upload the source and start conversion, keeping the original separately.\n4. Download the output and compare page count, fonts, images, and important graphics with the original.\n5. Validate the resulting file against the required profile and retain the report with your records.\n\nDo not submit a file based only on its filename or a successful conversion message. Compliance and visual correctness are separate checks.\n\n## Validate the Result\n\nThe [veraPDF validation documentation](https:\u002F\u002Fdocs.verapdf.org\u002Fvalidation\u002F) describes checks against PDF\u002FA requirements. Use an appropriate validator or the receiving archive's own preflight process, then inspect any failures rather than assuming a rendered page proves conformance.\n\nReview visible content as well: text should remain readable, images complete, and page dimensions correct. A file can pass a standards check while still containing a source typo or an unwanted page. Preserve signed originals because rewriting a PDF can invalidate existing signatures.\n\n## Troubleshooting\n\n| Problem | What to check |\n| --- | --- |\n| Validator reports font problems | Embedding, substitution, and source font availability |\n| Requested profile is unsupported | The tool's available profile and archive requirements |\n| Features change | Encryption, multimedia, signatures, or attachments |\n| Appearance differs | Fonts, color handling, transparency, and page geometry |\n\n## Frequently Asked Questions\n\n### Is PDF\u002FA the same as a searchable PDF?\n\nNo. Archival conformance and a searchable text layer are separate properties.\n\n### Can I preserve an encrypted archival file?\n\nCheck the required profile and archive policy. Encryption is restricted by PDF\u002FA requirements; do not assume a password-protected PDF is compliant.\n\n### Which file should I keep?\n\nKeep the original, the reviewed archival copy, the validation report, and the required descriptive metadata according to your retention policy.\n","en",1791699055807]