ASCII Tools

ASCII tools handle the text-to-byte conversion work that sits at the base of almost every encoding problem. A full set of browser-based utilities covering every direction programmers, students, and hobbyists reach for: text into binary, hex, decimal, Base64, Morse code, HTML entities, UTF-8 bytes, plus the reverse decoders from each format back to text. All client-side, all handle any length of input, all free. For Unicode-aware work beyond the 128-character ASCII range, see the UTF-8 decoders and the Unicode category.
What you can do with ASCII tools

Encode text into numeric formats: binary, hexadecimal, decimal code points, UTF-8 bytes, plus octal and arbitrary bases from 2 to 36.
Encode text into serialization formats: Base64 (standard or URL-safe), HTML entities for XSS-safe escaping, plus data URIs for inlining and byte arrays for C or Python literals.
Turn text into physical-world formats: Morse code with Web Audio playback at configurable WPM, or a rendered PNG image with font and color control.
Decode back to text from whatever the upstream system produced: Base64, binary, byte values, or any numeric base.
Change case with locale awareness for Turkish, Azerbaijani, and Lithuanian (where the default .toLowerCase() produces wrong results).

Reach for ASCII tools when the input fits in the 128-character ASCII set (English letters, digits, common punctuation) and you want to move it in or out of a different encoding. For text containing emoji, Greek, CJK, or accented characters, the UTF-8 decoders preserve those multi-byte sequences correctly. For Unicode-specific work like normalization or homoglyph detection, the Unicode category is the right place.
The ASCII toolkit
The most common tools at a glance. The full category page lists every ASCII utility including octal, data URIs, image rendering, arbitrary-base, and case conversion.

Tool
What it does
When to use

ASCII to Binary
Converts text to 8-bit binary with strict ASCII, byte, or UTF-8 mode and separator choice.
Teaching binary representation, fuzzing a text parser with bit-level inputs, or preparing test vectors for a protocol decoder.

ASCII to Hexadecimal
Encodes text as hex, code points or UTF-8 bytes, uppercase, 0x prefix, JSON-array output.
Preparing a hex literal for C source, reading what bytes a string produces on disk, or preparing a SQL injection test payload.

ASCII to Decimal
Converts text to decimal code points or byte values. Strict, byte, UTF-8, or code-point mode.
Seeing the decimal value of each character for programming exercises, or preparing a numeric-only payload.

ASCII to Base64
Encodes as Base64 with Unicode handling, URL-safe variant, optional 76-char line wrap.
Building a data URI, preparing a payload for a JSON API, or encoding a string for safe transport through URL query parameters.

ASCII to UTF-8 Bytes
Encodes as UTF-8 bytes in hex, decimal, percent, binary, or octal, with separator and prefix.
Seeing the UTF-8 byte pattern for non-ASCII characters, or generating percent-encoded URL fragments.

ASCII to Morse Code
Encodes to ITU Morse with Web Audio playback at adjustable WPM and copy-ready output.
Learning Morse with audio feedback, preparing training material, or producing a Morse audio file for a project.

ASCII to HTML Entities
Encodes as HTML entities with XSS-safe escape, numeric decimal, or numeric hex. Handles emoji.
Escaping user input before HTML insertion, encoding special characters that break markup, or preparing safe XML content.

Base64 to ASCII
Decodes Base64 to text. URL-safe variant auto-detected, missing padding fixed, UTF-8 aware.
Reading a Base64 payload from a JWT, email header, or API response without running base64 -d in a terminal.

Binary to ASCII
Decodes binary to ASCII, Latin-1, or UTF-8 text. 7 or 8 bit chunks, auto-detect format.
Decoding a binary-encoded message or test output where each chunk represents one character.

Bytes to ASCII
Decodes decimal, hex, or binary byte values to text. UTF-8 or Latin-1, auto-detect base.
Pasting the output of xxd, a Python byte list, or a packet dump column straight into readable text.

How to choose the right ASCII tool

If you are encoding text into a numeric format, pick the base that matches your downstream consumer: binary for bit-level work, hex for memory dumps and cryptographic work, decimal for teaching code points, octal for legacy Unix formats.
If the target is network or storage transport, Base64 is the most common choice. For URL-friendly variants, the URL-safe mode avoids + and /.
If the destination is a web page or XML document, HTML Entities escapes dangerous characters. For embedding entire small resources in markup, a data URI is closer.
If the input contains accented characters, Greek, CJK, or emoji, use the UTF-8 decoders instead. ASCII tools work on those but the naming and metadata target the 128-character ASCII set.
For case changes with non-English text, always use the locale-aware versions rather than browser default .toLowerCase(), which mangles Turkish, Azerbaijani, and Lithuanian.

Frequently asked questions
Q: What does ASCII actually cover?
ASCII defines 128 characters: 95 printable (letters, digits, punctuation, space) and 33 control codes (null, tab, newline, bell). Everything beyond that (accented letters, curly quotes, emoji, CJK) is not ASCII, it is Unicode. The tools accept non-ASCII input and handle it as UTF-8 bytes by default, so you can paste anything and get a sensible result.
Q: What is the difference between “code points” and “bytes” in the encoder options?
A code point is the Unicode number for a character (for example U+00E9 for é). A byte is the actual 8-bit value on disk. For ASCII characters they are the same number. For anything else, one code point can be multiple bytes in UTF-8 (1, 2, 3, or 4). Bytes are usually what you want for transmission; code points for teaching or inspecting Unicode.
Q: Why is there a separate lowercase and uppercase tool?
Turkish has a dotted and dotless I (İ, ı) that JavaScript’s default .toUpperCase() and .toLowerCase() get wrong. The same applies to Azerbaijani and Lithuanian. The dedicated tools use the correct locale-aware transformation. For English and most European languages, the built-in works fine.
Q: Can I decode back to the original text?
Yes. For every encoder, there is a matching decoder in this category or an adjacent one. ASCII to Base64 has its partner at Base64 to ASCII, and so on for binary, bytes, and arbitrary base. Encoding is lossless: decode gives you back exactly what you encoded.
Q: Are my inputs sent to a server?
No. Every ASCII tool runs fully client-side. Text, binary, hex, and every other format stay in the browser. The network tab confirms zero requests during any encode or decode operation.
Related categories
ASCII tools sit at the base of text encoding work. The UTF-8 decoders handle the multi-byte side of the same problem, for inputs that contain characters outside the ASCII range. The Unicode category covers everything Unicode-specific: normalization, spoofing detection, escaping, code-point manipulation. For base-to-base conversions that do not start or end in ASCII text (for example Base32 to hex), the binary and encoding category has the cross-base converters.