아서 vs 니까: The Real Difference Between Korea's Two 'Because' Endings
아서 and 니까 both mean "because," but they aren't interchangeable. 아서 states a natural, objective cause — 비가 와서 못 갔어요 (it rained, so I couldn't go). 니까 gives the speaker's own reasoning, and it's the only one of the two that can lead into a command or suggestion: 바쁘니까 가세요 (since you're busy, go ahead). Swap them and a perfectly good sentence turns ungrammatical.
Every Korean textbook drops 아서 and 니까 into the same "because" unit like they're twins. They're not. They're the kind of pair where mixing them up doesn't just sound a little off — one direction of the swap breaks the sentence outright.
The rule that saves you: 니까 owns commands and suggestions
Here's the one fact that clears up 90% of the confusion: if what comes next is a command, a request, or a suggestion — 가세요 (go), 하지 마세요 (don't), -자 (let's) — 니까 is the only grammatical option. 아서 cannot lead into that kind of sentence. Not "sounds a bit stiff." Ungrammatical, the kind of thing a TOPIK grader circles in red.
바쁘니까 가세요.
ba-ppeu-ni-kka ga-se-yo.
Since you're busy, go ahead.
니까 + command — correct
*바빠서 가세요.
ba-ppa-seo ga-se-yo.
(ungrammatical)
아서 can't lead into a command, ever
오늘 피곤하니까 일찍 자자.
o-neul pi-gon-ha-ni-kka il-jjik ja-ja.
I'm tired today, so let's sleep early.
니까 + suggestion (-자) — same rule
The logic: 아서/어서 glues two events into one continuous thread — it wants a result, not an instruction. 니까 steps back and frames a reason for what should happen next, which is exactly the shape a command needs.
아서 reports a fact. 니까 argues a case.
Past the command rule, the two split on tone. 아서 narrates a cause like a fact of the world — this happened, so that happened: 비가 와서 못 갔어요 (it rained, so I couldn't go). Nobody's opinion is in that sentence; the rain caused the absence, full stop. 니까 is the speaker stepping in with their own logic: 내가 해봤으니까 알아 (I've done it myself, so I know). That's not a neutral chain of events — it's a claim, backed by the speaker's own experience, offered as justification. If 아서 is a caption, 니까 is closing argument.
| 아서/어서 | (으)니까 | |
|---|---|---|
| What it marks | an objective cause, a fact of the situation | the speaker's own reasoning or justification |
| Can lead into a command, suggestion, or -을게? | No — ungrammatical | Yes — this is its main job there |
| Attaches after past tense (았/었)? | Basically never | Yes — 했으니까, 갔으니까 are completely normal |
| Reads like... | "X happened, so Y happened" | "Here's my reason for Y" |
A text message that uses both correctly
Watch how a normal exchange reaches for each one without anybody thinking about the grammar.
너 어디야? 나 벌써 20분째 기다리고 있어.
neo eo-di-ya? na beol-sseo i-sip-bun-jjae gi-da-ri-go i-sseo.
Where are you? I've already been waiting 20 minutes.
미안, 버스를 놓쳐서 늦었어.
mi-an, beo-seu-reul no-chyeo-seo neu-jeo-sseo.
Sorry, I missed the bus so I'm late.
괜찮아. 밖이 추우니까 카페 안에서 기다릴게.
gwaen-cha-na. ba-kki chu-u-ni-kka ka-pe a-ne-seo gi-da-ril-ge.
It's fine. Since it's cold outside, I'll wait inside the café.
기다려 줘서 진짜 고마워. 5분만 더!
gi-da-ryeo jwo-seo jin-jja go-ma-wo. o-bun-man deo!
Thanks so much for waiting. Just 5 more minutes!
천천히 와, 급한 거 아니니까.
cheon-cheon-hi wa, geu-pan geo a-ni-ni-kka.
Take your time, since it's not urgent.
This is exactly the kind of pattern that's hard to absorb from a grammar table and much easier to absorb from watching two people actually text each other — which is the whole bet behind learning Korean through a running story instead of isolated example sentences.
The politeness trap, and the idioms that never change
Here's where learners quietly hurt themselves. 니까 carries a whiff of self-justification — useful when you're explaining a decision, disastrous when you're apologizing. 늦어서 죄송합니다 (sorry for being late) is the correct, clean version. 늦었으니까 죄송합니다 technically parses, but it reads like you're building a defense — "since I was late, [obviously] I'm sorry" — instead of just owning it. Save 니까 for decisions, not apologies.
A few set phrases fossilized around 아서 long ago and never budged. Meeting someone: 만나서 반갑습니다 (nice to meet you — literally "having met, I'm glad"). Thanking someone for an action: 와 줘서 고마워 (thanks for coming), 도와줘서 고마워 (thanks for helping). Every thanks-for-doing-X phrase in Korean runs on 아서. Drop 니까 into any of them and it just sounds like machine-translated Korean — grammatical, maybe, but nobody talks that way.
Frequently asked questions
What's the simplest rule to remember 아서 vs 니까?
If a command, request, or suggestion follows, you need 니까 — 아서 can't lead into one, period. Everywhere else, 아서 states a plain cause and 니까 frames the speaker's own reasoning. When you're unsure which tone you want, 니까 reads more assertive and 아서 reads more neutral.
Can 아서 attach to a past-tense verb?
Basically no. 아서/어서 attaches straight to the verb stem and doesn't stack with 았/었 — you won't hear 갔어서. 니까 handles past tense fine: 갔으니까 (since I went), 했으니까 (since I did it). Any past-tense feeling in an 아서 sentence comes from context, not a tense marker on 아서 itself.
Is 니까 rude?
Not inherently — it's just assertive. It only reads as blunt or defensive when it lands somewhere 아서 fits better, especially apologies. 늦었으니까 미안해 sounds like you're justifying yourself rather than saying sorry. For excuses and thanks, 아서 is the softer, more neutral pick.
Why does 만나서 반갑습니다 use 아서 and not 니까?
It's a fossilized set phrase, not a live grammar choice — literally "having met you, I'm glad." Like most Korean greeting and thank-you formulas, it locked in with 아서 long ago. 니까 there isn't wrong so much as it's simply not a phrase anyone says.
Are there other ways to say "because" in Korean?
Yes — 때문에 (due to, often points at blame), (으)므로 in formal writing, and 라서 as a casual shortcut for 이어서 after 이다. But 아서 and 니까 cover the large majority of everyday spoken "because," which is why they're the pair every textbook puts head-to-head.