Upload a PNG, JPEG, WebP, GIF, SVG, or other image your browser can read — get a full data URL, the raw payload after the comma (usually Base64),
a copy-ready <img> tag, and a CSS url() value. Preview updates live. Base64 is encoding, not encryption. Nothing leaves your device.
Used only in the generated <img> snippet.
Use this when your API expects raw Base64 without the data: prefix.
It reads your image file with the browser’s FileReader API and produces a data URL — a text form of the file that can be pasted into HTML, CSS, JSON, or tests. That is handy for inline images in email templates, small icons in prototypes, fixtures in Storybook or unit tests, and quick clipboard sharing — without running a local Base64 CLI.
A data URL looks like data:[mime-type][;parameters];base64,<payload> for binary images. Some SVG files may be exposed as UTF-8 with percent-encoding instead of Base64; the “payload only” field still contains whatever comes
after the first comma. Always verify what your consumer expects.
Base64 adds roughly 33% overhead versus raw binary, and very long strings can slow editors or bloat HTML. For production sites, prefer hosted assets or CDN URLs instead of giant inline data URLs — use this tool for convenience, not as a replacement for asset pipelines.
Base64 is not encryption — anyone with the string can decode the image. Encoding strips EXIF only insofar as you are creating a new data representation from decoded pixels; the tool does not upload your file to DroidXP.
Image Compressor to shrink files before embedding, Image Converter to change format, or Base64 Encoder for generic text or file workflows.
alt text for the HTML snippet.<img> tag, or CSS url() as needed.No. FileReader runs locally in your tab. The Base64 string never has to leave your machine unless you paste it elsewhere.
No. It is reversible encoding for transport — not secrecy. Anyone with the string can recover the bytes.
Base64 expands binary size. Large photos produce huge strings — normal, but often unsuitable for inline HTML in production.
Some browsers emit SVG as percent-encoded text rather than Base64. The payload field still matches what appears after the comma in the data URL.
Many clients support inline images via data URLs, but support varies. Test in your target clients; some strip long data URLs.
You are copying an encoding of the file bytes as the browser provides them. For privacy-sensitive sharing, prefer removing EXIF in a dedicated tool before embedding.
Only droidxp-itb-alt stores your optional alt text. Image bytes are never persisted. Clear resets the alt field and removes that key.
This page accepts image/* only. For arbitrary files, use a general Base64 encoder if the site offers one.
Very large files can make the tab sluggish. We warn above ~2 MB; consider compressing first.
Follow your policy. Nothing is sent to DroidXP, but clipboard and screen tools can still expose the string.
After the page is cached, it can work offline. No network is required to read the file and generate Base64.