SharePoint PDF opening in browser fix

PDF Opening like folder on SharePoint Document Library

SharePoint PDF Opening in Browser Fix Explained

SharePoint PDF opening in browser fix is required when PDF files open in the browser instead of downloading from SharePoint document libraries.

We recently had a client run into a bit of a strange issue with PDFs stored in SharePoint. Whenever they clicked on a PDF in a document library, instead of opening in the usual PDF viewer, it would behave as if it were opening directly in the browser – not what they were expecting. Oddly enough, when they clicked the three-dot menu (the ellipsis) and chose “Open in browser” or “Open in app”, everything worked just fine.

The Fix

According to Microsoft guidance on SharePoint file handling, SharePoint controls whether PDFs open in the browser or download based on library and file-handling settings.

After a bit of digging, what actually resolved the issue was turning off a setting in the document library:
“Allow people to access this document library in the browser without an internet connection.”

Once we disabled that setting, it didn’t fix the issue immediately – but after waiting for about an hour, things started working normally again.

Why This Might Happen

We can’t say for certain what was going on behind the scenes, but our theory is that it has something to do with how the browser and SharePoint handle offline caching. When the “access without an internet connection” option is enabled, it likely kicks in some additional JavaScript or service worker behaviour to manage offline functionality. That might interfere with how certain file types – like PDFs – are handled by default.

So if you’re seeing odd behaviour with file types in SharePoint, particularly around how they open, it’s worth checking if that offline access option is enabled. Disabling it could help clear things up – just don’t forget to give it some time to take effect.

If PDF behaviour issues persist across libraries, businesses can fix Microsoft 365 and SharePoint issues by correcting governance, permissions, and document settings.

Why SharePoint PDFs Open in the Browser by Default

SharePoint PDFs opening in browser is not a bug — it is a design choice intended to improve quick preview access. SharePoint uses browser-based viewers to allow users to read documents without downloading files locally, which helps reduce storage duplication and supports mobile and remote access. However, for many organisations, this behaviour disrupts workflows that rely on offline editing, secure file handling, or controlled document distribution.

When a SharePoint PDF opening in browser fix is required, it is usually because users expect files to download automatically for annotation, signing, or compliance reasons. Understanding that this behaviour is driven by document library settings and browser handling is critical before applying any fix.

Common Scenarios Where This Issue Becomes a Problem

A SharePoint PDF opening in browser fix is most commonly required in regulated industries such as construction, healthcare, legal, and finance. In these environments, staff often need to download PDFs for compliance records, offline review, or controlled sharing with third parties.

Other common scenarios include shared document libraries used by external collaborators, project teams accessing files through Microsoft Teams, or organisations migrating from legacy file servers to SharePoint Online. In each case, PDFs opening in the browser instead of downloading can cause confusion, version control issues, and user frustration.

Applying a proper SharePoint PDF opening in browser fix ensures consistency across libraries and aligns file behaviour with real operational needs rather than default platform behaviour.

Best Practices After Applying the Fix

Once a SharePoint PDF opening in browser fix has been applied, it’s important to test the behaviour across multiple browsers and devices. Some browser extensions and security policies can override SharePoint settings, causing PDFs to still open in-browser for certain users.

Administrators should also document the change as part of governance standards so future libraries inherit the correct behaviour. Regular reviews of document library settings help prevent the issue from resurfacing after updates or migrations.