아니면 · 또는 · 혹은: Or / Alternatively

English gets by with one little word, "or." Korean spreads the same job across three sentence conjunctions — 아니면, 또는, 혹은 — that differ almost entirely by register, plus one is secretly also "or else." And there is a trap underneath all three: when you want to join two nouns inside a clause ("coffee or tea"), Korean usually reaches past these conjunctions for a particle instead. Sort out the register grading and the sentence-vs-particle split, and "or" stops tripping you up.

아니면: the spoken "or" — and "or else"

아니면 (informal; spoken) is the everyday "or." It is literally 아니다 ("to not be") + -(으)면 ("if"), so its bones mean "if not." That etymology gives it a double life English keeps apart:

(a) offering an alternative — "A? Or B?":

커피 마실래요? 아니면 차 드릴까요?

keopi masillaeyo? animyeon cha deurilkkayo

Would you like coffee? Or shall I get you some tea?

우리 지하철 탈까요? 아니면 그냥 걸어갈까요?

uri jihacheol talkkayo? animyeon geunyang georeogalkkayo

Shall we take the subway? Or just walk?

(b) warning — "otherwise / or else": because 아니면 literally means "if not," it naturally issues consequences. This is a meaning 또는 and 혹은 simply do not have.

서두르세요. 아니면 늦어요.

seodureuseyo. animyeon neujeoyo

Hurry up. Otherwise you'll be late.

That second sense — "do this, or else that bad thing happens" — is one of the most useful conversational moves 아니면 gives you, and it comes free from the "if not" core.

또는: the neutral, written "or"

또는 (neutral; written) is the clean "or" of forms, instructions, signs, and lists. Built from ("again / also") + the topic particle , it simply presents two equivalent options with no extra flavor — no warning, no chattiness. It is what you meet on a payment screen or an application form.

현금 또는 카드로 결제하세요.

hyeon-geum ttoneun kadeuro gyeoljehaseyo

Please pay by cash or card.

이름 또는 사번을 입력하세요.

ireum ttoneun sabeoneul imnyeokaseyo

Enter your name or employee number.

Notice how at home 또는 is in written, semi-formal contexts. Say it in a casual chat and it sounds like you are reading aloud from a manual.

혹은: the formal, slightly literary "or"

혹은 (formal; literary/academic) is the most elevated of the three. It is the Sino-Korean 혹(或) ("perhaps / possibly") + , and beyond "or" it carries a shade of "or possibly," which is why it thrives in formal writing and literary prose where a writer weighs alternatives.

전화 혹은 이메일로 연락 주세요.

jeonhwa hogeun imeillo yeollak juseyo

Please contact me by phone or email. (formal)

그것은 우연 혹은 운명이었다.

geugeoseun uyeon hogeun unmyeong-ieotda

It was chance, or perhaps fate. (literary)

💡
Read "or" up a register ladder: 아니면 (chatting) → 또는 (forms, instructions, neutral writing) → 혹은 (formal, literary "or possibly"). And remember only 아니면 also means "or else / otherwise" — that warning sense is uniquely its own.

아니면 as "or, actually…": reformulating in speech

In conversation, 아니면 does more than list two ready-made options — it often launches a fresh proposal or a self-correction, "or, actually… / or how about…". Rather than choosing between two things already on the table, the speaker floats a second idea on the fly, frequently after a pause. This is another gift of the "if not" core: "if [that first idea] isn't it, then how about…".

여기서 기다릴까요? 아니면 그냥 안에서 볼까요?

yeogiseo gidarilkkayo? animyeon geunyang aneseo bolkkayo?

Should we wait here? Or, actually, shall we just meet inside?

내일 만날까? 아니면, 음... 이번 주말이 낫겠다.

naeil mannalkka? animyeon, eum... ibeon jumari natgetda

Shall we meet tomorrow? Or… hmm, this weekend would be better. (banmal, thinking aloud)

This reformulating 아니면 is purely a spoken move — you would not find it in the clean lists where 또는 lives. It is one more reason 아니면 is the conjunction of conversation and 또는/혹은 the conjunctions of the page.

The trap: joining two nouns uses the particle -(이)나, not a conjunction

Here is the boundary that catches learners. The three words above are sentence conjunctions — they head a clause and connect it to what came before. But very often "A or B" is not two clauses; it is two nouns filling one slot ("I'll have coffee or tea"). For that, Korean prefers the particle -(이)나, attached directly to the first noun: 커피나 차, 밥이나 빵 (이 after a consonant, 나 after a vowel).

커피나 차 중에 뭐 마실래요?

keopina cha jung-e mwo masillaeyo?

Coffee or tea — which would you like?

