Create and publish custom Chrome apps & extensions
Sometimes, you might not be able to find an app or extension in the Chrome Web Store that meets your users’ needs. If that happens, you can create your own custom app or extension that users can add to their device running Chrome OS or Chrome Browser. For example, as an administrator, you can automatically install a custom bookmark app that links to your HR system on users’ Chrome devices.
Before you begin
- If your app or extension links to a website as a target in the manifest, use Google Search Console to verify that your organization owns the website.
- For privately hosted apps and extensions, control which users can publish them to the Chrome Web Store. You can also skip verification for websites that your organization doesn’t own. For details, read Chrome Web Store Permissions.
Step 1: Build the app or extension
As a developer, you can build an app or extension, such as the example bookmark app provided in the steps below. For instructions on building more advanced Chrome apps and extensions, see the Getting Started Tutorial.
- On a computer, create a folder for the app or extension files, naming it the same as the app or extension name.
- Create the manifest.
- In the app or extension folder, save the file as manifest.json.
- Create the logo.
- Create a 128p by 128p logo for your app.
- In the app folder, save the file as 128.png.
Step 2: Test the app or extension
As a developer, you can test your app or extension to make sure it works in Chrome Browser or on a device running Chrome OS.
- Choose the type of test device you need:
- Apps—Sign in to your Google Account on a Chrome device.
- Extensions—Sign in to your Google Account on a Chrome device or Chrome Browser on a Windows®, Mac®, or Linux® computer.
- Save the app or extension folder on your test device.
- Go to chrome://extensions/.
- At the top right, turn on Developer mode.
- Click Load unpacked.
- Find and select the app or extension folder.
- Open a new tab in Chromeclick Appsclick the app or extension. Make sure it loads and works correctly.
- If needed, make changes in the manifest.json file, host the app folder, and retest it. Repeat until the app or extension works correctly.
Troubleshoot problems with your app or extension using Chrome logs:
- In Chrome, click MoreMore toolsDeveloper Tools.
- Verify your information. For example, check for the correct the app ID and version number.
Step 3: (Optional) Create an app collection
As an admin, you can optionally create an app collection for your organization. Then, you can recommend Chrome apps and extensions that your users can browse and install. For details, see Create a Chrome app collection.
As a developer, you can choose to make apps and extensions available for everyone or control who can install them. There are 3 ways you can publish app and extensions in the Chrome Web Store:
- Public—Everyone can see and install the app or extension.
- Unlisted—Only users with the app or extension link can see and install it. The app doesn’t appear in the Chrome Web Store search results. You can share the app or extension link with users outside your domain.
- Private—Only users in your domain can see and install the app or extension. Or, you can restrict the app or extension to trusted testers that you specified in your developer dashboard.
To add an app or extension in the Chrome Web Store, zip the folder that contains your files. Then, Publish it in the Chrome Web Store.
Step 5: Manage the app or extension
As an admin, you can use the Google Admin console to set policies that control the use of apps and extensions on Chrome devices and Chrome Browser on Windows, Mac, or Linux computers. For details, see Set Chrome policies for one app and Set a Chrome policy for multiple apps.
As a Microsoft® Windows® administrator, you can use Group Policy to set policies that control the use of apps and extensions in Chrome Browser on managed Windows computers. For information about how to install and configure Chrome policy templates, see Set Chrome Browser policies on managed PCs.