Portable Document Format (PDF) — first launched by Adobe in 1993 and now an open ISO standard — has long been the de facto standard for documents shared via the Web. Thanks to the free Adobe Reader application and Apple’s inclusion of Preview in Mac OS X, anyone who happens across a PDF on a Web site can open it. But what if you just want to read the PDF quickly like any other Web page and move on, without having to download it, open it in Preview or Adobe Reader, and deal with the file in your Downloads folder later?
The Mac enjoys Web-based PDF support out of the box; Safari has natively rendered PDFs for many years. Chrome, Google’s increasingly popular Web browser, also now includes native support for PDF. But Firefox, the last of the big three Mac browsers, has long struggled to display PDFs, forcing users to download PDF files and read them in Preview or Adobe Reader. At various times, an assortment of plug-ins have enabled Firefox to display PDFs internally, but many of those have come and gone, leaving Firefox users confused as to the options.
This status quo has been shaken up with the arrival of Adobe Reader 10.1.3, Adobe’s free application-and-browser-plug-in bundle. However, installing the Adobe Reader PDF plug-in can affect browser behaviour in various ways. It’s time, then, for an overview of what you can do with PDFs in your browser of choice, what you can’t do, and what you might want to figure out how to do.
Safari — Apple’s Safari has long sported the capability to display PDF files as though they were just another Web page — click a link ending in .pdf and the linked file appears within the existing browser window, with no additional configuration required. If you want to save the PDF to your hard disk, you have a few options:
- If you know that a link leads to a PDF you want to download, Control-click the link and choose one of the Save As items from the contextual menu.
- For a faster approach, Option-click the link leading to the PDF to download the file instantly to your Downloads folder.
If you have already loaded the PDF into a Safari window, you can Control-click anywhere on the PDF and choose Open in Preview, choose File > Save As, or click the Download button that appears at the bottom of the screen. (Those controls tend to disappear; if you don’t see them, move the mouse pointer to the bottom center of the screen.)
There is another, more permanent, way of forcing Safari to download PDFs; if you would like downloading to be Safari’s default method, you’ll need to resort to the command line. Quit Safari, and then, in Terminal, copy and paste this line and press Return:
defaults write com.apple.Safari WebKitOmitPDFSupport -bool YES
The drawback to this approach is that it disables inline rendering totally. To get it back, use this command in Terminal:
defaults write com.apple.Safari WebKitOmitPDFSupport -bool NO
Once you’re viewing a PDF in Safari, you have only a few options available by Control-clicking anywhere in Safari’s window. You can select and copy text, and you can zoom in and out. You can also change the page display to show one or two pages, either at a time or continuously scrolling. Searching works, and internal links and Web links are hot, but Safari cannot show any bookmarks. And, of course, you can print the PDF using File > Print.
Chrome — Chrome’s PDF handling closely resembles Safari’s; the inline PDF renderer is enabled by default, and you can save PDF links to disk either from a contextual menu or by Option-clicking the link. Once a PDF is loaded in a Chrome window, you can save it either from another contextual menu or by clicking the floppy disk icon that appears in the lower right corner of the window whenever you move the pointer in that general location.
Unlike Safari, though, the option to disable inline rendering entirely is easily accessible — type
chrome://plugins/ into Chrome’s address bar and hit Return, and a list of plug-ins is displayed. Then, simply click the Disable link under “Chrome PDF Viewer” and Chrome will treat .pdf links as files to be downloaded, rather than pages to be displayed. In a further improvement over Safari, no restart is required in order to toggle between the two.
As with Safari, there aren’t many things you can do with a PDF in Chrome. You can zoom in and out, select and copy text, print the PDF, search for text, and, unusually, rotate the view. Internal and external links work, but again, no bookmarks are shown.
Firefox — Firefox does things differently. The good people at the Mozilla Foundation have clearly decided that native PDF support isn’t necessary — clicking a link to a PDF file displays a dialog asking “What should Firefox do with this file?” Firefox can either open the file in Preview (or whatever your default PDF program may be), or it can save the file to disk. But what it can’t do is display the file in a browser window.
In the past, various plug-ins have enabled PDF browsing in Firefox, but have either suffered from inelegant interfaces or have failed to maintain compatibility with Firefox updates.
The compatibility of Schubert|it’s PDF Browser Plugin has waxed and waned over the years; it currently seems to work in Firefox 12, but even when it works, it’s quite minimal, lacking even text selection, a surprising omission in a plug-in that costs $69 for commercial use; it’s free for personal and educational use. (Interestingly, Schubert|it’s PDF Browser Plugin can also take over PDF rendering for both Safari and Chrome, though it’s unclear why anyone would want that, since it’s slower and generally less capable.)
Nitro PDF Software’s PDF Download talks a good game, offering options to save, open inline or open as HTML any .pdf link, but fails to deliver — the HTML option produces a page that bears only a passing similarity to the original document, while the “inline” option actually converts PDFs to images; the results are both fuzzy and slow to appear. Clearly, something more robust is required.
disk. Most notably, though, it offers an optional sidebar that can show either page thumbnails or PDF bookmarks.
What it lacks is support for printing (you’ll want to download and print from Preview instead). But its main flaw is that it is slow, both to load documents initially and sometimes to display pages even after loading. Short documents, such as a one-page flyer from my Web site, load without grief; longer files such as Apple’s product documentation come in rather slowly, but not
unacceptably so. The Mozilla support site does, to be fair, acknowledge that this plug-in in still in beta.
Adobe Reader: One Size Fits All? — In theory, Adobe Reader 10.1.3’s browser plug-in should provide a unified and consistent style of interaction with PDFs across all three popular browsers. Unfortunately, although the Adobe Reader plug-in works as advertised in Safari, it doesn’t work at all in Chrome, and may or may not work in Firefox.
Installing the Adobe Reader plug-in overrides Apple’s built-in PDF rendering in Safari, and also disables the capability to switch off inline PDF display in the Terminal. Fortunately, then, if you prefer Safari’s built-in PDF capabilities, removing the plug-in is a simple matter of deleting these two files (your admin password will be required):
Adobe Reader’s plug-in interacts with Chrome rather oddly. Chrome’s list of plug-ins shows that the Adobe Reader plug-in is available, but if you disable Chrome’s own PDF renderer, enable Adobe’s plug-in, and then attempt to view a PDF, your reward will be a black screen with a small message saying “Can’t load plug-in.” In short, the Adobe Reader plug-in simply does nothing for Chrome users.
And so we return to Firefox, which, in its usual quirky and unpredictable style, works well with the Adobe Reader plug-in, except when it doesn’t. In earlier versions of Firefox, including version 3, the Adobe Reader plug-in worked well. The combination of Firefox 12 and Adobe Reader 10.1.3, however, has a major flaw that causes Firefox to display nothing but a blank screen when you click a .pdf link. This bug, according to a blog post on Mozilla’s Web site, affects most users; as if that weren’t enough, it can also cause crashes in Macs running in 32-bit mode. In my testing, on a recent MacBook Pro running Mac OS X 10.7.3 Lion, I spent a lot of time
staring at blank pages, without managing a single successful PDF display or experiencing a single crash. Adam Engst, however, clearly has powers I do not possess; Firefox, he tells me, quite elegantly displayed inline PDFs on his 2008 Mac Pro running Mac OS X 10.6.8 Snow Leopard.
This odd level of compatibility is a shame, since while the Adobe Reader plug-in feels slower (particularly on load) than the built-in options in Safari and Chrome, it offers more capabilities. A click on the swirly-A logo in Adobe Reader’s floating toolbar reveals roughly the same controls as are in the full Adobe Reader application, with a sidebar showing page thumbnails, bookmarks, attachments, and search results. It’s easy to jump to specific pages, and you’re provided with precise zoom options, along with buttons to show the entire page and to zoom to the full width of the page (Chrome offers similar shortcut buttons). You can also rotate the document, view its document properties, and adjust page display options. A
right-hand sidebar provides access to tools for creating and converting PDFs, but those require a paid account with Adobe, and I was unable to get the signing and commenting tools also available in that sidebar to work.
In the end, the Adobe Reader plug-in is a somewhat odd beast — more capable than the built-in PDF renderers and Firefox’s PDF Viewer, but slower and a bit clumsy due to the way it tries to shoehorn all of Adobe Reader into a Web browser window. If you want those features, you may be best off simply downloading the PDF and working with it in the full Adobe Reader application.
Recommendations — Since PDF is intended to be a unifying technology, one which provides consistent layout behaviour across platforms, it’s ironic that there is so little consistency between browsers in their handling of online PDF files. Fortunately, this translates to choices and options for the user. But what choices to make?
For Chrome’s growing number of users, there is no choice — you’ll be using its built-in renderer, though that’s not a terrible thing. Firefox users, on a good day, have a little more choice — PDF Viewer, despite occasional performance issues, is a functional and useful PDF display tool. What PDF Viewer lacks in features, it makes up for by actually working, which remains the Achilles heel of the Adobe-Mozilla partnership, and so at the moment PDF Viewer has to be the PDF renderer of choice for Firefox users. Should Adobe correct this problem, a rethink might be in order, but at time of writing I cannot recommend Adobe Reader under Firefox.
Which brings us neatly back to Safari, definitely the most PDF-friendly browser of the three. Built-in support is strong, but the capability to select (albeit in an inelegant manner) between Apple’s and Adobe’s renderers is a bonus. For those who wish only to view the occasional PDF on the Web and move on, Safari’s built-in PDF renderer is fine, but for those who use PDF more frequently, Adobe Reader comes out ahead on features. This is hardly surprising given the extent to which Adobe Reader (and Acrobat Pro) have always offered far more comprehensive support than Mac OS X’s Preview for the format that Adobe itself created.
Now, if Adobe could just get the plug-in working in Chrome and Firefox, it might be possible to make a unified recommendation.
(Thanks to Roger Cohen for additional information for this article.)