Base64 Encoder and Decoder / GUIDE
Standard Base64 and URL-safe Base64 explained
Standard Base64 and URL-safe Base64 use different characters. Check which variant an integration expects before pasting an encoded value.
Notice the alphabet
Standard Base64 can include plus and slash characters. The URL-safe variant substitutes hyphen and underscore for those positions. Padding rules can also differ between systems. A string that looks similar is not necessarily accepted by every decoder.
Check the receiving specification
Tokens and APIs often define their own expected representation. Follow that specification instead of guessing from the field name. This site’s text tool is designed for standard Base64; it should not be treated as a universal token or binary-file decoder.
Avoid accidental URL changes
When a value is placed into a URL parameter, the surrounding URL encoding is a separate step. A plus sign can be interpreted as a space in some form-encoding contexts. Build the parameter using the intended API or encoder, and test that the receiving application gets the original value.
Before you finish
- Identify the required alphabet.
- Check padding expectations.
- Test the received parameter value.