GZIP Decompress Guide | Decompress .gz Files Online Free

GZIP decompression (often called gunzip) restores a single compressed stream back to its original bytes. You need it when you download access.log.gz, inspect a base64 gzip payload from an API, or decode HTTP responses sent with Content-Encoding: gzip. This guide explains how the GZIP format works (RFC 1952), how it differs from Zlib and raw DEFLATE, and how to decompress gzip online in your browser with our free Gzip Decompress tool. No install, no account, and processing stays on your device.

Key facts: GZIP decompression (quick reference)

Use this block when you need a concise answer for search or AI summaries:

• GZIP is a file format that wraps DEFLATE-compressed data with a header, optional metadata, and a CRC-32 checksum (RFC 1952).
• Magic number: Valid GZIP streams start with bytes 0x1F 0x8B. In Base64, many gzip payloads begin with H4sI.
• One stream per .gz: A plain .gz file holds exactly one decompressed file. Multiple files use .tar.gz or .tgz (tar archive inside gzip).
• gunzip is the usual Unix name for GZIP decompression; gzip -d does the same thing.
• HTTP gzip: Browsers and APIs often send gzip-compressed bodies with Content-Encoding: gzip. The payload is a gzip stream, not Zlib (RFC 1950).
• vs Zlib: Zlib uses a 2-byte header (often 78 9C) and ADLER-32. GZIP uses a 10-byte header and CRC-32. Same DEFLATE engine, different wrapper.
• Privacy: Our Gzip Decompress tool runs in your browser with JavaScript. Your logs and API strings are not uploaded for server-side decoding.

What is GZIP compression?

GZIP (GNU zip) is a lossless compression format built on the DEFLATE algorithm (LZ77 plus Huffman coding). Jean-loup Gailly and Mark Adler designed the on-disk .gz wrapper so Unix tools could compress single files for storage and transfer. Today GZIP is everywhere: web servers, CDN edge caches, log rotation (logrotate), database dumps, npm package tarballs, and backup pipelines.

Common reasons developers search for gzip decompress or gunzip online:

• Log forensics: Open rotated *.log.gz files without SSH access to production servers.
• API debugging: Decode gzip-compressed JSON from Postman, curl, or browser DevTools when the client did not auto-inflate.
• Data pipelines: Inspect export.csv.gz or events.json.gz from S3, BigQuery exports, or analytics dumps.
• Release artifacts: Peek inside .gz assets when you only have a laptop and no gunzip installed.
• Security review: Validate whether a suspicious download is actually gzip (magic bytes) before running it through other tools.

Figure 1: Typical GZIP decompression path from input stream to readable output.

GZIP file structure (what gunzip actually does)

Understanding the wrapper helps you pick the right decoder and fix "incorrect header check" errors:

• Header (minimum 10 bytes): Magic 1F 8B, compression method (8 = DEFLATE), flags for optional fields (original filename, comment, extra field, header CRC).
• DEFLATE bitstream: The compressed payload (same core algorithm as Zlib and ZIP entries).
• Trailer (8 bytes): CRC-32 of the uncompressed data plus uncompressed size modulo 2³² (ISIZE field).

If your bytes start with 78 01, 78 9C, or 78 DA, you likely have Zlib, not GZIP. Use our Zlib decompression guide and the Zlib Decompress tool instead.

GZIP vs Zlib vs raw DEFLATE

How to decompress GZIP: methods compared

Method 1: Decompress GZIP online with the free Gzip Decompress tool (easiest)

The fastest way to decompress gzip online without a terminal is our Gzip Decompress page. It uses the Pako library in your browser to inflate gzip streams from pasted Base64 or uploaded files.

Steps to decompress gzip in your browser

1. Open Gzip Decompress in Chrome, Firefox, Edge, or Safari.
2. For text or Base64: Paste your gzip-encoded string into the left Input (Base64 or Raw) field. The tool decodes and decompresses as you type when the payload is valid.
3. For binary files: Use Or Upload Gzip File and choose a .gz or .gzip file. The decompressed text appears in the right Decompressed Output panel.
4. Read the output, copy it from the output field, or save it locally using your browser's usual copy workflow.
5. If you see an error banner, confirm the file starts with gzip magic bytes and is not Zlib-only or a .tar.gz you meant to extract with tar.

