You can now get AI-generated type-ahead suggestions in the Console and Sources panels.

To enable this feature, go to Settings > AI Innovations and toggle Code suggestions.

Important: This feature is rolled out over time and may not be available for you yet. Restrictions based on age, location, and language may apply. To learn more, see AI assistance requirements.

Enhancements for the Dev Tools MCP server

Since launching the public preview of the DevTools MCP server with v0.2.1, we landed various improvements with contributions from the community and released v0.9.0.

• Node.js support has been extended down to Node.js 20.
• Network requests and console messages can be paginated to save tokens and filtered based on request type (for example, scripts, stylesheets, images) and message type (log, warning, error).
• Screenshots can be output to a specific path and in various formats.
• Configurable tool categories let you organize which capabilities are exposed, reducing unnecessary noise.
• You can now pass launch arguments to the Chrome instance used by the MCP server.
  See the public changelog on GitHub for the full list of changes and bug fixes, and learn more about the DevTools MCP server in the announcement blog post.

Quicker access to AI assistance

DevTools now includes more links that open AI assistance. The Ask AI context menu item has been renamed to Debug with AI and amended with direct actions AI can help you with, based on context.
With the additional new button in the top-right corner of DevTools you can open AI assistance from anywhere within DevTools.

Debug the full performance trace with Gemini

After recording a trace in the Performance panel, you can now chat about the full trace, related Performance insights, and field data with Gemini without selecting specific context in advance, all within the same conversation. This lets you look at performance issues more holistically before diving deeper.
After identifying a potential problem with the help of Gemini, you can seamlessly select a more specific context item like a trace event or a Performance insight for closer inspection and continue the same chat.
Likewise, all insights in Performance > Insights are now available for you to chat about with Gemini.

Toggle drawer orientation

The drawer can now also be moved to the side. This lets you view panels side-by-side instead of stacked. Right-click a panel name in the main tab bar and select Move to drawer to move the selected panel to the drawer.
Add additional panels to the drawer from ⋮ > More Tools.

Google Developer Program

The Google Developer Program is now integrated into DevTools, with direct links for profile management and new badges to earn.
Important: This feature is rolled out over time and might not be available for you yet.
Badges are an opt-in feature. To enable badges, go to Settings > Preferences > Account and toggle Earn badges.

Miscellaneous highlights

These are some of the many notable fixes and improvements in this release:

• The Application panel now supports storage inspection for all worker types, including Service Workers, Shared Workers, and Dedicated Workers.
• :target-current is now shown in the Styles panel.
• The Network panel can now filter requests based on a new Is ad-related boolean.

Download the preview channels

Consider using the Chrome Canary, Dev, or Beta as your default development browser. These preview channels give you access to the latest DevTools features, let you test cutting-edge web platform APIs, and help you find issues on your site before your users do!

Get in touch with the Chrome DevTools team

Use the following options to discuss the new features, updates, or anything else related to DevTools.

• Submit feedback and feature requests to us at crbug.com.
• Report a DevTools issue using the More options > Help > Report a DevTools issue in DevTools.
• Tweet at @ChromiumDev.
• Leave comments on What's new in DevTools YouTube videos or DevTools Tips YouTube videos.

What's new in DevTools

A list of everything that has been covered in the What's new in DevTools series.

Original source Report a problem

CSS and UI

Stable release date: October 28th, 2025

Unless otherwise noted, the following changes apply to Chrome 142 stable channel release for Android, ChromeOS, Linux, macOS, and Windows.

Absolute positioning for the ::view-transition element

View transitions use a pseudo subtree of the element, with ::view-transition being the root of that transition. Previously, the ::view-transition element was specified to have position: fixed. The CSS Working Group resolved to make this position: absolute and so Chrome now reflects that change.
This change shouldn't be noticeable because this element's containing block remains the snapshot containing block in either the absolute or fixed case. The only noticeable difference is in getComputedStyle.
Tracking bug #439800102 | ChromeStatus.com entry | Spec

active View Transition property on document

The View Transitions API lets developers start visual transitions between different states. The primary SPA entry point is startViewTransition(), which returns a transition object. This object contains several promises and functionality to track transition progress, and lets you manipulate transitions, for example, by skipping the transition or modifying its types.
From Chrome 142, developers no longer need to store this object. A document.activeViewTransition property represents this object, or null if no transition is ongoing.
This also applies to MPA transitions, where the object is only available through pageswap and pagereveal events. In this update, document.activeViewTransition is set to this object for the duration of the transition.
Tracking bug #434949972 | ChromeStatus.com entry | Spec

:target-before and :target-after pseudo-classes
These pseudo-classes match scroll markers that are before or after the active marker (matching :target-current) within the same scroll marker group, as determined by flat tree order:

• :target-before: Matches all scroll markers that precede the active marker in the flat tree order within the group.
• :target-after: Matches all scroll markers that follow the active marker in the flat tree order within the group.
  Tracking bug #440475008 | ChromeStatus.com entry | Spec

Range syntax for style container queries and if()

Chrome enhances CSS style queries and the if() function by adding support for range syntax.
It extends style queries beyond exact value matching (for example, style(--theme: dark)). Developers can use comparison operators (such as > and <) to compare custom properties, literal values (for example, 10px or 25%), and values from substitution functions like attr() and env(). For a valid comparison, both sides must resolve to the same data type. It is limited to the following numeric types: , , , , , , and .
Tracking bug #408011559 | ChromeStatus.com entry | Spec

Interest Invokers (the interestfor attribute)

Chrome adds an interestfor attribute to and elements. This attribute adds "interest" behaviors to the element. When a user "shows interest" in the element, actions are triggered on the target element, for example, showing a popover. The user agent detects when a user "shows interest" in the element through methods such as holding the pointer over the element, hitting special hotkeys on the keyboard, or long-pressing the element on touchscreens. When interest is shown or lost, an InterestEvent fires on the target, which has default actions for popovers, such as showing and hiding the popover.
Tracking bug #326681249 | ChromeStatus.com entry | Spec

Mobile and desktop parity for select element rendering modes

