그런데 · 근데: But / By the Way (Topic Shift)

If you listen to five minutes of natural Korean conversation, you will hear 그런데 — usually in its contracted form 근데 — over and over. It is the single most common spoken conjunction, and it is tricky for English speakers because it does two different jobs that English splits between two different words. Sometimes 그런데 is "but" (a mild contrast). Just as often it is "by the way / so / anyway" (a topic shift that contradicts nothing at all). Learners who were taught only "그런데 = but" end up baffled when a Korean opens a totally friendly new topic with it — where's the contrast? There isn't one, and that's the whole point of this page.

Job 1: mild contrast ("but / however")

In its first job, 그런데 works like a gentler 하지만: the second clause pushes back on the first. But it's softer — less of a hard reversal, more of a "…though" or "and yet."

You could use 하지만 in both of these. The difference is texture: 하지만 states a flatter opposition, while 그런데 keeps the conversation soft and open-ended, as if the two facts are just sitting next to each other with a slight tension.

Job 2: topic shift ("by the way / so / anyway")

This is the job English does not map onto "but." Here 그런데 introduces new-but-related information or steers the conversation to a fresh topic — and it carries no contrast whatsoever.

Nothing is being contradicted in either sentence. The first is a clean topic change ("so, by the way…"); the second adds a related follow-up ("…and, on that note…"). If you mechanically render these 그런데/근데 as "but," you get nonsense — "But what did you do yesterday?" Translating every 그런데 as "but" is the classic learner trap.

근데: the contraction that runs conversation

In real speech, 그런데 almost always shortens to 근데 [geunde]. This isn't sloppy or substandard — it's simply how the spoken language works, the way English "going to" becomes "gonna." 근데 peppers casual conversation as a soft "so / anyway / but" pivot, often several times a minute, and using it is a mark of natural fluency.

The one hard rule: 근데 is spoken only. In formal writing — reports, essays, official emails — you write out 그런데 (or reach for the more formal 그러나 if a real contrast is meant). Writing 근데 in a business document reads the way "gonna" would in a cover letter.

The softening opener: 근데 말이야 / 그런데 말이에요

A very common conversational move is to pad the pivot with 말이야 / 말이에요 (literally "it's the thing that…"), which softens the transition and gently claims the floor — roughly "so, listen…" or "here's the thing…".

These openers buy you a beat before you drop your actual point. They're pure discourse lubricant, and they sound very native.

Where it comes from: 그렇다 + -(으)ㄴ데

그런데 is transparently 그렇다 ("to be so") + the connective ending -(으)ㄴ데. Since 그렇다 is ㅎ-irregular, 그렇- + -은데 loses the ㅎ, giving 그런데 — "it being so, …". And -(으)ㄴ/는데 is exactly the "set the scene, then pivot" ending you meet inside clauses (covered on -(으)ㄴ/는데): 비가 오는데 우산이 없어요 ("it's raining, and — the thing is — I have no umbrella"). That clause-level ending does the same dual work as the conjunction: it can set up a mild contrast or just supply background before a turn. So 그런데 is literally that pivot, promoted to the front of a new sentence. Once you see that -(으)ㄴ데 is neutral about whether a contrast follows, the two jobs of 그런데 stop looking like a coincidence.

그런데 vs 하지만: contrast that reverses vs. a pivot

Keep 그런데 apart from the pure adversatives on the 그러나 · 하지만 · 그렇지만 page. 하지만 always reverses — it needs a genuine contradiction. 그런데 may or may not — it's happy to reverse, but it's equally happy to just pivot. So the two are only interchangeable in 그런데's contrast job; in its topic-shift job, 하지만 can't stand in.

Common Mistakes

1. Using 하지만/그러나 for a friendly topic change. Steering to a new topic is 그런데's specialty; the pure reversers can't do it.

2. Writing 근데 in formal text. The contraction is spoken only; formal writing wants the full 그런데.

3. Using 그런데 for a sharp contrast in formal writing. 그런데 is soft and spoken; a crisp written "however" wants 그러나.

Key Takeaways

• 그런데 does two jobs: mild contrast ("but") and topic shift ("by the way / so / anyway") — the second has no contrast at all.
• Don't reflexively translate 그런데 as "but"; check whether the clauses actually clash.
• 근데 is its everyday spoken contraction — natural and constant in conversation, but spoken only; write 그런데.
• 근데 말이야 / 그런데 말이에요 are soft floor-claiming openers ("so, listen…").
• It's 그렇다 + -(으)ㄴ데, inheriting that ending's neutral "background-then-pivot" nature.
• Versus 하지만: 하지만 always reverses; 그런데 may just pivot. For a sharp formal contrast, use 그러나.