을/를: The Korean Object Marker and When to Drop It
을/를 marks the object of a sentence — the thing the verb acts on. Use 을 after a word ending in a consonant (책을, "the book") and 를 after a word ending in a vowel (영화를, "the movie"). In casual speech, Koreans drop it constantly when context is obvious (밥 먹었어?, not 밥을 먹었어?). It comes back in writing, formal speech, and anywhere the sentence would otherwise be ambiguous.
Textbooks teach 을/를 in week two and then spend the rest of the course pretending it's optional trivia. It's not trivia — it's the marker that tells you what the verb is doing something to. But here's the twist your textbook skips: fluent Korean speech drops it more often than it uses it. Learning when you can skip it is half the actual skill.
The mechanical rule (10 seconds)
| Last sound of the word | Marker | Example |
|---|---|---|
| Consonant (책, 밥, 사람) | 을 | 책을 → chaek-eul |
| Vowel (영화, 커피, 노래) | 를 | 영화를 → yeong-hwa-reul |
That's the entire spelling rule — no exceptions, no irregulars. It's the same batchim logic as 은/는 and 이/가: consonant-ending words get the consonant-starting marker (을), vowel-ending words get the vowel-starting one (를). If you already have that instinct from 은/는 vs 이/가, you already have this one.
책을 읽어요.
chaek-eul il-geo-yo.
I read a book.
책 ends in ㄱ (consonant) → 을
영화를 봐요.
yeong-hwa-reul bwa-yo.
I watch a movie.
영화 ends in 아 (vowel) → 를
물을 마셔요.
mul-eul ma-syeo-yo.
I drink water.
물 ends in ㄹ (consonant) → 을
What "object" actually means, verb by verb
"Object" sounds abstract until you see it verb by verb: it's whatever noun receives the action, gets consumed by it, or shows up as the target. English objects and Korean objects mostly line up — but not always, and the mismatches are where learners get tripped up.
| Verb | Typical object | What the object is doing |
|---|---|---|
| 먹다 (eat) | 밥을, 라면을 | the food going into your body |
| 보다 (watch/see) | 영화를, 드라마를 | what your eyes take in |
| 만나다 (meet) | 친구를, 사장님을 | the person you meet — yes, people take 을/를 too |
| 배우다 (learn) | 한국어를, 운전을 | the skill or subject being acquired |
| 걸다 (hang/make) | 전화를 | idiomatic: 전화를 걸다 = "make a call," not "call to a phone" |
That last row is the trap. English attaches "to" or "for" to a lot of these ideas (call to someone, wait for the bus), and learners instinctively reach for 에게 or 를 based on the English preposition instead of the Korean verb. 전화를 걸다, 버스를 기다리다 — Korean doesn't care what English does with prepositions. Learn the object per verb, not per translation.
When Koreans drop it (and when that breaks something)
Here's the part your textbook undersells: in casual, spoken Korean, 을/를 gets dropped constantly. Not sometimes — constantly, the way English speakers say "got it" instead of "I have got it." 밥 먹었어? (not 밥을 먹었어?) is the completely normal way to ask "did you eat?" between friends. Adding the particle back doesn't make it wrong, just stiffer — closer to reading off a script.
저녁 먹었어?
jeo-nyeok meo-geo-sseo?
Did you eat dinner? (저녁을 → 저녁, dropped without a second thought)
아직. 오빠는 먹었어?
a-jik. o-ppa-neun meo-geo-sseo?
Not yet. Have you?
나도 아직. 라면 먹을까?
na-do a-jik. ra-myeon meo-geul-kka?
Me neither. Want to eat ramyeon?
콜! 근데 그 매운 라면은 빼줘.
kol! geun-de geu mae-un ra-myeon-eun ppae-jwo.
Deal! But skip the spicy one. (는 swaps in for 를 to single that one out — dropping alone wouldn't do that)
- Safe to drop: the object is obvious from context, you're speaking casually, and nothing else in the sentence needs emphasis. 커피 마실래? ("want coffee?") loses nothing.
- Risky to drop: two nouns in a row could both plausibly be the object, or the sentence is your only chance to clarify who did what to whom — dropping invites a "wait, what?"
- Never drop in writing or formal/polite registers: 제출해 주세요 ("please submit [it]") needs 서류를 or 과제를 spelled out on paper, even if you'd skip it out loud to a friend.
- Swap, don't just drop, when you want contrast: replacing 를 with 는 (라면은 안 좋아해, "ramyeon, I don't like" — unlike other things) does a different job than silence.
The 를 that isn't an object: 좋아하다 vs 좋다
This is the one that quietly breaks people's model of the whole system. 좋아하다 ("to like") behaves like a normal action verb and takes 를: 커피를 좋아해요, "I like coffee." But 좋다 ("to be good") is a descriptive verb — grammatically closer to an adjective than a verb — and it takes 가, not 를: 커피가 좋아요, "coffee is good" (or, in practice, "I prefer coffee").
커피를 좋아해요.
keo-pi-reul jo-a-hae-yo.
I like coffee.
좋아하다 = action verb → object takes 를
커피가 좋아요.
keo-pi-ga jo-a-yo.
Coffee is good. / I prefer coffee.
좋다 = descriptive verb → subject takes 가, not 를
Frequently asked questions
How do I know if a word ends in a consonant or vowel for 을/를?
Look at the last syllable's block, not the last letter of the romanization. If it has a bottom consonant (받침/batchim) like 책 or 밥, use 을. If the syllable ends in a pure vowel sound like 화 or 피, use 를. Say the word out loud — your ear usually gets there faster than the rule does.
Is it wrong to always keep 을/를 and never drop it?
Not wrong — just noticeably formal, like never using contractions in English. Keeping every particle is completely correct and is actually the safer choice while you're still learning, since dropping requires knowing when context makes the object obvious.
Can 을/를 mark more than one noun in a sentence?
Yes, in a specific pattern: possessor plus body part or belonging. 친구가 나를 팔을 잡았어요 ("my friend grabbed my arm") marks both "me" and "arm" with 을/를, because the arm belongs to the person being grabbed. This double-object pattern is normal for body parts and close possessions.
Why do some verbs take 가 instead of 를 for what looks like an object?
Because they're not action verbs — they're descriptive verbs (state, not action), and Korean marks states with 가, not 를. 좋다 (be good), 싫다 (be disliked), 필요하다 (be needed), and 무섭다 (be scary) all follow this pattern, unlike their action-verb cousins.
Does dropping 을/를 ever actually change the meaning, not just the tone?
Rarely, but yes — mostly when the sentence has two nouns that could each be read as subject or object. "엄마 아빠 불렀어" without particles is momentarily ambiguous about who called whom; "엄마가 아빠를 불렀어" isn't. When a sentence could go two ways, that's exactly when native speakers put the particle back.