code Text Encoding Converter

About the Text Encoding Converter

Convert text between different encoding formats instantly with our free online tool. Transform plain text to binary, hexadecimal, Morse code, Base64, and more. All processing happens in your browser — your data never leaves your device.

Supported Formats

Standard Encodings

• Plain Text — Human-readable text (UTF-8 supported)
• Binary — Base-2 representation using 0s and 1s (8 bits per character)
• Hexadecimal — Base-16 representation (0-9, A-F)
• Decimal (ASCII) — ASCII/Unicode code point values (0-127 for ASCII)
• Octal — Base-8 representation (0-7)

Base64 Encodings

• Base64 (Standard) — Binary-to-text encoding using A-Z, a-z, 0-9, +, / and = padding
• Base64 URL-Safe — Modified Base64 using - instead of + and _ instead of /, with no padding. Safe for URLs, filenames, and JWT tokens.

URL & Web

• URL Encoded — Percent-encoding for safe use in URLs (spaces become %20)

Ciphers & Fun

• Morse Code — Telegraph encoding using dots (.) and dashes (-). Letters separated by spaces, words by /
• ROT13 — Simple letter substitution cipher rotating each letter by 13 positions. Self-reversing.

What is Morse Code?

Morse code is a method of encoding text characters using sequences of two different signal durations: short (dot) and long (dash). Developed by Samuel Morse in the 1830s for telegraph communication, it remains useful today in amateur radio, aviation, and emergency signaling. The most famous Morse code message is SOS: ... --- ...

What is ROT13?

ROT13 (rotate by 13 places) is a simple letter substitution cipher that replaces each letter with the letter 13 positions after it in the alphabet. Because the Latin alphabet has 26 letters, applying ROT13 twice returns the original text — making it its own inverse. ROT13 provides no cryptographic security; it's used to hide spoilers, puzzle answers, or mildly obscure text content.

Standard vs URL-Safe Base64

Standard Base64 uses characters + and / which have special meanings in URLs. URL-safe Base64 replaces these with - and _ respectively, and omits the trailing = padding characters. This variant is commonly used in JWT (JSON Web Tokens), data URLs that might appear in query strings, and anywhere Base64 data needs to be URL-compatible without additional encoding.

Common Use Cases

• Debugging network protocols and data transmission
• Understanding character encodings and binary representation
• Encoding data for URLs and web applications
• Learning computer science fundamentals
• Working with low-level data formats
• Hiding text content (spoilers, puzzle solutions)
• Converting messages to Morse code for fun or signaling

Privacy

All conversions happen entirely in your browser using JavaScript. Your text is never uploaded to any server, making this tool safe for sensitive content.