Decode a Base64 string back into an image.
Paste a string and decode to preview.
Three steps
Drop in a full data URL or a bare Base64 string.
The image renders immediately, along with its format and dimensions.
Save it as a normal image file.
Why this one
Base64 copied out of a JSON payload rarely has the data URI prefix, and the format is detected rather than demanded.
A truncated or wrapped string is the usual cause, and saying so beats an empty box.
Base64 in an API response often contains something you would not paste into a random website. This one does not send it anywhere.
The short version
Base64 turns up whenever an image has to travel through something that only carries text: a JSON API, a config file, a database column, a webhook payload. Decoding it back to a picture is a small job that usually appears at the least convenient moment, in the middle of debugging why the wrong thing is being returned.
Questions
Usually it was truncated on copy, or line breaks were introduced by whatever displayed it. Both are common when pulling a long string out of a terminal or a JSON viewer.
No. A bare Base64 body works, and the format is detected from the decoded bytes rather than trusted from the prefix.
Whatever it originally was. Base64 is an encoding, not a format, so a PNG encoded and decoded is still a PNG.
Only what your browser will hold in a text field. Very long strings, several megabytes of text, can make the tab sluggish while decoding.
Free, and staying free
Thridy is a library of thousands of 3D icons in one consistent style, free for commercial use with no attribution and no account. The tools exist so you never have to upload an image to somebody else's server to resize it.
Keep going
Stamp text or a logo onto an image.
Write text on an image with stroke and shadow.
Combine 2, 4, 6 or 9 images into one grid.
Strip EXIF, GPS and camera data from a photo.
Read the EXIF data hidden inside a photo.
Turn an image into a Base64 data URL.