Microsoft Edge DevTools provide access to experimental features that are still in development. This article lists and describes the experimental features that are in either:

• The latest version of the Canary preview channel of Microsoft Edge.
• The latest version of the Stable release of Microsoft Edge.

All channels of Microsoft Edge have experimental features. You can get the latest experimental features by using the Microsoft Edge Canary channel. To view the full list of experiments that are available in your version of Microsoft Edge, see the Settings > Experiments page in DevTools.

These experiments could be unstable or unreliable and may require you to restart DevTools.

The following experimental features are turned on by default. You can use these features right away, without changing any settings. You can turn off these default experimental features, if needed.

Turned on by default in Microsoft Edge Canary 129:

• Enable background page selector (for prerendering)
• Autofill panel
• Enable webhint
• Show issues in Elements
• Open source files in Visual Studio Code
• Enable speculative loads panel in Application panel

Turned on by default in Microsoft Edge Stable 128:

• Enable background page selector (for prerendering)
• Autofill panel
• Enable webhint
• Show issues in Elements
• Open source files in Visual Studio Code
• Enable speculative loads panel in Application panel

Experimental features are constantly being updated and might cause performance issues. This is one reason you might want to turn off an experiment.

To turn an experiment on or off in Microsoft Edge:

1. To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.

2. In DevTools, on the main toolbar, click the Customize and control DevTools () button, and then click the Settings () button. Or, press Shift+?.

3. On the left side of the Settings panel, select the Experiments page:

   

4. Select or clear the checkbox for an experiment. Some experiments are selected by default.

5. Click Close () in the upper right of DevTools Settings.

6. Click the Reload DevTools button.

To restore the default settings for which experimental features are turned on:

1. To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.

2. In DevTools, on the main toolbar, click the Settings () button. Or, press Shift+?. The Settings panel opens, with the Preferences page selected.

3. At the bottom of the Preferences page, click the Restore defaults and refresh button, and then click Close ().

You can filter the experimental features by text included in the title.

1. To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.

2. In DevTools, on the main toolbar, click the Settings () button. Or, press Shift+?. The Settings panel opens, with the Preferences page selected.

3. On the left side of the Settings panel, select the Experiments page.

4. Click in the Filter text box and enter text, such as timeline. As you type, only the matching checkboxes are shown in the Experiments page.

5. To end filtering, clear the Filter text box.

We're eager to hear your feedback about experimental features. To share feedback with us, Contact the Microsoft Edge DevTools team.

The experiments checkboxes that appear in the latest version of the Canary preview channel of Microsoft Edge are listed below. The Stable release is also noted, following behind the addition or removal of checkboxes in Canary.

Some Microsoft Edge Add-ons can define custom color themes for DevTools. If you install an add-on that defines a custom color theme for DevTools, you need to enable the Allow extensions to load custom stylesheets experiment to view the add-on themes.

See also:

• Apply a color theme to DevTools

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

To capture JavaScript stack traces when DOM nodes are added to the DOM at runtime, enable this experiment. This experiment adds the Stack Trace tab in the Elements tool, grouped with the Styles tab:

After you enable the experiment, you can test it as follows:

1. In a new window or tab, open a webpage that creates DOM nodes dynamically via JavaScript, such as the TODO demo app.
2. In the rendered demo page, create a new todo item.
3. In the rendered demo page, right-click the new todo item, and then select Inspect. DevTools opens, showing the Elements tool.
4. Click the Stack Trace tab, which is grouped with the Styles tab.

See also:

• Get started viewing and changing the DOM

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Makes the Protocol monitor tool available in DevTools:

The Protocol monitor tool displays the messages that are sent and received by DevTools, to debug the inspected page. DevTools communicates with the inspected page by using the Chrome DevTools Protocol (CDP).

To select this checkbox and then open the Protocol monitor tool:

1. Select this Protocol Monitor checkbox as described in Turning an experiment on or off, above.

2. In Quick View at the bottom of DevTools, click the More tools (+) button, and then select Protocol monitor.

   Or, open the Command Menu, such as by pressing Ctrl+Shift+P (Windows/Linux) or Command+Shift+P (macOS), and then type protocol in the text box. Then select Show Protocol monitor.

   The Protocol monitor tool is displayed in the Quick View panel at the bottom of DevTools.

