Fix "Failed to Load PDF Document" Error in Chrome
Chrome shows "Failed to load PDF document" when its built-in viewer can't render the file. Here are all the fixes — from simple reloads to recovering the content entirely.
Chrome's "Failed to load PDF document" error appears in the built-in PDF viewer when PDFium — Chrome's PDF rendering engine — can't process the file. Unlike Adobe's errors, Chrome gives no error code, making diagnosis harder. The causes range from trivially simple (reload the page) to complex (PDF spec version incompatibility). This guide covers them in order from fastest to fix.
Why Chrome Shows This Error
Chrome renders PDFs using PDFium, an open-source PDF engine that Google maintains. PDFium is less strict than Adobe but also has its own limitations: it doesn't support PDF encryption using certain algorithms, struggles with some AES-256 encrypted files, and occasionally fails on PDFs with broken cross-reference streams. The error appears instead of a partial render — Chrome either shows the PDF or shows the error message, there's no middle ground like Adobe's partial rendering.
Fix 1 — Hard Reload the Page
Press Ctrl+Shift+R (Cmd+Shift+R on Mac) to hard reload. If the PDF is served from a URL, Chrome sometimes caches a partial file from a previous interrupted load. A hard reload bypasses the cache and downloads fresh. If the PDF opened from a local file (dragged into Chrome), close the tab and drag the file in again — Chrome sometimes holds a file lock that prevents re-reading. This trivial fix resolves the error roughly 20% of the time when the file itself is fine.
Fix 2 — Download the File and Open Locally
If the PDF is served over the internet, click the download icon in Chrome's toolbar (top right when a PDF is open) to save it to disk. Then open the downloaded file by dragging it into a new Chrome tab. This removes network-related causes — timeouts, partial transfers, server headers that confuse Chrome's MIME detection. If the local copy opens but the online version doesn't, the problem is with how the server is serving the file, not the PDF itself.
Fix 3 — Disable Chrome PDF Viewer and Use Adobe Instead
Chrome's built-in viewer can be disabled in favour of Adobe Reader. Go to chrome://settings/content/pdfDocuments and toggle "Download PDFs" on. Chrome will now download PDFs instead of opening them inline. Open the downloaded file in Adobe Reader. This is a permanent workaround if specific PDFs consistently fail in Chrome but open fine in Adobe. You can also try Edge's PDF viewer, which is based on a different engine and handles some files Chrome can't.
Fix 4 — Check If the PDF Is Encrypted
Chrome cannot open AES-256 encrypted PDFs that require a password before any content is displayed. It shows "Failed to load PDF document" instead of a password prompt — a known Chrome bug that exists since 2019. Test this: try to open the PDF in Firefox. If Firefox asks for a password, the file is encrypted and you just need to enter the correct password. If you're the document owner and want to make it universally accessible, use FixMyPDF's unlock tool to remove the encryption.
Fix 5 — Re-process Through FixMyPDF
If the PDF opens in other viewers but not Chrome, it likely uses a PDF feature PDFium doesn't support. Running the file through FixMyPDF's compressor (at Low compression) re-writes the internal structure using standard, widely-supported PDF features. Download the output and try opening in Chrome again. This works because the re-processing strips non-standard constructs and rebuilds the cross-reference table — the two most common PDFium incompatibilities.
Try Compress PDF Now — Free
Browser-based, private, and instant. No account or software required.
Open Compress PDF