(으)면 meaning — the Korean "if" that does more than one job (28 real examples)

(으)면 is the ending textbooks translate as "if", and that translation is right about half the time.

The other half it means "when" — not a hypothetical at all, but something that reliably happens. 찾으면 is "if you find it" in one sentence and "when you find it" in the next, and Korean does not mark the difference. The listener works it out from whether the thing is likely.

That is why subtitles are unreliable here. A translator picks one reading and commits to it, and you never see that the original left both open.

Every example below came out of clips we transcribed for our shadowing library, so these are the shapes it actually takes in speech rather than the ones a textbook builds to demonstrate a rule.

으면 or 면 — which one you hear

The 으 is a connector, not part of the meaning. It appears only when the stem ends in a consonant, purely so the two sounds can join.

찾다 → 찾으면. 가다 → 가면.

So you will meet both shapes constantly, and they are one ending. If you search for 면 alone you will miss half the examples; if you search for 으면 you will miss the other half.

The entries below keep whichever shape the speaker actually used.

Why subtitles keep hiding this one

A subtitle line has to fit on screen and has to read as natural English, and (으)면 is the first casualty of both constraints.

The usual fix is to drop the conditional entirely. 찾으면 말해줘 becomes "let me know" — accurate in effect, but the "if you find it" has quietly gone. You hear a two-clause sentence and read a one-clause one, and after a hundred of those your ear stops expecting the seam.

The second fix is worse for learners: the translator picks "when" because the outcome is certain, and now the sentence looks like it is about timing. Nothing in the Korean said that.

This is the specific reason a conditional you have technically "learned" can stay invisible for months. It is on screen constantly and almost never in the translation.

Setting up a condition — casual

The base use: name a situation, then say what follows from it.

The clause order is fixed and it is the opposite of the flexible English one. The condition always comes first, then the result. You cannot append it the way English appends "if you want" to the end of a sentence.

Notice how many of these are not hypothetical at all. Several describe things the speaker fully expects to happen.

One thing to watch as you read: how rarely these are genuinely hypothetical. Korean reaches for this ending whenever one thing depends on another, including chains of events that are already underway. English would use "when", "once", or nothing at all for many of them.

• 이거 두 개 섞어서 먹으면은 (meogeumyeoneun) — Mixing these two... Literally: 먹으면은 is said 머그며는.
• 짜장면 이런 거였으면 좋겠다 (geoyeosseumyeon) — I hope you get something like jjajangmyeon. Literally: 거였으면 is said 거여쓰면.
• 뭔가 보물을 하나만 찾으면. (chajeumyeon) — If I find just one treasure. Literally: 찾으면 is said 차즈면.
• 진짜 아무도 믿으면 안 돼. (mideumyeon) — You can never trust anyone. Literally: 믿으면 is said 미드면.
• 웃으면 안 돼 웃으면 안 돼 (useumyeon) — You can't laugh, you can't laugh. Literally: 웃으면 is said 우스면.
• 날 보고 있으면 따라해야지. (isseumyeon) — If you're looking at me, copy what I'm doing. Literally: 있으면 is said 이쓰면.
• 눈을 안 보고 있으면 어떡해 (isseumyeon) — How could you not make eye contact? Literally: 있으면 is said 이쓰면.
• 얘들아 빨리 나왔으면 일해라 (nawasseumyeon) — Guys, if you're out, get to work. Literally: 나왔으면 is said 나와쓰면.
• 가만히 있었으면 안 뽑았잖아 (isseosseumyeon) — If you stayed quiet I wouldn't have picked you. Literally: 있었으면 is said 이써쓰면.
• 아 왕눈이가 없으면 재밌지. (eopsseumyeon) — Oh, without big eyes it's more interesting. Literally: 없으면 is said 업쓰면.
• 니 없는 척 햇으면서 지금! (haeseumyeonseo) — You pretended you didn't all this time! Literally: 햇으면서 is said 해스면서.
• 그럴 거였으면 첫 번째 턴에 (geoyeosseumyeon) — If it was going to be like this. Literally: 거였으면 is said 거여쓰면.
• 어 앉고 싶은 데 앉으면 돼 (anjeumyeon) — You can sit wherever you want. Literally: 앉으면 is said 안즈면.
• 형 갔으면 형 무조건 저거야 (gasseumyeon) — If hyung went in, hyung would definitely be that. Literally: 갔으면 is said 가쓰면.

Asking with a condition — casual

The same ending inside a question, and this is where it becomes useful for speaking rather than just listening.

어떻게 하면 ("what if I do it how") is the standard way to ask for instructions, and it sounds far less blunt than a direct imperative question.

The rising intonation does the work of the question mark; the ending itself does not change.

These are also the entries most worth memorising whole. A conditional question is a request with the edges filed off, and the pattern transfers to almost any verb you already know.