By using the size and multiple attributes, the element can be rendered as an in-page listbox or a button with a popup. However, these modes don't have consistent availability across mobile and desktop Chrome. In-page listbox rendering is unavailable on mobile, and a button with a popup is unavailable on desktop when the multiple attribute is present.
This update adds the listbox to mobile and a multi-select popup to desktop, and ensures that opt-ins with the size and multiple attributes result in the same rendering mode across mobile and desktop. The changes are summarized as follows:

• When the size attribute has a value greater than 1, in-page rendering is always used. Mobile devices ignored this before.
• When the multiple attribute is set with no size attribute, in-page rendering is used. Mobile devices previously used a popup instead of an in-page listbox.
• When the multiple attribute is set with size=1, a popup is used. Desktop devices previously used an in-page listbox.
  Tracking bug #439964654 | ChromeStatus.com entry | Spec

Support download attribute in SVG element

This feature introduces support for the download attribute on the SVGAElement interface in Chromium, aligning with the SVG 2 specification. The download attribute enables authors to specify that the target of an SVG hyperlink should be downloaded rather than navigated to, mirroring the behavior already supported in HTMLAnchorElement. This enhancement promotes interoperability across major browsers and ensures consistent behavior between HTML and SVG link elements, thereby improving developer experience and user expectations.
Tracking bug #40589293 | ChromeStatus.com entry | Spec

Graphics

WebGPU: primitive_index feature

WebGPU adds a new optional capability that exposes a new WGSL shader built-in, primitive_index. It provides a per-primitive index to fragment shaders on supported hardware, similar to the vertex_index and instance_index built-ins. The primitive index is useful for advanced graphical techniques, such as virtualized geometry.
Tracking bug #342172182 | ChromeStatus.com entry | Spec

WebGPU: Texture formats tier1 and tier2

Extend GPU texture format support with capabilities like render attachment, blending, multisampling, resolve and storage_binding.
Tracking bug #445725447 | ChromeStatus.com entry | Spec

Web APIs

FedCM—Support showing third-party iframe origins in the UI

Before Chrome 142, FedCM always showed the top-level site in its UI.
This works well when the iframe is conceptually first-party (for example, foo.com might have an iframe foostatic.com, which is not meaningful to the user).
But if the iframe is actually third-party, it is better to show the iframe origin in the UI so users better understand who they are sharing their credentials with. For example, a photo editor might be embedded in a book publishing web app and might want to let users access files they stored before with the photo editor. This capability is now available.
Tracking bug #390581529 | ChromeStatus.com entry | Spec

Stricter *+json MIME token validation for JSON modules

Reject JSON module script responses whose MIME type's type or subtype contains non-HTTP token code points (for example, spaces) when matched with *+json. This aligns with the MIME Sniffing specification and other engines. It is part of the Interop2025 modules focus area.
Tracking bug #440128360 | ChromeStatus.com entry | Spec

Web Speech API contextual biasing

This feature enables websites to support contextual biasing for speech recognition by adding a recognition phrase list to the Web Speech API.
Developers can provide a list of phrases as well as updating them to apply a bias to the speech recognition models in favor of those phrases. This helps improve accuracy and relevance for domain-specific and personalized speech recognition.
ChromeStatus.com entry | Spec

Media session: add reason to enterpictureinpicture action details

Adds enterPictureInPictureReason to the MediaSessionActionDetails sent to the enterpictureinpicture action in the Media Session API. This allows developers to distinguish between enterpictureinpicture actions triggered explicitly by the user (e.g. from a button in the user agent) and enterpictureinpicture actions triggered automatically by the user agent due to the content becoming occluded.
Tracking bug #446738067 | ChromeStatus.com entry | Spec

Security

Local network access restrictions

Chrome 142 restricts the ability to make requests to the user's local network, gated behind a permission prompt.
A local network request is any request from a public website to a local IP address or loopback, or from a local website (for example, an intranet) to loopback. Gating the ability for websites to perform these requests behind a permission mitigates the risk of cross-site request forgery attacks against local network devices such as routers, and reduces the ability of sites to use these requests to fingerprint the user's local network.
This permission is restricted to secure contexts. If granted, the permissions additionally relaxes mixed content blocking for local network requests (since many local devices are not able to obtain publicly trusted TLS certificates for various reasons).
Learn more in New permission prompt for Local Network Access.
Tracking bug #394009026 | ChromeStatus.com entry | Spec

User input

Interoperable pointerrawupdate events exposed only in secure contexts

The PointerEvents specification restricted pointerrawupdate to secure contexts in 2020, hiding both the event firing and the global event listeners from insecure contexts. Through this feature, Chrome will match the updated specification and become interoperable with other major browsers.
Tracking bug #404479704 | ChromeStatus.com entry | Spec

Sticky user activation across same-origin renderer-initiated navigations

This feature preserves the sticky user activation state after a page navigates to another same-origin page. The lack of user activation in the post-navigation page prevents some use cases like showing virtual keyboards on auto-focus, and this has been a blocker for the developers who want to build MPAs over SPAs.
Note: Browser-initiated navigation requests (reload, history navigation, typed URL in address bar) are not covered by this feature.
Tracking bug #433729626 | ChromeStatus.com entry | Spec

Origin trials

Device Bound Session Credentials

A way for websites to securely bind a session to a single device.
It lets servers have a session be securely bound to a device. The browser will renew the session periodically as requested by the server, with proof of possession of a private key.
Origin Trial | Device Bound Session Credentials: Second origin trial begins | ChromeStatus.com entry | Spec

Original source Report a problem

Texture format support capabilities extended

The new GPU feature lets developers port existing content to the web without needing to rewrite it for WebGPU's lower capabilities. It supports new "r16unorm", "r16snorm", "rg16unorm", "rg16snorm", "rgba16unorm", and "rgba16snorm" texture formats with render attachment, blendable, multisampling capabilities and "read-only" or "write-only" storage texture access. It also allows existing "r8snorm", "rg8snorm", "rgba8snorm" texture formats with render attachment, blendable, multisampling and resolve capabilities. More texture formats can also be used with "read-only" or "write-only" storage texture access.
The new GPU feature enables "read-write" storage texture access for specific formats, crucial for projects like porting Unreal Engine to the web. Note that enabling "texture-formats-tier2" at device creation automatically enables "texture-formats-tier1".
See the following snippet and chromestatus entry.

