PDF/A for court e-filing: what it is and why courts require it
Federal courts require PDF/A. Most state courts too. Here's the actual reason — and why the conversion is non-trivial.
By PDFOnly Team · May 8, 2026 · 6 min read
If you've e-filed a brief on PACER or a state CM-ECF system in the last decade, you've probably been bounced back at least once with the message "submission must be PDF/A." Why this format specifically, and what does the conversion actually do?
What PDF/A is
PDF/A is the archival subset of PDF — formally, ISO-19005. The 'A' stands for archival. It's a strict subset that removes anything that could break long-term reproducibility.
The motivation: a PDF created today might need to render identically in 50 years. Standard PDF allows things that break that promise — externally-linked fonts (might not exist later), JavaScript (might not run), encryption (might lock the file with no recovery), embedded multimedia (might use codecs that disappear). PDF/A bans all of that.
What the conversion actually does
Running a PDF through a PDF/A converter (we use Ghostscript with strict compliance flags):
1. Embeds all fonts in full — including subset embedding for license-restricted fonts. Result: every glyph renders the same way regardless of what's installed on the reader's machine. 2. Locks the color profile — typically to sRGB or DeviceRGB. Eliminates surprises on color management when opened in different readers. 3. Strips JavaScript — none allowed. 4. Strips encryption — no password-protected PDF/A. Want to encrypt for transit? Encrypt the wrapper, not the content. 5. Forbids external dependencies — no externally-linked images, fonts, or files. 6. Validates against the spec — the output is verifiable against ISO-19005-1b/2b/3b.
The three flavors
- PDF/A-1b — based on PDF 1.4 (2005). Most restrictive. No transparency, no JPEG2000, no layers. Use when targeting old systems. - PDF/A-2b — based on PDF 1.7 (2011). Adds transparency, JPEG2000, OpenType fonts, layers. Modern default — what most courts now accept. - PDF/A-3b — adds the ability to embed arbitrary file attachments. Useful if you need to attach the source spreadsheet or XML to the archive.
The 'b' suffix means "basic" compliance (visual fidelity). There's also 'a' (adds tagged accessibility) but that's harder to produce reliably.
Why courts care
Court records have to last forever (or at least decades). If a 2026 motion is filed and someone needs to retrieve it in 2056, the PDF needs to render then exactly as it does now — same fonts, same color, same layout. Standard PDF doesn't guarantee that. PDF/A does.
PACER (federal courts) and most state CM-ECF systems require PDF/A-1b or PDF/A-2b. The exact requirement varies — check your local court's user manual.
The gotcha most filers hit
Not every PDF source produces a clean PDF/A on conversion. Common issues:
- Encrypted source PDFs — must be unlocked first (we have an Unlock PDF tool). - Source PDFs with embedded JavaScript — the converter strips it but warns. Verify the resulting form fields still work. - Source PDFs with custom color profiles — converter normalizes to sRGB, slight visual shifts possible. - Source PDFs with non-standard fonts — converter embeds; output file size jumps.
For high-stakes filings, run a validator (like veraPDF) on the result before submitting. Saves a rejection.
Bottom line
PDF/A is the format that makes "I e-filed it; it's official" actually true 50 years from now. Convert before submission. Default to PDF/A-2b. Validate with veraPDF if it's important. We bake all of this into our [PDF to PDF/A tool](/tools/pdf-to-pdfa).