See also:

• Use the Chrome DevTools Protocol (CDP) in WebView2 apps
• [Experimental] Protocol monitor in What's New In DevTools (Chrome 92).

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 105

Whether to display a checkbox to expose internals in heap snapshots in the Memory tool.

See also:

• Record heap snapshots using the Memory tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 122

Temporarily disables the indentation markers in the Sources tool. The indentation markers are the vertical lines that indicate the indentation level of the code:

See also:

• Sources tool overview

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

The Advanced Perceptual Contrast Algorithm (APCA) replaces the AA/AAA guidelines contrast ratio in the Color Picker. The Color Picker is used in the Styles tab in the Elements tool.

APCA is a new way to compute contrast. It is based on modern research on color perception. Compared to AA/AAA guidelines, APCA is more context-dependent. The contrast is calculated based on the following spatial properties of the text, color, and context.

• Spatial properties of text that include font weight and size.
• Spatial properties of color that include perceived contrast between text and background.
• Spatial properties of context that include ambient light, surroundings, and intended purpose.

See also:

• New color contrast calculation - Advanced Perceptual Contrast Algorithm (APCA) in What's New in DevTools (Microsoft Edge 89).
• Change colors with the Color Picker in CSS features reference.
• Test text-color contrast using the Color Picker

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Adds a Switch to Accessibility Tree view button in the Elements tool that toggles between the DOM tree and the accessibility tree. The button label toggles to Switch to DOM Tree view.

If this Experiment checkbox is cleared, the Elements tool lacks the button:

If this Experiment checkbox is selected, the Elements tool has the button:

The Accessibility Tree view in the Elements tool:

See also:

• Test accessibility using the Accessibility tab
• Full accessibility tree view in the Elements tool in What's New in DevTools (Microsoft Edge 90).

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

You can use the visual Font Editor to edit fonts. Use it define fonts and font characteristics. The visual Font Editor helps you do the following:

• Switch between units for different font properties
• Switch between keywords for different font properties
• Convert units
• Generate accurate CSS code

To use the visual Font Editor:

1. To open DevTools, right-click the webpage, and then select Inspect. Or, press Ctrl+Shift+I (Windows, Linux) or Command+Option+I (macOS). DevTools opens.

2. In DevTools, on the main toolbar, select the Elements tab. If the Elements tab isn't visible, click the More tabs () button, or else the More Tools () button.

3. In the Styles tab, select the Font Editor icon.

   

Some browser channels have the checkbox label Enable new Font Editor tool within the Styles pane.

See also:

• Edit CSS font styles and settings in the Styles pane

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Enables automatic contrast issue reporting in the Issues tool.

See also:

• Find and fix problems using the Issues tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Enables experimental cookie features.

See also:

• View, edit, and delete cookies

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Whether to sync CSS changes in the Styles tab in the Elements tool.

See also:

• Edit CSS font styles and settings in the Styles pane

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

This was a previous label of the checkbox. See the above section.

new as of Microsoft Edge 106

Highlights a violating node or attribute in the Elements tool's DOM tree.

See also:

• Inspect, edit, and debug HTML and CSS with the Elements tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 104

Controls whether to group resources into separate Authored and Deployed trees in the Page tab of the Sources tool. This feature in the Sources tool allows you to group source files in two folders depending on whether these are:

• Original source files (authored, that is, files with your local edits).
• Production files (deployed files that are on the web server after compiling and bundling the source files).

See also:

• Using the Page tab to explore resources that construct the current webpage in Sources tool overview.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 106

In the Sources tool's tree view, omits code that's included in the Ignore list.

See also:

• Add content scripts to the Ignore List
• Enhanced ignore listing
• Improved Ignore list setting

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 105

Selecting this checkbox causes important DOM properties to be highlighted in the Properties tab in tools such as the Elements tool, for the DOM tree element that's currently selected. This new experiment makes major properties easier to see. Some properties appear in bold, and others appear in bold and have a star icon next to them.

This highlighting is useful because in JavaScript, objects inherit from parent objects, which themselves inherit from other ancestors, sometimes amounting to hundreds of properties. This experiment helps you find the main properties.

The Object Properties viewer is in several tools, including Elements, Sources, Console, and Network. It provides a tree view of properties of objects.

