Practical example
Encode a short UTF-8 value such as café ✓ and decode it again to confirm that the system preserves non-ASCII characters.
Tip: JWT uses Base64URL. Paste one part (between dots) to decode.
Base64 is a text-based encoding that converts binary data into ASCII characters. It’s commonly used to embed small files or safely transmit data in JSON, URLs, emails, or HTTP payloads.
Use this tool to encode plain text to Base64 or decode Base64 back to readable text. Everything runs locally in your browser.
Learn the workflow behind this tool and what to check next.
Base64 changes binary or text data into a transport-safe representation. It does not encrypt, authenticate, or validate the original content.
Use the expected character encoding, normally UTF-8, before encoding text so non-ASCII characters decode consistently.
Distinguish standard Base64 from URL-safe Base64 and preserve or remove padding only when the receiving format requires it.
For files and binary payloads, compare a checksum or byte length after decoding instead of judging the result as text.
Treat encoded passwords, tokens, certificates, and personal data as exposed because anyone can reverse Base64 without a key.
Encode a short UTF-8 value such as café ✓ and decode it again to confirm that the system preserves non-ASCII characters.
JWT segments use Base64URL, where - and _ replace + and / and padding may be omitted. Standard Base64 decoders can reject them.
Base64 is transport encoding, not encryption. Never treat an encoded password, token, or customer record as protected.
You may also find these tools useful.