How to Password Protect a PDF on Mac Without Acrobat

To password protect a PDF in Preview on Mac, use File > Export, give the copy a new name, open Permissions and select Require Password To Open Document. Enter and confirm the required passwords, apply the settings and save. Apple says the changes take effect when the PDF is next opened. 1

For a browser-local alternative without Acrobat, Protect PDF applies AES-256 encryption on your device. Whichever route you use, test the actual saved copy and keep the password in a suitable password manager. Naming a file “protected” does not establish that it requires a password.

Decide which protection you need

A permissions-only file that opens freely does not meet a requirement to encrypt access. Similarly, a UI action described as locking a file against accidental edits should not be treated as evidence of PDF encryption. Test the behavior you need.

Add an open password in Preview

These menu steps follow Apple's current guide. Use the macOS version selector in that source when your installed version has different controls. 1

1. Open the PDF in Preview.
2. Choose File > Export. Enter a different output name so the source can remain unchanged.
3. Click Permissions.
4. Select Require Password To Open Document. Enter the open password and retype it for verification.
5. Review the allowed actions and enter and confirm the Owner Password requested by the dialog. Apple documents that the owner and open passwords can be the same or different.
6. Click Apply, then Save.
7. Close the document and reopen the saved copy to check the prompt. Apple notes that the settings take effect on the next opening.

Keep the password securely rather than copying an example passphrase from a tutorial. Follow your organization's password and retention requirements. Do not email an unprotected source by mistake merely because the protected copy is also open on screen.

Apple also documents File > Edit Permissions for managing settings after protection has been established. Consult the version-specific guide rather than assuming every macOS dialog is identical. 1

Use browser-local encryption instead

BytesPDF Protect PDF offers a focused workflow for an unsigned, unencrypted PDF:

1. Choose the PDF on your device. Signed and already-encrypted files are refused rather than silently rewritten.
2. Set and confirm a long, unique open password.
3. Choose optional permission settings deliberately. If you need a distinction between reader and owner access, use a different owner password and understand that permission flags are advisory.
4. Create and download the protected copy.
5. Reopen that download in the reader the recipient will actually use. Confirm that it asks for a password and opens with the intended one.

The current tool processes one PDF at a time. Its input cap is 150 MB on desktop or 50 MB on mobile, subject to device memory. It does not upload document content or passwords to BytesPDF. It is not a password-reset service, an unlocker or a promise that every PDF viewer will handle every protected document identically.

The AES-256 description above applies to BytesPDF's implementation. This guide does not infer Preview's encryption algorithm from its interface or claim that both tools produce identical files.

Verify before you send

Do not rely only on an already-open preview, where a reader may have access cached for that session. Close it and open the exact saved output again. Test the expected password prompt and inspect the pages after authentication. If practical, have the intended recipient test a non-sensitive sample through the same delivery workflow before sending important records.

Permission behavior is a separate check. A “no copying” choice is not a guarantee against screenshots, other readers or redistribution after the recipient has legitimately opened the document. Read the owner versus user password guide before depending on those flags.

For a complex form, links, attachments or accessibility requirements, inspect those features too. Keep the master until the protected copy is confirmed usable; encryption success alone does not certify every document feature.

Sending the protected PDF by email

First confirm that encrypted attachments are accepted by the recipient's organization. Some submission systems require a readable, unencrypted PDF for automated processing. Do not add a password against those instructions and assume it improves acceptance.

When password protection is appropriate, send the password through a separate approved channel, not in the same email, its subject or the filename. Confirm the recipient's identity and access before disclosing it. The safe-delivery guide covers that handoff in more detail.

PDF encryption does not hide the email subject, filename, recipient list or the fact that a message was sent. It also does not replace document minimization or proper redaction when a recipient should never receive certain information.

Source and limitations

Apple's Preview password and permissions instructions: 1, checked September 27, 2026. Browser instructions describe the current BytesPDF implementation. No hands-on macOS compatibility matrix, encryption benchmark or compliance certification is claimed. BytesPDF publishes this guide and benefits if you use its tools.