-(으)ㄴ/는데: But / Whereas (Contrast & Background)

If you learn only one connective beyond -지만, make it -(으)ㄴ/는데. It is one of the most-used endings in spoken Korean, and English has nothing that maps onto it cleanly. We reach for "but" or "and" to translate it, but its real job is subtler: it lays down a contrasting or scene-setting backdrop, and then lets the next clause land against that backdrop. Sometimes that backdrop genuinely opposes what follows ("my brother is tall, whereas I'm short"); sometimes it just sets the stage for a question or a comment ("it's raining out, and I don't have an umbrella"). This page covers the contrast/background meaning and its allomorphy; its close relative — the way -는데 politely opens a conversation, request, or discovery — gets its own treatment on -는데 as background setup.

The core: a contrasting backdrop, not a hard "but"

Compare two ways of saying the same rough thing:

In both, the first clause is not a fact you are arguing against so much as a setting you place the second clause inside. That is the feel of -(으)ㄴ/는데: "given that X is the case… Y." It is softer and more conversational than -지만, and it is exactly why it feels natural before a question, a suggestion, or a piece of new information.

Notice there is no real "but" in that last sentence — English would just say "and." The 는데 clause frames the situation ("it's raining out, that's the backdrop") so the problem in the second clause has somewhere to land.

The allomorphy: this ending forces the adjective/verb split

Here is the part learners have to drill, because -(으)ㄴ/는데 does not attach to every stem the same way — unlike -지만, which ignores word class entirely. The ending you choose depends on the word class and the tense:

The single most useful thing to realize is that this split is not new. It is the exact same fork as the attributive (noun-modifying) system: present verbs take -는 (가는 사람, "the person who goes"), adjectives take -(으)ㄴ (좋은 사람, "a good person"). The -데 ending just glues onto whichever attributive form the word already uses. If you can build 가는 and 좋은, you can build 가는데 and 좋은데. Master one and you get the other for free.

In 먹는데 the ㄱ before 는 nasalizes to [ŋ] — you actually say meongneunde, and the romanization shows it. In 좋은데 the ㅎ of 좋다 quietly drops before the vowel, so it comes out joeunde. Both are worth pronouncing out loud a few times.

Past tense collapses the split

One relief: in the past tense, the word-class fork disappears. Everything — verbs, adjectives, the copula — takes -았/었는데. You never say ×좋았은데; a past adjective takes the same -는데 as a verb.

The copula: 이다 → 인데

The copula 이다 becomes 인데 (and 아니다 → 아닌데). This is a workhorse for introducing yourself and setting up context.

Here 생일인데 is doing pure setup work: "it's my birthday, that's the backdrop, so…" and then the invitation follows. This bleeds straight into the request/discovery use covered on the background page.

-는데 vs -지만: the distinction to internalize

English "but" covers both -지만 and -는데, so beginners over-use the blunt one. The rule of thumb:

• -지만 is a flat adversative between equals: it weighs two facts and says the second runs against the first. "Expensive but pretty."
• -(으)ㄴ/는데 frames the first clause as the scene or context you're contrasting with or building on. It is softer, and it can lead into a question or request where -지만 cannot.

The first genuinely balances two opposing properties. The second isn't really contrasting anything — 비싼데 just sets the stage ("it's a little pricey, and given that…") before floating the question. Whenever your second clause is a question, suggestion, or request and the first is merely the context for it, Korean strongly prefers -는데.

Because -는데 softens rather than confronts, it also sounds warmer in comparisons between people. You can say 형은 크지만 저는 작아요, but 형은 큰데 저는 작아요 sounds more like an easy observation than a debate point.

Common Mistakes

1. Using the verb ending -는데 on an adjective. Adjectives take -(으)ㄴ데, exactly as they take -(으)ㄴ in attributive position. This is the number-one error.

• ❌ 이 방은 좋는데 좀 작아요. — wrong: 좋다 is an adjective, so it can't take 는데.

2. Using the adjective ending -은데 on a present-tense verb. Present action verbs and 있다/없다 take -는데, never -은데.

• ❌ 저는 매일 운동한데 살이 안 빠져요. — wrong: 운동하다 is a verb, so it needs 하는데.

3. Defaulting to -지만 for a setup. When the first clause is background for a question or request, -지만 wrongly asserts a contrast and sounds abrupt.

• ❌ 지하철역을 찾지만 어디에 있어요? — wrong: you're not contrasting, you're giving context to ask.

4. Marking past tense in the wrong place. If the first clause happened in the past, the tense goes on the -는데 clause as -았/었는데; don't leave it in the present and hope the second verb carries it.

• ❌ 열심히 준비하는데 결과가 안 좋았어요. — wrong: the preparing was also in the past.

Key Takeaways

• -(으)ㄴ/는데 sets a backdrop. It is not a hard "but" — it lays down a contrasting or scene-setting first clause that the second clause lands against, which is why it also opens questions and requests so naturally.
• The ending tracks word class, exactly like the attributive system: present verbs and 있다/없다 → -는데; adjectives → -(으)ㄴ데 (좋은데, 큰데); copula → -인데.
• Past tense collapses the split: everything takes -았/었는데 (봤는데, 좋았는데).
• -지만 vs -는데: -지만 pushes back (real contrast between equals); -는데 frames context, especially before a question or request. When your second clause asks or suggests something, choose -는데.