.svg?width=900)
Image: Wikimedia Commons — Google Chrome logo.
📌 KEY HIGHLIGHTS
- Chrome 157 reached stable on 3 November 2026: version 157.0.8103.38/.39 on Windows and Mac, 157.0.8103.38 on Linux and Android.
- HTML-in-Canvas is now stable — real, selectable HTML can be drawn inside a canvas in 2D, WebGL and WebGPU apps.
- The update fixes 213 security flaws: 7 Critical, 77 High, 75 Medium and 54 Low. Google has not said any of them is being actively exploited.
- Android gains the on-device Language Detector API, and developers get new CSS corner, text-overflow and HTML-insertion features.
- Chrome 158 is already scheduled for 17 November 2026 — Chrome now ships a new major version every two weeks.
What happened?
Google promoted Chrome 157 to the stable channel on Tuesday, 3 November 2026, for Windows, Mac and Linux, with the Android build following through Google Play. A small share of desktop users had already received it in late October through Google's early-stable rollout, but 3 November is the date the release went wide. The rollout is gradual, so some machines may take days to be offered the update.
The version numbers to look for are 157.0.8103.38 or .39 on Windows and Mac, and 157.0.8103.38 on Linux and Android. If your About page shows 156 or older, you are on the previous release and missing this round of fixes. ChromeOS had no separate stable 157 note posted as of 4 November — Chromebook users get the update through the system update instead.
This is also the new normal for Chrome's pace. Since Chrome 153 in September 2026, Google has shipped a major version every two weeks, and the next one, Chrome 158, is already dated 17 November 2026.
| Platform | Chrome 157 version | Status |
|---|---|---|
| Windows and Mac | 157.0.8103.38 / .39 | Rolling out |
| Linux | 157.0.8103.38 | Rolling out |
| Android | 157.0.8103.38 | Via Google Play |
| ChromeOS | Via system update | No separate stable note yet |
Chrome 157 new features explained: HTML-in-Canvas
The headline developer feature is HTML-in-Canvas, which Google announced on 26 October and shipped stable in Chrome 157. Until now, a web developer building a game, a 3D scene or a design tool on a <canvas> faced a trade-off: anything drawn on the canvas was just pixels. Text could not be selected, translated or read by a screen reader, and buttons drawn there were not real buttons.
HTML-in-Canvas changes that. A page can now put live HTML elements inside a canvas — in 2D, WebGL and WebGPU — and the browser keeps treating them as HTML. Text stays selectable and copyable, Ctrl+F finds it, translation and autofill work, screen readers can read it, and the content can even be warped over a 3D surface or run through shaders. Google lists large canvas apps, 3D scenes and games, media editing and export, and shader-style effects as the main uses. Three.js, PlayCanvas, Babylon.js and PixiJS already support it, according to Google.
There are limits worth knowing. It is a Chrome-only feature for now: Mozilla and WebKit have had standards-position requests open since 2024 and 2026 respectively, with no verdict yet. Developers should check for support at runtime and keep a normal HTML fallback for other browsers. For privacy, cross-origin images and iframes, system colours and visited-link colours are never drawn into the canvas.
Image: Wikimedia Commons — Google Chrome running on Windows 11.
The 213 security fixes — and why updating matters
The other half of Chrome 157 is security. Google's release note lists 213 fixes: 7 Critical, 77 High, 75 Medium and 54 Low. Google found 130 of the flaws internally; external researchers reported the rest and have been paid $31,000 in bounties so far.
Two of the Critical flaws show the scale. CVE-2026-121156 is a buffer overflow in Dawn, Google's WebGPU implementation, reported by Zhenpeng "Leo" Lin with a $10,000 bounty. CVE-2026-121229 is memory corruption in ANGLE, the graphics layer, which Malwarebytes notes could let a remote attacker run code outside the sandbox through a crafted web page. The remaining Critical issues are use-after-free flaws in WebGL, Prerender, Geometry and Core. Google has not said any of the 213 flaws is being actively exploited, and no Chrome 157 entry appeared in CISA's Known Exploited Vulnerabilities catalogue as of 3 November — but the fixes only protect you once the update is installed and the browser has restarted.
More new in Chrome 157
Android picks up the Language Detector API, which was already on desktop. Websites can now detect the language of text on the phone using an on-device machine-learning model, without sending the text to a cloud server — useful for multilingual apps and for privacy-sensitive content.
For front-end developers, Chrome 157 adds CSS corner shorthand properties that set border-radius and corner shape together, a custom string for text-overflow (so clipped text can show "(more)" instead of "..."), and text-decoration-inset for underline spacing. The Background Fetch API now enforces CORS like a normal fetch, closing a way sites could bypass security checks, and there are renewed HTML insertion and streaming methods for adding markup to a page. Capability Elements — the camera, microphone and geolocation controls — gain a compact icon-only display mode.
Why it matters for readers in India
Chrome is the default browser for most Indian users on both phones and computers, so a release with 7 Critical fixes is a security update for practically everyone reading this. If you bank, pay via UPI, or file taxes in the browser, running an old Chrome build leaves the door open to the exact flaws this release closes — update before you shrug it off.
For Indian developers, the two features that matter most are HTML-in-Canvas and on-device language detection. Games, edtech apps and design tools built for Indian users can now put real, readable, translatable text inside canvas scenes instead of flat images — and a language detector that runs on the phone, without sending user text to a server, fits India's multilingual web far better than a cloud call for every snippet.
Should you care?
How to update Chrome to 157
On a computer, open Chrome, click the three-dot menu, go to Settings → About Chrome. Chrome checks for the update and installs it; click Relaunch to finish. On Android, open the Play Store, search for Chrome and tap Update, or wait for the automatic update. After relaunching, About Chrome should show 157.0.8103.38 or higher. If you build with JetBrains tools, our PhpStorm 2026.3 explainer covers the other big developer update this week, and IntelliJ IDEA 2026.3 brings the same AI workspace to Java developers.
FAQs
What is new in Chrome 157?
Chrome 157, stable from 3 November 2026, brings HTML-in-Canvas for developers, the on-device Language Detector API on Android, new CSS features, and 213 security fixes — 7 of them rated Critical by Google.
How do I update Chrome to version 157?
On desktop, go to Settings → About Chrome and click Relaunch after the update downloads. On Android, update Chrome from the Google Play Store. The new version is 157.0.8103.38 (or .39 on some Windows and Mac machines).
What is HTML-in-Canvas in Chrome 157?
It is a new API that lets developers draw live HTML elements inside a canvas in 2D, WebGL and WebGPU. The content stays real HTML, so text can be selected, translated and read by screen readers, even when it is part of a 3D scene or a game.
Are the Chrome 157 security flaws being exploited?
Google has not said any of the 213 flaws is being actively exploited, and CISA's Known Exploited Vulnerabilities catalogue had no Chrome 157 entries as of 3 November. The fixes still only protect you after you update and relaunch.
Takeaway: Chrome 157 is a security update first and a developer release second — 213 fixes, 7 of them Critical, plus HTML-in-Canvas going stable. Check your version, relaunch, and you are done in two minutes.
On desktop, open Chrome → Settings → About Chrome and check the version number — if it still shows 156, update and relaunch before your next browsing session.
Sources
- Chrome 157 Release Notes — Chrome Platform Status
- New to the web platform in October — web.dev
- Chrome 157 fixes 213 security issues, including 7 critical flaws — Malwarebytes
- Chrome 157 fixes over 200 security flaws, 7 of them critical — PCWorld
- Chrome 157 Is Out: 213 Security Fixes and What Is New — Chrome Geek
Comments
Post a Comment