-아서 vs -(으)니까: Choosing Your 'Because'

Korean gives you two everyday ways to say "because," and English translations flatten them into the same word — which is exactly why learners misuse them for years. -아/어서 and -(으)니까 are not free variants. They differ in what kind of clause is allowed to follow, in whether they can carry tense, in which fixed social phrases demand them, and in the stance the speaker takes toward the cause. Get the diagnosis right and the choice makes itself; translate blindly and you will produce sentences that sound, at best, oddly stiff and, at worst, rude.

The single most useful mental move is to stop translating and start diagnosing. Before you pick an ending, ask two questions: Is a command or suggestion coming next? and Am I reporting a plain fact, or am I laying out my own reasoning? Those two questions resolve the overwhelming majority of cases.

The one-sentence answer

Use -아/어서 when the cause is presented as an objective, natural fact and the sentence just reports an outcome. Use -(으)니까 when you are giving your own reasoning — especially when you are about to tell someone to do something. If there is a command, a request, or a suggestion after the "because," you almost always need -(으)니까.

Both sentences pin the "rain" as the cause. But the first simply narrates a result, so -아서 fits. The second is me reasoning at you and ending in an order, so only -(으)니까 works.

Feature 1: What can follow — commands and suggestions

This is the difference that matters most for sounding natural, because it is a hard grammatical wall, not a nuance. -(으)니까 can be followed by a command, a request, a suggestion, or a proposal. -아/어서 cannot. If your second clause is an imperative (닫아, 닫으세요), a "let's" form (가자, 갑시다), or a proposal (-(으)ㄹ까요?), -아/어서 is ungrammatical.

Now the same idea with -아서, which breaks:

• ✗ 추워서 창문 닫아. — wrong: -아서 cannot head a command.
• ✓ 추우니까 창문 닫아. — "It's cold, so close the window."

The reason is structural. -아/어서 fuses the two clauses into a single tightly-bound event chain — one thing flows into the next as a natural consequence — and a command is not a "consequence" that flows out of a fact; it is a fresh speech act aimed at the listener. -(으)니까 keeps the two clauses looser: it presents the first as grounds you are offering, and grounds can perfectly well support "so do this." English has no matching split, which is why English speakers reach for -아서 everywhere and unknowingly produce ungrammatical commands.

Feature 2: Tense on the ending

-(으)니까 can carry the past tense (-았/었-) on its own clause; -아/어서 cannot. The past marker lives on the -(으)니까 clause directly (바빴으니까), but with -아/어서 the tense is forced onto the final verb only, and the -아서 clause stays tenseless.

• ✗ 바빴어서 못 갔어요. — wrong: -아서 never takes -았/었- on its own clause.
• ✓ 바빠서 못 갔어요. — "I couldn't go because I was busy." (the past sits only on 갔어요)

This is not an arbitrary rule; it follows from the same tight-binding logic. Because -아/어서 welds its clause to the main event, that clause has no independent time reference — it borrows the tense of the whole sentence. -(으)니까, being looser, can time-stamp its own grounds. So when you specifically want to say "because it was the case that…," -(으)니까 is often your only clean option.

Feature 3: Fixed social phrases demand -아서

Apologies, thanks, and greetings are frozen constructions in Korean, and they overwhelmingly select -아/어서. Using -(으)니까 here is a classic tell of a non-native speaker — it reframes a warm social ritual as a cold statement of grounds, so a thank-you starts to sound like an excuse or a demand for credit.

Swap in -(으)니까 and a native ear winces:

• ✗ 도와주시니까 감사합니다. — off: in a set thank-you, -(으)니까 sounds like you are pointedly stating your reason for thanking, almost transactional.

Memorize the -아서 versions as whole units: 늦어서 죄송합니다, 와 주셔서 감사합니다, 만나서 반갑습니다, 기다리게 해서 미안해. These are the phrases you will say most often, so building the -아서 habit here pays off immediately.

Feature 4: The stance — objective fact vs your own reasoning

When both endings are grammatically legal, they still differ in feel, and native speakers choose deliberately. -아/어서 frames the cause as an objective, self-evident fact ("rain → wet ground," no one could dispute it). -(으)니까 frames the cause as the speaker's own reasoning or a freshly noticed basis — it foregrounds your judgment, which is why it dominates in persuasion, instructions, and explanations you expect the listener to accept.

The -(으)니까 stance also produces its signature "discovery" reading: now that I look / as it turns out. Because -(으)니까 can present a newly perceived basis, it naturally reports something you found upon doing the first action.

Here nothing is being caused; -(으)니까 simply links "I opened the door" to "and there was the snow I then noticed." -아/어서 cannot produce this "and then I discovered…" nuance at all.

A quick note on form

Both endings attach to the verb or adjective stem. -아/어서 follows vowel harmony: a bright-vowel stem takes -아서 (좋아서, 작아서), other stems take -어서 (먹어서, 늦어서), and 하다 becomes 해서. -(으)니까 inserts -으- only after a consonant-final stem and attaches straight to a vowel-final one:

For the fuller treatment of each ending on its own, see -아서: cause and sequence and -(으)니까: giving your reason. When your "because" is heavier or more written, a third option, -기 때문에 and its relatives, enters the picture.

Decision flow

Common Mistakes

1. Using -아서 before a command or suggestion. This is the number-one error, and it is a hard grammatical break, not a nuance.

• ❌ 배고파서 우리 밥 먹으러 가자. — wrong: -아서 can't head a "let's" clause.

2. Putting past tense on the -아서 clause. Tense goes on the final verb; the -아서 clause stays tenseless.

• ❌ 어제 아팠어서 학교에 못 갔어요. — wrong: no -았/었- on -아서.

3. Using -(으)니까 in a set apology or thank-you. It reframes a warm ritual as a cold statement of grounds.

• ❌ 늦으니까 죄송합니다. — off: sounds like you're stating a reason, not apologizing.

4. Treating them as interchangeable in a plain report. When you are simply narrating cause → result with no command and no argument, -아/어서 is the natural, unmarked choice; defaulting to -(으)니까 makes you sound like you are insisting on your reasoning.

• ❌ 감기에 걸리니까 목이 아파요. — awkward as a plain report of symptoms.

5. Forgetting the -으- with consonant stems on -(으)니까. After a consonant you need the linking -으-.

• ❌ 시간이 없니까 빨리 가자. — wrong: 없- is consonant-final.

Key Takeaways

• Command coming? → -(으)니까. -아/어서 cannot head an order, request, or "let's."
• Past tense on the clause? → -(으)니까 (바빴으니까); -아/어서 leaves tense on the final verb.
• Apology, thanks, greeting? → -아/어서 (늦어서, 만나서, 도와주셔서). -(으)니까 sounds like excuse-making.
• Stance: -아/어서 = objective fact; -(으)니까 = your own reasoning, persuasion, and "now that I look…" discovery.
• Diagnose, don't translate: run the two questions before you pick.