Debug HTTP Basic Auth headers instantly
If an API is returning 401 errors and you suspect the Authorization header is malformed, paste the Base64 portion (the part after "Basic ") into the decoder. You will immediately see whether the credentials are in the correct username:password format. A very common mistake is encoding just the username without the colon and password.
Create data URIs for small images
Small icons, SVGs, and images under about 5KB can be embedded directly in HTML or CSS as Base64 data URIs, eliminating an HTTP request: background-image: url('data:image/png;base64,iVBOR...'). Encode your image file, copy the output, and paste it into the data URI. This is especially useful for critical above-the-fold images that you do not want to delay rendering.
Use URL-safe Base64 for JWT and OAuth tokens
JSON Web Tokens use URL-safe Base64 (without padding) for their header and payload sections. If you are manually constructing or debugging a JWT, enable the URL-safe option. The standard Base64 + and / characters would break URL parsing, which is why the JWT spec uses - and _ instead.
The size overhead calculation
Base64 encodes 3 bytes as 4 characters, giving a 4/3 = 33% overhead. But with padding and line breaks (some implementations add them), it can reach 37%. This matters when embedding images in HTML — a 10KB image becomes ~14KB as Base64. For images larger than about 5KB, a separate file request is usually faster despite the extra round trip.
Combine with the hash generator
A common pattern in API security is: hash a message with SHA-256, then Base64-encode the hash for inclusion in a header. Generate the hash with the Hash Generator, copy the hex output, then encode it here. Some APIs use Base64 of the raw hash bytes rather than the hex string — be sure to check the API documentation.