ITU/NATO alphabet · phone-spelling

Spell with the NATO phonetic alphabet

Alpha · Bravo · Charlie. Useful for spelling names, codes, or passwords over the phone.

NATO Phonetic Workspace
Input size
8 B
8 chars
Output size
43 B
spelled
Separator
" "
custom
Alphabet
NATO
ITU
Separator
input · text
output · NATO phonetic
Hotel Echo Lima Lima Oscar (space) Four Two
Quick Start

How to use NATO phonetic

Spells each letter using the ITU/NATO alphabet. Numbers and common punctuation also supported.

  1. 01

    Type text

    Any text — name, code, password.

    Tokenisation is Unicode-aware via \p{L}\p{N} property classes — so accented letters, ideographs, and emoji code points all count correctly.

    anyUTF-8Unicodecode pointslive
    input · textraw · UTF-8
    HELLO
    loaded · UTF-8UTF-8 · ready
  2. 02

    Each letter spelled

    H=Hotel, E=Echo, etc. Case-insensitive.

    Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.

    A-Z 0-9livememoisedoptionssnappy
    letters · optionsspelled · live
    Hotel Echo Lima Lima Oscar
    options applied · livelive
  3. 03

    Separator

    Default space. Try dash, newline, or any custom string.

    Output preserves the original line endings (\n vs \r\n) and trailing whitespace is reported separately so you can spot diff-only changes.

    customline endingswhitespacediff-cleanreproducible
    sep · counted - · ready
    Hotel - Echo - Lima
    counted · livecounted
  4. 04

    Copy or download

    One click.

    Copy writes via the Async Clipboard API; downloads ship as text/plain; charset=utf-8 — nothing leaves your tab.

    copyclipboardtext/plainblobclient-side
    export · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Text-processing fundamentals worth knowing

Tokenise with Unicode classes

Use \p{L}\p{N} with the u flag so accents, ideographs, and emoji count properly.

Normalise line endings

Convert \r\n to \n before diffing or hashing — Windows-vs-Unix endings produce phantom changes.

Mind invisible characters

Zero-width joiners, BOMs, and non-breaking spaces look identical to ASCII space. Strip them before comparison or storage.

Stream don’t slurp

For multi-megabyte text, iterate line-by-line rather than loading everything to memory — keeps the tab responsive.

Choose collation deliberately

Default JS sort is code-point order, not human alphabetical. Use Intl.Collator for locale-aware sorting.

Re-run after normalisation

NFC vs NFD changes byte length but not visible glyphs. String.prototype.normalize() before counts and comparisons.

Use Cases

When to use NATO phonetic

Anywhere clarity over voice matters.

Phone calls

Spell IDs, codes, postcodes without ambiguity. Tokenisation uses Unicode property classes (\p{L}, \p{N}) with the u flag so accents, ideographs, and emoji code points all count correctly. Surrogate-pair-aware counts mean 🚀 weighs 1, not 2.

Unicode-correct

Customer support

Read tickets, order numbers clearly. Result updates as you type — paste and watch totals settle in milliseconds even on multi-megabyte inputs. Heavy work runs through a memoised reducer so the editor never janks.

diff-clean

Radio comms

Standard for aviation, military, maritime. Output normalises line endings to LF for clean diffs across platforms. Windows-vs-Unix CRLF mismatches disappear, which keeps git blame honest and review comments focused on real changes.

instant counts

Spelling names

Difficult names over a noisy line. Code-point counts are stable across NFC/NFD normalisation. Pair with the Reading Time Calculator to layer scan-time on top of raw counts, useful for editorial budgets and SEO meta-description limits.

platform-aware

Memorize codes

Generate flash cards for studying. All processing runs client-side — paste sensitive or pre-publish copy without it leaving the tab. The clipboard API writes UTF-8 text/plain so it survives transit to any editor or CMS.

code-point-accurate

Voice assistants

Help Alexa/Siri pick up letters correctly. Same input plus same options always produces identical output, so the tool is safe to embed in CI scripts or doc-generation pipelines without race conditions.

lossless
FAQ

Frequently asked questions

ITU / NATO phonetic — Alpha through Zulu plus Niner for 9 (avoiding 'nine' / 'no' confusion).
No — all input is uppercased before lookup.
Numbers spelled as English words. Common punctuation: Stop, Comma, Dash, Slash.
Yes — each line is processed independently and joined with newline.
No. All processing runs locally.
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!