A look at an early version of Microsoft's new Chromium-powered Edge browser
This could be your new default browser on Windows — Microsoft is rebuilding its Edge browser on Chromium. The software maker has been testing versions of this browser internally at Microsoft …
Context & Ripple Effects
Microsoft confirmed in December that it would rebuild Edge on Google's open source Chromium project and ship it beyond Windows 10 to Windows 7, Windows 8, and macOS — an admission that its own EdgeHTML engine could not sustain the browser's position as the Windows default. The March build now circulating is the first tangible evidence of that rebuild in practice.
The early version pairs Chrome extension support and a recognizably Chrome-flavored interface with leftover Edge touches like dark mode, matching what The Verge found when it examined the early build's extension support and mixed UI. A later report adds that launch will include an IE mode, privacy tools, and Collections, signaling Microsoft intends this for enterprises still pinned to legacy web apps.
First-order effects
- Microsoft's internal testers get a browser that runs Chrome extensions out of the box, removing the single biggest practical reason users abandoned original Edge.
- Windows 10's default browser slot is being prepared for a Chromium-powered replacement, per the December reporting, so every future Windows install ships Google's rendering engine under Microsoft branding.
Second-order effects
- Google gains one of the world's largest software vendors as a de facto Chromium distributor and contributor, extending the engine's reach into enterprise Windows fleets and onto macOS.
- Web developers' remaining incentive to test against EdgeHTML collapses, since the new Edge renders like Chrome — engine-specific QA work for Microsoft's old browser becomes obsolete.
Third-order effects
- If the pattern holds, the web converges further on a single dominant open-source engine, leaving engine diversity to Apple's WebKit and Firefox's Gecko while competition shifts to the browser shell above the engine — features like Collections, privacy tooling, and sync rather than rendering.
- Microsoft trading its own engine for reach echoes a broader pattern of platform owners adopting rivals' infrastructure to stay relevant where they lost — a structural retreat from building foundational web technology toward curating distribution on top of it.
The trend: Browser engines are consolidating around Google's Chromium, with Microsoft's defection converting the last major holdout from engine competitor into engine distributor.