-(으)니까: Because (Speaker's Reasoning) & Discovery

Korean has two everyday words for "because," and -(으)니까 is the one that puts the speaker front and center. Where -아/어서 states a cause impersonally — the way rain causes wet ground — -(으)니까 says "here is my reasoning." That single difference in stance explains everything -(으)니까 can do that -아/어서 cannot: it can head a command, it can head a suggestion, it can carry its own tense. And as a bonus, the same ending has a second life marking discovery — the "when I did X, I found that Y" of noticing something new.

Forming it

Attach -(으)니까 to the verb or adjective stem:

• Stem ends in a consonant → -으니까 (먹다 → 먹으니까, 좋다 → 좋으니까, 없다 → 없으니까)
• Stem ends in a vowel → -니까 (가다 → 가니까, 바쁘다 → 바쁘니까)
• ㄹ-stem → -니까, and the ㄹ drops before the ㄴ (살다 → 사니까, 멀다 → 머니까)

Unlike -아/어서, this ending can take a tense marker — 바빴으니까 ("because [I] was busy"), 갔으니까 ("because [I] went"). That is your first sign that -(으)니까 behaves like a fuller, more independent clause.

Job 1: a reason rooted in the speaker's judgment

The plain causal use looks a lot like -아/어서 in a bare statement, and in many neutral sentences either would pass. The difference is one of stance: -(으)니까 presents the reason as something the speaker is asserting and standing behind.

But the stance becomes decisive the moment the main clause stops being a plain statement. Because -(으)니까 foregrounds the speaker's own reasoning, it can license the two moods that -아/어서 flatly refuses: commands and suggestions. This is the single most important thing to know about the ending.

It freely heads commands and suggestions

Try swapping -아/어서 into any of these and it breaks (×시간 없어서 서두르자). A suggestion or an order is an act of the speaker's will, and it needs a reason grounded in the speaker's judgment — which is precisely what -(으)니까 supplies and -아/어서 suppresses. This is why the rule of thumb works: if the second clause is a command (-(으)세요, -아/어라) or a suggestion (-자, -(으)ㅂ시다), you must use -(으)니까.

Job 2: discovery — "when I did X, I found Y"

Here -(으)니까 does something -아/어서 never does. When the main clause is in the past, -(으)니까 can drop its "because" meaning entirely and instead mark a discovery: the speaker performed the first action and, as a result, found out or encountered the second. It is the grammar of noticing.

Notice the shape: the -(으)니까 clause is a first-person action (I went home, I opened it, I went outside), the main clause is past, and it reports a state the speaker had no way of knowing until the action revealed it. English uses "when" here, not "because" — 집에 가니까 아무도 없었어요 is "when I got home, nobody was there," not "because I got home, nobody was there." The tell for the discovery reading is that the main clause describes something found, not something the speaker did on purpose. This 보니까 pattern ("upon looking / trying") is especially common: 먹어 보니까 맛있었어요 ("I tried it and it was good"), 만나 보니까 좋은 사람이었어요 ("having met him, he turned out to be a nice person").

The politeness trap: don't thank or apologize with 니까

Because -(으)니까 spotlights the speaker's own reasoning, using it in an apology or a thank-you makes you sound like you are justifying yourself — exactly the wrong note. These social formulas belong to -아/어서. Saying ×와 주니까 감사합니다 lands like "Since you came, I thank you," which is cold and transactional; the warm, correct form is 와 주셔서 감사합니다.

Why English speakers get this wrong

English "because/so" is blind to mood and to stance — one word covers impersonal cause, personal justification, and even the "when I found…" reading, which English just handles with "when." So the two errors are mirror images. Coming from English, learners default to -아/어서 everywhere (because it's taught first) and then hit a wall the moment they try to attach a command — ×시간 없어서 서두르세요 is ungrammatical. Then, over-correcting, they start using -(으)니까 in apologies, where it sounds rude. The fix is to route by the second clause: command/suggestion → 니까; apology/thanks → 아/어서; neutral statement → either, with 니까 adding a "this is my reasoning" flavor.

Common Mistakes

1. Using -아/어서 before a command or suggestion. These moods require -(으)니까; -아/어서 is grammatically blocked.

2. Using -(으)니까 in an apology or thank-you. It sounds like an excuse; use -아/어서.

3. Adding -으- to an ㄹ-stem. An ㄹ-stem takes the plain -니까 and drops its ㄹ — it never takes -으니까.

4. Expecting the discovery reading with a present main clause. The "when I found…" sense needs a past main clause.

5. Assuming -(으)니까 is always the polite, neutral choice. In many contexts a bald -(으)니까 reason to a stranger or a superior can sound curt or self-justifying; a softer -아/어서 or -(으)ㄴ데요 is warmer. Match the ending to the social situation, not just the grammar.

Key Takeaways

• -(으)니까 gives a reason as the speaker's own judgment, and can take a tense marker (바빴으니까).
• Because of that stance, it freely heads commands and suggestions — where -아/어서 is blocked (시간 없으니까 서두르자).
• With a past main clause, it marks discovery: 집에 가니까 아무도 없었어요 = "when I got home, nobody was there."
• Never use it for apologies or thanks — those require -아/어서 (와 주셔서 감사합니다).
• Route by the second clause: command/suggestion → 니까; apology/thanks → 아/어서; neutral → either.