---
myst:
  html_meta:
    "description lang=en": "Install custom unsigned chrome extensions automatically on your workspace when it spawns up."
    "keywords": "Kasm, How to, How-to, Chrome, Extensions, Custom, Unsigned"
    "property=og:locale": "en_US"
---
```{title} Installing Custom Unsigned Chrome Extensions
```

# Custom Chrome Extensions

Administrators may need to force install custom chrome extensions automatically when launching a new instance of a workspace. This guide will cover how to achieve this with {doc}`File Mapping</guide/file_mappings>`.

## Video Tutorial

This video will walk you through installing a custom unsigned chrome extension on your workspace.

```{raw} html
<iframe src="https://www.youtube.com/embed/H70iPS_DNnQ?si=Y7LI69Eg39uibGCp" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
```

## Installing Custom Chrome Extensions on your Workspace

1\. Zip your extension's source code directory. Make sure you zip the directory and not the source files.

```{figure} /images/custom_chrome_extensions/zip_source_files.png
:align: center
**Zip source code files with zip command**
```

2\. In your Kasm dashboard, go to "Admin" -> "Workspaces" -> "Edit" -> "File Mapping" -> "Add File Mapping"

Set the type to "File Upload" and give it an appropriate name and description. Set the "Destination Path" to something like `/tmp/extension/your-extension.zip`

Set both Writable and Executable to Disabled and save the changes.

```{figure} /images/custom_chrome_extensions/file_mapping.png
:align: center
**Workspace-level file mapping settings**
```

```{note}
File Mapping can be set at both the workspace level and at the group level.
```

3\. In your Workspace's Docker Run Config Override, use the following config (make sure to replace it with your extension's name and path):

```{code-block} JSON
{
  "hostname": "kasm",
  "environment": {
    "APP_ARGS": "--load-extension=/tmp/extension/your-extension"
  }
}
```

```{figure} /images/custom_chrome_extensions/run_config.png
:align: center
**Docker run config override**
```

4\. In your Workspace's Docker Exec Config, use the following config (make sure to replace it with your extension's name and path):

```{code-block} JSON
{
  "first_launch": {
    "user": "root",
    "cmd": "bash -c 'unzip /tmp/extension/simple-chrome-extension-master.zip -d /tmp/extension/'"
  }
}
```

```{figure} /images/custom_chrome_extensions/exec_config.png
:align: center
**Docker exec config**
```

Your workspace will now have the custom extension loaded to Google Chrome.

```{figure} /images/custom_chrome_extensions/extension.png
:align: center
**Custom chrome extension in action**
```