Fix a PDF that will not open on your phone

Which of the five problems you have

Run these three checks before you change anything. They take a minute and point at the right section below.

• Try a second PDF on the same phone. If it opens, the reader is fine and the first file is broken, unfinished, or locked. If nothing opens, the reader or the phone is the problem.
• Look at the file size. A download of a few kilobytes for a file that should be pages long never finished. Download it again over a stable connection.
• Read the exact message. A password request means the file is protected, not broken. A "can't open file" or blank preview points at the reader app or the download.

This triage mirrors the standard order reader makers themselves suggest: check the file and the app before anything else, with an outdated reader, a wrong default app, and an incomplete download as the first suspects.

On Android: the reader is usually the problem

Android opens a PDF through whichever app is set as the default, and that choice is often the fault. If you once tapped "always" on an app that cannot read PDFs, every PDF since has gone to the wrong place with a "can't open file" error. Open Settings, then Apps, find the app that grabs the file now, tap Open by default, and clear the default so you can pick a proper reader.

If the reader is the right app and the file still fails, update it in the Play Store. Reader makers commonly suggest updating and clearing cache as early steps: an outdated reader carries bugs that break newer files. To clear cache, open Settings, then Apps, then See all apps, pick the reader, then Storage and cache, then Clear cache. A full cache mostly shows as slowness rather than failed opens, so treat this as hygiene.

On iPhone: check Files and iCloud first

iPhone mail apps preview attachments, and a file that has not finished syncing shows as a failed preview rather than anything useful. Open the Files app and look at the file itself: a cloud icon with a downward arrow means it is still in iCloud and not on the phone yet. Tap it and wait for the download to finish before judging the file.

If the file is on the device and still will not render, open it in Books rather than the mail preview: the file is usually fine and the phone copy or the viewer is not. Keeping iOS itself updated is general hygiene for rendering bugs.

When the file itself is broken

A download that dropped halfway is the most common broken file. The fix is boring and works: delete the fragment and download again over stable Wi-Fi, then check the size looks plausible before opening it.

If a complete download still fails everywhere, including on a computer, the file is damaged and needs repair rather than a new reader. Run it through the repair tool in a phone browser tab: nothing is uploaded and nothing is installed.

Two other cases dress up as a broken file. A password prompt means the file is protected, so follow the protected PDF guide instead of repair steps. A very large scan that opens on a laptop but dies on a phone can be memory or reader limits rather than damage: shrink a copy with the compress tool and open the smaller file on the phone.

The no install fallback: open it in a browser tab

Both major phone browsers read PDFs on their own. Chrome opens PDFs from web links and inside its own downloads view without any reader app; files stored in Drive preview inside the Drive app. On iPhone, Safari renders a PDF link inline. So if the reader app is fighting you, skip it: open the file, or its link, directly in the browser.

The same trick covers repair and conversion. The repair, compress and PDF-to-images tools below run inside the tab, so a file that will not open in an app can still be repaired or shrunk from the browser, as long as the download is complete, the file is unencrypted, and the browser engine can still read it. And if no reader on the phone will render the pages at all, the PDF to images tool turns the pages into pictures you can read in any gallery app.