DevTools Logo

Numeronym Generator

Numeronym Generator

Abbreviate words the tech-industry way — internationalization → i18n, accessibility → a11y — with a reference table of the classics.

Free text works — every word becomes first letter + interior letter count + last letter.

Try a sample:

Examples

The classic trio

Input
internationalization localization accessibility
Output
i18n l10n a11y

The three words that made the pattern software culture's default shorthand, in one paste.

Unicode edge

Input
über città
Output
ü2r c2a

Letter counting uses the Unicode letter class, so accents count as letters and stay in position.

Short-word guard

Input
the fox ran
Output
the → —, fox → — (dashes, letter counts shown)

Three-letter words cannot compress; the tool flags them instead of producing a misleading abbreviation.

About this tool

A numeronym abbreviates a word by keeping its first and last letters and replacing everything between with the count: internationalization becomes i18n because exactly eighteen letters sit between the i and the final n. The pattern goes back decades — Apple engineers used 3Com-era numeronyms in the 1980s — but it became software culture's shorthand through i18n and l10n, the localization-world terms that were too long to type in every commit message. The Numeronym Generator applies the rule mechanically to any word you type, so you can coin a team-internal abbreviation without miscounting the interior letters.

The mechanics are simple and strictly followed: first letter, interior letter count, last letter. Words shorter than four letters cannot become numeronyms — with only two interior letters the form would shrink nothing — so fox, the and cat stay unconverted and are flagged in the table rather than silently mangled. Multi-word input converts word by word: paste a glossary and every eligible word gets its abbreviation, letter count and a copyable column. Hyphenated compounds like cross-platform count letters only (c11m), and apostrophes contribute no letters, so don't is d2t — the rules are stated, not guessed.

Letter counting is Unicode-aware via the Unicode letter class, not byte lengths or ASCII ranges. Über becomes Ü2r with the umlaut preserved as the first letter, città becomes c2a, and non-Latin scripts abbreviate by the same rule. Original letter case is preserved on the kept letters — JavaScript shortens to J8t, keeping the signature capital J. That matters for brand words, where the abbreviation must remain recognizable as the thing it abbreviates.

The reference table lists the classics with context: i18n (internationalization), l10n (localization), a11y (accessibility), g11n (globalization), m17n (multilingualization), t9n (translation), c14n (canonicalization, XML's normalize-to-one-form), k8s (kubernetes), p13n (personalization) and n7m — numeronym itself, the pattern's favorite self-reference. Every listed entry is re-derived by the same pure function the generator uses, so the table can never drift out of sync with the rule. Everything runs on the device; nothing is uploaded, and the abbreviation list copies in one click for commit messages, docs or style guides.

What this tool does not do

  • The rule is fixed — first/interior-count/last; pattern-style numeronyms like e2e or b2b are a different convention and are not generated.
  • Hyphens and apostrophes are not preserved in the output; only letters participate in the abbreviation.
  • The reference table covers widely used numeronyms; team-internal coinages belong in your own style guide.

How to use this tool

  1. Type or paste words

    Enter one word or a whole list — free text works, punctuation and digits split the tokens naturally.

  2. Read the word-by-word table

    Each row shows the word, its numeronym and its letter count; words under four letters show a dash instead of a fake abbreviation.

  3. Check the reference table

    Browse the classics — a11y, i18n, k8s, c14n — to see the convention you are coining into.

  4. Copy the abbreviation column

    One click copies every convertible numeronym, one per line, for commit messages and docs.

Use cases

Naming internal tools

Coin short project codenames the way k8s did — recognizable to the team, compact in URLs, repos and Slack.

Commit and doc shorthand

Use a11y or i18n correctly in commit prefixes, issue labels and docs, and verify new coinages count what you think they count.

Teaching the convention

Show students or new teammates how the abbreviation pattern works with live letter counts and the reference table.

The numeronym rule and its edges

Input shapeBehavior
4+ lettersfirst letter + interior count + last letter (internationalization → i18n)
≤3 lettersNo conversion — at least one interior letter is required (fox stays fox)
Hyphenated compoundLetters counted across the hyphen, hyphen not kept (cross-platform → c11m)
ApostropheApostrophe is not a letter (don't → d2t)
Unicode lettersCounted by the Unicode letter class (über → ü2r, città → c2a)
Mixed caseFirst/last letters keep original case (JavaScript → J8t)

The reference table is validated by the same function — every listed numeronym re-derives from its word.

Common mistakes

Mistake:Miscounting interior letters by hand.

Fix:The whole point of the tool: i18n is 20 letters, and one miscount gives you i17n in a PR title forever. Let the counter do it.

Mistake:Numeronymizing tiny words.

Fix:A 3-letter word has nothing to compress — abbreviations like e2e are letter-pattern numeronyms, not this rule. The table dashes short words instead of faking it.

Mistake:Assuming numeronyms are self-explanatory.

Fix:k8s reads as noise to anyone outside the team. Pair a new coinage with the full word on first use, exactly like the reference table does.

Frequently asked questions

What exactly is a numeronym?

A numeronym is a word abbreviated to first letter + count of interior letters + last letter: internationalization has 18 letters between its i and n, so it becomes i18n. The form existed in 1980s computing (canonically attributed to DEC and Apple engineers) and went mainstream through the localization vocabulary — i18n, l10n — because those words are unwieldy in commit messages. Today a11y, k8s and n7m are everyday examples across software culture.

Why can't short words become numeronyms?

The pattern needs at least one interior letter to replace, so the word must have at least four letters. fox has only one interior letter; abbreviating it to f1x saves nothing and reads as a typo. That is why the tool dashes words of three letters or fewer and shows their letter count instead — the honest answer is "this word cannot compress under this rule," not a fabricated abbreviation.

How are accented and non-Latin letters handled?

Letter counting uses the Unicode letter class, not ASCII: é, ü, ñ and letters from any script count as letters, and the first/last letters keep their accents and original case. über becomes ü2r, città becomes c2a, JavaScript becomes J8t. Hyphenated compounds count their letters across the hyphen (cross-platform → c11m) because the hyphen itself is not a letter.

Is k8s really derived from kubernetes with this rule?

Yes — kubernetes has ten letters, eight of them interior, so the rule produces k8s. The same mechanical derivation gives a11y from accessibility, c14n from canonicalization, and n7m from numeronym itself, which is the community's favorite self-reference. The tool's reference table is validated by the same function, so every entry re-derives correctly rather than being typed in by hand.

When should I use a numeronym — and when not?

Use one where the audience already knows the term: commit prefixes, issue labels, internal docs, team naming. Avoid them in user-facing copy or first contact with newcomers — k8s reads as noise to someone who has never seen it, and a11y used around accessibility newcomers can obscure the actual topic. The practical pattern: pair a fresh coinage with the full word on first use, then use the short form.

Is anything sent to a server?

No. The generator is pure string processing in your browser — no API, no logging, no network call. Your word list persists locally between visits so a running glossary survives a refresh, and the abbreviation column copies in one click for commit messages, style guides or docs.

References & standards