when did edge retire is a question with a surprisingly clear answer: Microsoft's legacy EdgeHTML browser was formally retired on January 14, 2020, when Microsoft ended support for the classic version. The company then shipped the replacement — a Chromium-based Edge — to all supported Windows 10 devices through Windows Update.
That date matters more than most people realize. Millions of users opened their browsers one morning to find an entirely different application, and many wondered what happened to the version they had used since 2015. Businesses that had built internal tools on EdgeHTML suddenly faced compatibility decisions.
The change also reshaped the desktop browser market, pushing Chrome's engine into a third major browser and altering how developers approached cross-browser testing. For anyone asking when did edge retire, the answer carries real implications for security, compatibility, and planning.
Below you'll find the timeline, what actually changed, who was affected, and practical steps for verifying which version you're running today.
The Exact Retirement Date and What It Meant
January 14, 2020 is the date Microsoft officially ended support for the legacy EdgeHTML version of Edge. On that day, the company stopped shipping security updates for the classic browser and began automatic migration to the Chromium-based replacement. Microsoft documented the rollout in its official Microsoft Edge release notes.
The retirement happened in phases rather than as a single switch:
- April 2019: Microsoft announced the Chromium rebuild at its Build developer conference.
- Early 2020: The new Edge launched for general download.
- January 14, 2020: Support for classic Edge officially ended.
- Mid-to-late 2020: Automatic updates replaced classic Edge on Windows 10 machines.
Anyone tracking when did edge retire will find that the announcement-to-shutdown window was barely nine months — unusually fast for a product with hundreds of millions of installs. The timeline is one of the most searched aspects of when did edge retire, since many users remember the change happening gradually rather than on a single day.
How to apply this: Check your organization's browser inventory for any machines still pinned to legacy EdgeHTML, since those builds no longer receive security patches.
Why Microsoft Retired the Original Edge Browser
The short version: the original Edge couldn't keep pace with web standards because its rendering engine was isolated from the broader ecosystem. Most sites were built and tested against Chromium, and EdgeHTML users frequently ran into rendering bugs that site owners never saw.
Microsoft framed the decision around compatibility and fragmentation. As the company explained in its own announcement, the goal was to deliver "better compatibility for everyone" by aligning with the open-source Chromium project — the same engine behind Chrome and, later, other browsers. Understanding when did edge retire helps explain why the company chose a full replacement rather than incremental fixes.
The move also made commercial sense. Microsoft's browser share had stayed stubbornly low during the EdgeHTML era, and rebuilding on Chromium let the company focus on features like collections, vertical tabs, and enterprise policy controls rather than fighting engine-level compatibility battles.
For a decade-long view of browser market share, StatCounter is the standard reference, and its historical data shows Edge's share climbing meaningfully only after the Chromium switch.
When did edge retire questions often circle back to this root cause — it wasn't a branding decision, it was an engineering one. The answer to when did edge retire is inseparable from the compatibility failures that drove the decision.
How to apply this: If you maintain a website, re-test your pages in the current Edge release; anything that renders correctly in Chrome should render correctly now, which was not true before 2020.
Classic Edge vs. Chromium Edge: The Key Differences
The two browsers share a name but almost nothing else under the hood. This comparison explains why the retirement mattered so much for developers and IT teams. Knowing when did edge retire is only half the story; understanding what replaced it completes the picture.
| Feature | Classic Edge (retired) | Chromium Edge (current) | Action to take |
|---|---|---|---|
| Rendering engine | EdgeHTML | Blink (Chromium) | Re-test legacy web apps |
| Extension support | Very limited | Full Chrome Web Store access | Audit installed extensions |
| Update channel | Tied to Windows updates | Independent, frequent updates | Confirm auto-update is on |
| Platform support | Windows 10 only | Windows, macOS, Linux, mobile | Inventory all devices |
| Enterprise controls | Basic | Extensive group policy set | Review policy templates |
| Status | Unsupported since 2020 | Actively developed | Remove legacy shortcuts |
The practical takeaway is that "Edge" today is a different product that happens to reuse a familiar name. When did edge retire research usually surfaces this table's core point: the retirement was really a replacement, not a shutdown. People investigating when did edge retire often discover that the name continuity masks a complete technical overhaul.
How to apply this: In your browser compatibility matrix, list "Edge (Chromium)" and "Edge (legacy)" as separate entries so your testing plan reflects reality.
Who Was Affected by the Retirement
The biggest impact fell on three groups: enterprises with internal EdgeHTML-optimized applications, users on older Windows 10 builds that had delayed updates, and web developers who had written Edge-specific CSS or JavaScript workarounds.
For enterprises, the transition required auditing line-of-business apps. Microsoft published migration guidance for IT administrators, and its Microsoft Edge Enterprise documentation remains the reference point for policy and deployment questions. Many IT teams found themselves asking when did edge retire as part of their compliance and security planning.
For developers, the change was mostly liberating. Edge-specific hacks like the old -ms- CSS prefixes became unnecessary, and testing against Chrome effectively covered Edge too. One common scenario: a team that had maintained a separate IE/Edge testing pass discovered it could fold that work into its existing Chrome testing cycle.
When did edge retire timelines get discussed in IT planning meetings, the recurring theme was lead time — organizations that started auditing early reported a smoother migration than those that waited for the automatic update. The answer to when did edge retire became a benchmark for how quickly teams could adapt to platform changes.
How to apply this: If you still maintain any -ms- prefixed CSS or EdgeHTML-specific JavaScript, schedule a cleanup pass; those workarounds are dead weight now.
How to Confirm Which Edge Version You Have
This is the practical check most people actually need. Open Edge and look at the version number under Settings, then compare it to the current release. Anything in the 18.x range is the retired EdgeHTML build; modern versions run in the triple digits.
For a fuller picture of installed software across a fleet, tools like Google Analytics won't help — browser detection happens elsewhere — but a proper endpoint inventory tool will. On the web analytics side, checking your site's browser reports in a platform like Google Search Console shows which browsers actually visit your pages, which is useful for prioritizing compatibility work.
Microsoft's own release notes archive lists every version and its support status, which is the authoritative source for confirming whether a specific build is still maintained. Many support teams reference when did edge retire documentation when triaging browser-related tickets from users on older machines.
If you're still asking when did edge retire on a specific machine, the version number answers it faster than any documentation: 18.x means retired, anything newer means supported. The practical answer to when did edge retire is literally visible in your browser settings.
How to apply this: Pull a browser version report from your endpoint management tool this week and flag any device running an 18.x build for immediate update.
Frequently Asked Questions About when did edge retire
Did Edge stop working completely in 2020?
No — classic Edge continued to open for a while after support ended, but it stopped receiving security patches, making it unsafe for daily use. Microsoft gradually replaced it through Windows Update rather than disabling it overnight.
If you find an old machine still running EdgeHTML today, treat it as a security risk and migrate it, regardless of when did edge retire officially occurred.
Was Edge replaced or just updated?
It was genuinely replaced. The new Edge uses the Chromium engine, a different codebase entirely, even though the name and icon carried over. Bookmarks and some settings migrated automatically, but extensions and enterprise configurations often needed manual rework. Users expecting a routine update were surprised by how different the product felt.
This is why when did edge retire is often followed by questions about what actually changed.
Does the retirement affect Internet Explorer?
It's a separate story. Internet Explorer 11 was formally retired on June 15, 2022, more than two years after the classic Edge shutdown. Microsoft then introduced IE mode inside modern Edge for legacy sites. Confusing the two timelines is a common mistake — they involve different products, different dates, and different migration paths.
Can I still download the original Edge?
No legitimate source offers it. Microsoft removed classic Edge installers, and third-party downloads claiming to provide it should be treated as untrustworthy. If a tool or vendor insists you need the legacy browser, that's a strong signal the software needs replacing rather than accommodating.
The answer to when did edge retire is also the answer to why you can't get it back.
How did the retirement affect web developers' testing workflows?
Mostly by simplifying them. Before 2020, teams maintained separate test passes for EdgeHTML quirks; afterward, Chrome testing largely covered Edge. Some organizations still keep a lightweight Edge smoke test in their pipeline to catch browser-specific policy or extension behavior. If your CI pipeline still has an EdgeHTML stage, it's safe to retire it.
Knowing when did edge retire helps teams clean up obsolete testing infrastructure.
Key Takeaways and Your Next Step
The legacy EdgeHTML browser was retired on January 14, 2020, replaced by a Chromium-based build that shares only the name. Here's what to remember:
- Support for classic Edge ended in January 2020, with automatic migration following through Windows Update.
- The replacement is a different engine, so extensions and enterprise policies needed rework.
- Internet Explorer's 2022 retirement is a separate event — don't conflate them.
- Version 18.x means retired; anything newer means supported.
If you've been trying to pin down when did edge retire for an audit or migration plan, the answer is clear enough to act on today. Start by pulling a browser version report across your devices and flagging anything still on EdgeHTML — then schedule the update before it becomes a security finding.
The question of when did edge retire has a definitive answer, and now you know exactly what to do with it.
