Google disables inline installation for Chrome extensions, which let users install them from third-party sites; existing extensions will be affected in 3 months
Emil Protalinski / VentureBeat :
Context & Ripple Effects
This 2018 decision is an early move in a decade-long tightening of Google's grip on the Chrome extension pipeline. It followed the ad-injector purge that saw Google disable 192 deceptive extensions after finding them on 5% of visitors' machines, and it set the template for later restrictions on what extensions can do and how they are distributed.
The arc since has been consistent: new data-access policies limiting what extensions can read, ad blocking narrowed to enterprise users, paid extensions shut down after fraud, the malware-driven delisting of The Great Suspender, and finally the disablement of Manifest V2 extensions. Killing inline installation is the distribution-side bookend: Google moves every install through its own storefront.
First-order effects
- Extension developers lose third-party sites as an install channel overnight — any 'Add to Chrome' button on an external page stops working once the change lands, with existing installs affected within three months.
- Users who installed extensions from developer sites or bundled downloads must now re-acquire them through the Chrome Web Store, where Google's review process is the only gate.
Second-order effects
- The Chrome Web Store becomes the sole chokepoint for extension distribution, shifting power over discoverability, review timelines, and policy enforcement entirely to Google — developers with storefront-hostile business models (ad injectors, data brokers) are squeezed out first.
- Rival browsers gain a positioning lever: openness of extension installation becomes a differentiator against Chrome's walled garden.
Third-order effects
- If the pattern holds, browser extension ecosystems consolidate around vendor-controlled storefronts with progressively narrower APIs — the endpoint visible in the later Manifest V2 cutoff — making platform policy, not web standards, the real regulator of browser add-on capabilities.
The trend: Browser vendors are steadily converting open extension ecosystems into gated platforms, with each policy round — inline installs, data access, paid extensions, Manifest versions — narrowing what runs outside the vendor's own store.