# Enabling Custom Chrome Extensions in io.Connect Desktop

**URL:** <https://community.interop.io/t/enabling-custom-chrome-extensions-in-io-connect-desktop/636>\
**Category:** io.Connect Desktop\
**Tags:** iocd-10, iocd-9\
**Created:** [July 31, 2026, 2:05pm UTC](https://community.interop.io/t/enabling-custom-chrome-extensions-in-io-connect-desktop/636 "2026-07-31T14:05:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)\
**Post date:** [July 31, 2026, 2:05pm UTC](https://community.interop.io/t/enabling-custom-chrome-extensions-in-io-connect-desktop/636/1 "2026-07-31T14:05:27Z")

</div>

io.Connect Desktop supports loading additional Chrome extensions and Chrome DevTools extensions into the Chromium used by io.Connect Desktop.

Extensions are configured in the `system.json` system configuration file of io.Connect Desktop:

- To add regular Chrome extensions, use the `"extensions"` top-level key.
- To add Chrome DevTools extensions, use the `"devToolsExtensions"` top-level key.

Both properties accept a list of URLs pointing to the location of the browser extension.

## Q: How do I load a Chrome extension?

Add the extension to the `"extensions"` top-level key in `system.json`. The following example demonstrates how to configure io.Connect Desktop to load a regular Chrome extension:

```json
{
    "extensions": ["https://path-to-chrome-extension"]
}

```

## Q: How do I load an extension from a local file path?

_Available since io.Connect Desktop 9.7_

The `"extensions"` and `"devToolsExtensions"` top-level keys also accept a list of objects with the following properties:

| Property | Type | Description |
| --- | --- | --- |
| `"allowFileAccess"` | boolean | If `true`, will allow the extension to read local files over the `file://` protocol and to inject content scripts in local pages. It’s required to set this to `true` if you want to load an extension from a local file path. Defaults to `false`. |
| `"path"` | string | Path to the extension. |

The following example demonstrates how to allow access to the file system in order to load a Chrome extension from a local file path:

```json
{
    "extensions": [
        {
            "path": "C:/path-to-chrome-extension",
            "allowFileAccess": true
        }
    ]
}

```