About Base64 decoding
Base64 decoding reverses the encoding process: each group of 4 Base64 characters is converted back into the original 3 bytes. Because the mapping is fixed and public, any Base64 string can be decoded by anyone — it is an encoding for safe transport, not a form of protection.
This decoder is deliberately forgiving, because real-world Base64 is messy. It automatically
strips whitespace and line breaks (common in MIME email and PEM certificates), converts
URL-safe Base64URL characters back to the standard alphabet (common in JWT tokens and OAuth
state values), and repairs missing = padding (common when tokens are trimmed by
shells or config parsers). If the input still cannot be decoded, you get a clear error message
explaining what is wrong instead of silent failure.
Common decoding tasks
- Reading values from
kubectl get secret -o yamloutput - Inspecting
Authorization: Basicheaders in request logs - Peeking inside JWT tokens (use the JWT Decoder for a formatted view)
- Recovering text from Base64 blobs in JSON payloads, environment variables, or email source