When a Decrypted PDF Still Won't Render on Your Mobile Reader
Mobile phones and tablets handle the bulk of PDF reading in Australia, whether you are reviewing an ATO statement on the train between Parramatta and the CBD, checking a contract on a regional Qantas flight, or marking up lecture notes in a Melbourne library. The expectation is simple: unlock the file, open it, and the content appears. When the decrypted document opens with blank pages, missing fonts, or a jumbled layout, the experience quickly turns frustrating. The good news is that most of these rendering faults are well understood, and the fix usually does not require a fresh copy of the original.
Mobile readers are stricter than their desktop counterparts about font embedding, form field structures, and the way permissions are recorded inside a PDF. A file that looked fine in Adobe Acrobat on a Windows PC can still trip up an iPad or a Pixel because the unlocking step changes how some metadata is interpreted. Rather than assuming the unlock failed, it helps to walk through the most common causes and try targeted remedies in order.
Why a freshly unlocked PDF breaks on phones and tablets
When owner-password restrictions are stripped from a document, the underlying page content is untouched, but the trailer dictionary, cross-reference table, and a few hidden flags are rewritten. Mobile readers on iOS and Android rely heavily on these structural records to decide where each page begins and which fonts to load. If any of them are slightly out of sync, the reader falls back to a safe mode, which often means blank pages, a "Cannot open" banner, or a single page that repeats itself.
Another frequent trigger is partial encryption. Some PDFs apply permissions to a subset of streams while leaving others open. After decryption, a phone reader may see what looks like a conflict between encrypted and unencrypted objects and refuse to render. This is particularly common with files exported from older versions of Nitro or from certain scanning software used by legal firms in Sydney and Brisbane.
Reflow logic also plays a role. Mobile readers switch on a hidden text extraction mode when they detect certain permission markers. Once those markers are removed, the reader can suddenly re-parse every page as continuous text, which is why a beautifully designed brochure might come out as a wall of broken sentences. Restarting the reader, or opening the file in a different app, often reveals whether the fault is structural or simply a viewer setting that has gone rogue.
Rebuilding the file before resending it
Before chasing a reader-specific bug, it is worth rebuilding the decrypted document so that it presents a clean structure to any mobile app. The fastest method is to open the file in a desktop viewer and re-export it. On Windows, printing to the Microsoft Print to PDF virtual printer produces a brand new file with refreshed cross-references and modern metadata. On macOS, the same effect can be achieved through Preview's "Export as PDF" option. Either approach strips residual encryption hints and forces every font reference to be rewritten.
A second method is to use a dedicated optimiser. PDF Decrypter Pro, available through its official office page, can re-save the unlocked file with linearised output, which mobile readers in Australia often prefer because it lets them stream pages as they load over an NBN connection. Linearisation also reduces the chance of the reader timing out on the first page when the signal is patchy in regional areas.
After rebuilding, rename the file with a simple ASCII name and avoid using cloud-syncing apps that try to "preview" the PDF the moment it lands in your Downloads folder. Quick Look on iOS and Files on Android are notorious for caching the broken version of a document, which can make it look as though the rebuild did nothing when in fact the issue is the preview thumbnail rather than the file itself.
Font and glyph problems on iOS and Android
Even after a clean rebuild, missing fonts remain the single biggest reason a decrypted PDF looks wrong on a phone. Many Australian organisations still ship documents with embedded font subsets that reference PostScript names which the mobile reader cannot resolve. The result is a page full of square boxes, random characters, or text that drops to a default Times New Roman while the rest of the layout stays intact.
The fix is to make sure the original fonts are fully embedded rather than subset. Most desktop optimisers have a flag for this. If you do not have access to one, opening the file in Adobe Acrobat Pro and re-saving with "Embed all fonts" checked will usually do the job. The same setting is available in LibreOffice Draw under the PDF export options, and the open-source route is popular with university students in Adelaide and Perth who do not want to pay for a commercial licence.
If you only need to read the document on a specific device, installing the missing font manually is another option. iOS users can drop a TTF or OTF file into a profile through the Fonts app, while Android users on stock Pixel or Samsung devices can copy fonts into the system fonts directory using a file manager. Keep in mind that some glyphs from Type 1 and OpenType CFF families still refuse to render on certain Android builds, so re-embedding remains the more reliable path.
Form fields, annotations, and silent permission flags
Decrypted documents sometimes appear correct but lose the ability to accept input. Drop-down lists refuse to expand, text fields are read-only, and signature boxes vanish. This is usually a sign that the unlock process altered the AcroForm dictionary without updating the interactive flag at the catalogue level. The file is technically open, but the reader thinks it is still protected.
For documents where commenting is the main goal, the workflow described in the article on restoring comment ability covers the precise flag sequence that needs to be repaired. In short, you want to ensure the AcroForm entry is present at the document catalogue and that each widget annotation has its print and read-only bits cleared. Once those two values are correct, the form reappears in apps like Xodo, PDF Expert, and the built-in Files reader on iPadOS.
Annotation layers can suffer a similar fate. Highlighting, sticky notes, and freehand drawings live in a separate content stream, and some desktop optimisers strip that stream when they rewrite the file. To keep them intact, disable any "flatten" or "clean metadata" options before re-exporting, then verify the result on a phone before you share the file with a colleague in Darwin or a client in Hobart.
Reader-specific quirks worth knowing
Not every mobile reader treats a decrypted PDF the same way. Adobe Acrobat Reader on iOS is the most forgiving with font substitution but is also the strictest about permission flags, so it will refuse to render a file that other apps will display. Foxit Mobile PDF is faster with large documents, partly because it aggressively caches page objects, which can mask rendering errors until you force a reload. Xodo and PDF Expert sit somewhere in between and are popular choices for Australian legal teams who need reliable annotation tools.
The built-in reader in Google Files and the Books app on iOS both enable reflow by default. If a decrypted document suddenly shows up as one long scrolling column with no images, switch reflow off. In Google Files, the toggle is hidden behind the three-dot menu while reading. In Books, you need to tap the screen, choose the layout icon, and select "Original PDF" rather than "Scroll View." Most users in Sydney and Brisbane do not realise this setting exists, and assume the file is broken when it is simply being rendered in a different mode.
Samsung's native PDF viewer, found on Galaxy devices sold through JB Hi-Fi and Telstra, has its own quirk. It does not honour the document's initial view magnification if the file has been linearised incorrectly, so every page opens zoomed to fit width, which on portrait phones can make tables look comically small. Using a different reader or rebuilding the file with proper linearisation both solve the problem.
Repairing the file and verifying on a fresh device
When the standard rebuilds do not help, the next step is to repair the internal structure. Ghostscript, qpdf, and the cross-platform toolkit mutool are three command-line options that can rewrite a PDF from scratch, even from a file that other tools refuse to open. Running qpdf --decrypt input.pdf output.pdf after the initial unlock is a common belt-and-braces approach used by IT contractors in mining towns like Kalgoorlie, where intermittent connectivity makes cloud repair tools impractical.
After any repair, test the file on a device that has never seen the document before. Clear the cache in your reader of choice, transfer the file through a channel that does not generate previews, and open it once. If it renders cleanly, the issue was almost certainly a stale thumbnail. If it still misbehaves, repeat the rebuild with a different optimiser and check the console output for warnings about damaged objects or unreferenced resources.
A short verification checklist saves hours of guesswork. Confirm that page count matches the original, that every embedded font is a TrueType or OpenType subset with no missing flags, that the AcroForm dictionary is intact, and that the file size is within ten per cent of the original. If all four pass, the document is ready to send.
Choosing a recovery approach at a glance
| Symptom on mobile | Most likely cause | Quickest fix |
|---|---|---|
| Blank pages or "Cannot open" banner | Stale cross-reference table after unlock | Re-export through desktop viewer or linearise |
| Square boxes and random characters | Subset or missing embedded fonts | Re-save with all fonts fully embedded |
| Reflow text with no images | Reader in scroll view mode | Toggle off reflow in Google Files or iOS Books |
| Form fields greyed out | AcroForm flag not refreshed | Clear interactive flag at catalogue and widget level |
| Annotations missing after rebuild | Optimiser flattened or stripped layers | Disable flatten and metadata clean before re-export |
| Table renders too small on Galaxy | Linearisation mismatch on Samsung reader | Rebuild with proper linearisation or switch to Foxit |
| File fails on every reader | Damaged object stream | Repair with qpdf or mutool from the command line |
Open the recovered file in a single reader first, confirm the page count and the first three pages look right, and only then copy it to the cloud account that syncs with your tablet, since catching a render fault before it propagates through iCloud, Google Drive, or OneDrive is the most reliable way to avoid having to chase the same problem across three devices later that afternoon.