Decompression runs client-side. That matters when you work with production logs, customer exports, or signed API responses you do not want to send to a third-party server.

Method 2: Decompress .gz files on the command line

gunzip (replace the .gz file)

# Decompress document.txt.gz → document.txt (removes .gz by default)
gunzip document.txt.gz

# Keep the original .gz after decompressing
gunzip -k document.txt.gz

# Same as gunzip
gzip -d document.txt.gz

zcat (view without extracting to disk)

# Print decompressed log to terminal
zcat /var/log/nginx/access.log.1.gz | head

# Search inside a .gz without creating a temp file
zgrep "ERROR" application.log.gz

tar.gz archives

# Extract all files from a tarball
tar -xzf release.tar.gz

# List contents without extracting
tar -tzf release.tar.gz

curl and HTTP gzip responses

Modern curl auto-decompresses when you pass --compressed. To inspect raw gzip bytes, omit decompression and save the body:

# Let curl inflate Content-Encoding: gzip
curl --compressed -s https://example.com/api/data

# Save raw gzip body to a file for offline decoding
curl -s -H "Accept-Encoding: gzip" https://example.com/api/data -o response.gz
gunzip -k response.gz

Method 3: Decompress GZIP in code

Python

import gzip
import base64

# From a .gz file on disk
with gzip.open("access.log.gz", "rt", encoding="utf-8") as f:
    print(f.read()[:500])

# From Base64 (common in JSON logs)
b64 = "H4sIAAAAAAAAA/NIzcnJVwjPL8pJAQBWsRdKCwAAAA=="
raw = base64.b64decode(b64)
print(gzip.decompress(raw).decode("utf-8"))

Node.js

const zlib = require('zlib');
const fs = require('fs');

// File
const input = fs.readFileSync('data.json.gz');
const text = zlib.gunzipSync(input).toString('utf8');
console.log(text);

// Base64 string
const fromB64 = Buffer.from(b64Payload, 'base64');
console.log(zlib.gunzipSync(fromB64).toString('utf8'));

PHP

<?php
$compressed = file_get_contents('dump.sql.gz');
$plain = gzdecode($compressed);
echo substr($plain, 0, 500);
?>

Common mistake: Calling gzuncompress() on a true .gz file. That function expects Zlib (RFC 1950), not the GZIP wrapper. Use gzdecode() for GZIP.

Tips and common mistakes

• Confirm the format: Open the file in a hex viewer or check the first two bytes. 1F 8B = GZIP; 78 in the first byte often means Zlib.
• .gz is not a folder: If you expected many files, you probably have .tar.gz. Decompress gzip first, then extract tar, or use tar -xzf once.
• Binary vs text output: Browser tools display decompressed content as text. For images, PDFs, or protobuf inside .gz, prefer writing bytes to disk with CLI or script decoders.
• Corruption: "unexpected end of file" or CRC errors usually mean truncated downloads or mixed formats. Re-download or verify the source pipeline.
• Disk space: GZIP can expand 10x or more for compressible text logs. Ensure free space before gunzip on large archives.
• Security: Decompression bombs (tiny .gz that expand to gigabytes) are rare but real. Only decompress files from trusted sources on production systems.

Related free tools

• Gzip Decompress - Paste Base64 or upload .gz files in the browser.
• Zlib Decompress - For RFC 1950 zlib streams (Git objects, many API payloads).
• Base64 Decode - Decode transport encoding before you gzip-decompress embedded payloads.
• Zlib decompression guide - Deep dive when your data is not GZIP.

Whether you are unpacking a rotated log, debugging a gzip API body, or learning how RFC 1952 wraps DEFLATE, a reliable gzip decompress online workflow saves time. Open the free Gzip Decompress tool, confirm magic bytes 1F 8B, and inspect your data in seconds.