-아서 vs -(으)니까: Two Kinds of 'Because'

English packs cause into a single word, because, and lets context sort out the rest. Korean splits it into two connective endings — -아서/어서 and -(으)니까 — and the split is not primarily about shades of meaning. It is about grammar: the two endings disagree over what kind of sentence they are allowed to finish. Get that firewall right and the nuance takes care of itself.

The quick answer

-아서/어서 marks a neutral, objective cause that is tightly welded to its result. It can only finish a plain statement, it never carries its own past-tense -았-, and it locks into fixed greetings, thanks, and apologies. -(으)니까 marks the speaker's reason or justification — the ground you are offering the listener — and it can finish anything at all, including commands, requests, and suggestions, and it takes tense freely. The one rule you must never break: if the main clause is an order, a request, or a "let's", you must use 니까.

The grammatical firewall

This is the part textbooks bury under "nuance," but it is the deciding factor. -아서 cannot be followed by a command, a request, or a suggestion. The clause it introduces is fused so tightly to the result that Korean refuses to let that result be anything but a statement. -니까 has no such restriction.

Watch what happens when the main clause turns into a suggestion:

You cannot say ×시간이 없어서 가자. The moment the sentence ends in 가자 ("let's go"), 아서 is off the table. The same is true for imperatives:

Try to say ×비가 와서 우산 가져가세요 and a native ear flinches. Because the ending is a command (-세요), only 니까 will carry it. This single constraint resolves a large fraction of learner mistakes before nuance ever enters the picture.

The nuance: neutral cause vs the speaker's reasoning

When both endings are grammatical — that is, when the main clause is a plain statement — they still differ. -아서 states an objective cause, presented as just how things are. -니까 offers a reason to the listener, foregrounding the speaker's own judgment ("since, as you can see…"). Compare:

The first is a flat report. The second sounds like you are giving the reason for the listener's benefit — answering an implied "why?", or justifying a decision. That is why 니까 dominates in explanations, excuses, and anywhere you are building an argument for someone:

And 아서 dominates where the cause is simply an observed fact leading to a state:

-아서 never carries its own -았-

Here is a hard, mechanical rule with no wiggle room: the clause before 아서 cannot take past tense. However far in the past the event is, 아서 stays in its base shape, and the tense lives on the main verb only.

The event is yesterday, yet it is 와서, never ×왔어서. The past -었- appears once, on 있었어요. Learners coming from English — where both halves of "it rained, so I stayed" are past — over-mark this constantly.

-니까, by contrast, takes tense normally. You can say 왔으니까, and sometimes you must, to pin the cause in the past independently of the result:

Here the eating (past) and the not-eating (present) sit in different times, and 니까 lets you tense them separately — 먹었으니까. Swapping in 아서 (먹어서) would work only if you dropped the past marker, and it would sound less like the reasoned justification you intend.

The fixed-expression zone: thanks, greetings, apologies

A cluster of everyday social formulas is locked to -아서, and they are worth memorizing as whole units:

There is a logic here worth internalizing. Thanks and apologies name the cause as the direct, inseparable ground of the feeling — the meeting is the gladness, the lateness is the thing you regret. That fused, objective quality is exactly what 아서 encodes. Swap in 니까 and you turn a warm formula into an argument: 늦었으니까 죄송해요 reads like "I'm apologizing because [as I'm pointing out to you] I was late" — you sound as if you are justifying yourself rather than apologizing, which is faintly rude. For genuine apologies and thanks, stay with 아서 (see -아서 for cause and, for the etiquette, sorry vs. thank-you register).

Allomorphy in one breath

• -아서 / -어서 / -여서 follows vowel harmony, exactly like the 해요 ending: 오다 → 와서, 먹다 → 먹어서, 하다 → 해서.
• -(으)니까 takes 으 after a consonant-final stem and bare 니까 after a vowel: 먹다 → 먹으니까, 가다 → 가니까. ㄹ-stems drop the ㄹ: 살다 → 사니까.

Side-by-side

Common Mistakes

1. Using 아서 before a command or suggestion. This is the number-one error, and it is a pure transfer from English, where "because" is indifferent to what follows. In Korean, a command or "let's" forces 니까.

2. Putting past tense before 아서. The past goes on the main verb only; 아서 stays in base form.

3. Using 니까 to apologize or thank. It flips a heartfelt formula into a self-justification.

4. Using 니까 for a plain, neutral cause where nothing is being justified. Grammatical, but it colors a flat report with an argumentative "since I'm telling you." For a simple statement of cause and effect, 아서 is the neutral default.

Key Takeaways

• Grammar first, nuance second. A command, request, or suggestion in the main clause forces 니까. A thank-you, apology, or greeting forces 아서.
• 아서 = neutral objective cause; 니까 = the speaker's reason offered to the listener.
• 아서 never takes its own -았-/-었-; the tense sits on the main verb. 니까 tenses freely.
• When the main clause is just a statement and no social formula is involved, either works — choose 아서 for a flat report, 니까 to foreground your reasoning.

For each ending on its own, see -아서 for cause and -(으)니까 for cause; for a related pair, compare -고 vs -아서; and for the noun-based alternative, 때문에.