The Broken Workflow
Google Chrome handles browser extensions similarly to how smartphones handle apps: it updates them entirely automatically in the background. Most of the time, this is ideal for security. However, if you rely on a highly specific, older version of an extension for a vital workflow—perhaps an outdated web scraper that interacts with a legacy corporate intranet, or a customized ad-blocker—Chrome’s automatic updates will constantly overwrite your preferred version with the newest release, instantly breaking your workflow and forcing you to manually downgrade the extension every single day.
Locking the Extension Version
To protect your specific software versions and stop Google Chrome from automatically updating a critical extension, you must utilize a slightly complex workaround involving Developer Mode and manual unpacking.
Chrome does not offer a simple “do not update” toggle for individual extensions. To freeze an extension, you must trick Chrome into thinking you are the developer actively building it. First, locate the `.crx` file (the installation package) for the specific older version of the extension you want to keep. Extract this `.crx` file into a standard folder on your desktop using an archive tool like 7-Zip. Next, open Chrome and navigate to chrome://extensions. In the top-right corner, turn Developer mode ON. Click the Load unpacked button that appears in the top-left. Select the folder where you extracted the extension. Because Chrome now considers this a “local” extension that you are theoretically programming yourself, it will completely bypass the Web Store update checks, locking the extension at that exact version forever.