Protect a PDF with a password screenshot

Protect a PDF with a password

Add a password to a PDF and choose whether it may be printed or copied. The file is sent to the tool server for that run and not stored.

Privacy First
0 Runs
Updated 2026-11-07
Runs on the tool server
Password used for this run only
The upload is not stored
The page count is checked

What this password protection does

Adds a user password to a PDF, so opening the file asks for it. The document is rebuilt with standard 128-bit PDF encryption, and the same run decides two permissions that travel with the file: whether it may be printed, and whether text and images may be copied out of it. Both are off unless you turn them on, because a protected contract is usually meant to be read and not redistributed.

How to use it

Choose the PDF, type the password someone will need to open it, and press Run. An owner password is optional: it is the password that removes the restrictions later, and leaving it blank uses the same password for both. The result is a new file you download, and the page shows its size.

What a password can and cannot do

A password stops someone opening the document, and the permission flags tell a compliant reader not to print or copy it. They are not a DRM system: a reader that ignores the flags can still display the pages, and the password is only as strong as the person you give it to. Nothing here claims otherwise.

Privacy and safety

The file and the password are sent to the tool server for this run and are not stored. The password is used once, in memory, to encrypt the file and is never written to a log or repeated in a message. An already-encrypted PDF is refused rather than re-encrypted, because re-encrypting a file we cannot read corrupts it.

Upload a PDF and give it a password: the file comes back as a new PDF that asks for that password before it opens, with printing and text copying each allowed or refused by a choice you make on the same form.

The work runs on the tool server, because a browser cannot write PDF password protection. The upload and both passwords are used for that one request: they are not written to disk and are not logged, and the produced file is returned rather than stored.

The two permission switches are instructions to a compliant reader, not a lock on the bytes. A reader that ignores the flags, or a tool that can already open the file, is not stopped by them; the password is the part that gates opening.

The two passwords

The user password is the one a reader asks for when the file is opened. The owner password is the one that removes the restrictions later; if you leave it blank, the same value is used for both, which is convenient but means the person you send it to can also lift the restrictions.

A password longer than 128 characters is refused with the measured length, and a blank or whitespace-only password is refused rather than trimmed, because trimming would protect the file with a value you cannot see or retype.

  • User password: required, up to 128 characters
  • Owner password: optional, blank reuses the user password
  • Printing and copying: each defaults to not allowed

Before you upload

A file that already has a password is refused, because re-protecting a document the server cannot read would corrupt it. Remove the existing password first, or use the unlock page if you know it.

The PDF may be up to 12 MB and 200 pages; both limits are checked before the document is rebuilt. The summary reports the page count and the two permission settings, so you can confirm what was written without opening the file.

How to use the protection form

Choose the PDF in the Upload step, then type the user password readers will be asked for and, when wanted, a different owner password for lifting the restrictions later. Set the printing and copying switches to allowed or refused before running, since they are written into the file at build time.

Press Run and download the rebuilt file when it returns. Read the summary's page count and permission settings to confirm what was written, and keep the password somewhere safe: there is no recovery on this page.

What to Expect

Best for

  • Sending a draft that should not open without a password
  • Turning off printing or copying for a document you are circulating
  • Producing a protected copy of a file you already own

Not ideal for

  • Recovering a file whose password you have forgotten
  • Stopping a determined reader, since the permission flags are advisory
  • Protecting a document larger than 12 MB or longer than 200 pages

What this tool keeps

  • Every page, in its original order
  • The page content itself, which is copied rather than re-rendered
  • The document's existing layout and fonts

What may need cleanup

  • The owner password, if you left it blank and now want a different one
  • The permission settings, which you must set before the file is built
  • A file that was already protected, which has to be unlocked first

Common errors

  • Uploading a file that is already password-protected and expecting a second layer
  • Assuming the copy and print flags prevent a screenshot or a photograph of the screen
  • Entering a password with a leading or trailing space, which becomes part of the password

Example use cases

  • Sending a contract draft to a client
  • Circulating a report that should not be printed
  • Archiving a document that must ask for a password

Sample input

A four-page invoice PDF with the password summer-2026, a blank owner password, printing allowed and copying refused.

Sample output

A file named protected.pdf with four pages, reporting printing allowed and copying not allowed, and the same value on both password roles.

Who this is for

  • Small businesses sending documents by email
  • Freelancers delivering a draft
  • Anyone who needs a password on a PDF without a desktop application

Frequently asked questions

What does protect PDF add to the file?

A password required before the file opens, with printing and text copying each allowed or refused by your choice.

Does it stop a determined reader?

No. The permission flags are advisory, so they are not a strong protection.

What are the limits?

Documents larger than 12 MB or longer than 200 pages are refused.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.