Question 1

What is Base64?

Accepted Answer

Base64 is a binary-to-text encoding scheme that converts binary data into a string of 64 printable ASCII characters (A–Z, a–z, 0–9, +, /). It lets binary data — like file bytes — travel safely through text-based systems such as JSON, HTML, email, and HTTP headers.

Question 2

Is Base64 encryption?

Accepted Answer

No. Base64 is encoding, not encryption. Anyone can decode it instantly — there is no key and no protection. Never use it to hide sensitive data; it is simply a way to represent binary data as text.

Question 3

Is Base64 safe to use?

Accepted Answer

Safe for transmitting data through text protocols, yes. Confidential, no — anyone who sees the string can decode it immediately. If you need to protect data, use real encryption (AES, RSA, etc.), not Base64.

Question 4

Why is Base64 larger than the original file?

Accepted Answer

Base64 encodes 3 bytes as 4 characters, making the output about 33% larger than the input. If the input length is not a multiple of 3, = padding characters are appended to fill the last group, adding a small amount extra for small files.

Question 5

What are the 64 characters used in Base64?

Accepted Answer

A–Z (26), a–z (26), 0–9 (10), + and / (2) — 64 characters total. The = sign is a padding character, not one of the 64, but appears at the end of encoded output. Base64URL replaces + with - and / with _ to make tokens URL-safe.

Question 6

What's the difference between Base64 and URL encoding?

Accepted Answer

Base64 converts binary data into a 64-character ASCII text string — it solves the problem of representing binary as text. URL encoding (percent-encoding) converts special URL characters like spaces into %XX sequences — it solves the problem of safely including special characters in a URL. They serve different purposes and do not replace each other.

Question 7

What is Base64URL?

Accepted Answer

Base64URL is a URL-safe variant of Base64: it replaces + with -, / with _, and usually omits the = padding. The resulting string can be placed directly in URLs, filenames, or HTTP headers without percent-encoding. JWT headers and payloads are encoded in Base64URL.

Question 8

How do I convert a file to Base64?

Accepted Answer

Open the File to Base64 tool, drag your file into the upload area, choose your output format — Raw Base64, Data URI, HTML img tag, CSS background, JSON, or API payload — and copy the result. All processing happens locally in your browser; the file is never uploaded to a server.

Question 9

How do I decode Base64 back to the original file?

Accepted Answer

Paste your Base64 string or Data URI into the Base64 to File tool. The tool auto-detects the MIME type from the Data URI prefix, or you can select the file type manually. Click Download to save the restored file.

Question 10

What file types can be Base64 encoded?

Accepted Answer

All of them. Base64 treats every file as raw binary data regardless of format — images, PDFs, fonts, audio, video, ZIP archives, executables — everything is supported. The MIME type is metadata you attach in the Data URI prefix to tell the receiver how to interpret the data.

Question 11

Is there a file size limit for Base64 encoding in a browser?

Accepted Answer

No hard limit, but files over 10 MB slow down noticeably. The browser must hold both the original file data and the Base64 string in memory at the same time, and the output is 33% larger — peak memory is roughly 2.3× the original file size. For large files, multipart/form-data upload or direct object-storage transfer is a better fit.

Question 12

Can I embed a font in CSS using Base64?

Accepted Answer

Yes. Use @font-face { src: url('data:font/woff2;base64,…') format('woff2'); } to embed a font directly in your stylesheet, saving an HTTP request. This works best for small font subsets; full font files are usually 200 KB+, which would make your CSS very large — use with care.

Question 13

Can images be stored as Base64?

Accepted Answer

Yes. A Base64 image can be embedded directly in HTML (<img src='data:image/png;base64,…'>) or CSS (background-image: url('data:…')), with no separate HTTP request. It works best for small icons under 5–10 KB; large images bloat the page and cannot be cached independently by the browser.

Question 14

What is a Base64 Data URI?

Accepted Answer

A Data URI embeds a file's content directly in a URL. The format is: data:[mime];base64,[Base64 string]. For example, data:image/png;base64,iVBORw0K… A browser can render it as an image, PDF, or other supported type without making a separate HTTP request.

Question 15

When should I use a Base64 image vs an external URL?

Accepted Answer

Use Base64 for small, one-off icons (under 5 KB) to save an HTTP round-trip. Use an external URL for large images, assets shared across multiple pages, or anything you want CDN-cached. Base64 images are baked into the HTML and cannot be cached independently — every page load re-transmits them.

Question 16

Which MIME type should I use for my Base64 file?

Accepted Answer

