How to Use Chrome Compatibility Mode

Chrome does not have a general compatibility mode that makes it render pages with Internet Explorer’s engine. Changing Chrome’s user-agent string can help test how a site responds to a browser identity, but it does not add Internet Explorer’s rendering behavior or legacy components. In a managed Windows organization, Chrome Enterprise Legacy Browser Support (LBS) can route selected URLs to another browser. For sites that require IE compatibility, Google’s documented setup uses Microsoft Edge in IE mode together with LBS.

If you are trying to open one old site on a personal computer, use the browser the site supports or contact its owner or administrator. LBS is an administrator-managed feature, not a consumer switch in Chrome settings.

1. Choose the approach that fits

Your need	Use	Limit
Open a legacy internal site on managed Windows devices	Chrome Enterprise integrated LBS, configured by an administrator	Requires managed policy and URL or site-list configuration.
Use a site that specifically depends on IE compatibility	Edge IE mode, with Chrome LBS routing the relevant URL	Configure and validate both browsers’ policies and matching site lists.
Test whether a site behaves differently based on browser identity	A user-agent switcher or developer testing method	Changes the user-agent string only; it does not reproduce another browser’s engine.
Visit an old site from a personal computer	Ask the site owner which browser is supported	There is no general Chrome setting that enables IE mode.

Google documents integrated LBS for Chrome 74 and later on Windows. Its specific Edge IE-mode LBS instructions list Edge 87 or later and Chrome 87 or later. The older LBS extension is obsolete: Chrome 88 and later support integrated LBS rather than installing that extension. Check Google’s current instructions before deployment because version requirements can change. Google: Set up integrated LBS for Windows; Google: Set up LBS for Microsoft Edge in IE mode; Google: Migrate from the LBS extension.

2. Test browser identity with a user-agent switcher

Use this method when you need to check whether a site serves different content based on the user-agent string. It is not a way to run the site in Internet Explorer.

In Chrome, install a user-agent switching extension from the Chrome Web Store, following your organization’s extension policy.
Open the extension and select the browser or device identity you want to test, or enter a custom user-agent string if the tool supports it.
Reload the page and inspect its response and behavior. Test the relevant page flows, not just the landing page.
Restore the normal Chrome user-agent after testing. If sites continue to treat the browser unexpectedly, Google suggests switching back to Chrome and clearing cookies.

Google notes that this kind of extension intercepts and modifies data communicated to the server, which can affect performance. User-agent spoofing does not improve privacy, and a site may identify the browser through other means. Google’s user-agent testing guidance.

What this test does and does not tell you

It can help test: server responses or site branches that depend on the user-agent string.
It does not test: another browser’s rendering engine, its built-in APIs, its security behavior, or legacy components such as ActiveX.
For actual compatibility: run the site in the browser environment it requires. If the application requires IE compatibility, test it in the configured alternate browser, such as Edge IE mode.

3. Configure Chrome LBS with Edge IE mode

This section is for administrators managing Chrome on Windows in a business or school. LBS routes selected URLs to an alternative browser; it does not transform Chrome into that browser. Google’s Edge IE-mode instructions require the two browsers to use the intended shared site list so that sites opened in Edge use IE mode.

Confirm requirements and scope. Check the Chrome and Edge versions against Google’s current instructions. Start with a test group and only the URLs that need legacy handling.
Use integrated LBS. Chrome 74 and later include integrated LBS functionality. For Chrome 88 and later, do not deploy the retired LBS extension; use integrated LBS.
Enable LBS and choose Edge. In the Chrome Admin console or Windows Group Policy, enable Legacy Browser Support and set the alternative browser path to ${edge}, following Google’s setup instructions.
Configure Edge for IE mode. Apply the Edge policies for IE integration and select Internet Explorer mode. Google’s setup also describes installing the Legacy Browser Support for IE Mode in Edge extension through policy.
Configure the site list. Use an IE/Edge enterprise site list or a shared XML site-list URL. Configure Chrome LBS and Edge to refer to the intended list. Add only the sites that need the alternate browser.
Apply and verify policies. Check chrome://policy and edge://policy. If Group Policy settings are missing, Google suggests running gpupdate /force.
Check URL routing before rollout. In Chrome, open chrome://browser-switch/internals. Enter a URL in URL Checker and inspect the Sitelist and Greylist sections. In Edge, use edge://compat to inspect IE-mode compatibility details.
Expand gradually. Test actual application workflows with the users and sites in scope, then broaden deployment if routing and behavior are correct.

