> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/compression/how-to-configure-gzip-and-brotli.md).

# How to Configure Gzip and Brotli

Step-by-step instructions for how to enable and configure Gzip compression and Brotli compression.

Medianova CDN supports **Brotli Compression** and **Gzip Compression** for reducing the size of eligible responses. Each compression method can be enabled independently, and the list of compressed content types can be customized.

{% hint style="info" %}
For details about compression behavior, see [Compression](/products/performance-cdn/static-content-delivery/advanced-configuration/compression.md).
{% endhint %}

## Configure Compression

Gzip and Brotli are configured per CDN Resource in the [Medianova Control Panel](https://cloud.medianova.com).

The following steps apply to both **Brotli Compression** and **Gzip Compression**.

{% stepper %}
{% step %}

### Open Text Optimization

Open your CDN Resource and navigate to **Optimization → Text**.

The page displays separate configuration sections for **Brotli Compression** and **Gzip Compression**.
{% endstep %}

{% step %}

### Enable Compression

Enable the toggle for **Brotli Compression** or **Gzip Compression**.

Both compression methods can be enabled independently.
{% endstep %}

{% step %}

### Configure Content Types

Review the content types configured for the selected compression method.

To add another content type:

1. Enter the MIME type in the **Content Type** field.
2. Select **+** to add it.

To remove a configured content type, select the **×** icon next to it.

Select **Show more** to display additional configured content types.
{% endstep %}

{% step %}

### Save the Configuration

Select **Save** in the pending changes bar.

Review the pending configuration changes and confirm the update.
{% endstep %}
{% endstepper %}

## Default Content Types

Brotli Compression and Gzip Compression include predefined content types.

You can modify these lists according to the content delivered by your CDN Resource.

To restore the predefined list for a compression method, select **Reset to default**.

{% hint style="info" %}
Only configure content types that are appropriate for compression. For the default content types and additional compression behavior, see Compression.
{% endhint %}

## Brotli and Gzip Selection

The compression format delivered to a client depends on the compression methods enabled for the CDN Resource and the encodings supported by the client.

Clients communicate supported compression formats through the `Accept-Encoding` request header.

If a supported compression format cannot be used, the response can be delivered without compression.

## Important Notes

* Brotli Compression and Gzip Compression are configured independently.
* Each compression method maintains its own list of content types.
* Configuration changes are not applied until the pending changes are saved.
* Removing a content type prevents that type from being eligible for the corresponding compression method after the updated configuration is applied.
* Use **Reset to default** to restore the predefined content type configuration.

## Related Concepts

* [Compression](/products/performance-cdn/static-content-delivery/advanced-configuration/compression.md)
* [Purge](/products/performance-cdn/static-content-delivery/advanced-configuration/purge.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/compression/how-to-configure-gzip-and-brotli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.