Skip to content

PDF to PDF/A

Make a PDF archive-ready (PDF/A-2b), and see exactly what changes first.

Drop a PDF here

Only your browser reads them.

How to use PDF to PDF/A

  1. Add one PDF file to inspect it. Drop your document or click Choose a file; a compliance check runs immediately without changing the original file.
  2. Review What will change in the sidebar. Check which pages have unembedded fonts or CMYK colors, and pick 150, 200, or 300 dpi if any pages need image conversion.
  3. Convert and save your archive copy. Click Convert to PDF/A to download the PDF/A-2b file after the post-conversion check completes.

Your files are processed on this device and never uploaded. They stay private, and there's nothing to delete afterwards.

What makes PDF/A-2b different from a regular PDF for archives?

A regular PDF can reference system fonts by name, rely on uncalibrated screen or print colors, and embed executable JavaScript or file attachments. Under the Library of Congress PDF/A-2 (ISO 19005-2) Format Description, PDF/A-2b bans dynamic behaviors and requires every font, color profile, and metadata field to be self-contained inside the document.

Self-contained fonts, sRGB OutputIntent, and XMP metadata

To guarantee identical rendering decades from now, PDF/A-2b mandates an embedded OutputIntent color profile and an XML XMP metadata packet declaring pdfaid:part 2 and pdfaid:conformance B. This converter synchronizes document creation and modification timestamps to whole seconds across both the Info dictionary and XMP stream so strict validators never flag a mismatch.

Every trailer file ID is also regenerated as a pair of 16-byte hexadecimal strings, and blank properties are cleaned so the metadata tree remains valid. Nothing leaves your browser, keeping 0 bytes on external servers.

PDF/A-2b versus PDF/A-1b for court e-filing

PDF/A-1b (ISO 19005-1) dates back to 2005 and forbids transparency and modern compression, whereas PDF/A-2b supports transparency, layers, and smaller file sizes. Most courts, tax agencies, and records offices accept PDF/A-2b by default for long-term digital submissions.

When preparing digital evidence packages from email correspondence before archiving, you can convert email messages into PDF evidence first and then standardize the resulting file to PDF/A-2b.

Pre-conversion compliance audit and automated PDF/A fixes

As soon as you drop a PDF, the tool runs pdfaCheck inside a Web Worker and displays What will change before touching a single byte. If a file already claims PDF/A conformance, a notice lets you know it will be re-checked and written cleanly as PDF/A-2b.

PDF element audited PDF/A-2b rule Action taken by converter Preserves vector text
Color space profile ICC OutputIntent required Embeds 3-channel sRGB profile Yes
Document metadata XMP must match Info dict Writes synchronized XMP packet Yes
JavaScript and actions 11 action types forbidden Strips scripts and auto-actions Yes
File attachments Embedded files disallowed Removes attached payloads Yes
Comments and forms Must be printable Marks visible annotations printable Yes

The embedded OutputIntent uses a 3-channel Flate-compressed profile matching the W3C Standard Default Color Space (sRGB). If your PDF contains interactive form fields that you want permanently baked into page graphics before archiving, you can also flatten interactive form fields and comments.

By showing the exact list of changes upfront in What will change, the tool removes guesswork before you commit. You know right away whether your document stays 100% vector or needs selective page rendering.

Why unembedded fonts and CMYK pages turn into searchable images

Standard PDFs often reference Base-14 fonts such as Helvetica, Arial, or Times by name without embedding the actual glyph outlines. Because a browser cannot extract proprietary desktop font files from your operating system, pages using unembedded fonts or DeviceCMYK print colors cannot pass PDF/A-2b as raw vector text.

Preserving vector text on compliant pages

Instead of rasterizing your entire document blindly, the converter inspects every page individually. Any page that already embeds its fonts (FontFile, FontFile2, or FontFile3) and uses RGB, Grayscale, or ICCBased colors remains 100% vector with zero quality loss.

Only the specific pages listed in What will change are rendered onto a canvas capped at 4,096 pixels per side and encoded as 0.88-quality sRGB JPEGs. Immediately afterward, an invisible, searchable text layer matching the original word positions is laid over each image so you can still search and copy text.

Because the rest of the file stays untouched as vector objects, a 40-page brief with 2 problematic cover pages keeps 38 crisp vector pages. That selective approach avoids unnecessary file bloat while still meeting strict PDF/A-2b rules.

Choosing 150, 200, or 300 dpi for rasterized pages

When one or more pages require image conversion, a Resolution for pages turned into images menu appears with three presets: 150 dpi for smaller files, 200 dpi (recommended default), and 300 dpi for sharpest print detail. Choosing 200 dpi balances crisp legal body text against reasonable file sizes for portal upload limits.

For scanned documents that lacked searchable text to begin with, run local OCR text recognition before archiving so every page remains indexable.

Post-conversion checks and verifying submissions with veraPDF

Once you click Convert to PDF/A, the writer prunes unreachable objects and saves with useObjectStreams: false so even older archival validators read every cross-reference cleanly. Immediately after saving, the tool re-runs its internal audit on the output bytes and warns you if any font, color, or metadata check failed to clear.

Tip: Before uploading a high-stakes filing to a court portal or national archive, test the downloaded PDF/A-2b file against the pdfa-2b profile in the open-source validator.

You can download and run the veraPDF Reference PDF/A Validation Documentation locally to get an independent pass/fail certificate. Checking against veraPDF is especially helpful when an institution enforces strict automated intake gates on fonts, color profiles, or XMP schemas.

Your original source PDF is never overwritten during conversion, as your browser saves a separate PDF/A-2b copy to your downloads folder. For preservation workflows that require uncompressed raster images instead of PDF containers, you can also export long-term archival TIFF images in the browser.

Questions

What is PDF/A and why do courts and archives require it?

PDF/A (ISO 19005) is a self-contained archival subset of PDF designed to display identically decades from now. It requires every font and color profile to live inside the file and bans external links, JavaScript, and embedded attachments that could break or pose security risks.

Which PDF/A conformance level does this converter create?

It produces PDF/A-2b, the most widely accepted conformance level for court e-filing, government portals, and university repositories. Level b ensures reliable visual reproduction without requiring structural accessibility tagging.

Why do pages with missing fonts or CMYK colors become images?

A browser cannot legally bundle proprietary desktop font files or print CMYK ICC profiles that are missing from your PDF. Rendering only those affected pages as sRGB images with an invisible searchable text layer underneath satisfies PDF/A-2b rules while keeping text selectable.

Is the converted PDF/A-2b file guaranteed to pass veraPDF?

The tool builds to PDF/A-2b rules and runs an automated check immediately after conversion. For strict court or regulatory submissions, verify the downloaded file in veraPDF because severely damaged font tables or unusual PDF structures may need specialized desktop repair.

What happens to JavaScript and attachments during PDF/A conversion?

All 11 forbidden action types, including JavaScript, Launch, and multimedia actions, plus embedded file attachments are stripped automatically. Visible annotations are marked printable while hidden or non-printable annotations are removed.

Are confidential legal or medical PDFs uploaded during conversion?

No. Compliance scanning, metadata rewriting, selective page rendering, and final PDF assembly all run inside your browser Web Worker, so 0 bytes leave your device.

Updated