sodcalculator

10 Tech How-To

Chrome Compatibility Mode for Legacy Sites

Guide 10-16527 · Updated · Step by step

Chrome doesn’t have a dedicated “compatibility mode” button, but you can still make old, outdated websites work by using the built-in tools like the legacy browser emulation in DevTools and the built-in IE Mode in Microsoft Edge. This guide shows you how to force Chrome to render a site as if it were an older browser, fix layout breaks, and handle ActiveX or Java-based features that modern Chrome blocks.

What You’ll Need

  • Google Chrome (current version) on Windows, Mac, or Linux.
  • The URL of the legacy site you need to access.
  • For the most stubborn sites: Microsoft Edge (already installed on Windows) or a legacy browser like Internet Explorer 11 (only on Windows 10/11 with the IE11 desktop app).

Step-by-Step

  1. Try the built-in legacy emulation in Chrome DevTools. Press F12 or Ctrl+Shift+I (Windows/Linux) / Cmd+Option+I (Mac) to open DevTools. Click the Device Toolbar icon (a rectangle with a phone) in the top-left corner, or press Ctrl+Shift+M / Cmd+Shift+M.
  2. Select a legacy browser profile. In the Device Toolbar, click the dropdown that shows a device name (e.g., “Responsive”). Scroll down to the Emulated Devices section and pick an older browser like Internet Explorer 10, Internet Explorer 7, or Nexus 5 (which uses an older Chrome engine). This changes the user agent and screen size, which fixes many layout and JavaScript detection issues.
  3. Change the user agent manually (if needed). If the site still thinks you’re on a modern browser, click the three-dot menu in DevTools (top-right), go to More tools > Network conditions. Under User agent, uncheck “Select automatically” and paste a legacy user agent string, e.g., Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko for IE11. Then reload the page.
  4. Disable modern JavaScript features that break old sites. In DevTools, go to Settings (gear icon) > Preferences. Under Network, check Disable cache (while DevTools is open). Under Debugger, you can disable JavaScript entirely by pressing Ctrl+Shift+P and typing “Disable JavaScript” – but this is a last resort because most legacy sites need JS for forms.
  5. Use Edge’s IE Mode (the most reliable method). Open Microsoft Edge, go to edge://settings/defaultbrowser, and enable Allow sites to be reloaded in Internet Explorer mode. Then click the three-dot menu > Reload in Internet Explorer mode. This uses the actual IE11 engine, so ActiveX controls and old Java applets work. Edge is preinstalled on Windows 10/11, so you don’t need to install anything.
  6. For truly ancient sites (IE6-IE9), use a virtual machine or third-party emulator. Download a free Windows 10 virtual machine from Microsoft’s Edge developer page, or use a tool like IE Tab (a Chrome extension) which uses an embedded IE engine. However, these require a Windows license or additional software.

Common Mistakes

  • Forgetting to reload after changing the user agent. The new agent string only applies after a full page reload (Ctrl+F5).
  • Using the Device Toolbar for desktop sites. The Device Toolbar also changes the viewport size, which may cause a site designed for 1024px to look broken. Instead, use the Network conditions panel to change only the user agent.
  • Expecting Chrome to run ActiveX or Java applets. Chrome dropped support for NPAPI plugins (Java, Silverlight, ActiveX) years ago. No emulation will bring those back – you must use IE Mode in Edge or a real IE11.
  • Disabling JavaScript entirely. Many legacy sites use JS for basic form validation. Disabling JS will break them more.

Tips

  • Use the “Sensors” panel to emulate touch. If the legacy site expects a touch device, go to More tools > Sensors and set the touch type to “Emulate touch” – this can fix hover-only menus.
  • Keep a list of user agent strings. Save a text file with common ones (IE7, IE8, IE9, IE10, IE11, old Chrome, old Safari) so you can paste them quickly.
  • Use Edge’s IE Mode for internal corporate tools. If you’re accessing a company intranet that requires IE, ask your IT admin to add the site to the Enterprise Site List – then it will automatically open in IE Mode without manual reload.
  • Check the site’s console for errors. Press F12, go to the Console tab, and look for red errors. They often tell you exactly which feature is missing (e.g., “ActiveXObject is not defined”).

Troubleshooting

  • Site still shows a blank page. Clear the cache and cookies for that site (DevTools > Application > Clear storage). Then reload with the legacy user agent.
  • Site says “Browser not supported” even with a legacy user agent. Some sites check for specific JavaScript APIs, not just the user agent. Try Edge’s IE Mode – it’s the closest thing to a real legacy browser.
  • Forms don’t submit. Check the console for errors about XMLHttpRequest or fetch. If the site uses old AJAX calls, you may need to enable Allow insecure content in the site settings (click the lock icon next to the URL > Site settings > Insecure content > Allow).
  • Layout is broken but the site loads. The site might rely on CSS that Chrome no longer supports (e.g., -ms-filter). Use Edge’s IE Mode – it applies the IE11 rendering engine, which understands those old CSS hacks.
  • ActiveX control won’t load. This is a hard block in Chrome. You must use Edge’s IE Mode or a real IE11. There’s no workaround in Chrome itself.

Frequently Asked Questions

Q: Does Chrome have a built-in compatibility mode like IE?
A: No, Chrome doesn’t have a one-click compatibility button. But you can emulate older browsers via DevTools (user agent) or use Edge’s IE Mode, which is the recommended workaround.

Q: Will Chrome run Java applets?
A: No. Chrome dropped NPAPI plugin support in 2015. Java applets require a legacy browser like IE11 or a plugin wrapper like CheerpJ, which is a third-party solution.

Q: Can I use Chrome extensions to emulate IE?
A: Yes, there are extensions like IE Tab that embed an IE engine, but they often require a separate install or a paid subscription. Edge’s IE Mode is free and built-in.

Q: Why does the site look fine in Firefox but not Chrome?
A: Different browsers render CSS differently. If the site uses old vendor prefixes (-webkit-, -ms-), Firefox might handle them better. Try the user agent emulation first, then Edge’s IE Mode.

Q: Is there a way to make Chrome ignore certificate errors for legacy sites?
A: Yes, but it’s risky. You can click the “Advanced” button on the warning page and choose “Proceed to site” (not recommended for public sites). For internal sites, you can add the certificate to your trusted store, but that’s an IT decision.

Q: What if the legacy site requires a specific browser version, like IE6?
A: IE6 is only available in a virtual machine. Download a Windows XP VM with IE6 from Microsoft’s modern.ie site (now archived) or use a third-party service. The DevTools emulation only goes back to IE7.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →