Sing vs sin: why do my nasal endings collapse into each other?

Because both endings are nasal sounds — air humming out through the nose rather than the mouth — and the only thing that separates them is exactly where in the mouth the tongue blocks the airflow, which is a small, easy-to-blur distinction if your first language doesn't require it.

30-second version: /n/ (sin) puts the tongue tip on the ridge behind the top teeth, nose humming. /ŋ/ (sing) lifts the back of the tongue to the soft palate instead, tip lying flat and doing nothing, same nasal hum. Both sounds vibrate the nose identically — the entire contrast is tongue position, nothing else — which is why it's easy to under-commit to the back-of-tongue gesture and land somewhere in between, closer to /n/.

Why this contrast is easy to lose

Several languages either merge final /n/ and /ŋ/ entirely or don't use /ŋ/ as an independent word-final sound at all, using it only before /k/ or /g/. Mandarin and several southern Vietnamese dialects are documented cases of this merger; several other languages have /ŋ/ but only ever before a /k/ or /g/, so English words that end the syllable directly on /ŋ/ with nothing after it — sing, long, thing — ask for a gesture those languages never require in that exact position.

The distinction matters because it's genuinely a different word, not a shade of accent — sin and sing, ran and rang, thin and thing are all real minimal pairs where this one tongue-placement choice is the entire difference.

How sayit tells them apart

The two sounds have distinct acoustic resonances from where the tongue makes contact — a front closure (/n/) and a back closure (/ŋ/) shape the air cavity differently even though both are nasalized. sayit's phoneme model reads that difference directly, so "sing" produced with the tongue tip forward (making /n/ instead of /ŋ/) shows up as a substitution at that final slot, with the "sounded like" hint naming "sin" if that's the real word it landed on.

What the fix looks like

Practice the two endings as a direct back-and-forth: say /n/ — tongue tip forward, feel it touch the ridge — then say /ŋ/ — pull the tip down and back, lift the back of the tongue instead, feel the contact point move from the front of your mouth to somewhere near the soft palate, well back. Doing this slowly, alternating, trains the tongue to actually move rather than staying in one comfortable, forward position for both.

A common secondary mistake worth checking for: adding a hard /g/ after /ŋ/ — "sing" becoming "sing-g." In most English varieties, word-final "-ng" is just /ŋ/ with no /g/ afterward; the /g/ only appears in words like "finger" where the spelling puts a vowel after the "ng." If your /ŋ/ is landing but with an extra /g/ tacked on, that's a separate, smaller fix from the tongue-placement issue.

Drill it

Sun vs sung is the closest direct pair available; also practice sin vs sing, ran vs rang, and thin vs thing by recording each word individually and comparing.

Record: "He sang a song while thinking about the long thing." Four /ŋ/-ending words in one sentence, none of them adjacent to a /k/ or /g/ that would make the back-of-tongue gesture easier by habit — a fair test of whether the sound holds up on its own.

The /phonemes/n and /phonemes/ng pages have the individual articulation steps.

How do I know it's improving?

Check whether the fix holds specifically on word-final /ŋ/ with nothing following it, since that's the hardest position — many learners can produce /ŋ/ correctly before a /k/ (where the tongue was already moving back anyway) well before they can produce it cleanly on its own at the end of a word. Isolate that specific position in your practice rather than only testing words where /ŋ/ is followed by another back consonant.

Try it

Open sayit free — no install, no card — and record the drill sentence above. If any /ŋ/ ending comes back as a substitution toward /n/, slow that one word down and check the back-of-tongue contact specifically before trying the full sentence again.