const adapter = await navigator.gpu.requestAdapter();
const requiredFeatures = [];
if (adapter.features.has("texture-format-tier1")) {
  requiredFeatures.push("texture-format-tier1");
}
if (adapter.features.has("texture-format-tier2")) {
  requiredFeatures.push("texture-format-tier2");
}
const device = await adapter.requestDevice({requiredFeatures});
// Later on, when dealing with "r8unorm" texture formats for example...
if (device.features.has("texture-format-tier2")) {
  // Use "read-write" storage texture access...
} else if (device.features.has("texture-format-tier1")) {
  // Use "read-only" or "write-only" storage texture access...
} else {
  // Fallback: Use another texture format...
}

Big thanks to the Intel folks for their work!

Primitive index in WGSL

The primitive_index is a built-in WGSL value that uniquely identifies the current primitive (for example, a point, line, or triangle) being processed by a fragment shader. It begins at 0, increments by 1 after every primitive is processed, and resets to 0 between each instance drawn.
When the "primitive-index" feature is available in a GPUAdapter, request a GPUDevice with this feature to get primitive index support in WGSL, and explicitly enable this extension in your WGSL code with enable primitive_index;. Once enabled, use the primitive_index built-in integer value in your fragment shader to access per-primitive data or perform logic that varies for each distinct geometric shape being rendered for example.
The following code snippet shows a fragment shader that renders the second primitive in red, and all other primitives in blue.

const adapter = await navigator.gpu.requestAdapter();
if (!adapter.features.has("primitive-index")) {
  throw new Error("Primitive index support is not available");
}
// Explicitly request primitive index support.
const device = await adapter.requestDevice({requiredFeatures: ["primitive-index"]});
const fragmentShaderModule = device.createShaderModule({code: `
enable primitive_index;
@fragment
fn main(@builtin(primitive_index) i : u32) -> @location(0) vec4f {
if (i == 1) {
return vec4f(1, 0, 0, 1);
}
return vec4f(0, 1, 0, 1);
}`});
// Send the appropriate commands to the GPU...

Explore more by checking out the Primitive Picking sample, and see the chromestatus entry.

Dawn updates

The DAWN_BUILD_MONOLITHIC_LIBRARY CMake variable used to handle the type of monolithic library to build has changed its default value from OFF to STATIC such that, by default the libwebgpu* files will be generated.
Dawn now handles properly wgpu::PresentMode::Undefined defaulting when configuring a wgpu::Surface. See issue 441410668.
This covers only some of the key highlights. Check out the exhaustive list of commits.

What's New in WebGPU

A list of everything that has been covered in the What's New in WebGPU series.

• Chrome 142
  • Texture format support capabilities extended
  • Primitive index in WGSL
  • Dawn updates

Original source Report a problem

CSS

Custom property enumeration in getComputedStyle()
When iterating over window.getComputedStyle(element) in Chrome, there was a bug where it forgets to include any custom properties set on the element. Therefore, length() on the returned object forgets to account for the number of custom properties set. This bug is fixed from Chrome 141, aligning Chrome with Firefox and Safari.

ARIA Notify API

ariaNotify provides a JavaScript API that lets content authors tell a screen reader what to read.
ariaNotify improves reliability and developer control compared to ARIA live regions, allowing for announcing changes not tied to DOM updates. This enables more consistent and ergonomic accessibility experiences across dynamic web applications. Iframe usage of this feature can be controlled using the "aria-notify" permission policy.

Update hidden=until-found and details ancestor revealing algorithm

The specification recently had some small changes to the revealing algorithms for hidden=until-found and details elements to prevent the browser from getting stuck in an infinite loop, these are now shipping in Chrome.

JavaScript

Align implementations on when RTP stats should be created
RTP stats objects, of type "outbound-rtp" or "inbound-rtp" in this case, represents a WebRTC stream. The identifier of this stream is the SSRC (a number). This feature aligns with the specification on when these stats should be created.

Media

Support restrictOwnAudio
The restrictOwnAudio property is a captured display surfaces constrainable property. It changes the behavior of system audio in a captured display surface. The restrictOwnAudio constraint only has an effect if the captured display surface inherently includes system audio; otherwise, it will have no impact.

windowAudio for getDisplayMedia()
Extends DisplayMediaStreamOptions for getDisplayMedia() with a windowAudio option. This new option allows web applications to hint to the user agent whether the user should be offered the ability to share audio when a window is selected. windowAudio can be set to exclude, system, or window based on application preference.
A web application that is configured for audio capture but wants to limit system audio capture when a window is selected should set windowAudio: "exclude".

Miscellaneous

Support width and height as presentation attributes on nested elements
This feature supports applying width and height as presentation attributes on nested elements through both SVG markup and CSS. This dual approach provides even greater flexibility for developers, allowing them to manage and style SVG elements more efficiently within complex designs.

Digital Credentials API (presentation support)
Websites retrieve credentials from mobile wallet apps using a variety of mechanisms, such as custom URL handlers and QR code scanning. This feature lets sites request identity information from wallets using Android's IdentityCredential CredMan system. It is extensible to support multiple credential formats (such as ISO mDoc and W3C verifiable credential) and allows multiple wallet apps to be used. This update adds mechanisms to help reduce the risk of ecosystem-scale abuse of real-world identity.

Navigation API: deferred commit (precommit handlers)
Normally, when navigateEvent.intercept() is called, the intercepted navigation commits (and therefore the URL updates) as soon as the NavigateEvent finishes dispatch.
This feature adds a precommitHandler option to navigateEvent.intercept(), similar to handler. It defers the commit until that handler (and all other precommit handlers) are resolved, and it allows the handler to change the navigation's URL, info, status, and history handling behavior (push/replace).