Match the MIME type to the file format: image/png for PNG, image/jpeg for JPEG, image/svg+xml for SVG, application/pdf for PDF, font/woff2 for WOFF2 fonts. The MIME type goes in the Data URI prefix and tells the browser or API how to handle the data.

Question 17

Can SVG files be Base64 encoded?

Accepted Answer

Yes. Encoding an SVG gives you data:image/svg+xml;base64,… which you can use in HTML or CSS. Because SVG is text, you can also use URL-encoded format (data:image/svg+xml,[percent-encoded SVG]), which is sometimes shorter for small SVGs.

Question 18

Should I use Base64 to send files in an API?

Accepted Answer

It depends on file size. For small files (under 1 MB), embedding Base64 in JSON is convenient and avoids multipart boundary handling. For large files, multipart/form-data is better — no 33% size overhead, supports streaming and progress tracking, and is more efficient for servers to process.

Question 19

How do I send a Base64 file in a JSON API request?

Accepted Answer

Pass the Base64 string as a JSON field value. Many APIs also require the MIME type: { "file": "[Base64]", "mimeType": "image/png" }. The Base64 for API tool generates a ready-to-use JSON payload with JS fetch, cURL, Python, and PHP code samples.

Question 20

How do I estimate the Base64 output size before encoding?

Accepted Answer

Formula: ⌈original bytes / 3⌉ × 4 characters. A 100 KB file becomes roughly 137 KB of Base64. The Base64 Size Calculator lets you enter the original file size and instantly see the encoded size before you commit to embedding it.

Question 21

Can I use Base64 images in HTML email?

Accepted Answer

You can, but with trade-offs. Some email clients display them fine; others block or break them. Base64 images significantly inflate the email's file size and may trigger spam filters. For high-deliverability emails, hosted images or CID attachments are safer options.

Question 22

What's the best way to include images in HTML email?

Accepted Answer

Three options: ① Hosted images — link to a CDN URL, best deliverability and smallest email size; ② CID attachments — send the image as a MIME attachment, reference with cid: in the HTML, good compatibility but complex to implement; ③ Base64 inline — embed directly in the HTML, works offline but large and prone to spam filtering.

Question 23

Why does JWT use Base64URL instead of Base64?

Accepted Answer

JWT tokens appear in URLs, HTTP headers, and cookies. Standard Base64 uses + and / which are special URL characters that would need to be percent-encoded. Base64URL replaces them with - and _ and drops = padding, making tokens URL-safe without any extra escaping.

Question 24

How do I decode a JWT?

Accepted Answer

A JWT has three dot-separated parts: Header.Payload.Signature. Decode the first two with Base64URL to get JSON. The third part is a cryptographic signature — you do not need the key to read the Header and Payload, only to verify the token has not been tampered with. The JWT Decoder tool does this in one click.

Question 25

Can I read JWT content without the signing key?

Accepted Answer

Yes. The JWT Header and Payload are only Base64URL-encoded, not encrypted — anyone who sees the token can decode and read them. The signature only proves the token was not modified; it does not hide the payload. Never store passwords, secret keys, or other sensitive data in a JWT Payload.

Question 26

Why do I get 'Invalid Base64' errors?

Accepted Answer

Common causes: ① String length is not a multiple of 4 — missing = padding; ② Characters outside the Base64 alphabet; ③ URL-encoded Base64 where + became %2B and / became %2F; ④ Base64URL format (contains - and _) rejected by a standard decoder; ⑤ Spaces or newlines mixed in.

Question 27

What does = or == at the end of Base64 mean?

Accepted Answer

= is padding. Base64 processes 3 bytes at a time, outputting 4 characters. If the last group has only 1 byte, == is appended; if it has 2 bytes, = is appended. This keeps the output length a multiple of 4, which decoders require to work correctly.

Question 28

Why does Base64 decoding fail when I paste a JWT or URL parameter?

Accepted Answer

JWTs and URL parameters use Base64URL, which replaces + with - and / with _ and omits = padding. A standard Base64 decoder rejects - and _. To fix: replace - back with +, _ with /, then pad with = characters until the length is a multiple of 4.

Question 29

My Base64 string looks correct but decoding fails. Why?

Accepted Answer

Check for hidden characters: MIME standards auto-insert line breaks (
) every 76 characters, which may have been copied along; the string may have leading or trailing spaces; or a data:…;base64, prefix was not stripped. Most decoders are strict — one extra character causes failure. Strip all whitespace and the Data URI prefix before decoding.

Base64 FAQ

Popular Base64 Tools