Appealing to Shared Knowledge: -잖아(요)

Some of the most Korean-sounding moves in conversation are the ones textbooks skip. -잖아(요) is one of them. It looks like it belongs in the Questions chapter, and it does — but it never really asks anything. Instead it takes a fact and hands it back to the listener with the flavour "come on, you know this." It reminds, it gently rebuts, it justifies. English reaches for a whole scatter of phrases to do this job — you know, as you know, but it's Sunday!, I told you, remember? — and Korean packs all of it into one invariant ending that clips onto any stem.

Get the feel of -잖아(요) and your Korean stops sounding like a list of announcements and starts sounding like a conversation between two people who share a history.

The core meaning: "you already know this"

The one idea behind -잖아(요) is presupposed shared knowledge. When you attach it, you are asserting that the information is something the listener can be expected to already know, has just witnessed, or should logically agree with. You are not delivering news — you are pointing at a fact you both have access to and reminding them of it.

In each case the speaker treats the fact as recoverable common ground: you've both seen the shop, you both know the prices, you both know what day it is. -잖아(요) simply calls that shared fact into service — usually to explain, justify, or gently correct.

It attaches to anything, including the past

Like its cousin -지(요)?, -잖아(요) is grammatically effortless: it clips onto any stem — verb, adjective, copula, past tense — with no agreement and no polarity juggling. The 요 marks polite 해요체; drop it for 반말.

Notice the pronunciation trap baked into the spelling. 잖아(요) is written with the double 받침 ㄶ (it is a squeeze of 지 않아), but the ㅎ is silent and the ㄴ slides onto the following vowel: 잖아 is read [자나] (jana), never "jan-ha." So 말했잖아 is malhaetjana, and 있잖아요 is itjanayo. Spell it with ㅎ, say it without.

Why it isn't really a question

The ending sits in the Questions family because of its confirming, agreement-fishing feel, but it does not expect an answer the way an information question does. Compare the two shared-knowledge endings side by side:

-지(요)? tentatively invites confirmation of something you believe but want ratified. -잖아(요) asserts the shared knowledge and presumes the matter is settled — the listener is expected to nod, not to decide.

English has no single equivalent

There is no one word to map -잖아(요) onto, which is exactly why learners under-use it. Depending on context it surfaces in English as:

• "you know / as you know" — invoking common ground: 여기 비싸잖아요 → "it's pricey here, you know."
• "but come on / but it's…!" — an exasperated appeal to the obvious: 오늘 일요일이잖아요 → "but it's Sunday!"
• "I told you / remember?" — reminding of a past exchange: 내가 말했잖아 → "I told you, remember."
• "as you can see / after all" — justifying: giving your reason as something already evident.

The unifying thread — the listener should already have this — is precisely what English scatters across all these phrases and Korean fuses into one suffix.

The social edge: it can sound like scolding

Here is the honest difficulty. Because -잖아(요) presumes "you should have known this," it carries a built-in undertone of mild reproach. Aimed sideways at a peer it is warm and matey — this song's great, you know. Aimed upward at an elder, a boss, or a customer, that same "you should have known" flavour reads as talking down or nagging, as if you're correcting someone who ought to have gotten it right.

This is not a grammar error — the sentence is perfectly formed — but it is a pragmatic one, and it's the kind that quietly makes native speakers wince. Toward a superior, drop -잖아요 and soften: 제가 지난주에 말씀드린 것 같은데요 ("I believe I mentioned it last week") hedges instead of accuses.

The lexicalized opener 있잖아(요)

You will constantly hear 있잖아(요) ("you know what… / listen…") launch a turn. It is -잖아(요) frozen onto 있다, functioning as a floor-grabber that flags "I'm about to bring something up you'll recognize." It softens the entry into a new topic rather than asserting a specific fact.

Its close relationship with the background-giving ending -거든요 is drawn out on the interactional -잖아요 page — worth reading once the confirming use here feels solid.

Common Mistakes

1. Using -잖아(요) for genuinely new information. This is the flagship error. -잖아(요) presupposes the listener already knows; deliver actual news with it and you assert shared knowledge that doesn't exist. Korean has a dedicated ending for volunteering fresh background — -거든요.

2. Aiming it upward where it sounds like a rebuke. Grammatical, but the "you should have known" undertone reads as scolding toward a boss, teacher, or customer.

3. Reading 잖아 as "jan-ha." The ㅎ of the ㄶ 받침 is silent; the ㄴ liaises onto the vowel. 좋잖아요 is jochanayo, not "jot-jan-ha-yo."

4. Treating it as an information question and waiting for a real answer. -잖아(요) fishes for recognition, not a verdict; pausing for a yes/no misreads its whole function.

Key Takeaways

• -잖아(요) appeals to presupposed shared knowledge — "you know this / as you know / but come on, remember?" It reminds, justifies, or gently corrects rather than asking.
• It clips onto any stem including the past with no agreement; 요 = polite 해요체, bare -잖아 = 반말.
• Spelled with ㄶ but pronounced [자나] (jana) — the ㅎ is silent, the ㄴ liaises.
• Contrast with -지(요)?: -지(요)? tentatively invites confirmation; -잖아(요) assertively presumes agreement.
• Two real errors: using it for new information (use -거든요 instead) and firing it upward, where "you should have known" turns into scolding.