Base64 & URL Encoder / Decoder

When do I need Base64 encoding in an automation workflow?

Most commonly for HTTP Basic Authentication headers (which require "username:password" Base64-encoded), for embedding small binary data like images in JSON payloads, and for some webhook signature schemes that expect a Base64-encoded HMAC.

What is the difference between Base64 encoding and encryption?

Base64 is not encryption or security, it is a reversible encoding scheme with no secret key. Anyone can decode Base64 instantly, as this tool demonstrates. Never use Base64 alone to protect sensitive data.

When do I need URL encoding instead of Base64?

URL encoding (percent-encoding) is for characters that are not safe inside a URL, like spaces, ampersands, or special symbols in a query string parameter. Base64 output itself often needs URL encoding too if you are passing it as a URL parameter, since Base64 can include characters like "+" and "/" that have special meaning in URLs.

Why did my decode fail with an error?

Base64 decode fails if the input length is not a multiple of 4 (after removing valid padding) or contains characters outside the Base64 alphabet (A-Z, a-z, 0-9, +, /, =). URL decode fails on a malformed percent-sequence, like a "%" not followed by two hex digits.

Is this safe to use for actual passwords or secrets?

The encoding/decoding happens entirely in your browser and nothing is transmitted, but as a general practice avoid pasting real production secrets into any browser tool when a local script or your terminal can do the same job just as fast.