Base64 to ZLIB Converter: Decode and Decompress Data
Decode Base64 and decompress the ZLIB/DEFLATE data inside it, for example a compressed field in an API response or a database column. No registration required.
Loading Base64 to ZLIB Converter...
How to Use Base64 to ZLIB Converter - Complete Guide
Paste Base64-Encoded ZLIB Data
Enter your Base64-encoded ZLIB data into the input area. This is data that was compressed with ZLIB (DEFLATE) and then encoded to Base64. You can:
Example: Base64-Encoded ZLIB Input
Here's what Base64-encoded ZLIB data looks like:
eJyrVspMUbKysDQwNDIxMDUxMTQwMjAzMzIx01GqyixQslIyMDA1MFTSUSooykxOVbIyNNEzNdBRykvMTVWyUvLKLz68UqkWAEO+Eic=
Automatic Base64 Decoding & ZLIB Decompression
The tool automatically decodes the Base64 text back to binary, then decompresses the ZLIB (DEFLATE) data to recover the original content.
Example: What the Step 1 Input Decodes To
{"id":8901240544102066246,"zip":"00501","price":14.50,"name":"José"}View & Export Decompressed Data
The decompressed original data appears in the output panel. You can copy it or download it:
Useful Resources
Frequently Asked Questions
What is Base64 to ZLIB conversion?
It undoes two steps at once. The Base64 text is decoded back into bytes, and those bytes are inflated with ZLIB (DEFLATE) to get the data that was compressed in the first place. It is the reverse of compressing something with ZLIB and then Base64-encoding it so it fits in JSON, a URL or a database text column.
How do I know if my data is ZLIB compressed vs GZIP?
Look at the first characters. ZLIB data starts with the byte 0x78, which in Base64 shows up as "eJ", "eN" or "eA". GZIP starts with "H4sI". If you paste GZIP here anyway, it is still decompressed and a note tells you it was GZIP; the Base64 to GZIP page is the better fit for .gz data.
Is my data sent anywhere?
No. Decoding and decompression run in your browser with the pako library, and the page never uploads what you paste or the files you pick.
Can I compress data back to ZLIB Base64?
Yes, the ZLIB to Base64 converter goes the other way: it compresses text with ZLIB and gives you the Base64.
What if the decompression fails?
The message says what went wrong: a character that isn't Base64 (with its line and column), "=" padding in the middle, data that is cut off, a checksum that doesn't match because the data is damaged, or input that is something else entirely, such as JSON, plain text or a ZIP file. Most of the time the string was not copied in full, so copying it again usually fixes it.
What's the difference between ZLIB and raw DEFLATE?
ZLIB wraps DEFLATE data in a 2-byte header and a 4-byte Adler-32 checksum; raw DEFLATE has neither. This page reads both. Data without a ZLIB header is tried as raw DEFLATE (what deflateRaw and .NET DeflateStream write), and a note says so when that is what it found.
What happens if the decompressed data is not text?
It still decompresses, but bytes such as an image can't be shown as text, so the output panel shows the size instead. Download saves the exact bytes, as decompressed.bin, or under the uploaded file's name without its .zlib ending.
When would I need to decode Base64 ZLIB data?
Typical cases are API responses or webhook payloads with a compressed field, compressed values stored in a database column, and single PDF streams copied out of a file. The whole PNG or PDF file is not ZLIB data, only parts inside it are, and the page tells you that if you try.
Related Tools
PDF to Base64
Convert PDF files to Base64 encoded strings for APIs and databases
Base64 to PDF
Convert Base64 encoded strings to PDF files with instant preview and download
File to Base64
Convert any file type to Base64 encoded strings for universal data transmission
Base64 to File
Decode Base64 strings to any file type with automatic format detection
GZIP to Base64
Compress data with GZIP and encode to Base64 format
Base64 to GZIP
Decode Base64 and decompress GZIP data with instant preview