Gzipped Base64 To Image
Text string back into an image
- image
This is the decoder half of a pair. You paste in a gzipped-then-base64 string - the kind produced by Image To Gzipped Base64 - and it reconstructs the actual IMAGE, ready to flow into the rest of your graph. Text goes in, a real image comes out.
Why does that exist? The node's own description tells you: "Load Gzipped Base64 Image string from SAA." It's built to receive images from mirabarukaso's SAA, the character_select_stand_alone_app - a separate standalone app that talks to ComfyUI over an API and shuttles images as compact text strings. ComfyUI_Mira is that author's personal toolkit, and this node is one of the seams connecting the app to the graph. If you're not using that app (or feeding ComfyUI images as base64 from somewhere else), this node isn't part of a normal workflow.
How it works
Images encoded as raw base64 are enormous, so SAA gzips them first and then base64-encodes, which keeps the payload small. This node reverses both steps in order: base64-decode, then gunzip, then rebuild the pixels into an IMAGE tensor ComfyUI understands. The key detail is that it expects that exact two-layer format - a plain base64 image string won't work, because there's no gzip layer for it to undo.
The inputs and outputs that matter
- base64text - a multiline STRING field. Paste the gzipped-base64 string here, or wire it in from an API/text node.
- image (output) - the decoded IMAGE, into a preview, a save node, a sampler, an upscaler, wherever.
That's the entire node. No format options - it does one decode and hands you the picture.
Installing it
ComfyUI Manager: search ComfyUI_Mira, install, restart. Or clone:
cd ComfyUI/custom_nodes && git clone https://github.com/mirabarukaso/ComfyUI_Mira.git
then restart. If it errors while loading, run pip install -r requirements.txt in the ComfyUI_Mira folder. The node lives under Mira/Util/Image.
Common issues
- Format has to match. This decodes gzip then base64. If you feed it a plain (non-gzipped) base64 image, it'll fail - that's not a bug, it's the wrong input. Use the matching Image To Gzipped Base64 to produce strings for this node.
- Truncated or mangled strings. Base64 is fragile to copy-paste errors and truncation. If decoding errors out, the string is almost always incomplete or corrupted in transit - re-copy the whole thing.
- It's a bridge, not a loader. If you just want to load an image file from disk, use the standard Load Image node. This one is specifically for reconstructing images that arrived as text.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| base64text | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| image | IMAGE | Load Gzipped Base64 Image string from SAA. |