JPG to Base64 encoder.

A data URI wraps the same Base64 in a prefix, data:image/jpeg;base64, that tells a browser what the bytes are. Raw Base64 is just the encoded bytes. APIs and databases usually want the raw form and take the MIME type in a separate field or header.

Many: upload endpoints that take an image in a JSON body, vision models from OpenAI, Google and Anthropic, AWS Rekognition, Cloudinary and Imgur. Each says in its docs whether it wants raw Base64 or a data URI.

In JavaScript, atob gives the bytes, or Buffer.from(text, "base64") in Node; in Python, base64.b64decode; every language has it built in. Write the bytes to a file with a .jpg extension and it opens anywhere.

You can, and for small images under about 50 KB it is convenient. Past that, the third larger text and the cost of reading it on every query add up; store the file in object storage and keep the URL instead.

Base64 writes three bytes as four characters from a 64-character alphabet, so the text is a third larger than the file, plus up to two padding characters. That is the price of carrying binary through systems that only take text.

Drop the JPG or choose it. The bytes are read and encoded in your browser, the preview and the file's size show on the left, and the Base64 with its character count on the right. Copy it, or download it as a text file.

The pane shows the first 1,200 characters so the page stays quick with a large photo; copy and download always carry the whole string. Compress the JPG first if the string is for a payload with a size limit.

No. The file is decoded, drawn and re-encoded by your browser's canvas, and the page makes no request with it. You can load the page, go offline and keep working; nothing is stored either.

No. The JPG to Base64 encoder is free and opens without a sign-in, an account or an install.

Up to 100 MB per file, the limit the tool states under its drop area. A larger file is refused with a plain message instead of being decoded.

No, it takes one file at a time. If you drop or choose several, only the first is used; run the tool again for the next one.

No. The text is made from the file's own bytes, unchanged, so EXIF and every other metadata field stay inside it. Nothing is re-encoded or resized.

About a third longer: Base64 writes every three bytes as four characters. The status line shows the exact character count and the overhead for your file.

Closest to the JPG to Base64 encoder: JPG to data URI converter, JPG compressor, WebP to Base64 encoder, SVG to Base64 encoder. Each opens on its own page, free and in the browser.

The JPG to Base64 encoder is one of 44 in its group. The group's page, /tools/jpg, lists them all.

The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.