Text to Base64
Paste plain text, including multilingual content, and encode it as UTF-8 Base64.
Add input to generate an output.
Turn local images into ready-to-use data URIs for HTML, CSS, and email templates. Fast, private, and built for everyday frontend work.
Drop your assets, choose an output mode, and copy the exact snippet you need.
or browse from your device
Choose an image to generate a Base64 data URI.
Work with UTF-8 text, raw Base64, and image data URIs in the same local browser workflow.
Paste plain text, including multilingual content, and encode it as UTF-8 Base64.
Add input to generate an output.
Paste raw Base64 or a Data URI to restore text, inspect image output, and copy the result.
Add input to generate an output.
Everything you need to move an image from a folder into a codebase without opening another editor.
Files are read with browser APIs and are never sent to a server or stored in an account.
Switch between raw Base64, Data URI, image tag, CSS, Markdown, and JSON output.
Queue up to 20 images, inspect each result, then copy or export the whole batch.
The converter uses FileReader and Canvas APIs already available in your browser. There is no backend step to wait for.
Choose one file or add a batch of assets from your device.
Optionally resize or optimize, then choose the format you need.
Copy the generated snippet into your project, documentation, email, or prototype.
A few practical notes about data URIs and the browser-based workflow.
A Base64 image is an image represented as text inside a data URI. It can be embedded directly in HTML, CSS, JSON, Markdown, or email markup.
No. The conversion happens locally in this browser tab using FileReader and Canvas. Closing the tab clears the working session.
JPEG, PNG, WebP, GIF, SVG, BMP, ICO, TIFF, AVIF, and HEIC files can be read as data URIs. Browser decoding determines which formats can also be previewed or optimized.
No. Data URIs are best for small interface assets, email templates, embedded demos, and portable snippets. Larger images are usually better as separate optimized files.
Encode your next image without leaving your workflow.