Text Encoding Toolkit
4 text encoding tools in one: a Base32 encoder/decoder, HTML entity encoder/decoder, JS/JSON string escaper, and a NATO phonetic alphabet converter.
- Pick an encoding tool from the pill bar: Base32, HTML Entities, String Escape, or NATO Phonetic.
- Type or paste your text into the input box, and choose a direction (encode/decode, escape/unescape, or text/code) where applicable.
- Click the action button to see the converted result appear instantly in the output panel.
- Copy the result with one click.
All processing happens entirely in your browser. Your data never leaves your device.
Key Features
- RFC 4648 Base32 encoder/decoder operating on UTF-8 text, with clear error messages for invalid input
- HTML entity encoder/decoder, with an option to numeric-encode non-ASCII characters
- JS/JSON string escape and unescape, producing a ready-to-paste quoted string literal
- NATO phonetic alphabet converter with two output formats: labeled lines or space-separated codewords
- Consistent copy-to-clipboard on every mode
- 100% client-side — safe for tokens, secrets, and sensitive text since nothing leaves your device
About Text Encoding Toolkit
Text encoding shows up constantly in software development and everyday digital life: Base32 is used in two-factor authentication secrets and DNS records because it avoids ambiguous characters; HTML entities keep special characters from breaking markup; escaped string literals let you safely embed arbitrary text inside JSON or JavaScript source code; and the NATO phonetic alphabet remains a classic way to spell text unambiguously over a noisy voice channel.
Rather than hunting down four separate single-purpose converters, the Text Encoding Toolkit bundles them into one tool with a consistent interface. Each mode is a focused, bidirectional (where applicable) converter: Base32 encode/decode operating on UTF-8 bytes, HTML entity encode/decode using the browser's own safe decoding trick, JSON-style string escape/unescape, and a one-way text-to-NATO-phonetic converter.
Everything runs locally in your browser with hand-rolled implementations (Base32 follows RFC 4648) or the browser's native DOM APIs — no data is ever sent anywhere, making it safe to use with secrets, tokens, or sensitive text. Looking for Morse code specifically? The dedicated Morse Code Translator & Audio Synthesizer covers that with adjustable WPM speed, Farnsworth timing, and WAV export.
Frequently Asked Questions
Both encode binary data as printable text, but Base32 uses a 32-character alphabet (A-Z and 2-7) instead of Base64's 64-character alphabet. Base32 output is longer, but it avoids visually ambiguous characters (like 0/O or 1/I/l) and is case-insensitive, which is why it's commonly used for things like two-factor authentication secret keys.
Yes. It decodes entities using a detached DOM element that is never inserted into the live page, so any markup or scripts in the input are never executed or rendered — the browser's parser is only used to resolve the entity references.
No, it's one-way (text → phonetic spelling) by design, since decoding phonetic words back to letters is rarely needed and ambiguous with free-form text. You can choose between a readable "letter — codeword" list or compact space-separated codewords.
It moved to its own dedicated tool — the Morse Code Translator & Audio Synthesizer — which adds adjustable WPM speed, Farnsworth spacing, a visual keying lamp, and WAV file export on top of the same text ↔ Morse conversion.