How to convert a pdf to pdf/a for legal filing
- Step 1Confirm the portal's exact requirement — Check the e-filing rule for the conformance level it mandates. This tool produces PDF/A-1b only. If the portal demands PDF/A-2b, PDF/A-3b, or strict validation, plan to use a certified converter for the final pass and use this tool only for internal tagging.
- Step 2Strip encryption and finalise content — PDF/A forbids encryption — remove any password with PDF Remove Password first. Confirm redactions are burned in (use PDF PII Redactor earlier in your workflow), because tagging does not re-check for hidden text under black boxes.
- Step 3OCR scanned exhibits before tagging — Discovery scans need a searchable text layer for review platforms. Run PDF OCR to add an invisible text layer, then convert. Note OCR re-emits each page as an image with the text layer drawn over it.
- Step 4Drop the finalised PDF into the converter — Load the document. Tagging happens in your browser — nothing is uploaded. There are no options to set; the tool always targets PDF/A-1b.
- Step 5Convert and download — The tool attaches the XMP
pdfaididentifier, the output intent, and the PDF-1.4 header, then re-saves. Download the tagged file. - Step 6Validate, then upload — Run the file through veraPDF before filing. Because fonts aren't re-embedded and the ICC profile is a stub, expect strict failures — if your portal validates strictly, use a Ghostscript- or Acrobat-grade converter for the version you actually submit.
What this tool covers for a legal filing — and what it doesn't
Map each PDF/A-1b expectation to whether the tag-only converter handles it.
| Filing concern | Handled by this tool | Where to handle it instead |
|---|---|---|
| Document carries a PDF/A identifier | Yes — XMP pdfaid:part=1, conformance=B | — |
| No encryption on the filed document | Source must already be decrypted | PDF Remove Password before converting |
| Redactions are permanent (no hidden text) | Not checked — tagging doesn't inspect content | PDF PII Redactor earlier in the workflow |
| Scanned exhibits are searchable | Not added | PDF OCR before converting |
| All fonts embedded for faithful rendering | Only if already embedded | Re-export from your assembly tool with fonts embedded |
| Passes strict portal validation (veraPDF) | No — stub ICC, no font re-embed | Ghostscript / Acrobat-grade converter for the final copy |
Conformance levels and what they require
Know which level your court actually mandates before you rely on a tag-only converter.
| Level | Adds over the prior level | Produced here? |
|---|---|---|
| PDF/A-1b | Reliable visual reproduction; fonts embedded; no encryption; PDF 1.4 | Identifier + intent + header only (best-effort) |
| PDF/A-1a | Tagged structure + Unicode mapping for accessibility | No |
| PDF/A-2b | Transparency, JPEG 2000, embedded files, PDF 1.7 base | No |
| PDF/A-3b | Arbitrary file attachments (e.g. source data) | No |
Tier limits for legal documents
Bundles and exhibit sets are often large — check the ceiling before conversion.
| Tier | Max file size | Max pages |
|---|---|---|
| Free | 2 MB | 50 pages |
| Pro | 50 MB | 500 pages |
| Pro + Media | 500 MB | 2,000 pages |
| Developer | 2 GB | 10,000 pages |
| Enterprise | Unlimited | Unlimited |
Cookbook
Concrete legal-workflow scenarios and exactly what the converter does — and doesn't — change in the filed document.
OCR a scanned exhibit, then tag it
A scanned contract exhibit must be both searchable for the review platform and PDF/A-tagged for the filing. Order matters: OCR first, tag second.
1. exhibit-12-scan.pdf (image-only)
→ PDF OCR → exhibit-12-searchable.pdf
(page image + invisible Helvetica text layer)
2. exhibit-12-searchable.pdf
→ PDF to PDF/A → exhibit-12-pdfa.pdf
+ pdfaid:part=1, conformance=B
+ GTS_PDFA1 output intent
+ %PDF-1.4 headerConfirm redactions before tagging
Tagging does not inspect content, so it will happily wrap a document whose 'redactions' are just black rectangles over selectable text. Burn redactions in first.
Wrong order (DANGER): draft with black-box overlays → PDF to PDF/A → hidden text still extractable from the 'archive' Right order: PDF PII Redactor (burns pixels) → PDF to PDF/A → no recoverable text under the redaction
Decrypt a protected client PDF first
A client sends a password-protected statement. PDF/A forbids encryption, so the password must come off before tagging.
client-statement.pdf (AES-encrypted)
→ PDF Remove Password (owner password) →
client-statement-open.pdf
→ PDF to PDF/A → client-statement-pdfa.pdf
Tagging an encrypted file would not produce a
clean archival document.What a portal's quick check sees
Portals that only sniff for the PDF/A identifier and output intent will accept the tagged file. The marker the portal reads is the XMP packet.
Portal ingest (lenient check) reads:
Metadata → XMP → pdfaid:part = 1
pdfaid:conformance = B
Catalog → OutputIntents → S = GTS_PDFA1
Header → %PDF-1.4
→ Accepted as 'PDF/A'.What a strict portal rejects
A portal running veraPDF-grade validation will catch the gaps. Plan for this if your court validates strictly.
Strict ingest (veraPDF PDF/A-1B) flags: 6.2.2 OutputIntent ICC profile invalid (stub) 6.3.x Font not embedded (if source lacked embeds) → Submission rejected. Fix: re-produce via a certified converter for filing.
Edge cases and what actually happens
Black-box redactions over live text
Hidden text remainsTagging does not inspect or alter page content, so redactions drawn as opaque rectangles over selectable text stay extractable in the 'archival' output. Burn redactions in with PDF PII Redactor before converting — a privilege waiver from a leaked redaction is far worse than a rejected filing.
Portal runs strict PDF/A validation
rejectBecause the output intent uses a stub ICC profile and missing fonts aren't re-embedded, a portal that validates with veraPDF or an equivalent will reject the file on the ICC and font-embedding rules. Use this tool for internal tagging, but produce the actual submission with a certified converter when the portal validates strictly.
Encrypted client or court document
rejectPDF/A forbids encryption and the tagger can't produce a clean file from an encrypted source. Strip the password with PDF Remove Password or PDF Unlock first.
Scanned exhibit with no text layer
Not searchableA tagged image-only scan satisfies a lenient PDF/A check but isn't searchable, which most discovery review platforms require. Run PDF OCR before tagging. OCR re-rasterises each page and overlays an invisible text layer.
Court mandates PDF/A-2b or PDF/A-3b
UnsupportedThis tool only writes the PDF/A-1b identifier. It cannot target 2b or 3b. Do not hand-edit the pdfaid:part value — the body must obey that part's rules. Use a converter that supports the mandated part.
Digitally signed filing
Signature brokenRe-saving changes the bytes and invalidates any existing digital signature. Convert to PDF/A first, then re-sign the archival copy with PDF Digital Signature if a signature is required on the submitted version.
Bundle exceeds the free-tier 2 MB / 50-page cap
BlockedCourt bundles routinely exceed 2 MB and 50 pages. Upgrade to Pro (50 MB / 500 pages) or higher, or split the bundle and tag each part. Note many portals also impose their own per-file size cap independent of this tool.
Transparency in letterhead or exhibit graphics
Not flattenedPDF/A-1 forbids transparency, and this tool does not flatten it. Firm letterhead logos with transparent backgrounds or highlighted-exhibit overlays will carry transparency into the output and fail strict 1b validation. Flatten in the source app before exporting.
Custom matter-management XMP metadata
ReplacedThe converter writes its own XMP packet (identifier, title, creator, dates). Bates ranges or matter IDs stored in custom XMP fields are not preserved — re-apply them, or store them in a sidecar manifest rather than the file metadata.
Frequently asked questions
Will a court e-filing portal accept the output?
It depends on how strictly the portal validates. Portals that simply check for the PDF/A identifier and an output intent will accept the tagged file. Portals that run strict veraPDF-grade validation will likely reject it because the ICC profile is a stub and missing fonts aren't re-embedded. Confirm your portal's behaviour, and use a certified converter for the final submission if it validates strictly.
Which PDF/A level does this produce for filings?
PDF/A-1b only. It writes pdfaid:part=1 and pdfaid:conformance=B. It cannot produce PDF/A-1a, 2b, or 3b. If your court's rule names a different level, you'll need a converter that supports it.
Does tagging guarantee my redactions are safe?
No. The converter does not inspect or alter page content, so redactions drawn as black boxes over live text remain extractable. Always burn redactions in with PDF PII Redactor before converting.
Are privileged documents uploaded to a server?
No. Tagging runs entirely in your browser; the document never leaves your device. Only an anonymous usage counter is recorded when you're signed in, with no document content. That keeps work-product and privileged material off third-party servers.
Can I convert a scanned court document to PDF/A?
Yes, but run PDF OCR first so the scan has a searchable text layer, then tag it. A tagged scan without OCR is acceptable to a lenient PDF/A check but isn't searchable, which most review platforms expect.
Will conversion invalidate a digital signature on the document?
Yes. Re-saving changes the bytes and breaks any existing cryptographic signature. Convert to PDF/A first, then apply the signature to the archival copy with PDF Digital Signature.
Can I convert a password-protected PDF for filing?
Not directly — PDF/A forbids encryption. Remove the password with PDF Remove Password or PDF Unlock first, then convert the decrypted copy.
Does it embed fonts so the document renders identically in court?
Only fonts already embedded in the source are preserved. The tool does not add missing fonts. For a filing where faithful rendering matters, re-export from your document-assembly software with 'embed all fonts' enabled before converting.
What size of bundle can I convert?
Free tier is 2 MB / 50 pages. Pro is 50 MB / 500 pages, Pro + Media 500 MB / 2,000 pages, Developer 2 GB / 10,000 pages, Enterprise unlimited. Many portals also impose their own per-file limits, so check both.
Should I keep the unconverted original?
Yes. Retain the original alongside the tagged copy. If a portal later requires a stricter validation pass, you'll want the source to re-produce the file rather than trying to repair the tagged version.
Does the validator I run matter?
Yes. veraPDF is the open-source reference validator for ISO 19005 — use the PDF/A-1B profile. Different validators are stricter or more lenient about the ICC profile and font rules, so validate with the same engine your portal uses if you can find out which it is.
Can I automate tagging across a large production?
For a production set, pair the @jadapps/runner and POST each file to the local pdf-to-pdfa endpoint so documents stay on your machine. The browser tool processes one file per run; Pro and above allow small batches. For a strict-validation production, route the final pass through a certified converter.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.