Password Converter: Hex, Binary, Base64
Convert a password to its UTF-8 bytes as hex, \x escapes, binary, decimal, Base64, Base64URL or percent-encoding, and decode those formats back.
The password is first converted to UTF-8 bytes; every format shows those same bytes. Encodings are reversible and are not encryption or hashing.
Runs entirely in your browser. Your data is never uploaded.
What is Password Converter (Hex/Binary/Base64)?
This converter shows the exact UTF-8 bytes of a password in seven common notations at once, and converts any of them back to text. It helps when a configuration file, API or debugging session needs the password as bytes instead of text.
How to use Password Converter (Hex/Binary/Base64)
- Choose the Direction: password → encodings or encoding → password.
- For encoding, type the password; every format appears with a copy button.
- For decoding, choose the Input format and paste the encoded value.
- Copy the result you need.
Example
Pa$$w0rd
Hex 5061242477307264 Base64 UGEkJHcwcmQ= Binary 01010000 01100001 00100100 00100100 01110111 00110000 01110010 01100100
When to use Password Converter (Hex/Binary/Base64)
Use it for configuration that expects hex or Base64 secrets, for checking how non-ASCII characters are stored, or for debugging authentication headers. Remember that these encodings are not encryption: anyone can decode them.
How Password Converter (Hex/Binary/Base64) works
The password is encoded to UTF-8 with TextEncoder. Hex writes each byte as two hex digits, the \x form prefixes each byte, binary uses 8 bits per byte, decimal lists byte values, Base64 follows RFC 4648 (Base64URL uses - and _ without padding), and percent-encoding escapes every byte. Decoding reverses the format and rejects bytes that are not valid UTF-8.
Common Use Cases
- Putting a password into a config that expects Base64
- Checking the bytes of a password with accented characters
- Decoding a Base64 value from a Kubernetes secret
- Building escaped strings for scripts
FAQs
Is Base64 a form of encryption?
No. Base64 only changes the representation; anyone can decode it. Kubernetes secrets, for example, are just Base64 and need separate protection.
Why does é become two bytes?
UTF-8 encodes characters outside ASCII with 2–4 bytes; é is C3 A9.
What is the difference between Base64 and Base64URL?
Base64URL replaces + and / with - and _ and drops the = padding so the value is safe in URLs and file names.