You might also need a screenshot if you publish it as unlisted or public.) (Depending on your extension, you might have other files, but this is the minimum needed to add an extension to the Chrome Web Store. To do so, you’ll need at least the following:Ī manifest file saved as manifest.json (This is a JSON file that describes what the extension does).Ī 128-pixel by 128-pixel logo, saved as 128.png. Once you’ve created your extension (if you need to, check out this tutorial on writing extensions), it’s time to package it up to add it to the Chrome Web Store. Note that you’ll need to request a developer account (if you don’t have one already) and pay a small, one-time fee to publish extensions. In this post, I’ll provide some guidance on how to get this done. But to use these methods, the extension needs to be present in the Chrome Web Store. Once the extension is created, the question becomes: How do you deploy it to your users? Most administrators use the Extension Install Forcelist policy, either via Chrome Browser Cloud Management or Microsoft Group Policy Object (GPO), to remotely install extensions to their users. I’ve written about the different methods of managing third-party extensions, but sometimes enterprises want to create their own custom extensions, so they can meet the exact needs of their users. IT administrators often need to manage extensions to protect and enable their employees who use Chrome.

Web chrome store