Category filter

Custom configuration profile to add Chrome extensions on macOS devices

Google Chrome extensions are small add-on applications and features that can be installed in Chrome to customize and enhance the browsing experience. They are essentially small programs integrated into the Google Chrome app and serve a single purpose. For example, a grammar checker extension is used to correct typos, and an ad blocker extension can remove unnecessary ads from popping up while web surfing, etc. Instead of manually adding Chrome extensions from the Chrome Web Store, the user can apply a custom configuration profile to add the extensions on macOS devices. IT admins can remotely deploy this custom configuration profile to multiple macOS devices in their organization using Hexnode’s Deploy Custom Configuration feature.


  • This configuration profile is supported on macOS 10.13 and later devices enrolled in Hexnode.
  • Ensure that the Google Chrome app is already installed on the device.


The configuration profile provided below is adapted from a third-party open-source site.

Configuration profile to add Chrome extensions

Replace CONFIGURATION NAME with the name you want the configuration to be called. Also replace the PLACE EXTENSION IDENTIFIER HERE with the ID of the extension you want to add in the endpoint’s Chrome browser. To get the identifier, go to the extension in the Chrome Web Store and get it from your URL. For example, the identifier of the Google Translate extension looks like this:

Retrieve the ID of the Chrome extension from its URL and add it to the configuration profile for Mac

What happens at the device end?

Once the policy and custom configuration are associated, click on the jigsaw icon at the top-right of the opened Chrome window to bring up the extensions manager. You can see the configured extension added to the list.

Extensions appear in the Chrome Extensions menu when you add it using configuration profiles for Mac


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager, or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across macOS devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • It is recommended to manually validate the configuration profile execution on a system before executing the action in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository