Silverlight Is Officially Dead, and Almost Nobody Noticed
Microsoft ended support for Silverlight on October 12, 2021, quietly closing the book on the browser plugin era that Flash's death began.
Microsoft pulled the plug on Silverlight support this week, and if you didn’t hear about it, that’s kind of the point. October 12 came and went, and one of the plugins that used to matter a great deal to how the web worked just… stopped being supported. No fanfare, no farewell blog post that anyone’s talking about, nothing like the send-off Flash got back in December 2020.
For anyone who wasn’t building web apps in the early 2010s, it’s worth explaining why this even mattered. Silverlight was Microsoft’s answer to Flash — a browser plugin for running rich, animated, interactive applications without relying on plain HTML and JavaScript, which at the time couldn’t do a lot of what developers wanted. Netflix famously used Silverlight to power its streaming player for years. A huge number of internal enterprise tools, especially in finance and healthcare, were built on it too, because it played nicely with .NET and gave Windows shops a familiar programming model.
Then HTML5 happened. Video tags, canvas, WebGL, and a browser ecosystem that got fast enough and capable enough to do natively what plugins used to do by force. Netflix migrated off Silverlight years ago. Most consumer-facing uses evaporated well before this month’s announcement — this is really just Microsoft formally closing a door that most people walked away from a long time ago.
The plugin era is basically over
What’s interesting is watching this happen right on the heels of Flash’s death. Two of the biggest browser plugins of the 2000s and 2010s, gone within about ten months of each other. Between them, Flash and Silverlight probably accounted for a huge share of “rich” web content for over a decade — games, video players, animations, dashboards, whole enterprise apps. Now that category of software is just… the web platform itself. Modern JavaScript frameworks and native browser APIs do the job.
There’s a real lesson here for anyone maintaining old software: if your enterprise app still depends on Silverlight, you’re now running on something with zero official support, zero security patches, and a shrinking pool of browsers even willing to run legacy plugin architectures. If you didn’t already have a migration plan, you needed one months ago. I’d bet there are still a surprising number of internal line-of-business tools out there quietly running on Silverlight in IE11 compatibility mode somewhere in a corporate network, and those teams have some uncomfortable conversations ahead.
It’s a small story in the grand scheme of things, but it’s a tidy bookend. The plugin-based web — the one where you needed a special runtime bolted onto your browser to do anything beyond static pages — is finished. What’s left is the open web platform, for better or worse, doing the job plugins used to do. Given how much pain plugins caused over the years, from security holes to crashes to “please update Flash Player” prompts, I don’t think many developers will miss them.