Base64
Decode
Decode
ТИП: КОНВЕРТЕР ИЗОБРАЖЕНИЙ
ТОЛЬКО В БРАУЗЕРЕ
Входной поток
------------------ STITCH
Ожидание сигнала...
ТИП: КОНВЕРТЕР ИЗОБРАЖЕНИЙ
ТОЛЬКО В БРАУЗЕРЕ
Входной поток
Tool guide
You paste text — either raw Base64 or a full data URI such as data:image/png;base64,iVBORw0... — and you get back an ordinary image file you can open anywhere. The decoding runs in your own browser, so the string is never uploaded. This is the tool you reach for when a picture arrives buried in a JSON API response, an email body, a database dump or a CSS background-image rule, and you need to see with your own eyes whether the payload is the right image or a truncated fragment. See also: encoding a picture back into Base64, decoding Base64 into any file type, checking what format the decoded image is.
Raw Base64 is just the encoded payload — letters, digits, plus signs and slashes. A data URI is the same payload with a data:image/png;base64, prefix that tells the browser what the bytes are. The input box accepts both; without a prefix the tool sniffs the format from the leading bytes. If detection fails, adding the prefix by hand is the reliable fix.
Usually the string was truncated on the way in — image Base64 often runs to hundreds of kilobytes and a terminal only shows you the tail. Second common cause: the payload is not an image at all but a PDF, a font or nested JSON. Third: quotes, a trailing semicolon or the closing bracket of url() came along with the copy. Strip those and paste the whole string.
No. Base64 taken from email sources or YAML config files is nearly always wrapped at 76 characters, and the whitespace is discarded during parsing because it carries no meaning in the encoding. Quotes around the value, JSON commas and backslash escapes are a different matter — those are treated as data and will break decoding, so remove them.
Transparency survives, because PNG carries an alpha channel and a transparent background stays transparent. Animation does not. The export writes a single raster frame, so an animated GIF comes out as its first frame only. If you need the full animation, save the original bytes to a .gif file another way and use this page purely to inspect what the string contains.
No. Parsing and preview rendering happen in page code inside your own browser, and the tool makes no network request carrying the contents of the input box. That makes it safe for screenshots out of internal systems or attachments from work email: the data stays on your device and is gone the moment you close the tab.
Usually, with one caveat. Mobile Safari and Chrome decode megabyte-scale strings in a second or two, but pasting that much text through a phone clipboard is often silently truncated by the operating system. If the preview is empty on mobile yet the same string decodes on a desktop, the clipboard is almost certainly the culprit.
Before: data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mNkYPhfDwAChwGA60e6kgAAAABJRU5ErkJggg==
After: A 1x1 PNG shown in the preview and saved to disk with Export PNG
Before: background-image: url(data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciLz4=)
After: The icon appears in the preview; Export PNG hands you a raster copy
Your rating and feedback help decide what to improve next.