Text to Binary Converter

How text becomes numbers

Worth understanding once, because it makes every result here make sense, and it is usually the actual homework question.

Computers store characters as numbers. Each character has an agreed number — capital A is 65, lower-case a is 97, a space is 32 — and the only thing that changes between binary, decimal, hexadecimal and octal is how that same number is written down.

Capital A is 65 in decimal, 1000001 in binary, 41 in hexadecimal and 101 in octal. Same letter, same number, four notations.

Which is why converting to binary and back is lossless and exact: nothing is being encoded or encrypted, only rewritten in a different base. Binary is not a code and provides no secrecy — anyone can convert it straight back, including in their head with a little practice.

The bases are useful in different places. Binary shows what is really stored and is what computing courses ask for. Hexadecimal is what programmers use in practice, because one hex digit is exactly four binary digits, so it is compact and converts back at a glance. Decimal is the character code you will see in programming documentation. Octal turns up mainly in file permissions and older systems.

The separator and bit width decide whether the output is usable

The settings people skip, and the reason a result sometimes cannot be decoded.

The separator — none, space, comma or newline — controls what goes between characters. Space is the usual choice and the one to use for anything a person will read or a teacher will mark, because each character is visibly separate. Comma suits pasting into a spreadsheet or an array. Newline gives one character per line, which is easiest for lining up against the original. None produces one continuous string, which looks impressive and is only decodable if every character uses the same fixed number of digits.

That is the catch worth knowing: with no separator, the bit width is what makes decoding possible. Eight digits per character is the standard, so a continuous run can be cut into eights. Seven-bit output is more compact and still works if you know to split by sevens. Mix the two and a continuous string becomes undecodable.

If you are given binary to decode and it comes out as nonsense, the separator or grouping is almost always why. Try splitting it into groups of eight, then of seven.

Morse code, and what it cannot carry

Morse is a genuinely different thing from the number bases — a real code, invented for the telegraph, which represents characters as dots and dashes.

Here a space between letters separates them, and a forward slash marks a word break, which is the standard written convention. So "hi there" becomes dots and dashes with a slash where the space was.

What it covers: the letters A to Z, the digits 0 to 9, and four punctuation marks — full stop, comma, question mark and exclamation mark.

What it does not: everything else. Accented letters, colons, semicolons, quotation marks, brackets, symbols, and any non-Latin script — Arabic, Urdu, Chinese, Cyrillic, Greek — all come out as a question mark. If your Morse output is peppered with question marks, that is why, and the fix is to simplify the text first.

And Morse has no capital letters. A and a are the same signal, so a message converted to Morse and back comes out in one case. That is not a bug in this tool — it is how the code has always worked.

Listening to it

The Morse can be played aloud, as a tone rather than just dots on a screen — a short beep for a dot, a beep three times as long for a dash, with gaps between them. That three-to-one ratio is the real thing, not an approximation.

It is worth doing even if you only want the written version, because Morse was designed to be heard rather than read. The rhythm is what makes it learnable: SOS is instantly recognisable by sound and completely unmemorable as three dots, three dashes, three dots. Anyone actually trying to learn Morse is taught by ear from the start, precisely because learning the written symbols first makes you slower.

Practical uses for the audio: checking a signal you have heard somewhere, generating a sound clip for a puzzle, escape room or geocache, letting a class hear what they have just written, or testing whether you can still pick out your own initials.

A note on non-English text

Worth stating because it affects a lot of people.

The number conversions handle plain English text perfectly. Characters outside the basic English set do not round-trip reliably at a fixed width — an accented letter, an emoji or a character in Arabic, Urdu or Chinese has a code number far larger than the range eight digits can hold, so the output either overflows the grouping or cannot be split back into characters correctly.

If you need to represent non-English text safely, Base64 is the right tool — Base64 Encoder handles any text, in any script, and converts back exactly. That is what it exists for.

For English text, homework, puzzles and code exercises, everything here works exactly as it should.

What this is not

One thing to be clear about, because it comes up.

None of these is encryption. Binary, hex, octal and Morse are all public, documented notations, reversible by anyone in seconds — which is the whole point of them. They are for representing text, not hiding it.

If you want text that cannot be read without a key, that is a different job. Hash Generator produces a one-way fingerprint, which is what you want for checking that something has not changed rather than for concealing it.

Everything runs on your own device and nothing is transmitted, which is worth knowing since these tools are commonly used on puzzle answers, exercise text and the occasional thing someone would rather not paste into a random website.

Related tools

Base64 Encoder is the right encoding for anything beyond plain English text, and handles every script exactly. Hash Generator produces one-way fingerprints, which is a different job from a reversible notation. Text Case Converter tidies text before you convert it, which matters for Morse since case is lost anyway.