Local processing: Conversion happens in your browser. This tool does not send the input to Cert Happens or a third-party conversion service.

Text is encoded as UTF-8 bytes, then represented as Base64.

2. Supported conversions

This tool converts between text, Base64, and hexadecimal without changing the underlying bytes unnecessarily. - **Text ↔ Base64:** Text is converted to or from UTF-8 bytes, then Base64 represents those bytes with printable characters. - **Text ↔ hexadecimal:** Each UTF-8 byte is represented by two hexadecimal characters. - **Base64 ↔ hexadecimal:** The tool converts the represented bytes directly, so arbitrary binary values do not need to become text first. Whitespace in pasted Base64 is ignored. Hexadecimal input may contain spaces or colon separators. Hex output uses lowercase characters without separators.

3. UTF-8 handling

Text conversions use UTF-8, not one-byte-per-character assumptions. That means ordinary ASCII text, accented characters, symbols, and emoji are converted according to their UTF-8 byte sequences. When decoding Base64 or hexadecimal to text, the represented bytes must form valid UTF-8. If they do not, use a Base64-to-hex or hex-to-Base64 conversion instead of forcing arbitrary binary data into text.

4. Encoding is not encryption

**Base64 is not encryption.** Hexadecimal is not encryption either. Both are reversible representations that can be decoded without a secret key. Encoding is useful for compatibility and transport. Encryption is used when the goal is confidentiality. A value can look unreadable and still provide no security against someone who recognizes the encoding. For the exam distinction, see the [Hashing, Encryption, and Encoding Quick Reference](/security-plus/quick-review/hashing-encryption-encoding/).

5. Local processing

The conversion code runs in your browser and does not make network requests. Input is not stored in localStorage or sessionStorage by this tool. Local processing reduces unnecessary data sharing, but it is still good practice to avoid pasting passwords, private keys, active session tokens, or other secrets into tools unless the task genuinely requires it.

6. Official references

- [RFC 4648: The Base16, Base32, and Base64 Data Encodings](https://www.rfc-editor.org/rfc/rfc4648) - [WHATWG Encoding Standard](https://encoding.spec.whatwg.org/)
Hash generator and checksum verifier Calculate SHA-256, SHA-384, SHA-512, or legacy SHA-1 digests and compare a checksum. Hashing, encryption, and encoding quick reference Review why hashing, encryption, and encoding solve different problems. Free IT and cybersecurity tools Browse useful tools, references, standards, and hands-on learning resources.