FedCM: Alternative fields in account selection
Adds support for phone numbers and usernames, in addition to or instead of a user's full name and email address as identifiers for disambiguating accounts in the account selector. Also, makes these new fields available for websites to affect the disclosure text.

Network / Connectivity

No-Vary-Search support for the HTTP disk cache
Lets the HTTP disk cache use the No-Vary-Search response header to share a cache entry between URLs that differ only in the query parameters.
Developers can use No-Vary-Search to specify query parameters that have no impact on the user experience. A common example might be an ID used to track conversions. Supporting this header in the HTTP disk cache means that if the user later goes back to that same page without the conversion ID, it can be used or revalidated from the cache rather than having to be fetched from scratch from the network.
Previously, No-Vary-Search support shipped for the navigation prefetch cache, prefetch and prerender speculation rules, and prerender. This launch makes it generally available to any feature that uses the HTTP disk cache.

Offline / Storage

IndexedDB getAllRecords() and direction option for getAll() and getAllKeys()
This feature adds the getAllRecords() method to the IndexedDB IDBObjectStore and IDBIndex. It also adds a direction parameter to getAll() and getAllKeys(). This functionality lets certain read patterns be significantly faster when compared to the existing alternative of iteration with cursors. In one test, a workload from a Microsoft property showed a 350ms improvement.
The getAllRecords() method combines getAllKeys() and getAll() by enumerating both primary keys and values at the same time. For an IDBIndex, getAllRecords() also provides the record's index key in addition to the primary key and value.

Performance

Speculation rules: desktop "eager" eagerness improvements
On desktop, "eager" eagerness speculation rules prefetches and prerenders now trigger when users hover on a link for a shorter time than the "moderate" mouse hover time.
The previous behavior, of starting prefetch and prerenders as soon as possible, was the same as "immediate" eagerness. This new behavior is more useful as it better reflects the author's intent to be more eager than the "moderate" and less eager than "immediate".

Security

Strict Same Origin Policy for Storage Access API
Adjusts the Storage Access API semantics to strictly follow the Same Origin Policy with regard to security. That is, using document.requestStorageAccess() in a frame only attaches cookies to requests to the iframe's origin (not site) by default.
Note: The CookiesAllowedForUrls policy or Storage Access Headers may still be used to unblock cross-site cookies.

Signature-based Integrity
This feature provides web developers with a mechanism to verify the provenance of resources they depend upon, creating a technical foundation for trust in a site's dependencies. In short: servers can sign responses with a Ed25519 key pair, and web developers can require the user agent to verify the signature using a specific public key. This offers a helpful addition to URL-based checks offered by Content Security Policy on the one hand, and Subresource Integrity's content-based checks on the other.

WebRTC

WebRTC Encoded Transform (V2)
This API allows processing of encoded media flowing through an RTCPeerConnection. Chrome shipped an early version of this API in 2020. Since then, the specification has changed and other browsers have shipped the updated version (Safari in 2022 and Firefox in 2023). This launch aligns Chrome with the updated specification as part of Interop 2025.
This launch does not cover the generateKeyFrame method, which is still under discussion.

echoCancellationMode for getUserMedia()
Extends the echoCancellation behavior of the MediaTrackConstraints dictionary. His previously accepted true or false and now additionally accepts the values "all" and "remote-only". This lets clients modify echo cancellation behavior applied to audio tracks received from microphones, controlling how much of the user system playout (all, or only audio received from PeerConnections) is removed from the microphone signal.

Managed ChromeOS only

Permissions Policy for Device Attributes API
The new Permissions Policy enables restricting access to the Device Attributes API, which is available only for policy-installed kiosk web apps and policy-installed Isolated Web Apps, both only on managed ChromeOS devices.
Additionally, the feature is controlled by content settings. Two new policies are introduced: DeviceAttributesBlockedForOrigins and DefaultDeviceAttributesSetting, to complement previously introduced DeviceAttributesAllowedForOrigins. The feature is enabled by default for policy-installed kiosk web apps and policy-installed Isolated Web Apps on managed ChromeOS devices.

Origin trials

Local network access restrictions
Chrome 141 restricts the ability to make requests to the user's local network, gated behind a permission prompt.
This origin trial temporarily allows for access to resources on local networks to originate from non-secure contexts. This will give developers more time to migrate Local Network Access requests to originate from a secure context.

Proofreader API

A JavaScript API for proofreading input text with suggested corrections, backed by an AI language model.

Extend CSP script-src (also known as script-src-v2)

This feature adds new keywords to the script-src Content Security Policy (CSP) directive. This adds two new hash-based allowlisting mechanisms: script sources based on hashes of URLs and contents of eval() and eval()-like functions. This is sometimes referred to as script-src-v2, although it is backward compatible with the existing script-src, and uses the same directive.
Extending hashes to cover URL and eval() hashes lets developers set reasonably strict security policies by narrowly allowlisting scripts by their hashes even when script contents are subject to frequent changes, and known-safe contents of eval() without permitting unchecked use of eval() broadly.
The new keywords override host-based script-src when provided. This allows a single header to be compatible with browsers that both do or do not implement the new keywords.

WebAssembly custom descriptors
Lets WebAssembly store data associated with source-level types more efficiently in new "custom descriptor" objects. These custom descriptors can be configured with prototypes for the WebAssembly objects of that source-level type. This lets you install methods on a WebAssembly object's prototype chain and call them directly from JavaScript using normal method call syntax. The prototypes and methods can be configured declaratively using an imported built-in function.

Deprecations and removals

Stop sending Purpose: prefetch header from prefetches and prerenders
Now that prefetches and prerenders are using the Sec-Purpose header for prefetches and prerenders, we will move to remove the legacy Purpose: prefetch header that is still currently passed. This will be behind a feature flag/ kill switch to prevent compat issues.
This will be scoped to speculation rules prefetch, speculation rules prerender, and Chromium's non-standard .

Original source Report a problem