To see the Object Properties viewer in the Elements tool:

1. Right-click an item in a webpage and then select Inspect. DevTools opens, with the page element selected in the DOM tree of the Elements tool.

2. In the Elements tool, select the Properties tab, which is grouped with the Styles tab.

   The Properties tab contains the list of properties for the selected element.

See also:

• Inspect, edit, and debug HTML and CSS with the Elements tool

To see the Object Properties viewer in the Sources tool:

1. Open a .js file.

2. Set a breakpoint on a line of code in the .js file.

3. Pause the debugger at that line by running the code on the webpage.

   Object properties are displayed in the Scope section in the right-hand sidebar. See View and edit properties and variables in JavaScript debugging features.

See also:

• Sources tool overview

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 114, new label for checkbox as of Microsoft Edge 128

Enables the background page selector, such as for prerendering debugging.

See also:

• Overview and timelines for migrating to Manifest V3 - service workers instead of background pages, for Microsoft Edge extensions.
• chrome.runtime - retrieves the background page.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 120

In the Network tool, the filter bar has been redesigned:

• The buttons are replaced by a Request types dropdown list.
• The checkboxes are replaced by a More filters dropdown list.

Filter bar with this checkbox cleared:

Filter bar with this checkbox selected:

See also:

• Filter resources in Inspect network activity.
• Filter requests in Network features reference.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 125

Adds an Autofill tool to DevTools, to record various events that the browser triggers when a user is filling in a form by using the browser's autofill feature. For example, when the browser remembers your address and autofills it in an address field.

See also:

• Autofill in Microsoft Edge Privacy Whitepaper.
• Autofill in Overview of WebView2 features and APIs.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 123, as Enable Autofill view.

new as of Microsoft Edge 124

This experiment improves the Performance tool's Main section to help you quickly identify postMessage events and handlers, by distinguishing events that are triggered by the postMessage method from other events that are displayed in the Performance tool. This experiment helps you investigate performance issues that are related to posting messages across various threads of an application, to view messages between windows, iframes, and dedicated workers.

Without this experiment, events that are triggered by dispatching and handling messages between threads of an application appear as generic scripting function-call events. With this experiment enabled:

• postMessage dispatch events appear as Schedule postMessage.
• postMessage handler events appear as On Message:

This experiment helps you investigate when a postMessage call occurred, and how long the message was queued before the postMessage handler starts. The dispatch events are linked to handler events by initiator arrows that appear when you click on either type of event:

See also:

• View messages between windows, iframes, and dedicated workers in Performance features reference.
• Performance recording event reference
• postMessage Trace Events demo (rendered)
• postMessage Trace Events demo (source code)
• postMessage events and handlers are distinguished from other events in What's New in DevTools (Microsoft Edge 124).

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 127

In the Performance tool, adds a landing page that's displayed when no performance traces have been recorded yet. The landing page displays performance metrics about the rendered page that are updated live, such as:

• Largest Contentful Paint (LCP)
• Cumulative Layout Shift (CLS)
• Interaction to Next Paint (INP)

See also:

• Introduction to the Performance tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

This is the older label for the checkbox. See the above section.

Controls whether to log DevTools uncaught exceptions in the Console tool.

See also:

• Console overview

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

webhint is an open-source tool that provides real-time feedback for websites and local webpages. The type of feedback provided by webhint includes:

• Accessibility
• Cross-browser compatibility
• Security
• Performance
• Progressive Web Apps (PWAs)
• Other common web development issues

The webhint experiment displays webhint feedback in the Issues tool. Select an issue to display documentation about the solution and a list of the affected resources on your website. Select a resource link to open the relevant tool, such as Network, Sources, or Elements:

See also:

• Find and fix problems using the Issues tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Displays syntax errors as wavy underlines under DOM nodes in the Elements tool.

See also:

• Wavy underlines highlight code issues and improvements in Elements tool in What's New in DevTools (Microsoft Edge 91).

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

The Open source files in Visual Studio Code experiment replaces the code editor of the Sources tool with Visual Studio Code, for editing local files. When you turn on this experiment, Developer Tools detects when you edit a local file, and prompts you to select a folder to use as your Workspace.

