Encoding Inspector
Detect Base64, hashes, UUIDs, JWT-looking strings, URL encoding, and show safe decoding attempts.
What is Encoding Inspector?
Find possible Base64/Base64URL, percent-encoded, hexadecimal, UUID-shaped or JWT-shaped values. Many plain strings happen to fit an encoding alphabet, so detection is only a hint.
How to use Encoding Inspector?
Step 1
Paste the suspicious encoded value.
Step 2
Review detected formats and safe decoding attempts.
Step 3
Move to a dedicated JWT, Base64, or URL tool when deeper inspection is needed.
Example input / output
SGVsbG8= decodes to Hello. A 64-character hexadecimal value might be a digest, a key or unrelated text; length alone cannot identify its algorithm or recover an original input.
Example input
SGVsbG8=Check the result
- Hashes are one-way identifiers and cannot be decoded back into original values.
- Binary Base64 output may not render as readable UTF-8 text.
Practical developer examples
Inspect decoded bytes
Base64 may contain a file rather than UTF-8 text. A decoding error or unreadable result is not proof that the source value is corrupt.
Use the producer's contract
Confirm whether a field is encoded, hashed, encrypted or opaque. An API key is often an opaque credential and has nothing meaningful to decode.
Common developer use cases
No decryption, key identification or hash reversal is performed. Decoded content is displayed as text and should be redacted before sharing.
Common issues
FAQ
Can this decode an API key?
Usually an API key is opaque. Its issuer, not its appearance, defines its meaning.
Does a successful decode prove Base64 was intended?
No. Some ordinary strings decode by coincidence; compare with the documented representation.