You can now check out a preview for the new Chrome DevTools Model Context Protocol (MCP) server. It brings the power of Chrome DevTools to AI coding assistants.
Previously, coding agents weren't able to see what the code they generate actually does when it runs in the browser. The Chrome DevTools MCP server changes this. AI coding assistants are able to debug web pages directly in Chrome, and benefit from DevTools debugging capabilities and performance insights. This improves their accuracy when identifying and fixing issues.
See for yourself how it works:

For more information see Chrome DevTools (MCP) for your AI agent.

Debug the network dependency tree with Gemini

The Performance > Insights > Network dependency tree insight now has the Debug with AI button that takes you to the AI assistance panel, so you can discuss and debug said tree with the help of Gemini.

Export your chats with Gemini

You can now export your current chat with Gemini or copy its response to clipboard by clicking the Export conversation button at the top action bar or Copy response under the Gemini's message in the chat.

Persisted track configuration in the Performance panel

When you configure a recorded track in the Performance panel, DevTools now saves your configuration and applies it when you import it back or record a new one.

Filter IP protected network requests

In the Network panel, you can now filter requests sent to IP Protection proxies.

Elements > Layout tab adds masonry layout support

You can now inspect masonry layout in the Elements > Styles tab.
Masonry layout is a layout method where one axis uses a typical strict grid layout, most often columns, and the other a masonry layout.

Lighthouse 12.8.2

The Lighthouse panel now runs Lighthouse 12.8.2.
Most notably in this version, Lighthouse separates found issues with CSS custom properties into their own error messages.
See also the full list of changes.
To learn the basics of using the Lighthouse panel in DevTools, see Lighthouse: Optimize website speed.
Chromium issue: 40543651.

Miscellaneous highlights

These are some of many notable fixes and improvements in this release:

• Performance: Request Idle callback events now include the timeout property (crbug.com/441679219).
• Accessibility. Screen readers will now read out the following:
  • 'This is a new feature' for promoted command menu items (crbug.com/441485154).
  • Code completion summary toolbar (crbug.com/433952045).
• Network: Right clicking a network log item selects it (crbug.com/368510578).

Download the preview channels

Consider using the Chrome Canary, Dev, or Beta as your default development browser. These preview channels give you access to the latest DevTools features, let you test cutting-edge web platform APIs, and help you find issues on your site before your users do!

Get in touch with the Chrome DevTools team

Use the following options to discuss the new features, updates, or anything else related to DevTools.

• Submit feedback and feature requests to us at crbug.com.
• Report a DevTools issue using the More options > Help > Report a DevTools issue in DevTools.
• Tweet at @ChromeDevTools.
• Leave comments on What's new in DevTools YouTube videos or DevTools Tips YouTube videos.

What's new in DevTools

A list of everything that has been covered in the What's new in DevTools series.

Original source Report a problem

What's New in WebGPU

Tint IR completed

A long running project (over 2.5 years) to increase the performance of the internals of Tint, the WGSL compiler has been completed. An Intermediate Representation (IR) was inserted into the backend between the current Abstract Syntax Tree (AST) and the backend code generators. The introduction of the IR allowed the Chrome team to remove all of the AST transformations and re-create them as IR transformations which, due to architectural differences, are substantially faster. The internals of Tint, on some platforms saw up to a seven times speed improvement from these changes.

This new IR unlocks significant potential for sophisticated, large-scale shader analysis and transformation, promising not just notable performance gains but also a smoother path for Chrome to deliver exciting new WebGPU features down the line.

From this milestone all backend code generators work from the IR representation, all AST transformations have been deleted, and all of the AST support code to run the transformations has been removed.

As part of the IR improvement work, the SPIR-V frontend (used by applications to convert SPIR-V to WGSL) was converted from generating an AST representation to generating directly to IR. This enhancement also introduces long-awaited features like float 16 support to the SPIR-V frontend.

Integer range analysis in WGSL compiler

The Chrome team is progressively rolling out a new integer range analysis for Tint, the WebGPU shader language compiler. Integer range analysis estimates the minimum and maximum values an integer variable can take during program execution without actually running the program.
This feature aims to improve efficiency by reducing the need for costly bounds checking and will soon be enabled by default across all platforms. See issue 348701956.

SPIR-V 1. 4 update for Vulkan backend

SPIR-V 1.4 support is rolled out where available on Android and ChromeOS devices. This update enables Tint, the WGSL compiler, to take advantage of new SPIR-V features, relaxations, and new instructions for more efficient code generation in certain scenarios when compiling Vulkan shaders. See issue 427717267.

Dawn updates

The standardized webgpu.h header, which defines the core WebGPU C API, is now finally considered stable. This stability applies specifically to the core API defined upstream, not including implementation extensions (for example, from Dawn or Emdawnwebgpu), so it is best to use the webgpu.h provided by the exact implementation you're linking against. While the header is stable, you might still encounter unintended differences between implementations as we continue to fix bugs and address compatibility across the ecosystem. If you do, file a bug.

Thanks to external contributor William Candillon, you can now find prebuilt Dawn binaries as artifacts on GitHub Actions. Those include static .lib files for Android, an .XCFramework bundle for Apple, and all the necessary header files. See Dawn PR #39 and an example of the artifacts.

This covers only some of the key highlights. Check out the exhaustive list of commits.

What's New in WebGPU

A list of everything that has been covered in the What's New in WebGPU series.

Chrome 141

• Tint IR completed
• Integer range analysis in WGSL compiler
• SPIR-V 1.4 update for Vulkan backend
• Dawn updates

Original source Report a problem

CSS typed arithmetic

Typed arithmetic lets you write expressions in CSS such as calc(10em / 1px) or calc(20% / 0.5em * 1px). This is useful in, for example, typography, as it lets you convert a typed value into an untyped one and reuse it for number accepting properties. Another use case is to multiply the unitless value by another type. For example, you can now cast from pixels to degrees.
Tracking bug #40768696 | ChromeStatus.com entry | Spec

CSS caret-animation property

