Microsoft's Chromium-based Edge browser to be generally available on Jan. 15, with new privacy features including InPrivate browsing and tracking prevention
After launching a beta test for the new Chromium Edge in September, Microsoft is now gearing up to officially launch the browser on January 15th, 2020.
Context & Ripple Effects
Microsoft's January 15 general-availability date closes out a year-long rebuild of Edge on Google's Chromium engine. Early builds leaked in March already showed support for Chrome extensions and a mixed Chrome/Edge UI (an early Chromium-powered Edge build), and by May Microsoft had committed to shipping an IE mode, privacy tools, and Collections at launch (the May feature roadmap).
The GA date matters because it moves Edge from a controlled beta to a product Microsoft can push broadly — and the new tracking prevention plus InPrivate features signal that privacy is being positioned as the wedge against Chrome rather than rendering performance.
First-order effects
- Windows users get a production browser on Jan. 15 that runs existing Chrome extensions — removing the single biggest practical barrier to switching from Chrome.
- Enterprise IT departments gain the previously promised IE mode, letting legacy intranet apps run inside the Chromium-based Edge instead of maintaining separate browsers.
Second-order effects
- Google now faces its chief OS rival shipping a first-party Chromium browser with tracking prevention turned toward ad-tech — pressure that lands directly on Chrome's own privacy roadmap.
- Extension developers get one codebase reaching both Chrome and Edge users, lowering the cost of cross-browser distribution and nudging the add-on ecosystem toward Chromium-only targets.
Third-order effects
- If Edge gains share on the back of extension compatibility and privacy defaults, browser competition consolidates into a fight over features and data handling layered on a shared Chromium core — with engine diversity itself becoming the structural casualty.
- Tracking prevention shipped by default in a major browser strengthens the case for regulators and platform vendors to treat blocking-by-default as the baseline expectation rather than an opt-in setting.
The trend: Browser competition is shifting from rendering engines to privacy defaults and extension ecosystems atop a shared Chromium base, with Microsoft's launch accelerating that convergence.