Spoken-Only Forms: -거든요, 근데, -잖아요

Some Korean forms are almost never written down in formal prose — but leave them out of your speech and you sound like a textbook read aloud. These are the conversational lubricants of 구어체: the endings and connectors that supply background, open a turn, flag shared knowledge, and buy thinking time. -거든요, 근데, and -잖아요 are three of the most frequent words in spoken Korean and three of the rarest in a report. This page is about deploying them — because using them well is precisely what makes your Korean sound like a person talking rather than a translation.

-거든(요): supplying unrequested background

-거든(요) attaches to a plain stem — verb or adjective + 거든요, past 았/었거든요 — and it does one specific job: it supplies background or a reason the listener didn't ask for, answering an unspoken "why?" or "here's the thing." It quietly frames what you just said, as if to say let me fill you in.

The feel is confidential, a little bit "let me explain." That is why it lands as friendly in speech and out of place in an impersonal document, where you would simply state the reason with -기 때문이다 or -아서.

Don't confuse background -거든요 with conditional -거든

The same shape -거든 has a second, separate life as a conditional ("if / when"), covered in -거든: the spoken 'if'. The two are told apart by position and intonation: background -거든(요) ends a sentence and falls; conditional -거든 sits mid-sentence and is followed by a main clause (usually a command or plan).

Compare that with sentence-final 시간 없거든요 ("the thing is, I don't have time") — same four letters, opposite function. Keep them apart.

근데: the all-purpose spoken opener

근데 is contracted from 그런데, and it is the single most common way to open a casual turn. It covers a huge range — "but," "so anyway," "by the way," "and then" — often carrying almost no adversative meaning at all, just marking that you are taking the floor.

In writing, 근데 gets restored to its full 그런데, and even that skews conversational — formal prose reaches for 그러나 ("however") or 하지만 instead. The contracted 근데 is pure speech and chat. (Its close relative for topic-shift is treated in 그런데/근데 topic shift.)

-잖아(요): flagging shared knowledge

-잖아(요) attaches to a plain stem and flags that what you're saying is something you both already know — "you know," "come on, as we're both aware." It appeals to shared ground, often with a nudge of you already know this, so agree with me.

Because -잖아(요) presupposes shared knowledge, using it about something genuinely new to the listener sounds pushy or presumptuous — you are claiming they already knew when they didn't. Its natural home is speech among people with common ground; it is essentially absent from formal writing.

The fillers and softeners that hold speech together

Fluent 구어체 is not just these three endings. It is threaded with discourse fillers that buy time and mark hesitation, and a softener that takes the edge off requests.

• 뭐 — "well, um, whatever, sort of."
• 그 — "uh…," reaching for the next word (often lengthened: 그으…).
• 저기 — "um, excuse me," a turn-opener to get attention gently.
• 막 — "just, like," vaguely intensifying or listing.
• 좀 — literally "a little," but in speech a politeness softener meaning "if you would."

That 좀 in the second example is doing real politeness work — it turns a bare command into a soft request. Drop it and 도와주실 수 있어요? is fine but flatter; with it, the ask feels considerate.

These forms belong to chat, too — not just speech

An important boundary: "spoken-only" really means "spoken-and-chat," not "audible speech alone." Texting, DMs, and comment threads are written channels that run on 구어체 grammar — because they are conversation that happens to be typed. So -거든요, 근데, and -잖아요 are perfectly at home in a text to a friend, even though they would be wrong in an emailed report. Chat also spells things as they sound, so you will see the reduced spellings native texters use — 뭐 written as 머, 그런데 as 근데 or even 근뎅, 좋아 as 조아. That phonetic spelling is the same 구어체 impulse pushed one step further onto the page; it is covered in texting: spelling as pronounced.

The lesson: the split is not "audible vs written," it is conversational vs expository. Chat sits firmly on the conversational side.

For English speakers: these are your "I mean," "like," "you know"

Do not think of 근데, 뭐, 막, -거든요, -잖아요 as sloppy or lazy. They are the exact functional equivalents of English's the thing is, I mean, like, you know, by the way — the connective tissue of natural conversation in every language. A learner who avoids them out of a wish to sound "correct" ends up sounding robotic, because real speech is not a string of textbook sentences; it is stitched together with exactly this kind of framing and hedging. The skill is not to eliminate them but to place them where a native would. The opposite failure is real too: over-stack 막 and 그 and the sentence stalls into filler soup. Aim for the natural density you hear from fluent speakers — present, but not wall-to-wall.

Common Mistakes

1. Writing -거든요 / -잖아요 into formal prose. These are speech-and-chat forms; in an essay or report they read as jarringly casual.

2. Stiffly avoiding these forms and sounding robotic. The reverse error. Speech built only from clean textbook sentences, with no 근데/뭐/-거든요, sounds translated and lifeless.

3. Using -잖아(요) about genuinely new information. It presupposes the listener already knew; applied to news, it sounds presumptuous.

4. Confusing background -거든요 with conditional -거든. Sentence-final -거든(요) supplies a reason; mid-sentence -거든 means "if/when."

Key Takeaways

• -거든(요) supplies unrequested background/reason — "the thing is…." Don't confuse it with conditional -거든 ("if/when").
• 근데 (from 그런데) is the all-purpose spoken opener: "but / so anyway / by the way." Formal writing restores 그런데 or uses 그러나.
• -잖아(요) flags shared knowledge ("you know, as we both know") — presumptuous if the info is actually new.
• Fillers 뭐, 그, 저기, 막 and softener 좀 are the functional twins of English I mean, like, you know — using them makes 구어체 sound alive; avoiding them sounds robotic, and overstacking them stalls the sentence.