> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/configuration/pluginssettings.md).

# Plugins Settings

The Plugins settings allow you to configure how Umbraco handles plugins. You can configure which file extensions plugins are allowed to serve, and a cache buster for plugin assets.

## Browsable file extensions

This setting allows you to customize what file types plugins are allowed to use for the front end. The default configuration looks like this:

{% code title="appsettings.json" %}

```json
"Umbraco": {
  "CMS": {
    "Plugins": {
      "BrowsableFileExtensions": [
        ".html",
        ".css",
        ".js",
        ".jpg", ".jpeg", ".gif", ".png", ".svg",
        ".eot", ".ttf", ".woff", ".woff2",
        ".xml", ".json", ".config",
        ".lic",
        ".map"
      ]
    }
  }
}
```

{% endcode %}

By default, plugins can serve markup, styles, scripts, source maps, images, fonts, configuration files, and license files. If you remove the `.html` entry, plugins cannot serve HTML files.

## Cachebuster

{% hint style="info" %}
The `Cachebuster` setting is available from Umbraco 18.1.
{% endhint %}

This setting lets you force browsers to re-fetch all package assets served from `/App_Plugins`. It is empty by default and has no effect until you set it.

Set it to a value that changes with each deployment, for example a build number or a git commit hash:

{% code title="appsettings.json" %}

```json
"Umbraco": {
  "CMS": {
    "Plugins": {
      "Cachebuster": "build-20260713.1"
    }
  }
}
```

{% endcode %}

A short hash of the value is included in the cache-busting query string that Umbraco appends to package asset URLs. When the value changes, the asset URLs of every package change at once. The value is resolved on the server, so it stays consistent across servers in a load-balanced setup.

Read more about how packages are cache busted in the [Umbraco Package](/umbraco-cms/extend-your-project/backoffice-extensions/umbraco-package.md#cache-busting) article.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/configuration/pluginssettings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.