Gzip Decompressor & Compressor
Decompress Base64 gzip or hex gzip data back to readable text, or compress text into Base64 gzip. Shows size comparison. Everything runs in your browser — nothing is uploaded.
Up to 1 MiB compressed input and 8 MiB decompressed UTF-8 text. Binary archives and ZIP files are not supported. Processing stays in your browser.
Gzip and HTTP compression
Gzip bytes commonly begin with 1f 8b 08. Base64 is a separate way to represent those bytes as text. HTTP Content-Encoding: gzip normally carries binary gzip bytes, not Base64; a browser may already have decompressed the response. Gzip is not a ZIP archive.
RFC 1952 · RFC 9110 §8.4.1.3Input Size
Output Size
Compression Ratio
How to Use Gzip Decoder
Choose Mode
Select Compress (text to gzip) or Decompress (gzip to text) mode.
Enter Input
Paste Base64-encoded gzip data or plain text depending on the mode.
Convert & Review
Click Convert and check the size comparison and output.
What is Gzip?
Gzip is a file format and software application for compression and decompression. It uses the DEFLATE algorithm, which combines LZ77 and Huffman coding. Gzip is widely used for reducing file sizes in web servers, data transfer, and file archiving.
Common Uses
Web Compression
HTTP servers compress responses to reduce transfer size
File Archiving
Creating .gz compressed archives of files
API Payloads
Compressing large JSON or text payloads in APIs
Why Base64 + Gzip Together?
Raw gzip data is binary — it cannot be stored or transmitted in places that only accept text. Base64 encodes the compressed bytes into safe ASCII characters, which is why "Base64-encoded gzip" shows up everywhere in modern systems:
Cloud error payloads
S3 and other cloud services return gzipped error bodies as Base64 in JSON
Serverless & queue messages
Lambda payloads and SQS/Kafka messages are compressed then Base64-encoded to stay text-safe
HTTP & API bodies
Large JSON payloads compressed with Content-Encoding: gzip and carried as Base64 in text fields
Logs & webhooks
Compressed log batches and webhook payloads shipped as Base64 strings
This tool handles the combination in one step: paste the Base64 string, and it decodes Base64 and decompresses gzip back to readable text. Hex-encoded gzip bytes (like 1f 8b 08) are also accepted.
Frequently Asked Questions
When compressing already-small or highly random data, Gzip compression may not reduce size, and Base64 encoding adds ~33% overhead. This tool shows the size comparison so you can evaluate the benefit.
This tool processes data entirely in your browser. Very large inputs (several MB) may work but could slow down your browser. For production compression of large files, use server-side tools.
No. Gzip compresses a single stream or file. The .zip format is an archive format that can contain multiple files with individual compression. Gzip is simpler and often used for single-file compression and HTTP content encoding.
Paste the Base64 string into the input box with Decompress mode selected. The tool first decodes Base64 back to binary gzip bytes, then decompresses them with the DEFLATE algorithm and shows the readable text. No manual two-step decoding is needed.
All three use the same DEFLATE compression algorithm but wrap it differently. Zlib adds a small header and checksum around the raw deflate stream. Gzip wraps deflate in a file format with a header, timestamp, and CRC32 checksum. In HTTP Content-Encoding, "gzip" is the standard value even though the payload is usually just a gzip-wrapped deflate stream.
gzip file.txt compresses to file.txt.gz and deletes the original; -k keeps it. Decompress with gunzip file.txt.gz or gzip -d. For many files at once, tar czf archive.tar.gz dir/ bundles and compresses in one step, and tar xf unpacks. zcat streams a .gz file without writing anything - handy for compressed logs.
This page does not offer a compression-level selector. It uses the encoder’s default settings; the result depends on your input. If you need a specific level, use a compression tool that exposes that setting.
zlib exposes levels 1-9: 1 is fastest with the largest output, 9 squeezes hardest and slowest, and 6 is the default near the sweet spot for text. Levels 7-9 usually win only single-digit percentages over 6 while taking noticeably longer. For web responses, CPU time often matters more than the last 5% of size.
Related Tools
Base64 URL Decoder Parser
Decode and encode Base64, parse URL-encoded strings, preview Base64 images, and decode JWT header or payload segments
Hex Decoder
Convert between hexadecimal and text — supports configurable delimiter and prefix options
Unicode Decoder
Convert between Unicode escapes and readable text
Authoritative References
Primary sources behind this tool - official standards and specifications, not secondhand summaries.
RFC 1952 - GZIP File Format Specification
The IETF GZIP file format specification: header fields, DEFLATE, and CRC32.
zlib - A Massively Spiffy Compression Library
The zlib compression library home — the reference implementation behind gzip.
Gzip - Wikipedia
The gzip format and tool history, from DEFLATE to tar.gz archives.