Why is my PDF opening in Chrome instead of Adobe Reader?

Because Chrome is registered as the default handler for .pdf files on your computer, which happens quietly during a Chrome install or a Windows update. The file is not associated with Chrome in any permanent way, so nothing about the PDF itself needs changing. You reassign the file type in your operating system settings and every PDF opens where you want from then on.

What does it mean when a file downloads as a Chrome PDF?

It usually means the saved file shows the Chrome icon in your downloads folder, which is a file-association display rather than a different file format. The bytes on disk are an ordinary PDF and any reader can open them. Changing the default handler makes the icon and the double-click behaviour follow the app you actually want.

How do I stop Chrome opening PDFs in a tab when I click a link?

That behaviour is controlled inside Chrome rather than by your operating system, which is why changing the Windows or Mac default does not affect it. Chrome keeps a PDF documents setting under Site settings with a choice between opening PDFs in Chrome and downloading them. Switching it to download sends the file to your downloads folder instead of rendering it in a tab.

Is Chrome's built-in PDF viewer bad?

It is a good reader and a limited editor, which is the distinction that matters here. It renders and prints reliably and handles most files faster than a heavy desktop application. What it does not do is let you sign, annotate, fill and flatten, or reorganise pages, and that gap is usually the real reason someone goes looking for this setting.

Do I need to install software just to sign or fill a PDF?

No, and this is worth knowing before you go hunting for a desktop installer. Signing, filling forms and annotating all run inside a browser tab now, without an account and without uploading the file anywhere. Changing your default app is still worth doing if you prefer a desktop reader, but it is not a prerequisite for getting work done on the document.

My PDF opens blank in Chrome but fine in Adobe Reader. Why?

That is a different problem from a default-app problem, and the usual cause is a dynamic XFA form. XFA documents describe fields and scripts rather than a drawn page, and browsers do not implement the format, so they display a placeholder instead of the form. In that specific case a desktop Adobe reader is the only thing that will work and no browser setting helps.

Will changing the default PDF app affect files already downloaded?

Yes, because the association is by file type rather than by individual file. Once .pdf points at your chosen application, every PDF already sitting in your downloads folder opens with it on the next double-click. On a Mac you have to use the Change All button rather than just picking an app, or the change applies to that one file only.

Does the default PDF app change how PDFs open on my phone?

No. Default handlers are per-device, so a change on your laptop has no effect on an Android phone or an iPhone. Mobile platforms have their own defaults, set through the share sheet on iOS or the default apps screen on Android, and they need changing separately if the same annoyance follows you across devices.

Why Is My PDF Opening in Chrome? Change the Default

Why is my PDF opening in Chrome? Almost always because Chrome claimed the .pdf file type on your computer, usually during an install or an update, and nobody asked you first. Nothing is wrong with the file. The association is a line in your operating system’s settings and you can move it in about forty seconds.

The complication is that two different settings produce symptoms people describe the same way, and fixing one does nothing for the other. Working out which one you have takes a single question.

Two different settings, often confused

Ask yourself where the PDF was when it annoyed you.

You clicked a link on a website and it rendered in a tab. That is Chrome’s own behaviour, decided by a setting inside Chrome. Your operating system was never consulted. Go to Fix A.
You double-clicked a file already saved on your computer and Chrome launched. That is the operating system’s file association. Chrome is simply the registered handler. Go to Fix B.

This is why so much advice on this topic fails. Someone changes the Windows default, clicks a link the next day, watches it open in a tab anyway, and concludes the fix did not work. Both settings exist and both may need changing.

Fix A: stop Chrome rendering PDFs in a tab

Chrome keeps a dedicated PDF setting with two states: render the file in a tab, or download it and leave it alone. The path is:

Open Chrome’s menu and choose Settings.
Select Privacy and security, then Site settings.
Scroll to the bottom and expand Additional content settings.
Choose PDF documents.
Under Default behavior, switch from Open PDFs in Chrome to Download PDFs.

