All Tools VerseBytes to text conversion decodes a list of numbers from 0 to 255 back into readable characters, so the bytes 72 105 become “Hi”. It is the reverse of seeing what a string looks like as raw storage, and the result depends on the encoding you decode with. This guide explains how bytes become text in ASCII and UTF-8, the common pitfalls, and free converters for each.
In this guide
What bytes to text means
Text is stored as bytes, and decoding turns those bytes back into characters using a known encoding. The same byte can mean different things under different encodings, so you must decode with the rule the text was created with. Seeing text as bytes in the first place is covered in our UTF-8 to bytes guide, and this is the return trip.
Bytes to ASCII
For bytes from 0 to 127, ASCII gives a direct mapping: 72 is H, 105 is i, 32 is a space. The bytes to ASCII converter reads a list of byte values and returns the characters. It is the right choice when you know the data is plain English text, and you can confirm any byte against our ASCII table reference.
Bytes to UTF-8
For anything beyond plain English, bytes above 127 form multi-byte sequences under UTF-8. The bytes to UTF-8 converter reassembles those sequences into the correct characters, including accents and emoji. This is the safer default for unknown data, since UTF-8 is the dominant encoding and is backward compatible with ASCII for the first 128 values.
Common pitfalls
Decoding with the wrong encoding produces garbled text, the classic sign of an encoding mismatch. A truncated byte stream that cuts a multi-byte character in half will fail to decode cleanly. And byte order matters for wider encodings. When text comes out as nonsense, the fix is almost always to decode with the encoding that actually created it rather than a guess.
When you need it
Bytes to text is everyday work when reading network data, parsing binary file formats, inspecting a buffer in a debugger, or recovering text from a hex dump. Anytime data arrives as numbers and needs to be read as words, decoding is the step that makes it human readable, and choosing the right encoding is what makes it correct.
Free converters used in this guide
Frequently asked questions
How do I convert bytes to text?
Decode the byte values with a known encoding. For values 0 to 127, ASCII maps each byte to a character; for anything else, use UTF-8.
What do the bytes 72 105 spell?
They spell “Hi”, since 72 is H and 105 is i in ASCII.
Why does my decoded text look garbled?
Almost always because it was decoded with the wrong encoding, so the bytes were interpreted by the wrong rule.
Should I use ASCII or UTF-8?
UTF-8 is the safer default, since it handles all characters and is identical to ASCII for the first 128 byte values.
Why does a cut-off byte stream fail to decode?
Because a multi-byte UTF-8 character was split, leaving an incomplete sequence that has no valid character.