Website Works in One Browser But Not Another
Short answer
Open the failing site in a Guest window of the same browser first. If it works there, the cause is an extension or that site's stored data in your profile, not browser compatibility. If it fails in Guest too, compare the two browsers' proxy, DNS and security settings — Edge and Chrome share an engine, so a genuine rendering difference between them is rare.
On this page
The page loads in Edge. In Chrome it hangs, shows a certificate warning, or renders with half its layout missing. The obvious conclusion is that Chrome has a problem with the site.
It almost never is. Chrome and Edge are both Chromium, so they have the same rendering engine, the same JavaScript engine and the same standards support. A page that genuinely renders differently between them is unusual enough to be worth reporting. Firefox and Safari do differ in real ways, but even there, the causes below explain far more cases than engine differences do.
What actually differs between two browsers on the same machine is everything around the engine: extensions, stored site data, proxy settings, certificate stores and DNS configuration.
Work through them in this order
Each test takes under a minute and rules out a whole category. Do not skip to the interesting one.
| Test | If the site works | If it still fails |
|---|---|---|
| Guest or Incognito window, same browser | Extension or site data | Not profile-related |
| A different device on the same Wi-Fi | Your machine | Your network or the site |
| Mobile data on your phone | Your network or DNS | The site itself |
| Site in a third browser | Narrow to one browser’s config | Genuinely broken site |
The first one alone resolves most cases, which is why “try another browser” is such common advice — it works, but it works for the wrong reason, and it leaves you using a browser you did not choose.
If a Guest window fixes it: your profile
A Guest window runs with no extensions, no cookies and no stored site data. If the site is fine there, one of those three is the cause.
Extensions first. Ad blockers, script blockers, privacy extensions and anything with a “tracking protection” feature regularly break sites that load functional code from a second domain. The symptoms are distinctive: a page that loads but has a dead button, an empty area where a map or video should be, or a checkout that spins forever.
Open chrome://extensions, turn off the usual suspects, reload. When you find
the culprit, most ad blockers let you whitelist one site from their toolbar icon
rather than disabling them entirely.
Then the site’s stored data. A corrupted service worker will happily serve a broken cached version of a site forever while a fresh profile gets the real one. Click the icon to the left of the address bar → Cookies and site data → Manage on-device site data → Delete. One domain, nothing else touched.
The broader question of which stored data costs what is covered in cache vs cookies vs browsing data, and it is worth knowing before you reach for the global clear button.
If Guest also fails: what differs between the browsers
Proxy and VPN
System proxy settings are shared between Chrome and Edge on Windows, but extension-based VPNs are not — they apply only to the browser holding the extension. So a browser VPN in Chrome and nothing in Edge means two different exit countries, and plenty of sites behave differently by region.
Check chrome://settings/system → Open your computer’s proxy settings to
confirm the system side, and chrome://extensions for anything VPN-shaped.
DNS
Chrome can use its own encrypted DNS resolver independently of the operating system, which means it can be resolving a domain differently from the browser next to it. Look at chrome://settings/security → Use secure DNS.
Turning it off temporarily is a legitimate test. If the site starts working, the secure DNS provider you selected has a stale or blocked record for that domain, and switching providers or reverting to your system resolver fixes it.
This matters more than people expect on corporate and school networks, where internal sites only resolve through the local DNS server and an encrypted resolver cannot see them at all.
Certificate warnings in one browser only
Chrome and Firefox maintain their own certificate trust stores; Edge and Safari lean on the operating system. A corporate network that inspects traffic installs its own root certificate, and if it landed in the Windows store but not Firefox’s, Firefox alone will complain.
A certificate warning is never something to click past casually, and what “your connection is not private” means covers which ones are safe to proceed through and which absolutely are not.
Hardware acceleration
If the problem is visual — flickering, black video, a canvas that renders as a grey box — the GPU path is the likely difference, because each browser makes its own decision about which driver features to trust.
Toggle Settings → System → Use graphics acceleration when available, restart
the browser fully, and retest. chrome://gpu shows what Chrome has blocklisted
on your driver.
When the site is genuinely at fault
Some sites really are broken outside one browser, and the shape is recognisable:
- A “please use Chrome” message on a site that then works fine when you ignore it. That is user-agent sniffing, not a real requirement.
- Banks, government portals and payroll systems that were built against one browser years ago and never retested. Depressingly common and not fixable from your side.
- Sites that need a plugin or a Java applet. No modern browser supports those, and a site still requiring one is not going to start working.
If a site fails in three browsers, in Guest mode, on your phone over mobile data and on a second machine, you have found a broken website. Keeping a second browser installed for one stubborn site is a reasonable accommodation. Switching your daily browser over it is not.
What switching browsers actually buys you
Less than the advice implies. Chrome, Edge, Brave, Opera and Vivaldi are all Chromium, so you are changing the interface and the default settings rather than the engine. Firefox is a genuine alternative engine and worth having installed for exactly that reason. Safari on macOS is the other.
But your extensions, your network, your DNS and your certificate store all follow you. A site that fails because an ad blocker ate its payment script will fail identically in the next browser once you install the same ad blocker there.
If the site works in a second browser, use it for that site and move on. That is a workaround, and it is fine to stop there.
What to expect
The Guest-window test resolves the majority of cases in under a minute, and the answer is usually an extension. Site data accounts for most of the rest.
Network-level causes — DNS, proxy, a corporate certificate — tend to affect several sites rather than one, and they are worth checking only once the profile side has been eliminated. If more than one device is failing on the same network, the problem moved out of the browser entirely and Wi-Fi connected but no internet on every device is the right starting point instead.