Loading Base64 to Brotli Converter...

How to Decompress Base64 Brotli Data

Step 1

Paste Base64-Encoded Brotli Data

Enter your Base64-encoded Brotli data into the input area. This is data that was previously compressed with Brotli and then encoded to Base64 for transmission. You can:

•
Paste directly: Copy Base64 Brotli data from your API response or database
•
Upload a file: Pick a raw .br file (it is turned into Base64 for you) or a text file that holds the Base64
•
Try the sample: Load example data to see the decompression in action
Step 2

Automatic Base64 Decoding & Brotli Decompression

About half a second after you stop typing, the page decodes the Base64 back to bytes and decompresses them with a WebAssembly build of Brotli, right in your browser:

•
Base64 decoding: Line breaks, URL-safe Base64 (- and _) and data: URIs are accepted; a bad character is reported with its line and column
•
Brotli decompression: The whole stream must decode; cut-off data or extra bytes after the end give an error instead of a partial result
•
Wrong format: If the bytes are GZIP, ZLIB, Zstandard, ZIP or plain text, the error says which
Step 3

View & Export Decompressed Data

Text shows up in the output panel. Binary content, such as an image, isn't shown; you get its size and a Download button instead:

•
Copy: Copies the decompressed text
•
Download: Saves the decompressed bytes exactly as they came out, named after an uploaded .br file when there is one

Frequently Asked Questions

What does this page do with my Base64?

It turns the Base64 text back into bytes and runs them through a Brotli decompressor, so you get whatever was compressed in the first place: JSON from an API response, a minified script, an image. If the result is text it is shown in the output panel; if it is a binary file you get a Download button that saves the exact bytes.

How do I know if my data is Brotli compressed?

Brotli has no signature bytes at the start, unlike GZIP (1F 8B) or ZLIB (78 xx), so the usual clue is where it came from: a response sent with Content-Encoding: br, or a file ending in .br. If the decompressor rejects the bytes, this page checks whether they are GZIP, ZLIB, Zstandard, LZ4, ZIP or plain text and says so. For GZIP or ZLIB data, use the Base64 to GZIP or Base64 to ZLIB pages instead.

Can I upload a .br file directly?

Yes. A raw .br file is read as bytes and converted to Base64 in the input box for you, and the download is named after the file without its .br ending (data.json.br saves as data.json). A text file that already holds Base64 is loaded as it is.

Is my data sent anywhere?

No. The Base64 decoding and the Brotli decompression both run in your browser, using a WebAssembly build of Brotli. Nothing you paste or upload is sent to our server, and nothing is kept: reloading the page gives you an empty editor.

Why do I get a "looks cut off" or "extra bytes" error?

"Cut off" means the Brotli stream stops before its last block, which usually happens when only part of a response or a truncated Base64 string was copied. "Extra bytes" means the stream ended cleanly but more data followed it, such as two strings pasted together. In both cases the page shows no output rather than a result that might be incomplete.

Can I compress data back to Brotli Base64?

Yes. The Brotli to Base64 page does the reverse: it compresses text or a file with Brotli and gives you the Base64.

When would I need to decode Base64 Brotli data?

Typical cases are reading a Brotli-compressed API payload that a logging or proxy tool saved as Base64, checking what a CDN actually served with Content-Encoding: br, looking inside .br assets from a build, and testing your own Brotli compression code against a known-good decoder.