Do Chrome Extensions That Claim to Run Silverlight Actually Work?
No Chrome extension can genuinely run Silverlight inside Chrome. Extensions are built from web technologies — JavaScript, HTML, CSS — and cannot load the native plugin code Silverlight consists of; the browser's ability to host such plugins was removed from Chrome entirely in September 2015, per the Chromium project's own deprecation guide. Anything in an extension store promising "Silverlight for Chrome" is either doing something other than what the name implies, or doing nothing at all.
Extensions and plugins are different things
The words get used interchangeably, but technically they're separate mechanisms. A plugin, as MDN's glossary defines it, was a piece of compiled native code the browser loaded to render content it couldn't handle itself — Silverlight, Flash, Java applets. An extension runs inside the browser's own sandbox, written in the same languages as web pages, with no path to executing an arbitrary native runtime like Silverlight's.
That distinction is exactly why Google's removal was final. As explained in the Final Countdown for NPAPI announcement, plugins ran with capabilities the web's security model was moving away from. Extensions were deliberately designed not to have those capabilities — so they can't be used as a back door to restore them. Background on the plugin architecture itself is in what was NPAPI, and why every browser dropped it.
What 'Silverlight enabler' extensions actually do
Extensions marketed around Silverlight have historically fallen into a few buckets:
- Launchers. Some detect a Silverlight page and hand the URL to a different program outside Chrome — historically Internet Explorer, today typically Microsoft Edge running IE mode. The content never runs in Chrome; the extension is a shortcut to another browser.
- User-agent tricks. Some change what the browser reports about itself so a website stops nagging about plugins. This silences the warning without making the app work.
- Leftovers and junk. Some are abandoned remnants of the pre-2015 era, or low-quality listings trading on a familiar search term. An extension that can't possibly deliver what its name promises deserves skepticism about what it does instead.
A related dead end: Chrome's replacement plugin interface, PPAPI, was never opened to Silverlight — we explain that in NPAPI vs. PPAPI: what's the difference.
The legitimate route for a legacy app
If you need a Silverlight app for work, the supported answer isn't in the Chrome Web Store. Microsoft's documented compatibility path is Internet Explorer mode in Edge, which re-creates the legacy IE environment for specific sites an administrator lists. It has real caveats for Silverlight specifically — covered in does Edge's IE mode run Silverlight — but it is an actual mechanism, maintained by an actual vendor, rather than a browser add-on making promises the platform can't keep.
Bottom line
An extension can redirect you, relabel your browser, or open something else on your machine — but it cannot resurrect a native plugin runtime the browser no longer knows how to load. If a listing claims otherwise, the claim is the first thing to distrust.