PDFCrowd can now generate PDF/A documents for long-term preservation and tagged PDFs that preserve document structure and reading order for accessibility workflows. Each output mode is enabled with one setting, without any extra tools or manual steps.
Archival PDFs with PDF/A
PDF/A (ISO 19005) is a family of standards designed for the long-term preservation of electronic documents. It makes a document more self-contained by embedding fonts and defining the colour information and metadata needed to reproduce its visual appearance over time. Archives, courts, government agencies, banks, and other institutions may require a particular PDF/A level.
Pick a level before you convert:
client.setConformance('PDF/A-2b') # reliable long-term archiving, the common choice
client.convertUrlToFile('https://example.com/report', 'report.pdf')
Supported levels include PDF/A-2, PDF/A-3 (which allows arbitrary file attachments), and PDF/A-4 variants. If the recipient does not require a particular level, PDF/A-2b is a practical default for visual archiving.
When you'd use it
- You need to keep documents for years (records, statements, reports).
- You're filing with a court or authority that requires PDF/A.
- You need a self-contained archival document designed to preserve its visual appearance over time.
Tagged PDFs for accessibility workflows
A tagged PDF carries the structure of your content — headings, paragraphs, lists, links, and reading order — that screen readers and other assistive tools rely on. The tags come from your HTML, so semantic markup produces a more meaningful document structure.
client.setTaggedPdf(True)
client.convertUrlToFile('https://example.com/report', 'report.pdf')
Tagging also supports cleaner text extraction and better reflow on small screens. It is an important part of accessible PDF creation, but it does not by itself guarantee compliance with PDF/UA, WCAG, or a particular accessibility policy. The source HTML and resulting PDF should still be tested against your requirements.
When you'd use it
- You want to preserve meaningful structure for assistive technologies in public reports, statements, or other customer-facing documents.
- You want cleaner text extraction, copy-and-paste, and content reflow.
PDF/A and tagged structure together
The supported PDF/A a levels combine archival conformance with tagged document structure and Unicode text:
client.setConformance('PDF/A-2a') # PDF/A-2a combines PDF/A with tagged structure
In WordPress
No code is needed. In the Save as PDF plugin, open Expert Settings → PDF Format, then choose a Conformance level or enable Tagged PDF in the Save as PDF plugin.
Important compatibility restrictions
- PDF/A conformance cannot be combined with encryption, fillable PDF forms, watermarks, or backgrounds.
- Tagged PDF cannot be combined with watermarks or backgrounds.
Which PDF setting should you use?
| Requirement | Setting | Important consideration |
|---|---|---|
| Archive reports, statements, or records | PDF/A-2b |
Check whether the recipient requires a specific PDF/A level. |
| Archive a document with tagged structure | PDF/A-2a |
Tagged structure supports accessibility workflows but is not, by itself, PDF/UA or WCAG compliance. |
| Preserve HTML structure without PDF/A restrictions | setTaggedPdf(True) |
Use semantic HTML and test the resulting PDF with the tools and standards relevant to your users. |
| Archive a document together with arbitrary attached files | PDF/A-3b |
Use an a variant if tagged structure is also required, and follow any domain-specific rules for the attachments. |
Available now in PDFCrowd API client 6.7.0 (converter 24.04) and the Save as PDF WordPress plugin 4.6.0.