• 어 에잇이 먹으면서 하는데? (meogeumyeonseo) — Oh THE8 is doing it while eating, huh? Literally: 먹으면서 is said 머그면서.
• 불 얘기했으면 뭐 나왔어요? (yaegihaesseumyeon) — What would we get if we said fire? Literally: 얘기했으면 is said 얘기해쓰면.
• 알러지가 있으면 어떡합니까? (isseumyeon) — What if I'm allergic? Literally: 있으면 is said 이쓰면.
• 일단 위아래로 입으면 될 듯? (ibeumyeon) — You probably put it on top to bottom. Literally: 입으면 is said 이브면.
• 맛 없으면 어떡하지...? (eopsseumyeon) — What if it doesn't taste good...? Literally: 없으면 is said 업쓰면.
• 이거 지금 찍으면 되는 건가? (jjigeumyeon) — Can I take the photo now? Literally: 찍으면 is said 찌그면.
• 약간 잡으면 더 예쁘겠죠? (jabeumyeon) — It would look prettier, right? Literally: 잡으면 is said 자브면.
• 미션 다시 뽑으면 안 되겠죠? (ppobeumyeon) — Can I draw a new mission? Literally: 뽑으면 is said 뽀브면.
• 새 거 집어넣으면 식나요? (jibeoneoeumyeon) — It cools if you put more oil in? Literally: 집어넣으면 is said 지버너으면.
• 이거 먹으면 배부를 것 같은데? (meogeumyeon) — I think I'll be full after eating all this. Literally: 먹으면 is said 머그면.
• 이거 지금 까서 먹으면 됩니까? (meogeumyeon) — Can I peel this and eat this now? Literally: 먹으면 is said 머그면.
• 이거 먹으면 인정입니까? (meogeumyeon) — Will you accept it if I take this? Literally: 먹으면 is said 머그면.
• 지금 손가락 넣으면 안 되겠죠? (neoeumyeon) — I shouldn't dip my finger in now, right? Literally: 넣으면 is said 너으면.
• 근데 이거 맞으면 끝인 거예요? (majeumyeon) — Are you out once you get hit? Literally: 맞으면 is said 마즈면.

Why "if" and "when" are the same word here

English splits these because English marks certainty in the conjunction itself. Korean marks it elsewhere — in the verb, in an adverb, or not at all.

내일 비가 오면 can be "if it rains tomorrow" or "when it rains tomorrow", and a Korean speaker choosing between them would add something: 혹시 for the doubtful one, or nothing at all if rain is forecast.

This is worth internalising rather than translating around. If you keep converting (으)면 to "if", you will keep hearing hesitation that is not there.

The three places learners get it wrong

First, putting the clauses in English order. 알려줘 찾으면 is not a sentence. The condition leads, always, and there is no version where it trails.

Second, reaching for (으)면 when the thing has already happened. If the cause is settled fact, Korean wants 니까 or 아서. Using a conditional for something everyone can see is true reads as sarcasm — which is a real usage, but not the one you meant.

Third, stacking it with a polite ending and expecting the politeness to travel backwards. (으)면 sits mid-sentence and carries no register at all. 찾으면 말해줘 and 찾으면 말씀해 주세요 differ only at the end, and the end is the only place that decides how polite you sound.

The entries below are all mid-sentence for that reason. Read the closing ending separately if you want to know the register.

How to practise this one

Pick ten entries from the statement section and say them out loud, then ask yourself for each one whether English would use "if" or "when". You will find the split is roughly even, and that the sentence itself rarely tells you.

Then watch something and count. (으)면 fires several times a minute in ordinary conversation — it is not a form you have to hunt for.

The question section is the more useful half for speaking. 어떻게 하면 되나요 ("what should I do", literally "if I do how, does it work") is a frame you can reuse immediately.

(으)면 next to the other endings you already know

It helps to place this one against its neighbours, because they overlap in translation and not in use.

니까 is the settled reason. The speaker treats the cause as established and moves on from it — you use it when nobody is going to argue that the thing happened. (으)면 makes no such claim; it opens a door and leaves it open.

아/어서 is closer to "and so". It chains events in the order they happened, which is why it cannot host a command — you cannot tell someone to do something because of a thing that has not occurred yet. (으)면 can host commands freely, and most of the entries below do.

는데 sets up background rather than cause. It says "here is the situation" and waits. If you can replace it with "and by the way", it is 는데 and not this one.

The practical test is whether the first clause is presented as true. If it is, you want 니까 or 아/어서. If it is being proposed, you want (으)면. Getting this wrong rarely makes you unintelligible, but it does make you sound like you are hedging things nobody was doubting.

FAQ

Does (으)면 mean "if" or "when"? Both, and Korean does not distinguish them. Which one an English translation picks depends on how likely the speaker treats the situation, and that information usually comes from context rather than from the sentence.

What is the difference between 으면 and 면? None in meaning. 으 is inserted when the stem ends in a consonant so the sounds can join — 찾으면 but 가면.

Is (으)면 formal or casual? Neither. It sits in the middle of the sentence, so politeness is decided by the ending that closes the sentence, not by this one.

How is it different from 니까? 니까 gives a reason for something already true. (으)면 sets up a condition that may or may not happen. We cover the difference in the 니까 page.

Where did these examples come from? From Korean idol and variety clips we transcribed for our shadowing library. They are lines people actually said, not sentences written to demonstrate the rule.