Use PDF/A when you need long-term, device-independent preservation, and use standard PDF for active, interactive, or encrypted work. PDF/A is defined by the ISO 19005 family and produces self-contained files with embedded fonts and metadata. It forbids encryption and certain active content, so sign or secure a file in your working copy before you convert it for the archive.
TL;DR:
- Choose the PDF/A part by features: PDF/A-1 suits text and scans, PDF/A-2 supports transparency and layers, PDF/A-3 embeds files, and PDF/A-4 adds PDF 2.0 profiles.
- Validate files at creation, receipt, and before permanent storage; recheck after edits, since merging pages, adding annotations, or applying passwords can break compliance.
- PDF/A does not protect against corruption or hardware failure, so retain backups, checksums, and a migration plan alongside validation reports and provenance records.
- When using PDF/A-3 or PDF/A-4f, decide whether embedded files belong to the preserved record and give them a separate preservation plan.
Table of Contents
- What are PDF and PDF/A, and why do both exist?
- How do fonts, color, metadata, and banned features differ?
- Which PDF/A part should you choose: -1, -2, -3, or -4?
- When should you use PDF/A and when should you stay with PDF?
- How do you create and validate a PDF/A file?
- What mistakes weaken a PDF/A archive?
- A pragmatic rulebook for busy teams
- Where can LawtonPDF help with your PDF workflow?
- FAQ
- Sources
What are PDF and PDF/A, and why do both exist?
Think of standard PDF as the flexible working format and PDF/A as the sealed archive copy. Both share the same roots, but they are built for different jobs.
- PDF is a general-purpose, page-oriented format. It can carry multimedia, scripting, annotations, and external references, and it exists as a family of formats with subtypes such as PDF/A, PDF/X, and PDF/UA for different use cases.
- PDF/A is the ISO 19005 family, developed to preserve the static visual appearance of documents over time. The standards require device independence, self-containment, and metadata.
- The problem PDF/A solves is quiet failure. A standard PDF can open years later with substituted fonts or shifted colors because a resource it relied on was never stored inside the file.
- The fix is to require everything needed for rendering inside the file. Purdue's preservation knowledge base notes that PDF/A embeds all fonts and color profiles and mandates descriptive metadata.
The practical result is a trade. You give up flexibility, such as forms, media, and passwords. In return, you get a file that should look the same on a machine that does not exist yet.
That trade is why you do not need to pick one format for everything. Most teams keep an editable master and a standard PDF for active use, then produce a PDF/A copy only for the version that must last.
How do fonts, color, metadata, and banned features differ?
Each PDF/A requirement removes one way a file can break over time. Here is what changes in practice.
- Fonts: Every font used must be embedded. Without embedding, a viewer swaps in a different font, and line breaks, spacing, and page counts can change.
- Color: PDF/A call for device-independent color, typically through embedded ICC profiles. Without them, the same RGB values can look different on different displays and printers.
- Metadata: Files must carry XMP metadata, so the document describes itself. An archive can then read title, author, and creation details from the file instead of from a separate catalog.
- Disallowed features: JavaScript, audio, video, and encryption are out. Standard PDF can include interactive features that PDF/A disallows because they threaten long-term rendering consistency.
PDF/A embeds fonts and metadata and forbids external dependencies, which is why the Illinois State Library points to it for long-term preservation of textual electronic records, while standard PDFs with multimedia and hyperlinks suit short- to medium-term storage.
Later parts of the standard loosen some of these limits under controlled conditions. PDF/A-3 allows embedded files. PDF/A-4 is built on PDF 2.0 and, according to a PDF Association webinar, can preserve some scripted content without executing it unless a user acts. It also adds profiles for embedded files and engineering documents. The core promise stays the same: the file must explain and display itself.
The banned-feature list has one consequence you should plan around. A PDF/A file cannot be password-protected. If a document must be confidential, protect the working copy and keep the archive copy in a secured storage system instead.
Which PDF/A part should you choose: -1, -2, -3, or -4?
Choose by the features your documents need, not by which part is newest. Here is a short map.
- PDF/A-1 is based on PDF 1.4. It is a simpler option, and it fits scanned documents and text-first records.
- PDF/A-2 builds on PDF 1.7 and adds transparency, layers, and JPEG 2000 compression. It fits modern print-ready documents that use those features.
- PDF/A-3 permits embedded arbitrary files. Choose it when the source data, such as a spreadsheet or XML, must travel inside the same file.
- PDF/A-4 is based on PDF 2.0, relaxes some requirements, and introduces new profiles. Consider it when you use PDF 2.0 features or have engineering and 3D needs.
If you work on print-ready files, the checks overlap with PDF/A-2 concerns such as transparency and color profiles. This PDF preflight checklist for books walks through those production steps.
One point should save you effort. The Library of Congress notes there is no obligation to migrate legacy PDF/A files to the latest part. There is no obligation to migrate legacy PDF/A files to the latest part, so pick the part that matches the features you need and leave older archives alone unless a real requirement pushes you to change.
When should you use PDF/A and when should you stay with PDF?
Match the format to what the document will do next. These scenario rules cover most cases.
- Legal or archival deposit: Use PDF/A. The record needs to render the same way years from now.
- Theses and dissertations: Use PDF/A. Institutions that accept them for long-term repositories commonly ask for it.
- Government publications and public records: Use PDF/A. Long retention is the whole point.
- Interactive forms: Use standard PDF. Form fields and scripts are exactly what PDF/A removes.
- Multimedia documents: Use standard PDF. Embedded audio and video are not allowed in PDF/A.
- Encrypted delivery: Use standard PDF. Archive formats cannot carry passwords.
Order matters when signatures or encryption are involved. The PDF Association describes PDF/A as an end-state format that prohibits encryption, so you apply encryption or signatures in active workflows and then convert to PDF/A for the archive. If you want background on how those protections differ, this overview of encryption, redaction, and signing is a useful companion. When a signature record must survive, produce an unencrypted, validated PDF/A copy and document the signature details alongside it.
Plan your time, too. Converting and validating may require access to the original source files, and batch jobs need tooling plus occasional manual fixes. Clean files may be quicker to convert. A mixed collection of scans, forms, and old exports may take more work.
Pro Tip: Always keep the editable original and record where each archived PDF/A came from, including the tool, the date, and the source file name.
How do you create and validate a PDF/A file?
Treat conversion as three checkpoints: create, validate, and re-validate. Skipping the middle step is how invalid files slip into archives.
- Create it properly. If your authoring application offers "Save as PDF/A" or an equivalent export, use it and select the part you chose earlier. If not, run the file through a conversion tool that targets that specific part.
- Validate at three moments. The PDF Association's guidance says to validate at creation, on receipt, and before moving files into permanent archives. A file from a colleague or vendor is only compliant if a validator says so.
- Use an open validator. veraPDF is an industry-supported open source validator with a command line interface, a Java API, Docker images, and web demos. It supports bulk processing and has test corpora for developers who build PDF/A check into their own systems.
- Handle failures calmly. Some failed files can be repaired by software. When repair does not work, recreate the file from its source. Complex interactive content may simply be incompatible with a strict PDF/A target, and that is a signal to keep it as standard PDF.
- Automate at scale. Command line tools and containerized validators fit institutional pipelines, so every file gets checked the same way without someone opening each one.
Validator disagreement used to be a real headache. Work on veraPDF helped resolve many cross-vendor differences and produced test suites and a reference implementation that institutions can rely on.
Pro Tip: Save each validation report next to the file it describes. When someone asks later why a record was accepted, you can answer in seconds.
What mistakes weaken a PDF/A archive?
Most archive failures come from habits, not from the format. A few precautions prevent the usual ones.
- PDF/A is not a backup. The PDF Association FAQ states that PDF/A is not a backup format. It keeps a file visually consistent but does not protect against corruption or hardware failure, so keep backups, checksums, and a media migration plan.
- Re-validate after any change. A file saved as PDF/A can become invalid after you merge pages, add annotations, or apply a password. Re-validate before archiving, every time.
- Decide about embedded files. If you use PDF/A-3 or PDF/A-4f, choose whether the embedded files are part of the preserved object. If they are, give them their own preservation plan.
- Keep records. Note the conversion tool, the validation report, and the provenance for each file. Future staff will need them if a repair is ever required.
A PDF/A file can fail validation after routine edits, and the PDF/A in a Nutshell guide lists merging pages, adding annotations, and password protection as common causes.
A pragmatic rulebook for busy teams
Preserve the final, authoritative copy and nothing more. Teams that convert every draft end up with large collections of files nobody needs, each one needing validation and storage. Keep editable originals for active work, and promote a document to PDF/A only when it becomes the record.
The second habit is discipline. Validate at several points and log the results. A conversion workflow takes effort to set up, but it costs far less than discovering later that a contract renders with the wrong characters or an image has lost its color.
My third view is about where files go during all this. Sensitive records, such as legal filings, patient documents, and financial statements, do not need to travel through an online converter just to be validated. Desktop-first tools that process files on your own hardware are a sensible fit for that work, and they let you meet the archive requirement without widening the circle of who can see the file.
— Lawton
Where can LawtonPDF help with your PDF workflow?
You can handle the working half of this guide on your own computer. LawtonPDF is a Windows application that processes everything locally, so your documents stay on your machine while you prepare them for the archive.
We offer tools to merge, organize, extract pages, rotate, flatten, watermark, protect, and unlock PDFs. We also compare PDFs, Word documents, text, images, spreadsheets, and folders, which helps you confirm that a converted copy matches its source. That is useful when you flatten annotations or merge files before the final validation pass.
The Free plan is available if you want to try it, and our Plus and Business plans are listed on our pricing page. Open it, pick the plan that fits, and start preparing your next file locally.
FAQ
How can you tell whether a file is a PDF?
Check the file extension, which should be .pdf, and open the file in a PDF reader. Renaming another file type to .pdf does not make it one.
What type of PDF should you use?
Use standard PDF for forms, multimedia, passwords, and everyday sharing. Use PDF/A for records that must stay readable and look the same for many years. When the file will be archived, pick the part that matches the features it needs, as covered above.
Is PDF high quality?
PDF preserves layout, fonts, and images well, so it suits both screen and print when it is created properly. Quality depends on how the file was made, including image resolution and whether fonts were embedded. PDF/A adds a further guarantee that those resources are stored inside the file.
Should "PDF" be capitalized?
Yes. PDF is an abbreviation for Portable Document Format, so it is written in capital letters. The same applies to PDF/A.