Google Chrome’s inline installation enforcement refers to the policy that blocks websites from installing extensions through a scripted prompt, requiring all installs to go through the Chrome Web Store. This article explains what triggered the change, how it works, what it means for users and developers, and how to handle it.
Background: Why Chrome Blocked Inline Installation
Inline installation was a feature that let websites trigger an extension install dialog directly from their own pages using a small JavaScript call. It was convenient for developers, but it also became a vector for deceptive practices—sites could trick users into installing extensions that changed search engines, injected ads, or collected browsing data. Google phased out inline installation starting in 2018, with the final removal in Chrome 75 for stable desktop users. The company’s stated goal was to reduce the number of unwanted extensions and to make the install process more transparent by forcing users to see the Chrome Web Store listing, where they can read reviews, check permissions, and see the developer’s information.
How Inline Installation Enforcement Works Now
In current Chrome versions, any attempt to call chrome.webstore.install() from a website is ignored, and the API has been removed entirely. Instead, the only supported way to install an extension is to visit its Chrome Web Store page and click the “Add to Chrome” button. When a user clicks a link to a Web Store listing, Chrome opens the store page in a new tab, and the user must explicitly confirm the install. There is no way for a website to bypass this flow—even if a user has enabled “Allow extensions from other stores” in developer mode, the inline install API simply does not exist anymore.
What This Means for Users
For everyday users, the enforcement means you will no longer see a popup asking “Add extension?” while you are on an arbitrary website. Any site that claims to install an extension directly is either using an outdated method (which will fail) or is trying to trick you into downloading a file that is not a real Chrome extension. The change also means you can verify an extension’s legitimacy before installing: you can see the total number of users, read reviews, and check the permission warnings on the Web Store page. If a site tells you to “enable inline installation” or “allow this site to install extensions,” that is a red flag—Chrome no longer supports that feature, and the site may be attempting a workaround that could harm your browser.
What This Means for Developers
Developers who previously relied on inline install links must update their websites. The old chrome.webstore.install() method is gone, so the only compliant approach is to link directly to the extension’s Chrome Web Store URL (e.g., https://chrome.google.com/webstore/detail/your-extension-id). You can still use a button on your site that says “Install Extension,” but it must be a simple hyperlink that opens the Web Store page—not a scripted install. Some developers use a “Install from Web Store” badge or a custom button that redirects to the store. There is no legitimate way to trigger the install without user navigation to the store.
Common Misconceptions and Troubleshooting
One common misconception is that inline installation is still possible if you enable “Developer mode” in chrome://extensions. That is not true—developer mode only allows loading unpacked extensions from your local machine, not from a website. Another misconception is that the enforcement is a bug or a temporary change; it is permanent. If you are a user and you see a site that says “Click here to install our extension” and nothing happens, it is because the site is using the old API. If you are a developer and your install link does not work, double-check that the URL points to the correct Web Store listing and that the extension ID is correct. Also, ensure that the extension is not set to “Unlisted” (which still works) or “Private” (which only works for the owner).
Alternatives to Inline Installation
For developers who want a smoother install experience, the only alternative is to guide users to the Web Store. You can create a landing page with a clear call-to-action button that links to your store listing. Some developers use a “Install” button that opens a popup with the store URL, but the actual install must happen on the store page. There is no official API to install an extension silently or to check if a user already has your extension installed from a website (the management API is only available to extensions themselves, not to web pages). The best practice is to make your Web Store listing attractive with clear screenshots and a concise description, and to provide a direct link on your site and in your documentation.
Frequently Asked Questions
Why did Google remove inline installation?
Google removed inline installation to reduce the number of malicious or deceptive extensions. The old API allowed websites to prompt users with an install dialog without showing the Web Store page, which made it easier for bad actors to trick users into installing unwanted software. Forcing the install through the Web Store gives users a chance to review the extension and its permissions before committing.
Can I still install extensions from a website?
Yes, but only by linking to the Chrome Web Store. A website can have a button that says “Install” and that button must open the store listing in a new tab. The user then clicks “Add to Chrome” on the store page. There is no way to install an extension directly from a website without visiting the store.
What if I see a site that says “Enable inline installation”?
That site is using outdated information or attempting a workaround. Chrome no longer supports inline installation, so there is no setting to enable it. If a site instructs you to do that, it is likely a scam or a phishing attempt. Do not follow such instructions, and do not download any files from the site.
How do I install an extension that is not on the Chrome Web Store?
You can load an unpacked extension in developer mode, but that is for development purposes only. For a normal user, the only safe way is to install from the Web Store. If an extension is not listed there, it may be outdated or unsafe. Loading unpacked extensions from unknown sources can compromise your browser and your data.
Does inline installation enforcement affect Chrome for Enterprise?
Yes, the enforcement applies to all Chrome desktop versions. Enterprise administrators can use policy settings to force-install extensions via the ExtensionInstallForcelist policy, which bypasses the Web Store prompt for managed devices. However, that is a separate mechanism and does not restore the old inline install API for websites.
Will inline installation ever come back?
There is no indication that Google plans to reinstate inline installation. The company has consistently emphasized security and transparency in extension distribution, and the Web Store is the only supported channel. Developers should design their websites accordingly.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Hogwarts Legacy Microsoft Visual C Runtime Error Fix
- Set Up UPI Payments Through WhatsApp
- Pair Oppo Enco Earbuds with Android, iPhone & Windows
- Fix Administrator Account Disabled Error in Windows 11
- How to Play Kodi on Smart TV from PC
- Factory Reset on Samsung Galaxy: What It Erases