Gzip + Base64 encode

UTF-8 → gzip (RFC 1952) → Base64; runs entirely client-side.

Shrink repetitive text before encoding: gzip compression reduces size, then Base64 makes it safe for text channels. Pair with the gzip+Base64 decode tool to round-trip.

Text
Base64 (gzip)

How it works

Input is encoded as UTF-8, compressed with the browser gzip stream, then the compressed bytes are Base64-encoded.

Output is not the same as plain Base64 of the text: decompression is required before reading the original.

When to use

Smaller strings over size-limited channels, quick experiments, or matching backends that expect gzip-then-Base64.

Privacy

Compression runs in your browser. This is not encryption; gzip + Base64 is reversible by anyone with the string.

Common questions

Same as plain Base64?
No. Plain Base64 only encodes UTF-8. Here the bytes are gzip-compressed first, so the output is shorter for repetitive text.
How do I reverse it?
Use the Gzip + Base64 decode tool in this section.
zlib instead of gzip?
This tool uses gzip headers. Raw zlib payloads need a different pipeline.
Very large input?
Huge pastes can be slow or hit memory limits; prefer smaller chunks for browser-based compression.