Free image tools

Convert Base64 to an image you can see and save

Paste a Base64 string or a full data URI and see the picture it contains. If it is the image you expected, download it as a file.

This tool needs JavaScript. It runs entirely in your browser; nothing is uploaded.

Private by design. Your files are processed by your own browser on your own device. They are not uploaded, stored or seen by Archive.London. Tool terms

How to use the Base64 to Image tool

  1. Copy the Base64 string or data URI from your code, API response or file.
  2. Paste it into the tool.
  3. Check the image preview.
  4. Download the image.

To convert Base64 to an image, open the Archive.London Base64 to Image tool and paste your Base64 string or data URI into the box. The tool decodes it in your browser and shows a preview. Check the picture, then download it as an image file. Nothing you paste is uploaded.

Getting a clean decode: common reasons Base64 fails

Most decoding failures come from the text, not the image. Check these first:

  • Truncation. Base64 strings are long, and consoles, logs and spreadsheets often cut them short. A partial string gives a broken or half-drawn picture.
  • Stray characters. Surrounding quotation marks, escaped slashes from JSON, or text copied from either side of the string will corrupt it.
  • The URL-safe variant. Some systems replace + and / with - and _. Standard decoders expect the original characters.
  • Not an image. The string may encode something else entirely.

You can often tell the format from the opening characters. PNG data begins iVBORw0KGgo, JPEG data begins /9j/, GIF begins R0lGOD and WebP begins UklGR. If your string starts with one of those, it is very likely an image of that type.

What decoding does, and why doing it locally matters

Base64 writes binary data as text, using four characters for every three bytes. Decoding simply reverses that, turning the characters back into the bytes of a file. A data URI is the same text with a prefix such as data:image/jpeg;base64, that names the type; you can paste it with or without that prefix.

The tool decodes in your browser and displays the result. Nothing you paste is sent to a server or stored.

That matters more than it might seem. Base64 strings pulled from API responses, databases and logs can contain customers' photographs, scanned identity documents or unreleased artwork. Pasting such data into a site that processes it remotely is a disclosure. Decoding on your own device is not.

Recovering an image is not the same as knowing its source

An image decoded from a string usually arrives without context. There is no filename, no folder and no surrounding page, and often no embedded caption or credit either. You have the picture but not its history.

For anyone who handles photographs professionally, that is the point at which to stop and trace the source before using it. Who made it, who holds the rights and what it shows are questions the pixels alone seldom answer, and provenance is established from records, not from the file's appearance.

Longer articles from Archive.London are collected in its journal.

Frequently asked questions

How do I view a Base64 string as an image?

Paste the string into the tool and it is decoded and displayed immediately. It accepts both a bare Base64 string and a complete data URI beginning with data:image. If the preview shows the picture you expected, use the download button to save it as an ordinary image file.

Why is my Base64 image not displaying?

The usual causes are a string that was cut short when copied, extra characters such as quotation marks or line labels at either end, or a URL-safe variant using - and _ in place of + and /. It is also possible the data is not an image at all. Copy the full string again and retry.

How can I tell what image format a Base64 string is?

Look at the first few characters. PNG files encode to text starting with iVBORw0KGgo, JPEG files start with /9j/, GIF files with R0lGOD and WebP files with UklGR. If the string is a data URI, the format is also stated in the prefix, for example data:image/png.

Is it safe to paste Base64 data into this tool?

The data is decoded by your browser on your own device and is not transmitted or stored, so pasting it here does not disclose it to anyone. Decoding an image for preview is a routine browser operation. As with any file, be cautious about what you then do with images from unknown sources.

Is there a size limit on the Base64 I can paste?

The tool sets no fixed limit, but very long strings are demanding for a browser to handle in a text box, and memory on the device is the practical ceiling. Icons, thumbnails and ordinary photographs decode without trouble. Extremely large images may be slow or fail, particularly on phones.

About the archive behind this page

Archive.London is the home of the Robert Harper Photograph Library: 95,487 photographs made across a career that began in the Condé Nast studios.

Read the archive in factsWrite to the archive