> [!WARNING]
> **Warning:** You're viewing the deprecated Manifest V2 version of this article. See [Manifest V3 - Extension hosting](https://developer.chrome.com/docs/extensions/how-to/distribute.md.txt) for the MV3 equivalent. The Chrome Web Store no longer accepts Manifest V2 extensions. Follow the [Manifest V3 Migration guide](https://developer.chrome.com/docs/extensions/develop/migrate.md.txt) to convert your extension to Manifest V3.

Most extensions are hosted in the [Chrome Web Store](https://chrome.google.com/webstore/category/extensions) to best [protect users from malicious
extensions](http://blog.chromium.org/2015/05/continuing-to-protect-chrome-users-from.html).

## Hosting

All extensions are distributed to users as a special ZIP file with a `.crx` suffix. Extensions
hosted in the [Chrome Web Store](https://developer.chrome.com/docs/webstore) are uploaded through the [Developer Dashboard](https://chrome.google.com/webstore/developer/dashboard) as `.zip`
files. The [publishing](https://developer.chrome.com/docs/webstore/publish.md.txt) process automatically converts the `.zip` into a `.crx` file.

There are three exceptions to the Chrome Web Store hosting rule:

1. Extensions that are distributed through the [enterprise policy](https://support.google.com/chrome/a/answer/7666985).
2. Unpacked extension directories from a local machine while in [developer mode](https://developer.chrome.com/docs/extensions/mv2/getstarted.md.txt#unpacked).
3. [Linux installation](https://developer.chrome.com/docs/extensions/mv2/linux_hosting).

[Read more about the hosting policy](https://developer.chrome.com/docs/extensions/mv2/hosting_changes).

## Updating

The Chrome Browser periodically checks for new versions of installed extensions and updates them
without user intervention.

To release an update to an extension, increase the number in the [`version`](https://developer.chrome.com/docs/extensions/mv2/manifest/version.md.txt) field of the
manifest.

```json
{
  ...
  "version": "1.5",
  ...
}
```

```json
{
  ...
  "version": "1.6",
  ...
}
```

Convert the updated extension directory into a ZIP file and locate the old version in the [Developer
Dashboard](https://chrome.google.com/webstore/developer/dashboard). Select **Edit** , upload the new package, and hit **Publish**. The browser will
automatically update the extension for users after the new version is published.