What hex formats are accepted?

The converter accepts continuous hex strings (e.g. 48656c6c6f), space-separated pairs (48 65 6c), colon-separated pairs (48:65:6c), and strings with a leading 0x prefix. All whitespace and separators are stripped automatically.

What is the difference between standard and URL-safe Base64?

Standard Base64 uses + and / as the 62nd and 63rd characters and may include = padding. URL-safe Base64 replaces + with - and / with _ so the output is safe to use in URLs and JWTs without percent-encoding.

Does hex-to-base64 always produce padding characters?

Yes by default. When the number of input bytes is not a multiple of three, one or two = characters are appended. You can disable padding for URL-safe output if your target system does not require it.

Is this tool safe to use with sensitive data?

All computation happens in your browser using the Web Crypto and built-in JavaScript APIs. No data is sent to any server, so it is safe for local development use. Avoid pasting production secrets into any online tool as a general precaution.

Swap decodes the current Base64 output back to raw bytes and displays those bytes as a lowercase hex string in the input field, letting you verify the round-trip conversion.

Hex to Base64 Converter

Paste a hexadecimal byte string and convert it to standard or URL-safe Base64 instantly.

Hex Input

Hexadecimal string

Alphabet: Standard URL-safe

Base64 Output

Quick examples

Summary

This tool converts a hexadecimal byte string into a Base64-encoded string entirely in your browser. It accepts space- or colon-separated hex pairs as well as continuous hex strings, and supports both standard and URL-safe Base64 alphabets. No data is sent to any server.

How it works

Paste your hex string into the input field (e.g. 48656c6c6f or 48 65 6c 6c 6f).
Select Standard or URL-safe Base64 alphabet.
Click Convert to generate the Base64 output.
Copy the result with the Copy button.
Use Swap to reverse the direction and decode Base64 back to hex.

Use cases

Converting hex-encoded cryptographic hashes or digests to Base64 for JWT or API use.
Transforming hex byte dumps from network captures into Base64 for embedding.
Encoding raw binary data expressed as hex for use in data URIs.
Verifying encoder/decoder round-trips during protocol debugging.
Preparing hex-formatted keys or nonces for Base64-based storage formats.
Converting hex color bytes or binary blobs for web or mobile data transport.

Frequently Asked Questions

Last updated: 2026-05-23 · Reviewed by Nham Vu