Why PDF Text Selection Can't Be Truly "Disabled"
A PDF is not a picture — it's a structured document containing text objects with font mappings, positioning, and encoding. Any tool that can render the PDF can also read those text objects, because the text must be present for the PDF to display it. "Disabling selection" is therefore always one of two things:
- A permission flag that tells the viewer "please don't let the user copy." Compliant viewers (Adobe Acrobat) obey. Non-compliant viewers (Chrome, Firefox, most mobile apps) ignore it entirely [citation:1][citation:4].
- Removing the text entirely by rasterizing pages to images. The text is gone — it's now pixels. Nothing can select what isn't there [citation:14][citation:6].
There is no third option. Any tool claiming otherwise is doing one of these two things.
The Two Modes Compared
| 🔒 Permission Flags | 🖼️ Rasterize Pages | |
|---|---|---|
| Text selectable? | Depends on viewer | No — never |
| Searchable? | Yes | No |
| Accessible (screen readers)? | Yes | No |
| File size | Unchanged | Much larger (images) |
| Respected by Acrobat? | Yes | N/A (no text) |
| Respected by Chrome? | No | Yes (no text to select) |
| Best for | Lightweight deterrent, compliant environments | Guaranteed no selection, visual-only documents |
Permission Flags — What Actually Happens
The PDF standard (ISO 32000) defines permission bits for copying/extraction. When you set the "disallow extraction" bit, you're asking the viewer to respect your wishes [citation:1]. Adobe Acrobat and Acrobat Reader honor this. But the PDF is not encrypted against reading — it's an honor system. Chrome's PDF viewer, Firefox's pdf.js, and most mobile viewers do not implement permission enforcement at all [citation:4].
Rasterization — The Guaranteed (but Lossy) Approach
Rasterization renders each PDF page to a canvas, encodes the canvas as an image (JPEG or PNG), and rebuilds a new PDF where each page is just that image. There is no text layer at all [citation:14][citation:6].
What you gain: Guaranteed no text selection, no copying, no search, no extraction — in any viewer.
What you lose:
- Search — the text is pixels, not characters.
- Accessibility — screen readers see images, not words.
- File size — a 200 KB text PDF can become 2 MB of images.
- Zoom quality — images pixelate when zoomed; vector text does not.
- Links and forms — all interactive elements are destroyed.
When to Use Which
| Scenario | Recommended |
|---|---|
| Internal document, users are cooperative | 🔒 Permission Flags |
| Public-facing PDF, want to slow casual copying | 🔒 Permission Flags (accept it's weak) |
| Confidential document that must not be copyable at all | 🖼️ Rasterize (accept the downsides) |
| Document that must remain searchable/accessible | 🔒 Permission Flags only |
| Images-only PDF (scanned document, screenshot) | Already unselectable — no processing needed |
| Legal document that must be legally enforceable | ❌ Use DRM or server-side access control, not PDF tricks |
What This Tool Cannot Do
- It cannot prevent OCR. Rasterized text can be OCR'd back to text by anyone with a scanner app.
- It cannot prevent screenshots. If a user can see it, they can screenshot it.
- It cannot enforce permissions in non-compliant viewers. Chrome ignores permission flags entirely [citation:4].
- It cannot protect against a determined attacker. PDF security is a spectrum, not a binary. This tool sits at the "casual deterrent" end.