Hex to Base64 Converter

Convert hex bytes to Base64 or decode Base64 back to the exact same bytes. Inspect offsets and ASCII evidence, switch Base64URL or MIME-style line wrapping, load local file bytes, batch-convert rows, and verify SHA-256 plus byte-for-byte round trips.

Messy hex acceptedHex ↔ Base64Base64URL + paddingByte round-trip audit

RFC 4648 byte evidence · Base64URL · MIME wrapping · local file intake

Hex ↔ Base64 Byte Inspection Studio

Make the raw byte array the source of truth, then convert, inspect, hash, batch-audit and export it without sending the data to a server.

Wave133 deep authority

Hex ↔ Base64Base64URL + padding76-column MIME outputSHA-256 + byte viewFile + batch handoff

Input modeOutputHex caseHex formatInspector row

Input

Selected output

Load local file bytesDownload MIME type

No file loaded

—raw bytes

—source notation

—Base64 round-trip

—padded Base64 chars / byte

—strict UTF-8

Ready.

Representations from the same bytes

Standard Base64Unpadded Base64URLCanonical / formatted hexStrict UTF-8 preview

SHA-256 & raw-byte handoff

The digest is calculated from the decoded raw bytes, not from the visible hex or Base64 characters.

—

File boundary. Files are read locally in the browser and limited to 5 MB here to avoid freezing the page. The MIME type field labels a downloaded Blob; it does not transform or validate the underlying bytes.

Byte inspector

Offset	Hex bytes	ASCII

—

Batch conversion audit

One non-empty input per line. Uses the same current input mode and output flavor. Up to 500 rows / 512 KB.

No batch run yet.

Explicit repeat-use projects

Nothing is auto-saved. “Save locally” stores text-input projects only in this browser. File bytes are never placed into local storage.

#	Project	Size	Action
No explicitly saved projects.

Standards and truth boundaries

Hex and Base64 are encodings of the same bytes; neither is encryption.
Base64 and Base64URL follow RFC 4648 alphabets. Unpadded Base64URL omits trailing = characters but preserves the same bytes.
“76-column MIME output” here means CRLF-wrapped standard Base64 at 76 characters per line. It does not construct a full MIME entity, headers, multipart body or email message.
Base64 parsing rejects mixed alphabets, impossible lengths, misplaced padding and non-canonical padding bits.
UTF-8 preview uses fatal decoding. Arbitrary binary data can convert perfectly while still being invalid text.
The inspector intentionally shows at most the first 256 bytes; downloads, hashes and conversions operate on the entire accepted byte array.