PDF to PDF/A online

What PDF to PDF/A does

PDF to PDF/A requests a PDF/A-2b export from LibreOffice for a document intended for preservation-oriented workflows.

The current service does not run an independent conformance validator, so the generated file must not be treated as certified solely because the conversion completed.

How to use this tool

Choose PDF document
Select one supported PDF document for PDF to PDF/A from your device and wait for its upload to finish.
Prepare the source
Confirm which PDF/A profile and validation process the receiving archive requires, and retain the unchanged source PDF.
Run PDF to PDF/A
Start the PDF to PDF/A job and leave the page open while its queued conversion is processed.
Review the downloaded file
Open the result, compare every page, and run the archive’s approved PDF/A validator before accepting it as conforming.

Common use cases

Prepare a validation candidate

Create a PDF/A-2b export to submit to an organization’s required conformance checks.

Test an archival workflow

Evaluate whether a document can be normalized without losing visible content before formal ingest.

Supported inputs

One unencrypted PDF file

Output

One PDF named converted-pdfa.pdf, requested with the LibreOffice PDF/A-2b export filter.

Limitations to know

No independent veraPDF or equivalent conformance report is produced by this tool.
Encryption, interactive media, unsupported fonts, signatures, and attachments may conflict with a preservation profile or change during export.
PDF/A conversion alone does not provide retention policy, backups, fixity checking, or legal compliance.

Privacy and document handling

The selected PDF document is uploaded to configured object storage so the PDF to PDF/A worker can process it.
The PDF to PDF/A result is stored as a separate output and made available through a time-limited signed download URL.
Before using PDF to PDF/A, do not upload confidential PDF document unless the current storage and retention information is suitable for the document.

Stored input and output objects are deleted automatically: files uploaded without an account are removed about 24 hours after upload, and files belonging to a signed-in account are removed after 7 days. A scheduled sweep enforces this hourly against the object store itself. Workers attempt to remove per-job temporary directories after processing. This does not delete stored input or output objects.

Read the Privacy Policy and Security page for verified implementation details and open questions.

Troubleshooting

An archive rejects the result

Run the archive’s validator, inspect its reported rule failures, and correct the source or use an approved preservation process.

The visual output changed

Compare fonts, transparency, colors, annotations, and page rendering with the source before acceptance.

A protected PDF cannot convert

Obtain an authorized unencrypted source rather than attempting to bypass access controls.

Still stuck? Review Help and common questions or contact support.

Frequently asked questions

Is every output guaranteed to be valid PDF/A-2b?

No. The export requests that profile but the service does not independently validate or certify conformance.

Does PDF/A guarantee long-term preservation?

No. Preservation also depends on storage, integrity checks, metadata, retention rules, and future migration.

Should I delete the original after conversion?

No. Keep the source until the converted file has passed required visual and technical validation.

How should I check my PDF to PDF/A result?

Open every PDF to PDF/A download and compare it with the unchanged source before sharing or deleting anything. Pay particular attention to this documented limitation: No independent veraPDF or equivalent conformance report is produced by this tool.