⌘ K
morse · international code · letters/digits/punct · live

Translate text to Morse Code

Convert plain text to International Morse Code (dots and dashes) or decode Morse back to text. Supports letters, digits, and common punctuation. Runs locally.

Morse Code Translator
Input
9 B
1 lines
Output
34 B
1 lines
Status
ready
live
Ratio
3.78×
out/in
input · text
output · morse
... --- ...   .... . .-.. .-.. ---
Quick Start

How to translate Morse Code

Letters within a word are separated by single spaces; words are separated by three spaces. The decoder accepts a forward-slash word separator as well.

  1. 01

    Pick a direction

    Text-to-Morse builds dot/dash sequences; Morse-to-Text parses them back.

    Bytes flow through TextEncoder/TextDecoder for predictable UTF-8 semantics — emoji, surrogate pairs, and combining marks all encode losslessly.

    modeUTF-8TextEncoderlosslesslive
    mode · raw bytesto morse · UTF-8
    text → morse
    loaded · UTF-8MIME · ready
  2. 02

    Type or paste input

    Letters, digits and supported punctuation only. Unknown characters pass through verbatim.

    Hash and signature operations call crypto.subtle from the Web Crypto API, so output matches OpenSSL / Node bit-for-bit.

    inputWeb Cryptosubtledeterministiclive
    input · optionstext · live
    SOS HELLO
    options applied · livelive
  3. 03

    Spacing convention

    1 space between letters, 3 spaces between words. Newlines are kept.

    Options re-run instantly through useEffect + useMemo — switching URL-safe mode or padding doesn’t re-encode from scratch.

    spacingmemoisedoptionsinstantreactive
    spacing · encoded1/3 · ready
    ... --- ...   .... . .-.. .-.. ---
    encoded · livelossless
  4. 04

    Copy or download

    One click to clipboard. Download as .txt.

    Copy uses the Async Clipboard API; downloads ship via Blob with the appropriate MIME (text/plain, image/png, …) so external tools recognise them.

    exportclipboardblobMIME-correctclient-side
    ok · copiedready · done
    Copied
    shipped · ready to shipsuccess
Pro tips

Encoding without surprises

Always UTF-8 first

Use TextEncoder / TextDecoder for bytes ↔ string conversion. btoa alone breaks on non-ASCII.

URL-safe vs standard Base64

Standard uses +, /, =; URL-safe swaps to -, _, no padding. Don’t mix them.

Hashes aren’t passwords

SHA-256 is fast; that’s good for fingerprints, bad for passwords. Use bcrypt / argon2 for credentials.

Watch padding rules

Some decoders are strict about = padding, others auto-pad. If round-trips fail at exactly 1 or 2 bytes, check padding.

Use Web Crypto for keys

Generate cryptographic keys via crypto.subtle, never Math.random. The latter is predictable.

JWT decode ≠ verify

Decoding a JWT just splits and base64-decodes. Verification needs the issuer’s public key / shared secret.

Related toolsROT13Caesar CipherA1Z26 CipherBacon CipherPolybius SquareASCII Converter
Use Cases

When to use Morse Code

Amateur radio, scouts, escape rooms.

Amateur radio prep

Practise sending and reading CW operating exchanges. Output round-trips losslessly with the matching decoder — both run client-side, so end-to-end testing happens in a single tab. Encoding flows through TextEncoder for predictable UTF-8 semantics.

RFC-compliant

Scout activities

Standard signalling exercise — generate practice cards. Web Crypto's subtle.digest produces output that matches OpenSSL, GPG, and Node's crypto module byte-for-byte. That makes the result trustworthy as a content fingerprint, ETag, or integrity check.

OpenSSL-matched

Escape rooms

Print Morse clues and let teams decode the message. Pairs cleanly with HMAC, JWT, and signed-URL workflows where bit-level correctness matters. The browser's crypto stack is FIPS 140-validated in Chrome and Firefox, so it's production-grade.

lossless

CTF challenges

Audio or visual Morse appears in CTFs frequently. Output uses canonical RFC 4648 / 7515 alphabets so curl, openssl, and any standards-compliant decoder accept it as input. URL-safe variants drop padding for tokens that travel in query strings.

byte-identical

Accessibility study

Demonstrate Morse as an alternative input channel. Heavy hashing runs through useMemo so large inputs don't block typing. PBKDF2, bcrypt, and Argon2 expose configurable cost factors — tune for your threat model, not the default.

spec-grade

ARG hints

Hide instructions inside dot-dash patterns or audio clips. Same input plus same options always yields identical bytes. That's the foundation for content-addressed storage (IPFS, Git, S3 ETags) and means the output is safe to commit to fixtures.

production-ready
FAQ

Frequently asked questions

International Morse Code (ITU). Letters, digits 0-9, and the standard punctuation set are supported.
Three spaces (the convention) or a slash with surrounding spaces. The decoder accepts both.
Unsupported characters pass through verbatim, so you can spot them in the output and edit if needed.
No — the table covers ITU letters, digits, and standard punctuation. Special prosigns are not encoded.
No. The translation runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!