Skip to main content

GZip / Deflate Compressor

Compress and decompress gzip, zlib, and raw deflate with native browser streams — nothing uploaded

Plain text

Compressed output

—

About the GZip

Gzip and deflate are everywhere: HTTP content encoding, SAML Redirect bindings (raw deflate), API payloads, and log archives. Debugging usually means piping through gzip -d on a terminal — or pasting compressed data into an online tool that ships it to a server.

This compressor uses the browser’s native CompressionStream and DecompressionStream — the same code Chrome ships for HTTP decoding — so nothing is installed and nothing is uploaded. Compress text to gzip, zlib, or raw deflate with Base64 output, or decompress any of the three from Base64 or hex, with byte counts and compression ratio.

How to use

  1. Pick compress or decompress, and the format (gzip, zlib, or raw deflate).
  2. For SAML SAMLRequest/SAMLResponse values choose raw deflate.
  3. Paste input — Base64 or hex is auto-detected when decompressing.
  4. Copy the result; byte counts and ratio are shown below the output.

Frequently Asked Questions

Which format does SAML Redirect binding use? ▾

Raw deflate — the DEFLATE compressed stream without the gzip or zlib wrapper. That is why a SAMLRequest value base64-decoded and gunzipped fails while inflating with raw deflate works. Select deflate-raw in this tool to decompress or produce exactly those payloads.

Does the browser’s compression differ from gzip on the command line? ▾

The compressed output may differ byte-for-byte from GNU gzip because compression levels and implementations vary — decompressed content is identical. For SAML and API debugging that is what matters; if you need a byte-identical gzip stream (rare, e.g. reproducible builds), use the command-line tool.