Fix "Something Went Wrong While Displaying This PDF" in Chrome
Chrome's "Something went wrong while displaying this PDF" has five different causes. This guide walks through each one and tells you exactly which fix applies to your situation.
"Something went wrong while displaying this PDF" in Google Chrome is a catch-all error that Chrome's PDF viewer shows when PDFium encounters a rendering problem it can't recover from. The frustrating part: it covers at least five distinct root causes, each with a different fix. This guide tells you how to identify which one applies to your situation.
Identify Your Specific Cause First
Before applying any fix, test these three things: (1) Can you open a different PDF in Chrome? (2) Does the problem PDF open in Firefox or Edge? (3) Is the PDF served from a URL or a local file? If only one PDF fails — especially from a URL — and others open fine, it's either file-specific corruption or a server configuration issue. If all PDFs fail in Chrome but work elsewhere, it's a Chrome profile or extension issue. If even local PDFs fail, it's a Chrome installation problem. This three-question test narrows the fix immediately.
Fix 1 — Disable Extensions That Intercept PDFs
PDF-related extensions — PDF editors, merge tools, annotation tools — can intercept Chrome's PDF rendering and cause this error. Go to chrome://extensions and temporarily disable all extensions. Try opening the PDF again. If it works, re-enable extensions one at a time to identify the culprit. Extensions that modify PDF behaviour include: Smallpdf, Adobe Acrobat, Kami, Foxit PDF, and any "PDF editor" Chrome extension. Disable the conflicting extension or use Incognito mode (which disables most extensions by default) to open PDFs.
Fix 2 — Clear Chrome's Cache
Ctrl+Shift+Delete → check "Cached images and files" → Clear data. Then reload the PDF. Chrome caches PDF responses and if the cache is corrupted — which happens during interrupted downloads — it serves the broken cached version. Clearing forces a fresh download. For PDFs accessed via a URL, also check whether the URL itself is still valid (not expired or moved) by opening it in an Incognito window, which uses no cache.
Fix 3 — Check for a Password or DRM
Some DRM-protected PDFs from publishers (textbooks, licensed documents) use encryption schemes Chrome doesn't support. Instead of a password prompt, Chrome shows this error. Test: open the same PDF in Adobe Reader. If Reader asks for a password or shows a DRM warning, that's the cause. For password-protected PDFs you have the password to, FixMyPDF's unlock tool removes the protection so the file can be opened universally in any viewer without DRM restrictions.
Fix 4 — Reset Chrome's PDF Viewer
Go to chrome://settings/content/pdfDocuments, toggle "Download PDFs" on, then off again. This resets Chrome's PDF viewer registration. Alternatively, type chrome://components in the address bar, find "PDF Viewer" and click "Check for update." An outdated PDFium component can cause rendering failures on PDFs that use features added to the spec after the installed version. Updating the component (or the whole browser via chrome://settings/help) usually resolves this.
Fix 5 — Re-process the PDF Through FixMyPDF
If the PDF uses features from PDF spec 2.0 that Chrome's current PDFium doesn't support, or contains non-standard constructs from obscure PDF authoring tools, running it through FixMyPDF's compressor normalises the file to widely-compatible PDF 1.4/1.5 structures. Download the output and open in Chrome — the normalised file will render correctly even on older viewer versions. This is the fix when all other methods fail and the PDF is confirmed to open in Adobe Reader.
Try Unlock PDF Now — Free
Browser-based, private, and instant. No account or software required.
Open Unlock PDF