The following post is an update from the original ‘SharePoint 2007 and Adobe PDF‘ post written in 2007. These notes are based on SharePoint 2010 Beta 2 (made publicly available in November 2009). Once the product has officially launched on 12 May 2010, an update will be posted if any changes are made to the process. The process is very similar to SharePoint 2007, with minor changes to folder location (14 instead of 12) and a slightly different administration user interface in the browser.
SharePoint Server 2010, like its predecessors, includes indexing and search capabilities. But what doesn’t come out of the box is the ability to index and search for PDF documents. PDF is a format owned by Adobe, not Microsoft. If you want to be able to find Adobe PDF documents, or have the PDF icon appear when viewing PDF files in a SharePoint document library (see image above), you will need to set it up for yourself. This post describes how to.
- Download and install Adobe’s 64-bit PDF iFilter*1 – http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
- Download the Adobe PDF icon (select Small 17 x 17) – http://www.adobe.com/misc/linking.html
- Give the icon a name or accept the default: ‘pdficon_small.gif’
- Save the icon (or copy to) C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES
- Edit the DOCICON.XML file to include the PDF icon
- In Windows Explorer, navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML
- Edit the DOCICON.XML file (I open it in NotePad, you can also use the built-in XML Editor)
- Ignore the section <ByProgID> and scroll down to the <ByExtension> section of the file
- Within the <ByExtension> section, insert <Mapping Key=”pdf” Value=”pdficon_small.gif” /> attribute. The easiest way is to copy an existing one – I usually just copy the line that starts <Mapping Key=”png”… and replace the parameters for Key and Value (see image below)
- Save and close the file

- Add PDF to the list of supported file types within SharePoint
- In the web browser, open SharePoint Central Administration
- Under Application Management, click on Manage service applications
- Scroll down the list of service apps and click on Search Service Application
- Within the Search Administration dashboard, in the sidebar on the left, click File Types
- Click ‘New File Type’ and enter PDF in the File extension box. Click OK
- Scroll down the list of file types and check that PDF is now listed and displaying the pdf icon.
- Close the web browser
- Stop and restart Internet Information Server (IIS)*2 Note: this will temporarily take SharePoint offline. Open a command line (Start – Run – enter ‘cmd’) and type ‘iisreset’
- Perform a full crawl of your index. Note: An incremental crawl is not sufficient when you have added a new file type. SharePoint only indexes file names with the extensions listed under File Types and ignores everything else. When you add a new file type, you then have to perform a full crawl to forcibly identify all files with the now relevant file extension.
That’s it. If you now perform a search, PDF files should be displayed in results where they match the search query, along with the PDF icon on display in results. The icon should also be visible in any document libraries that contain PDF files.
* Additional Notes:
- At time of writing, Adobe has published PDF iFilter 9 for 64-bit applications, tested on SharePoint 2007 but not yet listed as tested on SharePoint 2010. So far, it is working fine on my builds of SharePoint 2010 (Beta versions)
- When setting this up, I initially just restarted the search service rather than IIS but found myself locked out of SharePoint. Resetting IIS fixed it. I don’t know for certain if you also need to restart the search service. Will test on the next build and update here.
- As with SharePoint 2007, there are alternative PDF ifilters. The most well known is Foxit Pro – http://www.foxitsoftware.com/. Rumoured to perform indexing faster than using Adobe’s iFilter. I can’t comment, I haven’t tested it. Given PDFs don’t change (they are usually PDFs specifically to not be edited) they are only indexed when first uploaded or when you perform a full crawl. Most organisations should primarily be performing incremental crawls – updating the index with content that has been added or changed rather than re-indexing everything




