8 chars · 1 line
Waiting for input
8 chars · 1 line
Waiting for input
Encoded representation and hashes
aGVsbG8= decodes to hello, but those are different input representations. Text mode hashes the Base64 characters directly, while Base64 bytes mode validates and decodes the representation before hashing the payload bytes. This tool is free to use. No account or payment is required.
Last updated
The Base64 characters aGVsbG8= form their own byte sequence. Hashing them as text differs from decoding them to hello and hashing that payload.
VetaTool keeps both workflows available in the Hash Generator: Text preserves the representation, while Base64 bytes decodes standard or URL-safe Base64 before hashing.
The encoded and decoded forms represent related data but are not the same bytes.
aGVsbG8=
helloBase64 text: 333d6b3a3c1f5db6c9bdda5939b136986d170f4649172a68368d54ecb44c2ff2
decoded hello: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824Common questions
Only when Base64 bytes mode is selected. Text mode hashes the entered characters directly.
Yes. It accepts standard Base64 and URL-safe Base64, validates the encoding, and hashes the decoded bytes.
Debugging a specific Hash issue? Browse Hash troubleshooting.