Skip to content
OneKitly
Sign up · Sign in

Text to hex converter

Convert text to hexadecimal and back, byte by byte in UTF-8 — é is c3 a9 and an emoji is four bytes.

Related tools

All Encoding & decoding tools →
Hex to text converterDecode a hexadecimal string back into readable text (ignores spaces and 0x prefixes).Binary to text converterDecode 8-bit binary back into readable text (spaces between bytes are optional).Extract text between delimitersPull out every piece of text that sits between a start and an end marker. Takes a whole file, so a long log does not have to go through the clipboard.Text to binary converterConvert text to binary (8-bit) and decode binary back to text.Text to HTML tableConvert delimited data into an HTML table.Base64 Encoder / DecoderEncode and decode Base64 online — free.HTML Entity Encoder / DecoderConvert text to HTML entities and back, escaping <, >, &, quotes and optionally all non-ASCII characters.JSON String Escape / UnescapeTurn raw text into a JSON-safe string and back, with control characters, \uXXXX, emoji surrogate pairs and lone surrogates handled exactly like JSON.stringify.

Text to hex converter is free to use as often as you like, directly from this page. Its place is under Encoding & decoding; Hex to text converter and Binary to text converter answer the questions closest to this one.

How to use it

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. Get your result instantly, then copy or download it.

Frequently asked questions

What does Text to hex converter do?

Convert text to hexadecimal and back, byte by byte in UTF-8 — é is c3 a9 and an emoji is four bytes.

When would I actually use this?

Reading a payload someone sent you, embedding a small file in a config, and finding out why a query string breaks once it reaches the server.

What is the most common mistake?

Treating Base64 as a form of protection. It is an encoding, not encryption — anyone can decode it instantly, and a token pasted into a public issue is a leaked token.

How is Text to hex converter different from Hex to text converter?

They sit next to each other but answer different questions: Hex to text converter is the one to open when you need it to decode a hexadecimal string back into readable text (ignores spaces and 0x prefixes). Pick whichever matches what you're starting from — both are free.

Where do the figures come from?

The encodings follow their RFCs, so a round trip is lossless. URL encoding has two variants — one that encodes a space as %20 and one as a plus sign — and the tool says which it applies.

Further reading

All guides →
GuideBuilding a URL With Parameters That Survives a Copy-PasteThree encodings, one visible difference: %20 or +. The builder's form mode matches URLSearchParams byte for byte on seventeen values — but give it a base URL with a fragment and every parameter lands inside the hash, where no server sees it.ExplainerEscaping a String for JSON: Three Characters Are Mandatory, and One Is a TrapRFC 8259 requires exactly three things to be escaped inside a JSON string. Everything else is optional. The one that actually breaks pipelines is a lone surrogate — legal in JSON text, impossible in UTF-8, and silently replaced the moment your data is written out.GuideURL Encoding Explained: Percent-Encoding and Where It BitesPercent-encoding is decided per URL component, which is the whole source of the confusion. A slash is legal in a path and must be escaped in a query value; a space is %20 in a path and may be + in a form body. Here are the exact RFC 3986 sets, the three JavaScript functions that disagree, and the traps.ExplainerWhat Is Base64 Encoding?Base64 turns binary data into safe text. Here's what it does, why it exists, why it isn't encryption, and the size cost it adds.ExplainerWhat Is a JWT (JSON Web Token)?A JWT is a compact, signed token used to carry identity between services. Here's its three parts, how it's used for auth, and its security limits.ExplainerWhat Is Inside a JWT — and What It Does Not ProtectA JWT is signed, not encrypted. Anyone holding the token can decode the payload and read every claim in it. Here is a real token, decoded without any key, plus the three attacks the signature is supposed to stop and the one problem it cannot solve.