Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the TidBITS Content Network for Apple consultants.

What to Do When Your Web Browser Won’t Display PDFs

Sometimes you click a link in your Web browser and instead of it taking you to another Web page, the link goes to a PDF instead. For most of us, this is no problem: modern browsers have had the capability to display PDFs directly for a while now, and the result of clicking a link to a PDF usually results in the PDF appearing inside the browser window. For details about how this works in Safari and Google Chrome, see Steve McCabe’s “Wrangling PDFs in 2012’s Web Browsers” (1 June 2012), along with Agen Schmitz’s TidBITS Watchlist entry for “Firefox 19” (19 February 2013).

Nonetheless, whenever we publish a link to a PDF in one of our articles or Take Control books, it’s not uncommon to hear from frustrated readers who tell us that all they see when they click the link is a blank black or white page. Fortunately, the solution is simple and usually requires nothing more than removing a couple of files from your Mac.

In most cases, the cause of the problem is one or two older browser plug-ins from Adobe that don’t play nicely with today’s browsers: AdobePDFViewer.plugin and AdobePDFViewerNPAPI.plugin. These plug-ins are installed by Adobe Reader or by Adobe Acrobat Pro and are put in place to enable browsers to display PDFs using Adobe’s own PDF-displaying code. However, versions of Reader or Acrobat prior to version 10.1.3 provide plug-ins that are incompatible with some browsers; in particular, Safari 5.1 or later and recent versions of Firefox end up showing black pages (Safari) or white pages (Firefox) when the incompatible Adobe plug-ins are installed.

The fix is easy: quit your browser (this step is important!) and remove the plug-ins. You can usually find them in the Internet Plug-ins folder inside the main Library folder on your Mac — no, not the hidden Library in your Home directory (also known as ~/Library/Internet Plug-Ins) but the one at the top level of your hard disk (/Library/Internet Plug-Ins).

Open that folder, look for any files that begins with the name AdobePDFViewer, and drag them out of the /Internet Plug-ins folder (put them on the Desktop temporarily if you don’t want to trash them immediately). You will be asked to confirm the move by entering an administrator name and password.

Sometimes you won’t find the incompatible plug-ins in your main Library folder. If so, look in the Library folder in your Home directory instead. This folder is hidden by default in Mac OS X 10.7 Lion and 10.8 Mountain Lion (see “Dealing with Lion’s Hidden Library,” 20 July 2011). To reach it in the Finder, hold down the Option key, choose Go > Library, and then navigate to the Internet Plug-Ins folder. If you see the AdobePDFViewer plug-ins in that folder, drag them out; again, you may be asked to confirm the move by entering an administrator name and password.

Once the plug-ins are removed, launch your Web browser and try again — you should now be able to view PDFs right in the browser window using the browser’s native PDF support. (And if you don’t want to view PDFs in your browser at all, read “Wrangling PDFs in 2012’s Web Browsers” for instructions on disabling the functionality.)


Make friends and influence people by sponsoring TidBITS!
Put your company and products in front of tens of thousands of
savvy, committed Apple users who actually buy stuff.
More information: <>

Comments about What to Do When Your Web Browser Won’t Display PDFs
(Comments are closed.)

Anonymous  2013-04-30 22:07
What about browsers without integrated pdf viewers, like Chromium? (For some reason Chrome hangs on certain sites for me lately, and reinstalling didn't help, but Chromium works.)
Adam Engst  An apple icon for a TidBITS Staffer 2013-05-01 06:22
If there's no integrated PDF viewer support, the browser should just download the PDF like any other file.
Anonymous  2013-05-01 18:46
I was hoping to learn about a plugin that would display PDFs., but I don't think devs are spending time on this since Chrome itself offers this functionality. (I've read about a hack which entails downloading Chrome, pulling out the pdf reader module and inserting it into Chromium, but manually doing this every time Chromium comes out with a new version would make me crazy.)
Adam Engst  An apple icon for a TidBITS Staffer 2013-05-02 07:13
Ah, I understand. You can try Schubert's PDF plugin, but I don't know if it will work in Chromium.
Alan Forkosh  An apple icon for a TidBITS Supporter 2013-04-30 23:42
In an ideal word, my preference would be for PDF's to open directly in a preferred helper app (Preview or Adobe Reader) but with the option to open the link in either app available from the contextual drop-down menu obtained from right-clicking the the link.

As long as I prefer using Preview, opening first in the web browser and the right-clicking to open in Preview works well enough. However, I really prefer the interface provided via Schubert|it’s PDF Browser Plugin provides a list of apps that open PDF's. The major issues here are the fussy scrolling if you choose to view in the browser and the initially slow generation of the list of usable applications.
Ever since I bought a new MacBook Pro in Dec of 2011, I had problems with being able to download pdfs in Safari. I hoped it would be corrected when I upgraded to Lion, but it didn't. This article FIXED IT! Thank YOU!
Michael E. Cohen  An apple icon for a TidBITS Staffer 2013-05-09 12:40
You are very welcome!  2013-05-13 16:55
Just sayin', but when my browsers don't display PDFs, I consider them set up correctly.
Robert Vargas  2013-05-15 14:00
I had an unusual experience while following your directions. I dragged the plugins from the folder to the desktop and was not prompted to enter a password (nor did the plugins disappear from the plugins folder). I had to start over and delete files directly to the trash. Safari and Firefox were closed before I undertook the initial move.
Adam Engst  An apple icon for a TidBITS Staffer 2013-05-15 14:19
That is odd - you might run Disk Utility and click Repair Permissions, just in case something has gone out of whack with the underlying permissions.