How To Decode Encoded Text

How To Decode Encoded Text starts with identifying the encoding scheme — because the same string of characters can mean entirely different things depending on whether it was encoded as Base64, hexadecimal, URL percent-encoding, Morse code, or something else entirely. Once you know the scheme, decoding is mechanical. This guide walks through every common encoding type, shows you how to spot each one in the wild, and gives you the exact steps to reverse it — plus a quick-reference cheat sheet and links to free online tools.

Why Text Gets Encoded in the First Place

Encoding exists for several distinct reasons, and knowing the reason often points you to the scheme:

• Data transmission safety. Protocols like email (SMTP) were designed for plain ASCII text, not binary data. Base64 converts arbitrary binary — images, files, cryptographic keys — into a safe ASCII alphabet so it survives transport without corruption.
• URL safety. URLs may only contain a restricted set of characters. Percent-encoding (also called URL encoding) replaces unsafe characters such as spaces, ampersands, and non-ASCII bytes with a %XX sequence, where XX is the hexadecimal ASCII value of the character.
• Compact transmission. GSM 7-bit encoding packs text messages into fewer bits than standard 8-bit ASCII, squeezing more characters into a single SMS frame.
• Light obfuscation. ROT13 is used on forums and in puzzle communities to hide spoilers. It does not provide any real security — it just shifts letters far enough that the text is not accidentally readable at a glance.
• Cryptography and ciphers. Caesar ciphers, Atbash, and other classical substitution ciphers encode text to conceal meaning, requiring knowledge of the key or shift to reverse.

How to Identify the Encoding Type

Before you can decode anything, you need to identify what you are looking at. Each encoding has telltale signs in its character set, structure, and length.

Base64

Base64 uses the characters A–Z, a–z, 0–9, +, and /. The encoded string often ends with one or two = signs (padding), and its total length is always a multiple of 4. The URL-safe variant substitutes - for + and _ for /. Example: SGVsbG8= decodes to Hello.

Hexadecimal (Hex)

Hex-encoded text uses only the digits 0–9 and letters A–F (or a–f). Characters are always encoded as pairs — a single byte is always two hex digits — so you will often see groupings like 48 65 6C 6C 6F (which is "Hello"). An odd total number of hex digits, or characters outside the 0–F range, means it is not standard hex.

URL Encoding (Percent-Encoding)

URL-encoded strings contain %XX sequences where XX is always a two-digit hexadecimal value. Spaces appear as either %20 or +. If you see a string with lots of percent signs followed by two hex digits, it is almost certainly URL-encoded.

Morse Code

Morse code uses only three symbols: dots (.), dashes (-), and spaces. Individual characters are separated by single spaces; words are separated by a forward slash (/) or a triple space. Example: .... . .-.. .-.. --- decodes to HELLO.

A1Z26

A1Z26 encodes each letter as its position in the alphabet: A=1, B=2 … Z=26. The numbers fall between 1 and 26, separated by spaces or dashes. If all values are in that range, A1Z26 is the first thing to try. Use our Letter Number Converter to decode A1Z26 instantly.

ROT13

ROT13 shifts every letter 13 positions forward in the alphabet (A→N, B→O, and so on). The result looks like English-ish text — same word lengths, same proportion of vowels and consonants — but the words are not real English words. Numbers and punctuation are left unchanged.

Binary

Binary-encoded text contains only 0s and 1s, typically grouped into 8-bit bytes separated by spaces: 01001000 01100101. If the total bit count is a multiple of 8 and only 0s and 1s are present, it is binary-encoded ASCII.

Caesar Cipher

A Caesar cipher shifts the entire alphabet by a fixed number of positions. The result looks like readable text — word lengths are intact, common short words appear — but the actual words are gibberish. Because there are only 25 possible shifts, brute-forcing all of them is straightforward.

Step-by-Step Decoding Guides

Decoding Base64

1. If the string uses URL-safe characters, replace - with + and _ with /.
2. Check the length. If it is not a multiple of 4, append = signs until it is.
3. Run the result through atob() in a browser console, or paste it into our Base64 Encoder / Decoder.

Decoding Hex

1. Split the string into two-character pairs (e.g. 48 65 6C).
2. Convert each pair from base-16 to a decimal number: 48 (hex) = 72 (decimal).
3. Map each decimal value to its ASCII character: 72 = H, 101 = e, and so on. Use our ASCII Decoder to do this automatically.

Decoding URL Encoding

1. Replace every + with a space character.
2. Find each %XX sequence in the string.
3. Convert the two hex digits XX to a decimal value and look up the corresponding ASCII character. %20 → 32 → space; %41 → 65 → A.
4. In JavaScript, decodeURIComponent() handles the entire process automatically.

Decoding Morse Code

1. Split the string on single spaces to get individual character codes.
2. Split on / or triple spaces to find word boundaries.
3. Look up each dot-dash sequence in a Morse code reference chart. Use our Morse Code Translator to decode entire messages at once.

Decoding A1Z26

1. Split the encoded string on its delimiter (space, dash, or comma).
2. Map each number to its letter: 1→A, 2→B, 3→C … 26→Z.
3. Numbers outside the 1–26 range indicate a different encoding — check for ASCII or a shifted variant.

Decoding ROT13

1. For each letter, shift it 13 positions forward in the alphabet, wrapping around after Z.
2. A→N, B→O, C→P … M→Z, N→A, O→B … Z→M.
3. Applying ROT13 twice returns the original text — the encode and decode operation are identical.
4. Numbers, spaces, and punctuation are left unchanged.

Decoding Binary

1. Split the bit string into 8-bit groups (bytes): 01001000, 01100101, etc.
2. Convert each 8-bit byte from binary to decimal: 01001000 = 72.
3. Map each decimal value to its ASCII character: 72 = H. Our ASCII Decoder accepts decimal values directly.

Quick Identification Cheat Sheet

When you encounter an unknown encoded string, run through this table top to bottom until a row matches what you see.

Free Online Tools to Decode Encoded Text

Manual decoding is a useful skill, but for anything longer than a few characters, an online tool is far faster and less error-prone. Here are the relevant tools on this site:

• Base64 Encoder / Decoder — paste any Base64 string to get the decoded output instantly. Also handles the URL-safe variant.
• ASCII Decoder — converts ASCII decimal codes (and hex codes) back to readable text. Useful for both Hex and Binary decoding once you have the decimal values.
• Letter Number Converter — the main A1Z26 tool on the site. Handles letters-to-numbers and numbers-to-letters in both directions.
• Morse Code Translator — decodes dot-dash sequences to text and encodes text to Morse. Handles word separators automatically.
• Letters to Numbers Converter (Home) — the full converter supporting multiple encoding modes, including A1Z26, ASCII, and more.

Frequently Asked Questions