Chromium supports animation of the caret-color property. However, when animated, the caret's default blinking behavior interferes with the animation.
The CSS caret-animation property has two possible values: auto and manual. auto means browser default (blinking), and manual means the developer controls the caret animation. Additionally, users who are disturbed by or have adverse reactions to blinking or flashing visuals can disable the blinking with a user stylesheet.
Tracking bug #329301988 | ChromeStatus.com entry | Spec

highlights From Point API

The highlightsFromPoint API lets developers interact with custom highlights. It detects which highlights exist at a specific point within a document. This interactivity is valuable for complex web features where multiple highlights may overlap or exist within shadow DOM. By providing precise point-based highlight detection, the API empowers developers to manage dynamic interactions with custom highlights more effectively. For example, developers can respond to user clicks or hover events on highlighted regions to trigger custom tooltips, context menus, or other interactive features.
Tracking bug #365046212 | ChromeStatus.com entry | Spec

Scroll Into View container option

The ScrollIntoViewOptions container option allows developers to perform a scrollIntoView operation that only scrolls the nearest ancestor scroll container. For example, the following snippet only scrolls the scroll container of target to bring target into view, but won't scroll all of the scroll containers to the viewport:
target.scrollIntoView({ container: 'nearest' });
ChromeStatus.com entry | Spec

View transitions: Inherit more animation properties

Adds more animation properties to inherit through the view transition pseudo tree:

• animation-timing-function
• animation-iteration-count
• animation-direction
• animation-play-state
  Tracking bug #427741151 | ChromeStatus.com entry | Spec

View transition pseudos inherit animation-delay.

In addition to the previous update, the animation-delay property is now inherited through the view transition pseudo tree.
ChromeStatus.com entry | Spec

Nested view transitions groups

This feature allows view transitions to generate a nested pseudo-element tree rather than a flat one. This allows the view transition to appear more in line with its original elements and visual intent. It enables clipping, nested 3D transforms, and proper application of effects like opacity, masking, and filters.
Tracking bug #399431227 | ChromeStatus.com entry | Spec

Propagate viewport overscroll-behavior from root

This change propagates overscroll-behavior from the root instead of the body.
The CSS working group resolved not to propagate properties from the to the viewport. Instead, properties of the viewport propagate from the root () element. As such, overscroll-behavior should propagate from the root element. However, Chrome has had a longstanding issue: it propagates overscroll-behavior from the rather than the root. This behavior is not interoperable with other browsers. This change makes Chrome comply with the specification and become interoperable with other implementations.
Tracking bug #41453796 | ChromeStatus.com entry | Spec

CSS counter() and counters() in alt text of content property

This feature adds the ability to use counter() and counters() in the alt text of the content property. This provides more meaningful information to improve accessibility.
Tracking bug #417488055 | ChromeStatus.com entry | Spec

CSS scroll-target-group property

The scroll-target-group property specifies whether the element is a scroll marker group container. It accepts one of the following values:

• 'none': The element does not establish a scroll marker group container.
• 'auto': The element establishes a scroll marker group container forming a scroll marker group containing all of the scroll marker elements for which this is the nearest ancestor scroll marker group container.
  Establishing a scroll marker group container lets any anchor HTML elements with a fragment identifier that are inside such a container to be the HTML equivalent of ::scroll-marker pseudo-elements. The anchor element whose scroll target is currently in view can be styled using the :target-current pseudo-class.
  Tracking bug #6607668 | ChromeStatus.com entry | Spec

Support font-variation-settings descriptor in @font-face rule

CSS allows developers to adjust a font's weight, width, slant, and other axes using the font-variation-settings property on individual elements. However, Chromium-based browsers lack support for this property within @font-face declarations. This feature supports the string-based syntax for font-variation-settings as defined in CSS Fonts Level 4. Invalid or unrecognized feature tags are ignored per specification. No binary or non-standard forms are supported. Variable fonts are becoming more widely adopted for both performance and typographic flexibility. Adding support for this descriptor in Chromium enhances control, reduces repetition, and supports a more scalable, modern approach to web typography.
Tracking bug #40398871 | ChromeStatus.com entry | Spec

DOM

ToggleEvent source attribute

The source attribute of a ToggleEvent contains the element that triggered the ToggleEvent to be fired, if applicable. For example, if a user clicks a element with the popovertarget or commandfor attribute set to open a popover, the ToggleEvent fired on the popover will have its source attribute set to the invoking .
ChromeStatus.com entry | Spec

Isolated Web Apps (IWAs)

Controlled Frame API (available only to IWAs)

This feature adds a Controlled Frame API available only to Isolated Web Apps (IWAs). Like similarly-named APIs on other platforms, Controlled Frame allows embedding all content, even third-party content that cannot be embedded in . Controlled Frame also allows controlling embedded content with a collection of API methods and events. For more information about Isolated Web Apps, see the Isolated Web Apps explainer.
Tracking bug #40191772 | ChromeStatus.com entry | Spec

JavaScript

Uint8Array to and from base64 and hex

Base64 is a common way to represent arbitrary binary data as ASCII. JavaScript has Uint8Arrays for binary data. However, it lacks a built-in mechanism to encode that data as base64, or to take base64 data and produce a corresponding Uint8Array. This feature adds the ability and methods for converting between hex strings and Uint8Arrays.
ChromeStatus.com entry | Spec

View transition finished promise timing change

The current finished promise timing happens within the rendering lifecycle steps. This means that code that runs as a result of promise resolution happens after the visual frame that removes the view transition has been produced. This can cause a flicker at the end of the animation if the script moves styles to preserve a visually similar state. This change resolves the issue by moving the view transition cleanup steps to run asynchronously after the lifecycle is completed.
Tracking bug #430018991 | ChromeStatus.com entry

Web APIs

ReadableStreamBYOBReader min option

This feature introduces a min option to the existing ReadableStreamBYOBReader.read(view) method. The method already accepts an ArrayBufferView into which it reads data, but currently does not guarantee how many elements are written before the read resolves. By specifying a min value, you can require that the stream wait until at least that many elements are available before resolving the read. This improves upon the current behavior, where reads may resolve with fewer elements than the view can hold.
Tracking bug #40942083 | ChromeStatus.com entry | Spec

