Electron 40.0.0 has been released! It includes upgrades to Chromium 144.0.7559.60, V8 14.4, and Node 24.11.1.

The Electron team is excited to announce the release of Electron 40.0.0! You can install it with npm via npm install electron@latest or download it from our releases website. Continue reading for details about this release.

If you have any feedback, please share it with us on Bluesky or Mastodon, or join our community Discord! Bugs and feature requests can be reported in Electron's issue tracker.

Stack Changes​

• Chromium 144.0.7559.60

  • New in 144
  • New in 143

• Node v24.11.1

  • Node 24.11.1 blog post

• V8 14.4

  • V8 roll increment

Electron 40 upgrades Chromium from 142.0.7444.52 to 144.0.7559.60, Node.js from v22.20.0 to v24.11.1, and V8 from 14.2 to 14.4.

New Features and Improvements​

• Added "memory-eviction" as a possible reason for a child process to exit. #48362
• Added bypassCustomProtocolHandlers option to net.request. #48883 ^{(Also in 38, 39)}
• Added support to import external shared texture as VideoFrame. #48831
• Automatically focus DevTools when element is inspected or breakpoint is triggered. #46386 ^{(Also in 37, 38, 39)}
• Enabled resetting accent color to follow system accent settings if a previous color has been set via window.setAccentColor(null). #48274 ^{(Also in 38, 39)}
• Updated nativeImage.createFromNamedImage to support SF Symbol names. #48772 ^{(Also in 39)}

Breaking Changes​

Deprecated: clipboard API access from renderer processes​

Using the clipboard API directly in the renderer process is deprecated. If you want to call this API from a renderer process, place the API call in your preload script and expose it using the contextBridge API.

Behavior Changed: macOS dSYM files now compressed with tar.xz​

Debug symbols for macOS (dSYM) now use xz compression in order to handle larger file sizes. dsym.zip files are now dsym.tar.xz files. End users using debug symbols may need to update their zip utilities.

End of Support for 37.x.y​

Electron 37.x.y has reached end-of-support as per the project's support policy. Developers and applications are encouraged to upgrade to a newer version of Electron.

What's Next​

In the short term, you can expect the team to continue to focus on keeping up with the development of the major components that make up Electron, including Chromium, Node, and V8.

You can find Electron's public timeline here.

More information about future changes can be found on the Planned Breaking Changes page.