Logo

MonoCalc

/

Soundex Calculator

Text
Encode one name, compare a pair, or work through a list
Up to 100 characters

Worked examples — each one exercises a different rule

Different implementations disagree on the edge cases

The census standard: vowels separate identical consonants, H and W are transparent, a second letter sharing the first letter's code is dropped, and the code is cut to four characters.

Encoding options

NARA fixes this at 4; longer codes are for research use
Decimal places on the similarity score

Soundex coding chart

DigitLetters
1B F P V
2C G J K Q S X Z
3D T
4L
5M N
6R
A E I O U Y H W

Vowels are not coded, but they separate identical consonants. H and W do neither — they are transparent.

American (NARA) Soundex · normalised as ASHCRAFT

A

261

First letter ADigits 261Truncated

Letter flow — hover a chip to highlight its row in the trace

AS 2HC 2R 6AF 1T 3

Step-by-step derivation

#LetterGroupDigitActionCode
1AVowelKept as the first character of the codeA
2SC G J K Q S X Z2Appended → A2A2
3HH / WTransparent — the previous consonant's code carries across itA2
4CC G J K Q S X Z2Same code as the previous consonant — collapsed into one digitA2
5RR6Appended → A26A26
6AVowelDropped — but it separates identical consonantsA26
7FB F P V1Appended → A261A261
8TD T3Beyond 4 characters — truncated awayA261

About This Tool

Soundex Calculator – Turn Names Into Phonetic Codes

Soundex is a phonetic index: it compresses a name into one letter and three digits so that spellings which sound alike land on the same code. Robert and Rupert both become R163. That single idea, patented by Robert C. Russell and Margaret King Odell around 1918, is still doing real work a century later inside genealogy databases, library catalogues, record-linkage pipelines and the SOUNDEX() function of almost every SQL engine. This Soundex calculator encodes a name, a pair of names, or a whole pasted list — and, unlike a plain code dumper, shows you every step of the derivation.

How the Soundex algorithm works

The input is uppercased, accents are folded away and everything outside A–Z is stripped. The first letter is kept verbatim as the head of the code. Every remaining letter is then mapped to a digit: 1 = B F P V, 2 = C G J K Q S X Z, 3 = D T, 4 = L, 5 = M N, 6 = R. Vowels plus H, W and Y are not coded at all. Letters that share a digit and sit next to each other collapse into one, the sequence is cut after three digits, and anything shorter is padded with zeros — which is why Lee becomes L000.

The two rules everyone gets wrong

The first is H and W transparency. When two letters with the same digit are separated only by an H or a W, they still count as adjacent and produce a single digit. That is why Ashcraft encodes as A261 and not A226. A vowel between them does the opposite: it separates them so both are coded, giving Tymczak → T522. The second is first-letter suppression— if the second letter shares the first letter's digit it is dropped, so Pfister is P236 rather than P123.

Why your database disagrees

Implementations diverge, and the differences bite in production. SQL Server's SOUNDEX() does not apply the H/W rule the same way, so it reports A226 for Ashcraft. MySQL never truncates — SOUNDEX('Quadratically') returns the six-character Q36324. The textbook Simplified Soundex skips both special rules. And Refined Soundex abandons the four-character format entirely for a ten-group chart that produces far fewer collisions. The variant selector encodes your name under all of them at once so you can see exactly where the codes part company.

Soundex is a recall tool, not a match
Smith, Smyth and Schmidt all collapse to S530, while Carr and Karr never match because their initial letters differ. Use the code to shortlist candidate records, then confirm them with a second signal such as a date of birth or an edit-distance score.

What you can do with the tool

Single mode encodes one name and prints a letter-by-letter trace table alongside a chip strip that shows which letters were kept, dropped, collapsed or truncated. Compare encodes two names, returns a match verdict and scores how close the codes are position by position. Bulk turns a pasted list into a Name → Soundex table with a collision rate, and Group clusters that list by code so duplicates surface immediately — the core move in any deduplication or record-linkage job. Reverse takes a code such as R163, decomposes it back into the candidate letter sets, and matches it against your own list or a built-in surname dictionary. Variants puts all five algorithms side by side.

Genealogy, deduplication and fuzzy search

The U.S. National Archives indexed the 1880–1920 federal censuses by Soundex precisely because enumerators wrote names by ear. If an ancestor has vanished from a census index, encoding the surname and searching by code recovers the mis-transcribed spellings. The same trick powers "sounds like" search over a customer or patient table: store the code in an indexed column, encode the query term, and match on equality. For surname particles such as Van, De, Mc or O', NARA sometimes filed a name both with and without the prefix — switch on prefix stripping to get both codes at once.

Limitations and alternatives

Soundex was tuned for English surnames and shows it: it is weak on Slavic, Chinese and Arabic transliterations, it is entirely dependent on the first letter being right, and it produces plenty of false positives. When precision matters more than recall, look at the Metaphone and NYSIIS codes shown alongside the Soundex result — both model English pronunciation more carefully. Every calculation here runs locally in your browser, so name lists never leave your device.

Frequently Asked Questions

Is the Soundex Calculator free?

Yes, Soundex Calculator is totally free :)

Can I use the Soundex Calculator offline?

Yes, you can install the webapp as PWA.

Is it safe to use Soundex Calculator?

Yes, any data related to Soundex Calculator only stored in your browser (if storage required). You can simply clear browser cache to clear all the stored data. We do not store any data on server.

How does the Soundex Calculator work?

The name is uppercased, accents are folded away and everything outside A–Z is stripped. The first letter is kept as-is, every remaining consonant is mapped to a digit from 1 to 6, adjacent letters sharing a digit collapse into one, vowels split them apart again, and the result is cut to four characters or padded with zeros. The tool shows that whole derivation letter by letter rather than just handing you the code.

Why do Robert and Rupert produce the same code?

Both encode to R163. Soundex keeps the initial R, drops the vowels, then codes B and P as 1 because they belong to the same group, R as 6 and T as 3. That is the entire point of the algorithm — it deliberately merges sounds that a census enumerator or a call-centre agent could plausibly have written down either way.

What is the H and W transparency rule?

When two letters with the same digit are separated only by H or W, they still count as one digit. Ashcraft therefore becomes A261 rather than A226, because the S and the C are treated as adjacent across the H. A vowel between them would instead keep them apart and both would be coded, which is why Tymczak becomes T522.

Why does my database return a different code?

Implementations disagree. SQL Server's SOUNDEX does not apply the H/W transparency rule, so it returns A226 for Ashcraft, and MySQL never truncates — SOUNDEX('Quadratically') returns the six-character Q36324. Switch the variant selector to the engine you are comparing against before assuming a bug in your query, and re-check against your specific server version.

How accurate is Soundex for matching names?

It is fast and famously forgiving, but also noisy. It only ever considers the first letter plus three consonant sounds, so Smith, Smyth and Schmidt all collapse to S530 while Carr and Karr do not match at all because their initials differ. Treat matches as candidates for review, not as confirmed identities, and consider Metaphone or NYSIIS when precision matters more than recall.

Is my list of names uploaded anywhere?

No. Encoding, grouping and export all run locally in your browser with no network requests, so customer, patient and genealogy lists never leave your device. Only your option settings are remembered, in local storage.