Get Installed Related Apps API on desktop

The Get Installed Related Apps API (navigator.getInstalledRelatedApps) provides sites access to if their corresponding related applications are installed. Sites are only allowed to use this API if the application has an established association with the web origin.
The API was launched in Chrome 80 for Android. Additional support for web apps on Desktop was enabled in Chrome 140.
Docs | Tracking bug #895854 | ChromeStatus.com entry | Spec

Http cookie prefix

In some cases, it's important to distinguish on the server side between cookies set by the server and those set by the client. One such case involves cookies normally always set by the server. However, unexpected code (such as an XSS exploit, a malicious extension, or a commit from a confused developer) might set them on the client. This proposal adds a signal that lets servers make such a distinction. More specifically, it defines the __Http and __HostHttp prefixes, which ensure a cookie is not set on the client side using script.
Tracking bug #426096760 | ChromeStatus.com entry | Spec

Service worker

SharedWorker script inherits controller for blob script URL

The specification states that workers should inherit controllers for the blob URL. However, existing code allows only dedicated workers to inherit the controller; shared workers don't. This fixes Chrome's behavior to align with the specification. The SharedWorkerBlobURLFixEnabled enterprise policy controls this feature.
Tracking bug #324939068 | ChromeStatus.com entry | Spec

Add ServiceWorkerStaticRouterTimingInfo

This feature adds timing information for the ServiceWorker Static routing API, exposed in the navigation timing API and resource timing API for developer use. ServiceWorker provides timing information to mark certain points in time.
This feature adds two pieces of Static routing API-relevant timing information:

• RouterEvaluationStart: Time to start matching a request with registered router rules.
• CacheLookupStart: Time to start looking up the cache storage if the source is "cache".
  Additionally, this feature adds two pieces of router source information: the matched router source and the final router source.
  Tracking bug #41496865 | ChromeStatus.com entry | Spec

Origin trials

Enable incoming call notifications

This feature extends the Notifications API to allow installed PWAs to send incoming call notifications—notifications with call-styled buttons and a ringtone. This extension helps VoIP web apps create more engaging experiences by making it easier for users to recognize and answer calling notifications. Additionally, this feature helps bridge the gap between native and web implementations of apps that have them both.
Origin Trial | Tracking bug #detail?id=1383570 | ChromeStatus.com entry | Spec

Crash Reporting key-value API

This feature introduces a new key-value API, tentatively window.crashReport, backed by a per-document map that holds data appended to crash reports.
The data placed in this API's backing map is sent in the CrashReportBody if any renderer process crashes occur on the site. This lets developers debug what specific state in their application might be causing a given crash.
Origin Trial | Tracking bug #400432195 | ChromeStatus.com entry | Spec

Add the clipboardchange event

The clipboardchange event fires whenever a web app or any other system application changes the system clipboard contents. This allows web apps like remote desktop clients to keep their clipboards synchronized with the system clipboard. It provides an efficient alternative to polling the clipboard with JavaScript for changes.
Origin Trial | Tracking bug #41442253 | ChromeStatus.com entry | Spec

Enable SharedWorker on Android

The long-standing demand for SharedWorker support on Android stems from several needs expressed by web developers:

• Resource sharing and efficiency: Developers aim to share a single WebSocket or Server-Sent Events (SSE) connection across multiple tabs, thereby conserving resources.
• Persistent resource management: A requirement to share and persist resources across tabs, particularly for technologies like WASM-based SQLite.
• Closing a feature gap: Other major mobile browsers, including Safari on iOS and Firefox on Android, already support SharedWorker, making Chrome on Android the last major browser to address this gap.
  Origin Trial | ChromeStatus.com entry | Spec

Removals

• Stop sending Purpose: prefetch header from prefetches and prerenders
  Prefetches and prerenders now use the Sec-Purpose header, therefore the legacy Purpose: prefetch header is being removed.
  This will be scoped to speculation rules prefetch, speculation rules prerender, , and Chromium's non-standard .
  Tracking bug #420724819 | ChromeStatus.com entry | Spec

• Deprecate special font size rules for H1 within some elements
  The HTML spec contains a list of special rules for

  tags nested within , , , or tags:
  These special rules are deprecated, because they cause accessibility issues. Namely, they visually reduce the font size for nested

  elements so that they "look" like

  elements, but nothing in the accessibility tree reflects this demotion.
  Tracking bug #394111284 | ChromeStatus.com entry | Spec

Original source Report a problem

Debug more insights with Gemini

Copy link to this section: Debug more insights with Gemini

In Performance > Insights, you can now click Debug with AI (previously Ask AI) to chat and debug with Gemini in the AI assistance panel more performance insights:

• Improve image delivery
• Legacy JavaScript
• Duplicated JavaScript
• Modern HTTP

The before and after adding the 'Debug with AI' button to more performance insights.

Emulate the 'Save-Data' header in 'Network conditions'

In the Network conditions panel, you can now emulate the behaviour of the Save-Data request header. This header is a network client hint which indicates the client's preference for reduced data usage. It's also available through the navigator.connection.saveData API.

The before and after adding the 'Save-Data' request header emulation to 'Network conditions'.
Chromium issue: 40668980.

See the Baseline status in a CSS property tooltip

In Elements > Styles, when you hover over any CSS property, you can now see, under the property's definition, its availability across major browsers according to its Baseline status.

The before and after adding the Baseline status to the CSS property tooltips.
Chromium issue: 417749762.

Override form factors in user agent client hints

In the Network conditions > User agent client hints drop-down, you now have options to override form factors, specifically, the values of the Sec-CH-UA-Form-Factors request header.

The before and after adding the options for form factor override to user agent client hints.
Chromium issue: 422218341.

Lighthouse 12.8.0

The Lighthouse panel now runs Lighthouse 12.8.0.

Most notably in this version, Lighthouse adds a new report: Mitigate DOM-based XSS with trusted types.

See also the full list of changes.

To learn the basics of using the Lighthouse panel in DevTools, see Lighthouse: Optimize website speed.

