Why does no password work on my read-only PDF/A file?

Because there is no password. Archival mode is a viewing decision your reader makes after spotting a flag in the file metadata, not a security control applied to the document. Nothing is encrypted, so nothing can be decrypted. Remove the flag and the file behaves normally.

Is editing a PDF/A file ever the wrong thing to do?

Yes, when the document is somebody else's record. Files are archived precisely to demonstrate they have not changed, so altering a deposited or officially issued copy undermines the reason it exists. Work on a duplicate and keep the original exactly as it arrived.

Will my edits be visible to anyone checking the file later?

The removed identification is itself a signal. Anyone comparing your file against an archived original can see that the declaration is gone, and most PDF editors also update the modification date. Treat the change as visible rather than silent.

Does turning off PDF/A mode in Acrobat modify the file?

No, which is its main advantage. The preference changes how your copy of Acrobat behaves and leaves every byte of the document alone. The limitation is that it only helps on your machine, so a colleague opening the same file hits exactly the same wall.

I removed the flag but the file is still not editable. Why?

Almost certainly a permissions password, which is a genuinely separate mechanism. PDF encryption can permit opening while forbidding editing, printing or copying, and no amount of metadata work touches it. That needs the password removed, assuming the document is yours to unlock.

Can I edit the file and keep it valid PDF/A at the same time?

Not simultaneously, no. Any edit invalidates the archival guarantee, because the file no longer matches what was archived. The workable sequence is to remove the flag, edit freely, then convert the finished document back to the level you were asked for.

Do I lose the embedded fonts when I remove the archival flag?

No. We clear one small block of metadata and leave the fonts, the colour profile and the page content exactly as they were. The file still renders identically anywhere; it just stops claiming to be an archival copy.

What happens if I edit a scanned PDF/A document?

You can annotate, reorder and delete pages, but you cannot retype the words, because a scanned archive is a series of page images. Editing the text requires optical character recognition first, and even then you are editing a text layer that sits over the picture rather than the picture itself.

Is there any way to make small corrections without a full round trip?

Annotations are the usual answer, and many readers allow comments even in archival mode. That works for review notes. Anything that changes the document content itself needs the flag removed, because the restriction exists specifically to prevent content edits.

My organisation says never to alter archived documents. Now what?

Follow it, and make a new version instead. Standard records practice is to keep the archived copy untouched and archive a corrected document alongside it as a separate version. Overwriting the original destroys the audit trail that made archiving worthwhile.

How to Edit a PDF/A File Without Breaking Compliance

Your PDF/A file will not let you edit it, and there is no password to remove. Nothing is broken. Your reader spotted an archival flag in the file and switched itself into a protected mode.

This wastes a genuinely absurd amount of people's time. We have watched someone spend half an hour hunting for a password that never existed, then conclude the file was corrupt. It is not corrupt, it is not encrypted, and the fix takes seconds once you know what you are looking at.

Why PDF/A mode is read only in the first place

A PDF/A file carries a small block of metadata announcing that it is an archival copy. Acrobat and several other readers watch for it and respond by disabling editing.

The reasoning is defensible. An archival copy exists to prove a document has not changed, so a reader that lets you casually edit one is helping you destroy the thing you were trying to preserve. Making it read-only turns the protection into a default rather than a discipline.

The reasoning is also invisible, which is the problem. The behaviour looks exactly like a permissions restriction, so that is what everyone assumes. Two clues distinguish them: archival mode usually shows a notification bar naming PDF/A, and no password prompt ever appears. Anything asking for a password is a different mechanism entirely.

Route one: turn off PDF/A mode in your reader

In Acrobat, open Preferences, go to Documents, and set the option for viewing documents in PDF/A mode to never. Reopen the file and it behaves like any other PDF.

What is good about this route is that the document is untouched. Not one byte changes, so the archival copy stays exactly as it was — which matters if it is somebody else's record.

What is limiting is that it only helps you. Send the file to a colleague and they meet the same wall, then ask what is wrong with the document you sent them. It also disables the behaviour for every archival file you open from then on, including ones you had no intention of touching.

Our rule of thumb: change the preference for something you are reading yourself. Change the file when other people need to work on it too.

Route two: unlock PDF/A for editing by removing the flag

Acrobat Pro does this under Preflight, where a fixup called Remove PDF/A information clears the declaration and saves a normal PDF. If you have Acrobat Pro, that is a perfectly good route.

If you do not, our PDF/A to PDF tool performs the same narrow operation in your browser. It clears the identification block and leaves everything else — embedded fonts, colour profile, page content, bookmarks, annotations — exactly as it found them. Nothing is uploaded, which matters given that archival documents are usually contracts, records and filings.

It also tells you which level the file declared before the change. Write that down. You will want it when you archive the finished version, and recovering it afterwards means inspecting a file you have already modified.

What the Acrobat preflight remove PDF/A fixup actually changes

Less than people expect, and that is deliberate on both our part and Adobe's.

The archival behaviour is triggered by one thing: the identification block in the file's XMP metadata. It is a claim the document makes about itself, not a lock. Remove the claim and readers stop treating the file as archival.

Everything that made the file durable stays. The fonts are still embedded, so it still renders identically anywhere. The colour profile is still attached. What changes is that the document no longer asserts it is a faithful archival copy — which is exactly right, because the moment you edit it, that assertion would be false.

You can confirm the before and after with our PDF/A validator, which reads the same metadata block. Run it on the original and the edited copy and the difference is one line.

How to re-archive an edited document properly

Treat this as a loop rather than a one-way trip. Remove the flag, make the changes, then convert the finished document back.

Keep the original. Copy it somewhere before you touch anything. Storage is cheap; reconstructing an archival copy you overwrote is not.
Note the declared level. The tool reports it. You need the same one on the way back.
Edit freely. Any editor works now, including our PDF editor.
Convert back when you are finished. Not before. Our PDF/A converter takes the level you specify. Archiving a draft achieves nothing, because the next edit invalidates it.
Validate before submitting. Re-archiving occasionally loses an embedded font, and you would rather find out now.

If step five turns up a problem, the cause is usually typography, covered in the fonts not embedded error. If you are unsure which level to convert back to, see PDF/A-1b versus PDF/A-2b.

When you should leave the file alone

One caveat we would rather state plainly than bury.

If the document is a signed contract, a deposited thesis, a court exhibit or anything officially issued, it was archived to demonstrate that it has not changed. Editing your own working copy is fine and normal. Editing it and then presenting it as the original is not, and the missing identification block is itself evidence that the file was altered.

Standard records practice is to leave the archived copy untouched and archive a corrected version alongside it. It costs a few kilobytes and preserves the audit trail that made archiving worth doing. If the format itself is new to you, what PDF/A actually is covers the background.