[...] This post was mentioned on Twitter by Joining Dots, Edwin Bastings. Edwin Bastings said: SharePoint 2010 en Adobe PDF http://bit.ly/9G4c8u Hoe PDF files te indexeren dmv iFilter in #SP2010 [...]
When uploading Microsoft document to a document library existing document properties are extracted to corresponding library columns. Is there a way to extract PDF properties to corresponding library columns?
Unfortunately not. The standard properties are indexed by SharePoint, such as author, title, date modified etc. so they will be visible in the search results (including the extracted metadata for refining search results) but they are not automatically promoted into SharePoint columns within the libraries.
Hi All,
I have published an article at http://www.mossgurus.com/adnan/default.aspx explaining How to Install and configure PDF iFilter (64 bit) for SharePoint Server 2010 or Search Server 2010 Express with screen shots of each important steps.
I do hope that you will find this article useful. Please leave your comments.
Thanks
Adnan Ahmed
Senior MS Solutions Consultant
Owner: http://www.mossgurus.com
Do you need to install the PDF iFilter on the database server or the sharepoint application server? That was not noted in the instructions…. Thanks.
Do I have to install the filter on every front server in my farm or only the server hosting Central Admin and or search service?
Hi Dustin and Wendy
The iFilter needs to be installed on the indexing/search servers. You shouldn’t need to install on the database server or the front-ends.
Cheers and best regards
Sharon.
Don’t forget to ensure that the right registry key is set as per Adnan’s instructions, as Adobe’s iFilter doesn’t know to register itself against the SP2010 search service.
Hi Craig, I’ve never needed to set that registry key to get PDF indexing to work. It’s included on Adobe’s own instructions but they don’t configure within the UI which I have assumed is the alternative. Useful to know for reference if someone has problems getting indexing to work as maybe it’s the cause in some set-ups.
hi,
in my production moss 2007 site, pdf documents are not overwriting, just showing pdf documents with out the update
is that an issue with moss2007
In my case until I’ve made suggested registry changes I was getting errors in the crawl log (The filtering process could not load the item) and PDF files content was not searchable.
Hi Thomas
Not sure I follow your comment. PDF docs are normally read-only and not updated so you wouldn’t be able to overwrite them. If you are running full Adobe Acrobat and making changes to the documents, you’d need to re-index (incremental crawl) to pick up the changes and see the changes in search results although the changes would be visible if you navigate direct to the docs.
Hi Leonid
Thanks for the feedback, seems the registry changes are required in some instances. Out of curiosity – what is your environment. Is it a single server or multi-server farm?
Am also thinking if you’ve installed the Reader that probably does the registry changes for you, but if you just install the iFilter you’ll need to do the extra config…
One note on adding the PDF icon to the DOCICON.XML. if you do not want the “read only / edit” dialog box to popup everytime for PDF files you need to add the attribute opencontrol=””
IS there a way to display a PDF file within a webpart or seomthing similar? I don’t want to allow people to download the actual PDF file itself, but want to display it’s content.
Hi Robert – curious, never heard of that one before.
Dave – view without download is always a tricky one in that there is always the work around if the file is cached in memory for viewing (and the good old analogue hack of screen scraping… Is there a reason why you don’t want the file to be downloaded? (Wondering if there’s an alternative solution that may work better)…
@Sharon – I am seconding Dave’s request. We want to be able to open the PDF in a webpage, similar to how PDF open on many non-SharePoint sites. If there anyway that you know of doing this?
The adobe installer doesn’t add these registry changes automatically. I have a single server/farm SP 2010 environment.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\Filters\.pdf]
“Extension”=”pdf”
“FileTypeBucket”=dword:00000001
“MimeTypes”=”application/pdf”
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf]
@=”{E8978DA6-047F-4E3D-9C78-CDBE46041603}”
Hi Aaron and Dave
I’ve create a blog post walking through a simple method to embed PDFs inside a web part. Hope that’s what you were after http://www.sharepointsharon.com/2010/08/embedding-pdfs/
Dave – technically it still doesn’t stop downloads because a) the file is downloaded into cache for viewing and b) the standard Adobe control includes the option to print and save locally. It’s a client-side control. The only way to prevent is to use a server control stream through Adobe Flash Player.
@Sharon – thanks for the how-to. What I am getting after is the ability to click on a PDF file in a document library and have that PDF displayed in the same browser window. The default behavior is to prompt you to save the file.
I found the fix – change “Browser File Handling” to “Permissive”.