Install Google Chrome Extensions on macOS with Applivery

The recommended way to install Google Chrome extensions on macOS is to import a Plist with the ExtensionInstallForcelist key (com.google.Chrome payload) into a macOS Policy, just like the Chrome homepage. Applivery scripts help you verify the result or serve as an alternative when you can't use a Policy.

Before you start

• macOS Devices managed by Applivery, with Google Chrome installed.

• The extension ID.

• Access to the Applivery Dashboard with permission to edit Policies and, if you use scripts, the Resources section.

How to get an extension's ID

The ID is a string of 32 lowercase letters (from a to p) that uniquely identifies the extension. You can get it in three ways:

1. From Chrome Web Store. Open the extension's page and copy the last part of the URL: https://chromewebstore.google.com/detail/extension-name/<ID>

2. From chrome://extensions. Turn on Developer mode (top-right corner). Each installed extension shows its ID below the description.

3. From Terminal on a Mac with the extension installed. The folder names in this directory are the IDs:

   ls ~/Library/Application\ Support/Google/Chrome/Default/Extensions/
   

   If you use several Chrome profiles, replace Default with the profile name (for example, Profile 1).

Recommended method: Policy with a Plist

Prepare the Plist

The following payload force-installs an extension. Replace EXTENSION_ID with your extension's ID:

	PayloadContent
	
			ExtensionInstallForcelist
			
				EXTENSION_ID;https://clients2.google.com/service/update2/crx
			
			PayloadDisplayName
			Google Chrome - Extensions
			PayloadIdentifier
			com.google.Chrome.extensions.REPLACE-UUID
			PayloadType
			com.google.Chrome
			PayloadUUID
			REPLACE-UUID
			PayloadVersion
			1
	

Each list entry has the format EXTENSION_ID;UPDATE_URL. To install several extensions, add one <string> per extension inside the same <array>.

What to put in the REPLACE-UUID placeholders

Replace each REPLACE-UUID with a UUID, a unique identifier with this format: 754C545B-75B5-4E50-927D-3BC06EBD47E0. There are two places:

• PayloadUUID: a full UUID.

• PayloadIdentifier: com.google.Chrome.extensions. followed by a UUID. It can be the same as the PayloadUUID one or a different one.

To generate one from Terminal on a Mac (each run returns a new one):

uuidgen

For example, if uuidgen returns A1B2C3D4-E5F6-4A7B-8C9D-0E1F2A3B4C5D:

<key>PayloadIdentifier</key>
<string>com.google.Chrome.extensions.A1B2C3D4-E5F6-4A7B-8C9D-0E1F2A3B4C5D</string>
<key>PayloadUUID</key>
<string>A1B2C3D4-E5F6-4A7B-8C9D-0E1F2A3B4C5D</string>

Any UUID v4 generator works too.

When to generate a new UUID

You don't need a new Plist or UUID for every extension.

Import it into an Applivery Policy

1

Open the Policy

Once in the Applivery Dashboard, go to any of your Policies 1 or create a new one.

2

Import the Plist

Click the + Add configuration button on the left-hand menu, then click + Import 2.

Paste the Plist or use the Upload XML button to upload the file.

3

Save

Save your changes.

Verify the result

Once the Policy has synced to the Device, open Chrome and check:

1. chrome://policy → click Reload policies and confirm that ExtensionInstallForcelist appears with the OK status.

2. chrome://extensions → the extension should appear installed and marked as managed by your organization.

Pin the extension to the toolbar

A force-installed extension is available in Chrome's extensions menu (the puzzle icon), but it isn't pinned to the toolbar. To have it pinned from the start, use the ExtensionSettings key with the toolbar_pin option.

ExtensionSettings groups all the settings for each extension in a dictionary, identified by its ID. It lets you force-install the extension and pin it to the toolbar in the same block, so it replaces ExtensionInstallForcelist for those extensions:

	PayloadContent
	
			ExtensionSettings
			
				aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
				
					installation_mode
					force_installed
					update_url
					https://clients2.google.com/service/update2/crx
					toolbar_pin
					force_pinned
				
			
			PayloadDisplayName
			Google Chrome - Extensions
			PayloadIdentifier
			com.google.Chrome.extensions.REPLACE-UUID
			PayloadType
			com.google.Chrome
			PayloadUUID
			REPLACE-UUID
			PayloadVersion
			1
	

To configure several extensions, add one key per ID inside the ExtensionSettings dictionary, each with its own <dict>. Import the Plist into the Policy just like with ExtensionInstallForcelist.

The extension ends up installed and pinned to the Google Chrome toolbar.

Using scripts

Applivery scripts (Bash on macOS) aren't needed to install the extension with the method above, but they're useful in two cases. You'll find more details in Scripts.

Verification script

Checks that the Plist with the extension has reached the Mac. Pass the extension ID as an argument (in double quotes).

#!/bin/bash
# Usage: the first argument is the Chrome extension ID
EXT_ID="$1"
PLIST="/Library/Managed Preferences/com.google.Chrome.plist"

if [ -z "$EXT_ID" ]; then
  echo "Missing the extension ID as an argument."
  exit 2
fi

if [ ! -f "$PLIST" ]; then
  echo "$PLIST does not exist: the Chrome configuration is not applied."
  exit 1
fi

if /usr/libexec/PlistBuddy -c "Print :ExtensionInstallForcelist" "$PLIST" 2>/dev/null | grep -q "$EXT_ID"; then
  echo "OK: extension $EXT_ID is in ExtensionInstallForcelist."
  exit 0
else
  echo "Extension $EXT_ID is NOT in ExtensionInstallForcelist."
  exit 1
fi

Alternative script: install without a Policy (External Extensions)

If you can't use a Plist, Chrome supports registering extensions externally through one JSON file per extension in a system path. This script creates it:

#!/bin/bash
# Usage: the first argument is the Chrome extension ID
EXT_ID="$1"
DIR="/Library/Application Support/Google/Chrome/External Extensions"

if ! [[ "$EXT_ID" =~ ^[a-p]{32}$ ]]; then
  echo "Invalid extension ID: $EXT_ID"
  exit 2
fi

mkdir -p "$DIR"
cat > "$DIR/$EXT_ID.json" <<EOF
{
  "external_update_url": "https://clients2.google.com/service/update2/crx"
}
EOF
chmod 644 "$DIR/$EXT_ID.json"
echo "Extension $EXT_ID registered. Restart Chrome so it detects it."

Troubleshooting