Files are processed in your browser, not uploaded. Privacy →
Deckle
Open a PDF
Skip to guide

Document security

PDF vs PDF/A: is an edited PDF still PDF/A?

By DeckleUpdated

PDF/A is a stricter version of PDF made for long-term archiving: every font is embedded, colours are defined, and features that could stop the file displaying the same way in future, such as encryption and JavaScript, are not allowed. A file ending in .pdf is not PDF/A just because it opens. After editing a PDF/A file in any general tool, including Deckle, treat the result as an ordinary PDF and check it with a validator before you submit it as PDF/A. Deckle does not create or validate PDF/A.

Remove PDF metadata

Three different privacy tasks

Password

Controls access

Metadata

Document properties

Redaction

Selected page content

Choose the change; inspect the saved copy

Conceptual comparison · access, properties and content require separate checks. No single task certifies complete privacy.

PDF vs PDF/A

Ordinary PDF PDF/A
Purpose Viewing, sharing, printing Archiving for decades
Fonts May rely on fonts installed on the reader's device All embedded
Encryption and passwords Allowed Not allowed
Audio, video, JavaScript Allowed Not allowed
External links to content Allowed Not allowed for content needed to display the page
Metadata Optional Required, in XMP
How you can tell File extension .pdf A PDF/A identifier in the XMP metadata, and a validator report

PDF/A has several parts and levels, such as PDF/A-1b, PDF/A-2u and PDF/A-3a. Courts, government archives and some tender portals require a specific one.

Why edits can break conformance

PDF/A rules apply to the whole file. A tool that rewrites the file can, without changing how the pages look:

  • drop or rewrite the XMP metadata that declares the file as PDF/A,
  • remove the file identifier in the trailer, which PDF/A requires,
  • change a document property so it no longer matches the XMP record,
  • add content that the PDF/A level forbids, such as encryption,
  • merge in pages from an ordinary PDF that uses unembedded fonts or undefined colours.

The file still opens and looks right, but a validator will reject it.

Deckle tools and PDF/A

Deckle tool Effect on a PDF/A file
Password protect PDF Adds encryption, which PDF/A does not allow
Remove PDF metadata Removing the XMP packet removes the PDF/A identifier, and removing the Document identifier removes the trailer ID that PDF/A requires
Merge PDFs Pages from ordinary PDFs may not meet PDF/A rules
Organize PDF pages, Split PDF, Rotate PDF The file is rewritten and its Producer property set to Deckle, which no longer matches the producer in the XMP record; validate before relying on conformance

None of these mean the output is unusable. They mean it should be treated as an ordinary PDF until a validator says otherwise.

How to keep a PDF/A submission valid

  1. Keep the PDF/A original unchanged. Deckle never overwrites the file you choose.
  2. Make page changes in the source document where you can, then export to PDF/A again from the source app.
  3. If you have to edit the PDF itself, do it in an app that saves as PDF/A, such as Adobe Acrobat Pro's preflight tools.
  4. Validate the final file with the validator your recipient names, or with a PDF/A validator such as veraPDF.
  5. Do not add a password to a PDF/A file. Use a protected channel to send it instead.

How to tell whether a file claims to be PDF/A

  • Adobe Acrobat Reader shows a bar saying the file claims compliance with the PDF/A standard and has been opened read-only.
  • Deckle's Remove PDF metadata lists an XMP packet if the file has one. A PDF/A file always does, though an XMP packet alone does not make a file PDF/A.

A claim in the metadata is not proof. Only a validator report confirms conformance.

Tips

  • Ask which PDF/A level is required before preparing a submission.
  • Leave the XMP packet and the Document identifier when cleaning a PDF/A file, and validate the result, if conformance matters.
  • Export from the source. Word's PDF options include ISO 19005-1 compliant (PDF/A), and LibreOffice and many design apps can export PDF/A too.
  • Keep a validation report with the submitted file.

Frequently asked questions

Is every PDF a PDF/A?

No. PDF/A is a separate ISO standard with stricter rules. Most PDFs are ordinary PDFs.

Can I password protect a PDF/A?

Not without breaking conformance. PDF/A does not allow encryption.

Does merging two PDF/A files give a PDF/A?

Not reliably. Different PDF/A levels and settings can conflict, and the merged file's metadata may not declare conformance. Validate the result.

Why does a portal reject my PDF as "not PDF/A"?

The portal ran a validator and the file failed, often because it is encrypted, a font is not embedded, or the PDF/A identifier is missing from the metadata. Export again as PDF/A from the source app and validate before uploading.

Can Deckle convert a PDF to PDF/A?

No. Use your source app's PDF/A export or a dedicated tool, then validate it.

Related tools

Sources