Chromium issue: 40543651.

Miscellaneous highlights

These are some of many notable fixes and improvements in this release:

• AI assistance:
  • Chat history is now cleared when you disable the corresponding AI feature in Settings.
  • Accessibility: Screen readers now announce context titles early, "Answer loading" when the answer starts streaming and "Answer ready" when the answer is complete.
• Elements:
  • The Styles tab can now evaluate sibling-index(), sibling-count(), and env() CSS functions (crbug.com/417128001, crbug.com/40196710).
  • Added support for ::view-transition-group-children pseudo element (crbug.com/425901164).
  • Added support for accessibility issues about interactive content in the element (crbug.com/427172874).
  • From the Computed tab, you can now navigate to longhand properties in Styles (crbug.com/41486012).
  • Easing, Color editors: You can now interact with bezier swatches for animation transitions and color swatches using the keyboard (crbug.com/401213421).
• Network: HAR files import now also includes request and response cookies (crbug.com/432995868).
• Device mode: Updated user agents for Apple devices to latest Safari 18.5.

Download the preview channels

Consider using the Chrome Canary, Dev, or Beta as your default development browser. These preview channels give you access to the latest DevTools features, let you test cutting-edge web platform APIs, and help you find issues on your site before your users do!

Get in touch with the Chrome DevTools team

Use the following options to discuss the new features, updates, or anything else related to DevTools.

• Submit feedback and feature requests to us at crbug.com.
• Report a DevTools issue using the More options > Help > Report a DevTools issue in DevTools.
• Tweet at @ChromeDevTools.
• Leave comments on What's new in DevTools YouTube videos or DevTools Tips YouTube videos.

What's new in DevTools

A list of everything that has been covered in the What's new in DevTools series.

Original source Report a problem

Device requests consume adapter

According to the WebGPU specification, an adapter is marked as "consumed" upon a successful device request. Consequently, any subsequent requestDevice() calls using the same adapter will now result in a rejected promise. Previously, these calls would return a device that was lost at creation. See issue 415825174.

Shorthand for using texture where texture view is used

A GPUTexture can now be used directly as a GPUBindingResource to expose to the shader for binding. It can also be used as a GPURenderPassColorAttachment view, a GPURenderPassColorAttachment resolveTarget, and a GPURenderPassDepthStencilAttachment view for improved ergonomics. This offers a simpler approach than using a GPUTextureView to get a default view. See issue 425906323.

WGSL textureSampleLevel supports 1D textures

1D textures can now be sampled using textureSampleLevel() for consistency with 2D textures. This lets you sample a 1D texture from a vertex shader which was previously only possible from a fragment shader with textureSample(). See issue 382514673.

Deprecate bgra8unorm read-only storage texture usage

Using "bgra8unorm" format with read-only storage textures is now deprecated. The WebGPU specification explicitly disallows this, and its prior allowance in Chrome was a bug, as this format is intended for write-only access and is not portable. See issue 427681156.

Remove GPUAdapter isFallbackAdapter attribute

As previously announced, the GPUAdapter isFallbackAdapter attribute is now removed. It's replaced by the GPUAdapterInfo isFallbackAdapter attribute that was introduced in Chrome 136. See intent to remove.

Dawn updates

The wgpuInstanceGetWGSLLanguageFeatures() function is used to get a list of WGSL language features supported by the instance. Previously it returned a WGPUStatus value. It has been updated to not return a value since it can't fail. See issue 429178774.
The wgpuSurfacePresent() function now returns a WGPUStatus error if the surface doesn't have a current texture. See issue 425930323.
The new wgpu::InstanceFeatureName::MultipleDevicesPerAdapter feature lets adapters create multiple devices without being "consumed". See issue 415825174.
The dump_shaders_on_failure device toggle lets you dump shaders only on failure for debugging purposes. It applies exclusively to D3 backends, though future expansion to other backends is possible. See issue 429187478.
Multiple changes have been made to the Vulkan backend to reduce overhead when submitting render passes, especially for improved performance on mobile GPUs. For example: caching VkFramebuffers.
This covers only some of the key highlights. Check out the exhaustive list of commits.

What's New in WebGPU

A list of everything that has been covered in the What's New in WebGPU series.

Chrome 140

• Device requests consume adapter
• Shorthand for using texture where texture view is used
• WGSL textureSampleLevel supports 1D textures
• Deprecate bgra8unorm read-only storage texture usage
• Remove GPUAdapter isFallbackAdapter attribute
• Dawn updates

Original source Report a problem

CSS and UI

Short-circuiting var() and attr()

When the fallback is not taken, var() and attr() functions evaluate without looking for cycles in that fallback.

Support font-feature-settings descriptor in @font-face rule

This feature supports the string-based syntax for font-feature-settings as defined in CSS Fonts Level 4. Invalid or unrecognized feature tags will be ignored per specification. No binary or non-standard forms are supported.
As OpenType fonts become more widely adopted, this enhancement will improve typographic control, reduce redundancy, and support a more scalable, modern approach to web design.

CSS custom functions

Custom functions are similar to custom properties, but instead of returning a single, fixed value, they return values based on other custom properties, parameters, and conditionals.

Continue running transitions when switching to initial transition value

When the transition related properties change, they are only supposed to affect newly started transitions. This means that if you change the transition properties, unless you also change the properties which have active transition animations, those transition animations will continue with the previously specified duration and easing.
Chrome incorrectly canceled transitions when the transition property was set to none, even though it doesn't cancel them if you only change the transition-duration. This change makes Chrome consistent with Safari and Firefox, allowing active transitions to continue running, until their property value changes triggering a new transition update.

Corner shaping (corner-shape, superellipse, squircle)

Enable styling corners, on top of the existing border-radius, by expressing the shape and curvature of the corner as a superellipse.
This allows shapes like squircles, notches, and scoops, and animating between them.

Add font-width property and descriptor and make font-stretch a legacy alias

Note: Previously the font-width property was added to these release notes. THis was an error as the property did not ship.

Support async attribute for SVG

Original source Report a problem