A read-only PDF has one of three causes - a permissions lock inside the file, scanned pages with no text layer, or the read-only attribute on the file itself - and each has a free fix: clear restrictions with a browser-based tool, run OCR on scans, or untick read-only in the file properties. This guide diagnoses your case in thirty seconds and gives exact steps for all three fixes, plus the legal boundaries worth knowing.
Quick answer: to make a non-editable PDF editable, first lift permission locks with the free Remove Restrictions tool (no password needed for owner-level locks), then edit directly or convert to Word. Scanned pages need OCR first. All of it runs free in your browser with nothing uploaded.
Causes and fixes at a glance
| Cause | Signature | Fix |
|---|---|---|
| Permission lock | Edits greyed out, text still selects | Remove Restrictions tool |
| Scanned pages | No text selectable at all | OCR, then edit |
| Disk read-only flag | OS refuses to save the file | Clear attribute in file properties |
On this page
- Diagnose your read-only PDF in 30 seconds
- Method 1: Remove permission restrictions (free)
- Method 2: Cover and retype - edit without unlocking anything
- Method 3: Convert to Word and rebuild
- Method 4: OCR for scanned read-only documents
- The disk-level read-only attribute
- What those permission flags actually mean
- Legal and ethical boundaries
- Troubleshooting
- FAQ
Diagnose your read-only PDF in 30 seconds
Before touching any tool, classify the file - each failure mode has a distinct signature:
Signature 1 - the file opens, text selects, but every edit option is grayed out or the editor reports "editing not allowed". This is a permissions lock: the document carries an owner password that sets flags like "Editing: Not allowed" in File > Properties > Security. Fix: Method 1.
Signature 2 - you can select text, and copying works, but your edits "do nothing" after saving. This is often a flattened or viewer-limited file: some free tools and print-to-PDF exports produce documents that look editable but are structurally inert. Test by opening in a second editor; if it behaves the same, treat it like permissions (Method 1) or route around with Methods 2-3.
Signature 3 - you cannot select any text at all; zooming in shows fuzzy edges. This is a scanned/image document: there is no text layer, so no editor can "edit text" that does not exist. Fix: Method 4 (OCR), or skip text entirely with Method 2.
Signature 4 - the file refuses changes at the operating-system level ("read-only" in the save dialog, or a padlock in File Explorer). That is the disk attribute, not a PDF feature. Fix: the disk-level section below - ten seconds in file properties.
Misdiagnosis wastes more time than any technical step: people run OCR on permission-locked files (nothing changes) or hunt for password removers on pure image scans (no password exists). Classify first, then fix.
Method 1: Remove permission restrictions (free)
Owner-password permissions are the most common read-only cause, and the good news is structural: these flags are policy, not encryption of the content. The document opens, displays and prints without any password - the flags merely ask editors not to modify it. Tools can therefore clear them mechanically.
With the free Remove Restrictions tool: drop in your file; it is processed locally in your browser; download the unrestricted copy. No password entry, no upload, no waiting.
After unlocking, verify the Security tab now shows "Editing: Allowed", then work normally: cover-and-retype small fixes in the Edit PDF tool, or convert to Word for structural changes (Method 3).
Two honest boundaries, stated plainly. First, this clears permission locks only - a document that requires a password just to open stays closed, and you should not attempt to bypass that (if it is your file, recover the password from the person or system that set it; password recovery services exist for legitimate owners). Second, authorization matters: clearing restrictions on your company's template or your own exported file is routine; stripping protection from licensed material or someone else's confidential document is not, regardless of technical ease.
Method 2: Cover and retype - edit without unlocking anything
Here is the trick most people never consider: permission flags restrain the editor's content-rewrite operations, but annotation-style additions - new text boxes, shapes, highlights - are usually permitted even on locked files. That is enough for the majority of real-world edits.
The workflow with the Edit PDF tool:
- Open the locked file normally. No unlock step needed.
- Cover the text you want to change: draw a rectangle filled with the page background color (white in most documents) over the old passage.
- Type the replacement in a new text box - choose font, size and color first, then align the baseline with neighboring lines.
- Save/download. The annotations become part of the page appearance; the underlying locked content is untouched underneath.
Why this often works where direct editing fails: PDF permissions distinguish between modifying existing content objects (forbidden by the flag) and adding new annotation objects (frequently allowed). Editors implement that distinction faithfully, so the annotation door stays open on files whose front door is locked.
Where it will not help: wholesale restructuring, or a document whose annotations are also locked. Then Method 1 or 3 is the honest answer. But for "fix a date, update a name, correct a price" jobs on locked files, this is the fastest legitimate path - and it has a bonus property: the original content survives underneath your additions, which for audit-minded environments is a feature, not a bug.
Method 3: Convert to Word and rebuild
When the change is structural - reordering sections, rewriting paragraphs, renumbering tables - the cleanest route is to leave the PDF world entirely, if only briefly.
Step 1. Run the file through the free PDF to Word converter. The DOCX that comes out is a brand-new document: PDF permissions do not transfer to Word files, so the result is fully editable regardless of the original's flags (conversion respects the source's copy/extract settings at the time of processing, so if copying was blocked at the file level, unlock with Method 1 first).
Step 2. Edit the DOCX freely in Word, Google Docs or LibreOffice - styles, fonts, sizes, structure, all of it.
Step 3. Export back to PDF with the free Word to PDF tool. The fresh file carries none of the old restrictions and embeds your fonts properly.
This is the method to reach for when edits exceed a paragraph, when you need the document in an editable format anyway, or when you control the template and want future versions born editable. It rebuilds layout rather than preserving it - keep the original locked file as the reference, and treat the new PDF as a derived version with its own metadata and history.
Method 4: OCR for scanned read-only documents
Scans are the second-largest source of "read-only" frustration, and no unlock tool helps because the problem is absent text, not blocked text. OCR - optical character recognition - is the fix: it reads the pixels, recognizes letterforms, and writes an invisible text layer onto each page.
With the free OCR PDF tool: drop in the scanned file, pick the document language (accuracy depends heavily on choosing correctly), and download the processed PDF. The pages look identical, but text is now selectable, searchable, copyable - and editable via the Word route.
Practical expectations, honestly stated: OCR quality tracks scan quality. Clean 300 DPI scans of typed pages typically recognize 98-99% of characters, with errors clustering at foreign words, unusual fonts and poor contrast. Handwriting remains unreliable. Always proofread anything consequential - a one-minute pass per page catches the stray character that matters.
After OCR, choose your edit path: cover-and-retype on the processed PDF (Method 2), or PDF-to-Word and back for structural changes (Method 3). And if the goal was never editing but only finding text, note that OCR alone already delivers searchability - often the actual need behind "I need to edit this scan".
The disk-level read-only attribute
The fourth cause lives outside the PDF entirely, and it takes ten seconds to clear once you know where to look.
Windows: right-click the file in Explorer > Properties > General tab > untick "Read-only" > OK. If the file lives in a synced or protected folder (OneDrive "Known Folder" backups, program directories), move it to Documents or the desktop first - sync engines and permissions on special folders can re-impose read-only behavior no matter how often you clear the flag.
macOS: right-click > Get Info > expand "Sharing & Permissions" > set your user to "Read & Write". For files on external drives formatted NTFS (which macOS cannot write natively), the read-only behavior is the filesystem, not the file - copy to the Mac's disk before editing.
Cloud-synced copies: a document checked out or opened by someone else in a shared workspace can present read-only until their lock releases. The "read-only" badge in Office/web viewers refers to that state - wait or use "Save as" to your own copy.
A quick sanity test separates disk-level from in-file causes: copy the file to a fresh folder and try editing the copy. If the copy edits fine, the original's folder or attribute was the culprit; if the copy is still locked, the restriction is inside the PDF and Methods 1-4 apply.
What those permission flags actually mean
PDF security has a two-password architecture, and the confusion between the two is responsible for most myths on this topic.
The user (open) password encrypts the document's content. Without it, the file is unreadable ciphertext - viewers cannot show you page one. This is real encryption (AES), and there is no legitimate tool-free way around it: you need the password from whoever set it.
The owner password does something entirely different: it is the key to a permissions dictionary that asks viewers to disable printing, copying, annotation or editing. The document's content is not hidden - you are reading it right now - so every viewer must already decrypt it to display pages. The owner password guards policy, not content. That is why permission-clearing tools work without any password: they edit the policy layer of an openable document, not its encrypted payload.
The practical upshot: when a file "opens but won't edit", you are dealing with the policy layer, and Method 1 is the matching key. When a file "asks for a password to open", that is encryption - a different problem entirely, solved by getting the password, not by tools. Knowing which wall you are facing turns a frustrating afternoon into a five-minute fix.
It is also worth knowing what permissions don't do: they are not DRM, they do not track or report access, and their enforcement is entirely up to the viewer software (some niche viewers ignore them entirely). They are best understood as tamper-resistant packaging - a strong social signal and a light technical fence, not a vault.
Legal and ethical boundaries
All of the methods above are ordinary, legitimate document work in the right hands - and inappropriate in the wrong ones. The line is authorization, and it is worth drawing explicitly.
Clearly fine: files you created; your company's internal documents and templates; documents sent to you for the express purpose of updating them (contracts in revision, drafts with tracked changes requested); public material not restricted by license; accessibility adaptations of documents you lawfully possess.
Requires thought and usually permission: licensed publications and paid templates (adaptation rights live in their license terms); documents where you are one party among several (edits to shared agreements should be visible to all parties); anything stamped confidential and belonging to a client or employer.
Not okay: stripping restrictions from someone else's copyrighted work to republish it; editing received invoices, statements, certificates or IDs; circumventing access controls on materials you are not licensed to use. Several of these are straightforwardly illegal in most jurisdictions (anti-circumvention provisions like the DMCA exist precisely for the tool-shaped edge of this), and the remainder violate contracts and trust.
A test that fits on a sticky note: would the document's owner be comfortable watching you do this? If yes, proceed - the tools above are the right ones. If no, the fix is a conversation, not an unlock.
Troubleshooting
Removed restrictions but the editor still refuses changes. You are probably in a signature-locked document: a certifying digital signature can enforce permissions independent of the password flags. Editing will break that seal - if the document is yours or authorized, clear the signature first (see the signed-PDF guide), then edit.
Unlock worked, but pages are images anyway. Permission removal and OCR solve different problems; this file needed both. Run OCR, then edit.
Converted Word file is garbled or empty. The source is likely a scan without a text layer. OCR first, then convert. If the source is native text but the result is garbled, the PDF uses an unusual font encoding - the cover-and-retype method avoids conversion entirely.
The restrictions come back after I save. Your editor is preserving the original document's security dictionary on export. Save via a different path - print-to-PDF, or export from the Word round trip - which produces fresh, unrestricted files.
Owner password required dialog appears on unlock. Some tools prompt for the owner password opportunistically; supplying it is cleaner when you have it. Without it, choose a tool that clears permissions from openable documents directly (as PDFEditorFree's does locally).
File edits fine on one computer, read-only on another. Compare the two environments: disk attribute, sync-client locks, or a viewer with restrictive default policy on the second machine. The file itself is rarely the variable.
Where read-only files come from (and how to avoid creating them)
Knowing the origin story of locked files helps in two directions: it tells you which fix likely applies before you diagnose, and it teaches you to never create the problem for your own recipients.
Export settings. Word, InDesign and most PDF generators expose a "restrict editing" checkbox (or full PDF/A + security presets). The single most common locked file in the wild is a Word export where someone ticked "Permissions password" "just to be safe". If you produce documents: leave restrictions off unless there is a concrete reason, because every restriction you add is a tax every future editor pays.
Print-to-PDF pipelines. Documents that arrived as images of themselves (virtual printers, fax services, screenshot exports) are inert by construction. No unlock applies; OCR is their only path to editability.
Signature-enforced locks. Certifying signatures commonly apply "no changes" permissions as part of signing. These are covered in the signed-PDF guide - the unlock tool alone will not help, and breaking the seal is a deliberate act, not a side effect.
Legacy protection habits. Files from law firms, HR systems and financial institutions often carry decade-old security dictionaries set by whatever enterprise tool produced them. They unlock identically to any other owner-password file.
Template libraries. Organizations deliberately lock templates so marketing materials stay on-brand. The right move there is not to unlock the company template - request the editable master, or save-as before modifying your personal copy.
The avoidance checklist for your own exports, in order of importance: no permissions password unless the document genuinely needs one; fonts embedded (so recipients' machines do not create substitute-font chaos); real text, not rasterized pages (so future OCR is never needed); and metadata that says which version the file is. Four settings, thirty seconds, and your files will never be the ones people write support tickets about.
Method 2 in depth: annotation strategies that survive permission checks
Because cover-and-retype is the workhorse for locked files, it deserves deeper treatment - a few professional habits separate clean results from obvious patches.
Background matching. Perfect covers start with perfect color sampling. On white pages, pure white (FFFFFF) is right. On tinted or textured pages, sample the exact pixel color: most editors' color pickers include an eyedropper, or zoom to 800% and read the hex from a pixel-precise screenshot. A cover that is one shade off is invisible on screen at 100% and glaring in print.
Edge discipline. Draw covers 1-2 pixels beyond the text's bounding box on every side. Tighter than that leaves ghosting edges of the old glyphs; looser than that on ruled or boxed layouts covers the rules you meant to keep. Zoom to 200-400% for the drawing itself, then zoom back out to verify at reading size.
Font discipline. When the replacement text cannot match the original typeface exactly (locked files rarely carry usable fonts), match three visible properties in order of noticeability: size (visual height, not the point number), weight (bold vs regular), and color. Letterform differences between Helvetica and Arial are far less detectable than a wrong size or weight.
Baseline alignment. The strongest tell of an amateur edit is a replacement line floating a hair above or below its neighbors. Align baselines, not box tops: nudge in single-pixel increments until the new line's feet sit in the same plane as surrounding text.
One-layer discipline. Resist stacking multiple covers and text boxes for one correction; a single cover plus a single text box per passage keeps the file manageable and the edit diffable. If a passage needs three lines of replacement, one cover over the whole block and one text box with three lines beats three separate patches.
Applied together, these produce edits that survive printing, zooming and skeptical review - which is the actual bar for documents that circulate beyond your desk.
Read-only in specific apps: quick answers for common environments
The same locked file behaves differently across the apps people actually use, and the fastest fix depends on which window you are staring at.
Adobe Acrobat Reader (the free one). Reader annotates but cannot edit content on any file - a frequent false alarm where the file is fine and the tool is read-only by design. If the Security tab shows "Editing: Allowed", your problem is the free viewer, not the file: move to a browser-based editor like PDFEditorFree.
Microsoft Edge / Chrome PDF viewers. Browsers display and (in Edge) annotate lightly, but never edit content. Useful for verifying text selection and copying - both work even on permission-locked files when flags allow - but the editing itself needs a real editor.
Preview on macOS. Preview adds annotations, shapes and signatures to almost any openable file, permission flags notwithstanding, because it treats them as markup rather than content edits. For quick visual fixes on a Mac, Preview frequently "just works" where stricter editors refuse; treat its output as an annotated copy.
Word's "PDF Reflow". Opening a PDF directly in Word converts it to an editable document on the spot - the built-in equivalent of Method 3, with quality that trails dedicated converters on complex layouts. Note that Word's conversion is a new document: permissions do not carry over, which is precisely why locked files so often go this route.
Google Drive preview. Opens, displays, and with one click sends the PDF into Google Docs conversion - a service-side cousin of Method 3 with the privacy trade-off that the file uploads to Google. Fine for public documents; think twice with confidential ones, where local processing wins.
The meta-lesson: when an app says a document is read-only, separate three questions - is it the app's limitation, the file's permission, or the content's nature (a scan)? Each has a different next step, and the diagnosis section at the top of this guide maps all three.
FAQ
Why is my PDF read-only? Usually one of three: owner-password permissions inside the file, scanned pages with no text layer, or the read-only attribute on the file itself. Diagnose by whether text selects and whether edits gray out, then apply the matching method above.
How do I make a non-editable PDF editable? Clear permission flags with the free Remove Restrictions tool, then edit or convert to Word. For scans, OCR first to create editable text. Everything runs locally in your browser.
Is it legal to remove restrictions from a PDF? On documents you own, control, or are authorized to modify - yes, it is routine practice. Circumventing protection on someone else's copyrighted or confidential material without authorization is not.
How do I edit a read-only PDF without the password? Permission (owner) locks are separate from open passwords and can be cleared without one, because the document is already readable. An open password cannot and should not be bypassed - recover it from the source instead.
Why can I select text but not edit it? Selection is display behavior; editing is a permission. The flags commonly allow copying while forbidding modification, which is exactly what protected business documents ship with.
How do I change a PDF from read-only on the file level? Windows: right-click > Properties > untick Read-only. macOS: Get Info > Sharing & Permissions > Read & Write. This clears only the disk attribute, not in-file permissions.
Does converting a read-only PDF to Word remove the protection? Effectively yes - the DOCX is a new file with no PDF permissions, fully editable. If extraction was blocked at the file level, clear restrictions before converting.
Will the author know I edited a protected PDF? PDFs make no notifications; edits happen locally. Discovery, where it matters, comes from content comparison, metadata and version history - one more reason to only edit what you are authorized to change.
Unlock and edit your PDF now
Drop your file into the free Remove Restrictions tool, then fix it with Edit PDF or the PDF to Word round trip - all local, all free, no signup. Related guides: editing signed PDFs and replacing text in a PDF.