From then on, clicking a PDF link saves the file to your downloads folder rather than rendering it. What happens when you then open that file is decided by Fix B, which is the part people miss.

Fix B: change the default app on Windows 11

Open Settings, go to Apps, and select Default apps.
Type .pdf in the search box and click the app currently listed beside it.
Pick the application you want, then confirm the change.

Windows may show a prompt trying to keep you on Edge before it accepts the change. Clicking through it is expected and nothing is at risk.

Fix B: change the default app on macOS

Select any PDF in Finder.
Press Command + I, or choose File → Get Info.
Expand the Open with section and pick your application.
Click Change All, then confirm.

Change All is the step people skip

Selecting an app in the Open with dropdown changes that one file. Without clicking Change All, every other PDF on the Mac keeps opening in Chrome, and it looks like the fix silently failed.

Edge and Firefox have the same setting

Chrome gets blamed for this most often because it has the largest share, but every major browser ships its own PDF viewer and its own switch for turning it off. If you moved your default away from Chrome and landed on another browser, you have moved the problem rather than solved it.

In Edge the equivalent lives under Settings, then Cookies and site permissions, then PDF documents, with a toggle for always downloading PDF files instead of opening them. In Firefox it sits in Settings under General, in the Applications list, where the row for Portable Document Format lets you switch from previewing in Firefox to opening in another application or saving the file.

The pattern is the same in all three: a viewer-versus-download choice inside the browser, and a separate file association in the operating system. Knowing that saves you hunting through the wrong menu.

Check the change actually took effect

Both fixes fail quietly in ways that look identical to not having changed anything, so it is worth thirty seconds to confirm. Test each path separately, because they are separate settings:

Test the operating system association. Find any PDF already on disk and double-click it. Your chosen application should open. If Chrome still launches, the association did not stick, and on a Mac the usual cause is having skipped Change All.
Test the browser behaviour. Click a PDF link on any website. It should land in your downloads folder rather than rendering in a tab. If it still renders, the Chrome setting was not saved, or you changed it in a different browser profile than the one you are using.
Check your profile if step two keeps failing. Chrome stores site settings per profile. Changing the setting while signed into a work profile does nothing to your personal one, and the two look nearly identical apart from the avatar in the corner.

The reason people actually look this up

Very few people care which application renders a PDF. They care because they tried to do something to the document and the tab would not let them. Chrome’s viewer displays and prints well and opens faster than most desktop readers. It is not built for changing a document.

If that is your situation, changing the default app is a detour. The things people usually want run in a browser tab already, without an install and without the file leaving the machine:

Sign a PDF by drawing a signature on a canvas and placing it on the page.
Fill a PDF form where the document has real form fields.
Annotate a PDF with highlights and notes.
Compress a PDF when a portal rejects it for being too large.

None of these needs the default handler changed at all, because you open them yourself rather than double-clicking a file. Change the default if you prefer a desktop reader for reading. Do not change it under the impression that it unlocks editing, because it does not.

When a desktop reader is the only option

There is one case where a desktop Adobe reader is not a preference but the only thing that works, and it is worth knowing so you stop fighting the wrong setting.

Dynamic XFA forms describe fields and scripts rather than a drawn page. Browsers do not implement the format, so instead of the form you get an empty page or a message asking you to wait. Many Indian government and tax forms are built this way. No default-app change and no browser tool fixes it, because there is nothing to render until software that understands XFA builds the page.

If a PDF is blank in Chrome and complete for a colleague on Acrobat, that is the shape you are looking at, and it is a different problem from the one this page solves.

Why this runs in your browser

The documents that push people into this settings hunt tend to be the ones that matter: a contract that needs signing today, a form due at a portal, a statement going to an accountant. Sending one to an anonymous converter to avoid installing software is a poor trade.

The tools linked here process files inside your own browser tab. The PDF is read by JavaScript on your device, the work happens in local memory, and the result lands in your downloads folder. Nothing is uploaded, so there is no server copy to leak or to forget about.