How to Translate a Password-Protected PDF When You Have Permission

To translate a password-protected PDF, first identify which lock you are dealing with, then make an unlocked working copy with the password you were given, translate that copy, and apply the right protection to the translated file. You cannot translate a file that is genuinely encrypted without its password, and you should not try. If you do not have the password, the correct next step is to ask the document owner for it or for an unprotected source file.

Most "how to translate a protected PDF" advice jumps straight to unlocking. That skips the decision that matters: an open password, a permissions password, a digital signature, and server-managed policy protection are four different situations with four different correct actions. Treating them the same way is how people end up with broken links, voided signatures, or a confidential file uploaded to a random "unlock" website.

BookTranslator does not accept password-protected or encrypted PDFs directly. Our PDF translator asks you to remove the protection first, using your own PDF editor, and then upload the unprotected copy. We do not attempt to bypass document encryption. The rest of this guide covers how to get from the protected original to an unlocked working copy you are entitled to translate.

Identify the Lock Before You Do Anything

Use this decision table first. It decides whether you can proceed at all.

Adobe's own guidance draws the same line: unlocking a PDF requires you to have the appropriate permissions, and without them you need the policy author or an administrator of the secured file. No unlocking tool changes who is entitled to the content.

What the Locks Look Like in a Real File

To make the distinction concrete, we generated four three-page PDFs on 2026-10-10 with selectable text and one web link per page: an unprotected original, a copy with an open password, a copy with a permissions password that blocks copying, and a copy with a permissions password that also blocks printing. All three protected copies use AES-256 encryption, created with the pypdf 5.1.0 library. We then inspected each file with pdfinfo (Poppler 26.08.0), a free command-line tool that reports a PDF's encryption state without changing the file.

The diagnostic is useful on its own. If pdfinfo cannot read the file at all, you have an open password and nothing downstream will work until you have it. If it reads the file and lists copy:no or change:no, you have a permissions password: the content is readable, but the author has restricted what you may do with it. Supplying the open password (pdfinfo -upw <password> file.pdf) turned the open-password fixture's result into print:yes copy:yes change:yes addNotes:yes, which confirms that this file had an open password and no extra permission limits.

On a Mac or PC without the command line, the same information appears in your PDF reader. In Acrobat, open File > Properties and check the Security tab. In macOS Preview, open the file and choose File > Edit Permissions to see whether printing, copying, and annotations need the owner password.

Make an Authorized Unlocked Working Copy

Once you have the right password, remove protection from a copy, not from the original. Keep the protected original as your record of what you received.

In Adobe Acrobat, Adobe's current desktop instructions are: All tools > Protect a PDF, then Set security properties under Advanced Properties, open the Security tab, and choose Change Settings. Clear "Require a password to open the document" to remove an open password, or clear "Restrict editing and printing of the document" to remove a permissions password, entering the permissions password if prompted. Then save the PDF, because the change only applies to the saved file (Adobe Help, updated 2025-09-23).

In macOS Preview, Apple documents that a PDF can have both an open password and a separate owner password that controls printing, copying text, and annotations, and that you change these under File > Edit Permissions (Apple Preview User Guide). Apple's guide ties the permission settings to the owner password, so have that password ready before you try to change them.

On the command line, any tool that supports PDF encryption can write a decrypted copy when you supply the password. In our fixture test, pypdf reported a successful user-password match for the open-password file and an owner-password match for the permissions file, and wrote unencrypted copies of both. A wrong password failed with File has not been decrypted, which is the behavior you want: no password, no copy.

We checked both unlocked copies against the original:

This is the point many guides miss. A proper decrypt removes the lock but keeps the document's text layer and link annotations, because it rewrites the same document without encryption. That is what a translation tool needs: real text it can read and a structure it can rebuild.

Why "Print to PDF" Is Not the Default Answer

A common shortcut is to open the protected file, print it, and save the printout as a new PDF. It sometimes works, but it has two problems.

First, it fails when the author blocked printing, which is exactly what our fourth fixture shows (print:no). Second, it creates a new document through the print pipeline instead of removing a lock from the existing one. Community reports note that the result can look different from the original (Mac Power Users forum), and anything the print path does not carry over, such as links, bookmarks, form fields, or accessibility tags, has to be checked by hand. Use it only as a last resort, and inspect the result before you translate.

Avoid Free "Unlock PDF" Websites for Confidential Files

If the document is protected, someone decided it was sensitive. Uploading it to an unknown unlocking service sends the file, and often its password, to a third party before you have even started translating. The WKU IT guidance linked here warns that unlocking programs and services may harm your computer or expose your personal information. Unlock locally with software you already trust, and review the document translation privacy checklist before choosing where the unlocked copy goes next.

Signed and Certified PDFs Need a Different Decision

A digital signature protects the exact bytes that were signed. Changing the signed content invalidates it, and unlocking the document does not change that. A translated file is, by definition, a changed file.

So do not try to "preserve" the signature through translation. Keep the signed original unchanged as the authoritative version, translate a copy, and label the translation as a translation. If the recipient needs a signed translated document, the signer has to sign the translated version, or the work has to start again from the unsigned source.

Translate the Unlocked Copy, Then Re-Protect It

With an unlocked copy in hand, the rest is a normal PDF translation:

1. Check that the copy is actually unlocked. Run pdfinfo again or reopen the security properties. Encrypted: no is the signal to proceed.
2. Check that it has real text. Try selecting a sentence. If you cannot select text, the pages are images and you need an OCR workflow. Our scanned PDF translation guide covers that path.
3. Upload and translate. Upload the unlocked PDF to the PDF translator, review the price before paying, and choose a target-only or bilingual output. Bilingual output is useful when someone has to check the translation against the protected original page by page.
4. Review the translated file. Use the PDF translation QA checklist to confirm pages, tables, links, and headings before anyone relies on the result. If the original contained form fields, follow the fillable PDF form guide instead of assuming they survived.
5. Re-apply protection that fits the translated file. Because you uploaded an unprotected copy, the translated PDF comes back as a standard PDF without a password. If the source was confidential, add an open password or permission limits in Acrobat or Preview before distributing it. Agree on the new password with the owner rather than reusing theirs by default.
6. Delete the unlocked working copy once the protected translation has been delivered, so an unprotected duplicate is not left behind.

A Handoff Checklist for Asking the Owner

Most stalled projects stall at the request, not the translation. When you ask the document owner for access, ask for everything at once:

• Which lock does the file use: open password, permissions password, signature, or server policy?
• Are you authorized to make an unlocked copy for translation, and where may that copy be processed?
• Can they send an unprotected source file instead of a password? This is usually cleaner, especially for signed documents.
• What protection should the translated file carry, and who sets the new password?
• Does the translation need to be signed, certified, or delivered with a translator's statement? Those requirements are outside what a machine translation tool provides.

If the owner will not grant access, stop there. The lock is doing its job, and the right outcome is to translate a different, authorized version of the content.