open file drag & drop · up to 5 MB (Pro: 100 MB)

url-safe — paste text to start // client-only

// output appears here


              curl -sX POST 'https://api.whittly.dev/v1/base64/encode' \
  -H 'Authorization: Bearer $WHITTLY_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":"hello world"}'


              const res = await fetch('https://api.whittly.dev/v1/base64/encode', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer ' + apiKey,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ input: "hello world" }),
});
const data = await res.json();


              const { data } = await axios.post(
  'https://api.whittly.dev/v1/base64/encode',
  { input: "hello world" },
  { headers: { Authorization: 'Bearer ' + apiKey } }
);

// probulk encode / decodepro·files over 5 MBproupgrade →

// about this tool

Base64 encoding converts binary or text data into a string of 64 printable ASCII characters, making it safe to include in URLs, HTML attributes, and JSON payloads. The decoder reverses the process, restoring the original bytes.

// when to use

Encode images or fonts as data URIs for inline embedding
Decode Base64-encoded JWT payloads to inspect claims
Encode binary data for safe transmission over text-only protocols
Use URL-safe mode to avoid + and / in query strings

// faq

What is the difference between standard and URL-safe Base64?

Standard Base64 uses + and / which are reserved characters in URLs. URL-safe Base64 replaces them with - and _ and removes = padding, making the output safe for use in URLs without additional encoding.

Does Base64 encrypt data?

No. Base64 is encoding, not encryption. Anyone can decode it without a key. Never use Base64 to protect sensitive data — use proper encryption instead.

// related tools

// about this tool

// when to use

// faq