SAN FRANCISCO, April 9, 2026, 07:32 PDT
Google pushed Chrome 147 to stable for desktop and Android earlier this week, and the very next day, Chrome 148 beta landed on Android. The back-to-back updates step up network protections in the live release, while the beta build gets fresh hardware-focused features.
It’s relevant now as Google tweaks how the browser shields local devices and how web apps get access. Most users will barely notice 147 arriving—it’s mostly security and stability under the hood. But for developers, the 148 beta hints at Android browsers stepping up to handle tasks that used to demand native apps.
Google’s Chrome 147 is heading out now, hitting Android as version 147.0.7727.49, while desktop users pick up 147.0.7727.55 or .56. According to the company, the Android build packs the same security patches as its desktop twin, except where specified.
Chrome 147 brings a tighter grip on Local Network Access. According to release notes, WebSocket connections to local addresses now hit a permission prompt, and WebTransport—Google’s low-latency protocol—runs into the same hurdle. There’s also a Web Printing API added, but only for Isolated Web Apps, Chrome’s signed, high-trust app format.
Chrome 148 beta for Android is taking a different tack. Rachel Andrew, posting on Chrome for Developers, noted the Web Serial API “provides an interface for connecting to serial devices.” With Google now enabling the feature on Android, browser-based control becomes possible for things like robotics kits, 3D printers, mills—basically any gear using a USB or Bluetooth serial connection. Chrome for Developers
After years on the sidelines due to process-lifecycle issues, Google is flipping SharedWorker back on for Android devices in Chrome 148 beta. The feature allows several pages to tap a single background JavaScript worker. This beta introduces an extendedLifetime option—a tweak designed so that worker can stick around even after all active clients have closed out.
The latest drops coincide with a new look for Chrome on Android. Google’s been pushing out its Material 3 Expressive redesign for settings—think card-like sections, gentler color tones, and more rounded corners. It’s a shift that makes Chrome resemble Android’s Settings more closely. Mindy Brooks, Google’s VP of product management and user experiences for Android, called Material 3 Expressive “one of our biggest updates in years.” NewsBytes
Chrome keeps setting the tempo, not just for Google. Opera 130 landed on April 8, running on Chromium 146. Microsoft’s schedule points to Edge 147 beginning stable rollout the week of April 9; Edge, according to the company, picks up almost every web-platform change Chromium gets.
Still, not everything is straightforward. Google indicated Chrome 147 for Android will roll out on Google Play gradually, and the Material 3 redesign is arriving via a server-side push. Andrew noted Google hasn’t finished digging into Android process behavior, despite SharedWorker’s return. Local-network permission prompts debuting in 147 may mean some enterprise and device-control web apps will need tweaks.
Most users won’t notice much in Chrome 147—just another round of stability and security fixes, nothing flashy. But for developers, this week’s release marks some real changes: stable builds now lock down local network access, the beta branch widens hardware access and expands background processes, and Chrome for Android’s UI edges closer to Google’s latest Android style.
