Skip to main content
CaseSwitch

Hex to Text Converter

Use the CaseSwitch Hex to Text Converter to turn hexadecimal byte dumps into UTF-8 text — or text into spaced hex pairs. Choose Encode or Decode, paste the value, and copy the result. Processing stays in this browser.

Written by the CaseSwitch editorial team. We maintain these tools in the browser so drafts, keys, and images stay on your device.

Last reviewed: 23 July 2026

Processed locally in your browser. Nothing is sent to a server.

Paste or type text to convert. Output stays empty until there is input.

Character count: 0 · Word count: 0 · Line count: 0

Examples

Encode Hi

Input

Hi

Output

48 69

Decode Hello

Input

48 65 6c 6c 6f

Output

Hello

Encode café

Input

café

Output

63 61 66 c3 a9

Encode CaseSwitch

Input

CaseSwitch

Output

43 61 73 65 53 77 69 74 63 68

Decode CaseSwitch hex

Input

43617365537769746368

Output

CaseSwitch

How to use

  1. Choose Encode (text → hex) or Decode (hex → text).
  2. Paste text or hex pairs (spaces optional on decode).
  3. Copy the result. Strip `0x` prefixes if decode fails.

What this tool is for

Tickets and protocol traces often show hex (`48 65 6c 6c 6f` for Hello). This page converts between UTF-8 text and hex dumps for short strings. It is a teaching and debugging aid, not a hex editor for firmware images.

How it works

Encode UTF-8–encodes the text and prints lowercase hex pairs separated by spaces. Decode strips whitespace, requires an even number of hex digits, builds a byte array, and decodes as UTF-8. Invalid hex fails instead of guessing.

When to use it

Reading a hex dump from a ticket, checking a short ASCII payload, teaching binary/hex alongside the Binary Code Translator, and round-tripping a brand string.

When not to use it

Not a hex editor for large binaries. Not a color picker (`#FF00AA` looks similar but is a different tool). UTF-16 dumps need a different interpretation than UTF-8.

How it compares to related tools

Binary Code Translator uses bitstrings. UTF-8 Encoder can show decimal or hex bytes. Base64 uses another alphabet.

Common mistakes

Odd number of hex digits. Mixing `0x` prefixes mid-stream without stripping. Assuming the dump is UTF-16LE. Pasting `#` color codes with the hash still attached.

Spaces and casing

Decode ignores whitespace, so `48 65` and `4865` both work. Encode prints lowercase hex with spaces for readability. Uppercase input hex is accepted on decode.

UTF-8, not “ASCII only”

English letters look like classic ASCII bytes, but café needs multi-byte UTF-8 (`c3 a9` for é). If decode yields replacement characters, the dump may be a different encoding.

Frequently asked questions

Does it accept 0x prefixes?+

Prefer raw hex pairs (`48 65 6c 6c 6f`). Strip `0x` if decode fails — this decoder expects contiguous hex digits after whitespace removal.

Can I convert a whole firmware image?+

Use a desktop hex editor. This page is for short strings.

Is output uppercase or lowercase?+

Encode prints lowercase pairs. Decode accepts either case.

Why must the length be even?+

Each byte is two hex digits. An odd count means a truncated dump.

Is my dump uploaded?+

No. Conversion runs in this browser.

How is this different from UTF-8 encode?+

Same UTF-8 bytes underneath. This page focuses on hex dump style; the UTF-8 tool also offers decimal lists.

Does this tool send my payload to CaseSwitch?+

No. Formatting, encoding, and naming conversions for this page run in your browser after load — your sample stays on the device.

Related tools