아침에는 보통 밥이나 빵을 먹어요.

achimeneun botong babina ppang-eul meogeoyo

In the morning I usually eat rice or bread.

The particle glues the two nouns into a single "or"-bundle that then takes its own particle (중에, 을) as a unit. Reaching for 아니면/또는 to do this job is the number-one "or" mistake — it splits what should be one noun phrase into two clunky pieces.

"or"RegisterExtra meaningJoins
아니면spoken, informalalso "or else / otherwise"clauses / whole options
또는neutral, writtenclauses or listed items
혹은formal, literary"or possibly"clauses or listed items
-(이)나 (particle)all registerstwo nouns in one slot
💡
Ask: are you offering a whole second option/clause, or just listing two nouns in one slot? Two clauses → 아니면 / 또는 / 혹은 (pick by register). Two nouns filling one role → the particle -(이)나 (커피나 차), which attaches to the noun and never sits at the head of a clause.

Common Mistakes

1. Using formal 또는 / 혹은 in casual speech. They sound stiff and bookish in conversation; everyday "or" is 아니면.

❌ 밥 먹을래? 혹은 커피 마실래?

Wrong register — literary 혹은 in casual chat; use 아니면.

✅ 밥 먹을래? 아니면 커피 마실래?

bap meogeullae? animyeon keopi masillae?

Wanna get food? Or grab coffee? (banmal)

2. Using a sentence conjunction to join two nouns. When "A or B" is one noun slot, the particle -(이)나 is the natural choice, not 또는/아니면.

❌ 주말에 등산 또는 낚시 갈 거예요.

Stiff — for casually listing two nouns, use the particle -(이)나 (등산이나 낚시), not written 또는.

✅ 주말에 등산이나 낚시 갈 거예요.

jumare deungsanina naksi gal geoyeyo

This weekend I'll go hiking or fishing.

3. Confusing 아니면 ('if not / otherwise') with 그러면 ('if so / in that case'). Both come from -(으)면, but they are opposites: 아니면 = "if not," 그러면 = "if so."

❌ 지금 예약하세요. 그러면 표가 없어요.

Wrong — 그러면 means 'if so,' but you mean 'if not / otherwise,' which is 아니면.

✅ 지금 예약하세요. 아니면 표가 없어요.

jigeum yeyakaseyo. animyeon pyoga eopseoyo

Book now. Otherwise there won't be any tickets left.

4. Using casual 아니면 in a formal notice. The reverse of mistake 1 — a clean written "or" wants 또는, not the conversational 아니면.

❌ 신분증 아니면 여권을 지참하세요.

Too casual for a formal notice; a clean written 'or' is 또는.

✅ 신분증 또는 여권을 지참하세요.

sinbunjeung ttoneun yeogwoneul jichamhaseyo

Please bring your ID or passport. (formal notice)

Key Takeaways

  • 아니면 = spoken "or," and uniquely also "or else / otherwise" (from 아니다 + -(으)면, "if not").
  • 또는 = neutral written "or" for forms and lists; 혹은 = formal/literary "or possibly" (Sino-Korean 혹 或).
  • Grade by register: 아니면 → 또는 → 혹은 as formality rises.
  • To join two nouns in one slot, use the particle -(이)나 (커피나 차), not a sentence conjunction — this is the split learners most often miss.

Now practice Korean

Reading grammar gets you part of the way. The exercises are where it sticks — free, no signup needed.

Start learning Korean

Related Topics

  • (이)나: Or, About, As Many AsTOPIK 2The multi-function particle (이)나 — non-exhaustive 'or' (커피나 차), casual 'or something' (영화나 볼까?), surprise at a large quantity (열 개나 먹었어요), and 'about' with round numbers — all threaded by one idea: an open, non-committal amount or choice.
  • 그러면 · 그럼: Then / In That CaseTOPIK 1The conversational 'then' that takes the previous statement as a condition and draws the next step from it — 그러면 and its ubiquitous contraction 그럼, which also stands alone as an agreement word meaning 'of course / okay then.'
  • 즉 · 다시 말해(서): That Is / In Other WordsTOPIK 3The restatement conjunctions that re-explain what you just said — terse, written 즉 ('that is, namely') versus the everyday spoken 다시 말해서 ('in other words') — plus 요컨대, 말하자면, and formal 곧, and why they restate rather than add or conclude.
  • Sentence Conjunctions 접속부사 and the 그렇다 PatternTOPIK 1The words that open a sentence and link it to the last one — 그리고, 그래서, 하지만, 그런데 — and the single insight that unlocks almost all of them: most are 그렇다 ('be so') plus a connective ending, so each conjunction has an ending twin.