When you select a folder to use as your Workspace, selecting any link to a file in DevTools opens the file in Visual Studio Code. In previous versions of Microsoft Edge, this action opened the file in the code editor of the Sources tool in DevTools.

Any edits that you make in DevTools now change the file on the hard drive and sync live with Visual Studio Code.

See also:

• Opening source files in Visual Studio Code - setting up your workspace.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 114

Enables Adaptive CPU throttling.

See also:

• Throttle the CPU while recording in Performance features reference.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Enables using Copilot in the Microsoft Edge Sidebar to explain HTML elements and CSS styles to help you better understand a particular element or style rule that's displayed in the Elements tool. To ask Copilot about an element or style rule, click the Copilot button next to it, and then ask follow-up questions.

This experiment is not available when the Sidebar is turned off.

See also:

• Inspect, edit, and debug HTML and CSS with the Elements tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Controls whether to live-update the heap profile.

See also:

• Record heap snapshots using the Memory tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Controls whether to show the sampling heap profiler timeline in the Performance tool.

See also:

• Introduction to the Performance tool
• Record heap snapshots using the Memory tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Adds an Invalidations section for Recalculate Style events in the Summary tab of the Performance tool. The Invalidations section provides information about the root cause for a Recalculate Style event, which might be helpful when investigating long-running Recalculate Style events that are causing performance issues.

The Invalidations section lists the DOM nodes that were invalidated as a result of a change on the webpage, such as a DOM mutation, and which the browser engine had to restyle during the Recalculate Style event.

See also:

• Introduction to the Performance tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Controls whether to show all events in the Performance tool.

See also:

• Introduction to the Performance tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

Controls whether to show V8 runtime call statistics in the Performance tool. V8 is the JavaScript engine that's used by Microsoft Edge.

See also:

• Introduction to the Performance tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 128

This experiment makes the Performance tool capture newly added traces, to support enhanced traces v2. This feature is being implemented in the upstream Chromium project. This experiment doesn't affect the capabilities of Microsoft Edge to capture enhanced traces and doesn't impact DevTools user's experience.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

See also:

• Share enhanced performance and memory traces
• Performance features reference
• Performance recording event reference

new as of Microsoft Edge 128

In the Performance tool, when exporting the trace file, stores the source code of compiled scripts in the trace file.

This experiment makes the Performance tool record script source text in traces. This feature is being implemented in the upstream Chromium project.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

See also:

• Share enhanced performance and memory traces
• Performance features reference
• Performance recording event reference

new as of Microsoft Edge 128

Adds a Trace Event section to the Summary tab of the Performance tool. The Trace Event section is displayed when you select an event in a recorded performance trace. The Trace Event section displays debugging information about the selected trace event, such as its name and duration.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

See also:

• Share enhanced performance and memory traces
• Performance features reference
• Performance recording event reference

Whether to halt at test breakpoints. This experiment makes breakpoints more reliable.

See also:

• Enable synchronization on instrumentation breakpoints
• The first time source files are loaded, breakpoints might not trigger

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 118

Whether to use scope information from source maps.

See also:

• Map the processed code to your original source code, for debugging
• Mapping minified code to your source code to show readable code in Sources tool overview.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 121

Adds a Speculative loads page within the Background services section of the Application tool, including a Rules page and a Speculations page:

The Speculation Rules API can be used to programmatically tell Microsoft Edge to pre-render certain pages. This is useful because pre-rendered pages are almost instantaneous to navigate to. The browser pre-renders, in a hidden way, the next pages that a user is likely to navigate to, while the user is still on the current page.

The Speculative loads page lists the speculation rules that the web author has defined in the webpage. The page provides debugging information that shows whether a rule was actually used, showing whether a particular page was pre-rendered.

The Rules page has columns:

• Rule set
• Status

The Speculations page has columns:

• URL
• Action
• Rule set
• Status

See also:

• Application tool, to manage storage

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge Canary 129

Enables annotations in the Performance tool.

See also:

• Introduction to the Performance tool

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

new as of Microsoft Edge 128

Enables the sidebar in the Performance tool.

Status:

• This checkbox is present in Microsoft Edge Canary 129.
• This checkbox is present in Microsoft Edge Stable 128.

This is an older label for the checkbox. See the above section.

Experimental work in progress (WIP).