Google documents two site-list paths: use the Internet Explorer site-list policy, or provide an XML site-list URL. Follow the detailed policy names and configuration steps in Google’s Edge IE-mode LBS setup and integrated LBS setup. Policy names and controls may vary with management method and product updates, so use the current administrator documentation rather than relying on a copied configuration.

4. Troubleshooting

Symptom	Likely cause	What to check or do
An old site still fails after changing Chrome’s user-agent	The site requires a different rendering engine or legacy technology, not just a browser identity string.	Use the site’s supported browser. For a managed organization, test the application in the configured alternate browser and, where required, Edge IE mode.
A managed URL opens in Chrome instead of Edge	LBS policy, URL rules, or site-list configuration does not match the URL; a greylist rule may allow either browser.	Check `chrome://policy`, then use `chrome://browser-switch/internals` URL Checker, Sitelist, and Greylist to inspect the decision and rules.
The URL opens in Edge, but the application is not in IE mode	Edge IE integration may not be enabled, or the Edge and Chrome configurations may not refer to the intended shared site list.	Verify Edge policies at `edge://policy`, inspect compatibility information at `edge://compat`, and confirm both configurations use the intended list.
The expected policy is missing or has not taken effect	The policy may not have applied to that user or device yet, or Group Policy may need refreshing.	Inspect `chrome://policy` or `edge://policy`; for Group Policy, run `gpupdate /force` and recheck.
The old LBS extension will not install or stops working	The extension is retired for current Chrome versions.	Use integrated LBS. Google says Chrome 88 and later support integrated LBS rather than installing the extension.
A site behaves oddly after user-agent testing	The site may have cached cookies or other browser-identification logic; the extension may also affect requests.	Switch back to Chrome’s user-agent and clear cookies. Test with the site’s actual supported browser if behavior depends on more than the user-agent.
An application using ActiveX, Java, or Silverlight does not work	Changing the user-agent does not supply legacy browser components.	Test the application in the supported alternate browser and follow the organization’s compatibility configuration.

5. Reliability, performance, and rollout notes

Route narrowly. Apply URL rules only to sites that need the alternate browser, then test the URL decision before broad rollout. This keeps routing easier to inspect and troubleshoot.
Validate both sides. Chrome can route a site to Edge, but Edge must also be configured for IE mode and the appropriate site list. Confirm the actual application flow in the target environment.
Prefer current integrated support. Google advises using the latest Chrome release for integrated LBS. Do not rely on the retired LBS extension for current Chrome deployments.
Account for user-agent testing overhead. A user-agent extension can affect performance because it intercepts and modifies communicated data. It does not provide privacy protection.
Do not infer compatibility from a label. A page loading after user-agent spoofing does not establish that its features work in another browser. Test forms, authentication, downloads, and the workflows the application actually uses.
No special screenshot cost model applies to browser compatibility mode. Chrome LBS and user-agent testing are browser configuration/testing approaches; the cited Google guidance provides no cost or performance benchmark for them.

6. Capture a browser result for review

If you need to save a rendered page for a bug report or review, capture it from the browser and environment you are testing. A screenshot records the visible result; it does not establish that the page used IE’s engine or that every application workflow works.

Or skip the browser setup

For a rendered website capture, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. It can return PNG, JPEG, WebP, or PDF from a GET request. It does not enable Chrome compatibility mode or replace testing in the required browser. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

With the Python and Node.js examples, check the response status before treating the body as an image; save the response using the file-writing method supported by your runtime. Replace the example target URL with the page you want to capture. ScreenshotNeo accepts cookie banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and responses include X-Page-Verdict and X-Billed headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000. Sign up free for 1,000 screenshots a month, with no card required.

7. FAQ

Does Chrome have an Internet Explorer mode?

No. Chrome does not have a general built-in mode that uses Internet Explorer’s rendering engine. Managed organizations can route selected URLs to another browser with LBS.

Can I make Chrome act like Internet Explorer with a user-agent extension?

You can change the user-agent string for testing, but this does not make Chrome render like IE or provide IE-specific components.

Can I turn on LBS on my personal computer?

Google documents LBS as an administrator-managed feature for managed Chrome environments. For a personal device, use the browser supported by the site or ask its owner for help.

Does taking a screenshot prove the site works in compatibility mode?

No. A screenshot shows a rendered page. Validate the application in the browser and mode it requires.