Skip to content
BEAD

Base64 Encoder / Decoder

Encode or decode Base64 strings instantly.

EncodingDeveloper
Base64

🔒 Encoding runs entirely in your browser.

</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/base64/run \
  -H "Content-Type: application/json" \
  -d '{
  "mode": "encode",
  "input": "your input here",
  "urlSafe": false
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/base64/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "mode": "encode",
  "input": "your input here",
  "urlSafe": false
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_base64

Full reference: developer docs · OpenAPI spec

About Base64

Base64 encodes binary data as ASCII so it survives transports that mangle non-text bytes (email, JSON, URLs). It expands the payload by ~33%, so don't use it for storage when you have alternatives.

UTF-8 mode handles non-ASCII characters correctly. URL-safe mode swaps +/ for -_ and drops padding — used in JWTs and URL fragments.

Frequently asked

▸What's URL-safe Base64?

Standard Base64 uses + and / characters that need percent-encoding in URLs. URL-safe Base64 replaces them with - and _, and usually drops the = padding. Pick the URL-safe variant when the result goes in a URL or JWT.

▸Is Base64 encryption?

No. Base64 is encoding — anyone can decode it instantly. It's used to ship binary data through text channels (email, JSON, URLs), not to hide it. If you need confidentiality, use AES Encrypt instead.

▸How big does the output get?

Base64 expands input by roughly 33% — every 3 bytes of input become 4 characters of output. For very large files this overhead matters; consider compressing first or using a binary-safe transport.

You might also like