Nginx gzip Explained: Configuration, Compression, and Best Practices

Introduction

The gzip directive enables HTTP response compression in Nginx. When compression is enabled, text-based content such as HTML, CSS, JavaScript, JSON, and XML is compressed before being sent to clients.

Smaller responses require less bandwidth and can be transferred more quickly, improving page load times and reducing network traffic. For this reason, enabling gzip is considered one of the simplest and most effective performance optimizations for web servers.

This guide explains how gzip works, how to configure it, recommended settings, and common configuration mistakes.

Test Environment

Operating System : AlmaLinux 10
PHP Version      : PHP 8.3
Web Server       : Nginx
PHP-FPM          : Enabled
Architecture     : x86_64
Last Tested      : July 2026

What Is gzip?

The gzip directive enables HTTP compression.

Example:

http {
    gzip on;
}

When enabled, Nginx compresses eligible responses before sending them to the client.

How It Works

Without compression:

HTML File
   │
   ▼
100 KB
   │
   ▼
Browser

With gzip enabled:

HTML File
   │
   ▼
Compress
   │
   ▼
30 KB
   │
   ▼
Browser

The browser automatically decompresses the response after receiving it.

Benefits of gzip

Enabling gzip provides several advantages:

Faster page loading.

Reduced bandwidth usage.

Lower network transfer times.

Better performance on slower connections.

Improved user experience.

Compression is especially effective for text-based content.

Check the Current Configuration

Search for the directive:

grep gzip /etc/nginx/nginx.conf

Example:

gzip on;

Enable gzip

Edit the configuration file.

sudo nano /etc/nginx/nginx.conf

Example:

http {
    gzip on;
}

Test the Configuration

sudo nginx -t

Expected output:

nginx: the configuration file syntax is ok

nginx: configuration file test is successful

Reload Nginx

sudo systemctl reload nginx

What Can Be Compressed?

Compression is most effective for text-based responses.

Examples:

HTML

CSS

JavaScript

JSON

XML

SVG

These files often shrink by 50–80%, depending on their content.

What Should Not Be Compressed?

Some file formats are already compressed.

Examples include:

JPEG

PNG

GIF

WebP

MP4

ZIP

RAR

7z

Compressing these files again usually provides little or no benefit and may increase CPU usage.

Relationship with gzip_types

The gzip directive simply enables compression.

The actual file types that are compressed are controlled by:

gzip_types

Example:

gzip on;
gzip_types
    text/css
    application/javascript
    application/json
    application/xml;

Without gzip_types, only a limited set of MIME types may be compressed.

Recommended Configuration

http {

    gzip on;

    gzip_vary on;

    gzip_min_length 1024;

    gzip_comp_level 5;

}

This provides a good balance between compression efficiency and CPU usage for most production servers.

Common Issues

Compression Does Not Work

Possible causes:

gzip is disabled.

The response is too small.

The MIME type is not included in gzip_types.

The client does not support gzip.

CPU Usage Increases

Compression requires CPU resources.

Using an excessively high compression level, such as:

gzip_comp_level 9;

may consume more CPU while providing only a small reduction in response size.

For most websites, levels between 4 and 6 offer a better balance.

Compressing Images

Some administrators attempt to compress JPEG or PNG files with gzip.

Since these formats are already compressed, doing so generally wastes CPU time without significantly reducing file size.

Best Practices

Enable gzip for production servers.

Compress only text-based content.

Use moderate compression levels.

Configure gzip_types appropriately.

Test the configuration before reloading Nginx.

Conclusion

The gzip directive enables HTTP compression in Nginx, reducing the size of text-based responses before they are sent to clients. Properly configured compression lowers bandwidth usage, improves page load times, and enhances the browsing experience with minimal configuration effort.

For most production environments, enabling gzip together with a sensible compression level and carefully selected MIME types provides an excellent balance between performance and CPU utilization.