How to convert a report pdf to the pdf/a archival standard
- Step 1Finalise the report and embed its fonts — Confirm content, figures, and signatures are final. In your layout app (InDesign, Word, LaTeX), export with 'embed all fonts' enabled — the converter preserves embeds but does not add missing fonts.
- Step 2Flatten transparency in the source for design-heavy reports — PDF/A-1 forbids transparency. If your report uses drop shadows, transparent overlays, or blend modes, flatten them at export time, because this tool does not flatten. PDF Flatten handles form fields and annotations but not page-content transparency.
- Step 3Remove any password — PDF/A forbids encryption. Strip protection with PDF Remove Password before tagging.
- Step 4Drop the report into the converter — Load the file. Tagging happens in your browser — nothing is uploaded. There are no options; the tool always targets PDF/A-1b.
- Step 5Convert and download — The tool adds the XMP
pdfaididentifier, the output intent, and the PDF-1.4 header, then re-saves. Download the tagged report. - Step 6Validate and file alongside the source — Validate with veraPDF; expect failures on the stub ICC and any transparency or non-embedded fonts. Archive the tagged report and keep the editable source (InDesign / Word) next to it for future re-export.
Report features vs. PDF/A profiles
PDF/A-1b is the oldest, strictest profile — this is what design-heavy reports run into.
| Report feature | Allowed in PDF/A-1b? | Allowed in PDF/A-2b? |
|---|---|---|
| Transparency / drop shadows / blend modes | No | Yes |
| JPEG 2000 compressed images | No | Yes |
| Embedded files (e.g. source data) | No | PDF/A-3 only |
| Bookmarks and internal hyperlinks | Yes (no JavaScript) | Yes |
| High-res JPEG / lossless images | Yes | Yes |
What this converter does to your report
Each change and whether it fully satisfies the matching PDF/A-1b rule.
| Change applied | Targets | Fully satisfied? |
|---|---|---|
XMP pdfaid:part=1, conformance=B | PDF/A identifier | Yes |
GTS_PDFA1 output intent (stub ICC) | Colour output intent | Partial — ICC is a stub |
%PDF-1.4 header, no object streams | PDF version constraints | Yes |
| Re-save preserving existing embeds | Font embedding | No — missing fonts not added |
| (not done) flatten transparency | No transparency allowed | No |
Tier limits for reports
Annual reports with imagery get large — check the ceiling.
| 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
Report-archiving scenarios and exactly what the converter changes — especially the design-heavy cases where PDF/A-1b is the strict bottleneck.
Text-dominant research paper — the clean case
A LaTeX-exported paper with embedded fonts and no transparency tags cleanly. This is the format PDF/A-1b was designed for.
Input: paper.pdf (Computer Modern embedded,
no transparency, 0.7 MB)
Output: paper-pdfa.pdf
+ pdfaid:part=1, conformance=B
+ GTS_PDFA1 output intent
+ %PDF-1.4 header
→ Closest to true PDF/A-1b this tool produces.Glossy annual report — flatten first
A design-heavy annual report with drop shadows and transparent overlays must have transparency flattened in the source before tagging, because PDF/A-1 forbids it and this tool doesn't flatten.
Wrong: report.pdf (transparency live)
→ PDF to PDF/A → tagged but FAILS 1b
(transparency not allowed)
Right: export from InDesign with transparency
FLATTENED → PDF to PDF/A → passes the
transparency ruleShrink a heavy report before archiving
A photo-heavy report over the size cap can be compressed first. Use lossless to keep figures crisp, or lossy if size is the priority.
report.pdf (62 MB, high-res photos)
→ PDF Compress (lossless or lossy) →
report-small.pdf (e.g. 14 MB)
→ PDF to PDF/A → report-small-pdfa.pdf
Note: avoid JPEG 2000 output — 1b forbids it.Confirm bookmarks survived
PDF/A-1 permits bookmarks and internal hyperlinks (it only bans JavaScript). After tagging, the report's navigation tree is intact.
Before: report.pdf with chapter bookmarks
After: report-pdfa.pdf — bookmarks preserved
(pdf-lib re-save keeps the outline tree)
JavaScript actions, if any, would violate 1b.Validation result to expect
veraPDF surfaces the known gaps. Treat passes/failures as a map of what to fix in the source.
veraPDF PDF/A-1B: PASS XMP identifier present PASS PDF version / structure FAIL OutputIntent ICC invalid (stub) FAIL Transparency present (if not flattened) FAIL Font not embedded (if source lacked embeds)
Edge cases and what actually happens
Report uses transparency or blend modes
Not flattenedPDF/A-1 forbids transparency entirely, and this tool only targets 1b and does not flatten. Annual reports with drop shadows, transparent logos, or highlighted callouts carry transparency into the output and fail strict 1b validation. Flatten transparency at export time in your layout app, or target PDF/A-2b (transparency-allowed) with a converter that supports it.
Report compressed with JPEG 2000
Forbidden in 1bPDF/A-1b does not allow JPEG 2000 image compression (PDF/A-2b does). If your report's images were exported as JPEG 2000, re-export them as baseline JPEG or a lossless format before tagging. PDF Compress and the lossless option help reduce size without JPEG 2000.
Non-embedded fonts in the layout export
Not fixedIf the report was exported without embedding fonts, the converter won't add them and the file fails the font-embedding rule — and a future reader without those fonts sees a substituted, re-flowed report. Re-export with 'embed all fonts' enabled.
Report over the free-tier 2 MB / 50-page cap
BlockedImage-rich reports routinely exceed 2 MB and 50 pages. Compress first with PDF Compress, or upgrade to Pro (50 MB / 500 pages) or higher.
Report contains JavaScript actions
Forbidden in 1bPDF/A-1 forbids JavaScript. A report with interactive form scripts or JavaScript-driven navigation violates 1b. Remove the scripts in the source (or via PDF Flatten for form fields) before tagging. Plain bookmarks and hyperlinks are fine.
Encrypted or DRM-protected report
rejectPDF/A forbids encryption. Remove protection with PDF Remove Password or PDF Unlock before tagging.
Output intent uses a stub ICC profile
By designThe colour output intent references a placeholder profile, not a real sRGB ICC blob, so strict validators reject it on the ICC rule. For a report where colour fidelity is audited (brand colours in charts), produce the archive with a certified converter that embeds a real ICC profile.
Custom report metadata (DOI, classification)
ReplacedThe converter writes its own XMP packet (identifier, title, creator, dates). A DOI, security classification, or keyword set stored in custom XMP fields is not preserved — re-apply it after conversion, or record it in your DMS catalogue alongside the file.
Frequently asked questions
Which PDF/A level is best for an annual report?
Design-heavy annual reports are usually a better fit for PDF/A-2b, which permits transparency and JPEG 2000 — but this tool produces PDF/A-1b only. For a text-dominant report (research paper, board minutes) 1b is sufficient and this tool's tagging works well. For a glossy report with live transparency, flatten it first or use a converter that targets 2b.
Will interactive features like bookmarks be preserved?
Bookmarks and internal hyperlinks survive — PDF/A-1 permits them and the re-save keeps the outline tree. What PDF/A-1 forbids is JavaScript, so any JavaScript-driven navigation or form scripts must be removed before tagging.
Does this tool flatten transparency for me?
No. PDF/A-1 forbids transparency, but this tool does not flatten it — you must flatten at export time in your layout application. PDF Flatten handles form fields and annotations, not page-content transparency like drop shadows.
Should I archive the original report alongside the PDF/A?
Yes. Keep the editable source (InDesign, Word, LaTeX) for future editing and the original PDF for reference, and archive the PDF/A as the immutable long-term record. If a stricter PDF/A pass is needed later, you'll re-export from the source.
My report is too big to convert — what now?
Free tier caps at 2 MB / 50 pages. Compress the report first with PDF Compress for size or the lossless option to preserve figure quality, or upgrade to Pro (50 MB / 500 pages) or higher. Avoid JPEG 2000 compression, which 1b forbids.
Will the output pass strict validation?
Not strictly. The tool tags the report and forces PDF 1.4, but the output intent uses a stub ICC profile and it doesn't re-embed missing fonts or flatten transparency. veraPDF will pass the identifier rules and fail on ICC, transparency, and any non-embedded fonts. Use it as a baseline; produce the final archive with a certified converter when strict validation is required.
Are my fonts embedded so the report renders identically later?
Only if they were already embedded in the export. The converter preserves existing embeds but does not add missing fonts. Re-export the report with 'embed all fonts' enabled before tagging so a future reader sees the exact typography.
Is my report uploaded anywhere?
No. Tagging runs entirely in your browser; the report never leaves your device. Only an anonymous usage counter is recorded when you're signed in, with no content — so confidential financials and draft research stay private.
Can I attach the source data to a PDF/A report?
Not with this tool. Attaching arbitrary files (a spreadsheet of the underlying data, for example) is a PDF/A-3 feature, and this tool only produces 1b. If your archive policy wants the data embedded, use a converter that targets PDF/A-3b.
Does converting change the report's appearance?
Tagging doesn't alter page content — figures, tables, and layout are unchanged. The visible risk is upstream: if you flattened transparency or compressed images before tagging, that step may change appearance, so review the report after those steps and before archiving.
How do I validate a report I've tagged?
Run it through veraPDF with the PDF/A-1B profile. Read the failures as a checklist for the source — typically transparency, JPEG 2000, the stub ICC profile, or non-embedded fonts.
Can I tag a whole library of reports at once?
The browser tool does one report per run; Pro and above allow small batches (Pro 5, Pro + Media 50). For a repository-scale job, pair the @jadapps/runner and POST each report to the local pdf-to-pdfa endpoint so confidential files stay on your machine.
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.