입니다 / 입니까: The Formal Copula

입니다 is the copula 이다 dressed in its most formal clothes — the "is / am / are" of news broadcasts, airport announcements, business presentations, and the moment you introduce yourself to someone for the first time. If 이에요 / 예요 is the copula you use with the barista, 입니다 is the copula you use on stage. It belongs to the 합니다체 (formal-polite speech level), and it comes with one enormous mercy for the learner and one small pronunciation trap. The mercy: unlike 이에요/예요, it does not change shape for the noun in front of it. The trap: it is spelled with ㅂ but spoken with ㅁ.

One shape for every noun

Here is the good news, and it is genuinely good. The everyday copula forces you to choose between 이에요 and 예요 depending on whether the noun ends in a consonant or a vowel. 입니다 abolishes that choice. It attaches identically to a consonant-final noun and a vowel-final noun:

학생 ends in a consonant, 의사 ends in a vowel — and both simply take 입니다. There is no 학생예요-style hunt for the right allomorph, no fusion, no contraction. Whatever the noun, you write 입니다 and move on. This is one of the few places where the formal register is easier to operate than the casual one.

Compare 김민수입니다 (name ends in the vowel ㅜ) with 이수진입니다 (name ends in the consonant ㄴ): same 입니다 on both. Where 이에요/예요 would split them, 입니다 treats them alike.

Why it never changes: the 이 stays put

The reason 입니다 is invariant is worth understanding, because it re-uses a frame that runs through the entire language. 입니다 breaks down as the copula stem 이 plus the formal ending -ㅂ니다:

이 (copula) + ㅂ니다 (formal declarative) → 입니다

The ㅂ of the ending simply becomes the batchim of 이, giving 입. Crucially, the 이 is always there — it is the stem, and a stem does not vanish. In the casual copula 예요, the 이 fuses into the ending after a vowel (친구 + 이에요 → 친구예요). But there is no vowel-fusion rule for 이 + ㅂ니다, so the 이 survives on every noun: 친구입니다, 의사입니다, 학생입니다. That is exactly why the form looks the same everywhere.

The same frame runs through every predicate

That -ㅂ니다 / -습니다 ending is not special to the copula. It is the formal-polite ending for all Korean predicates, and it picks its shape from the stem's final sound: a vowel stem takes -ㅂ니다, a consonant stem takes -습니다. Recognizing this shared frame is what lets you convert any 해요체 sentence into 합니다체 on the fly.

The copula 이 is just a vowel stem, so it slots into the -ㅂ니다 column alongside 가다. Once you see that 입니다 is the copula obeying the same rule as every other verb, it stops being a word to memorize and becomes a form you can build. For the wider picture of this speech level, see 합니다체, the formal-polite register and the formal present -ㅂ니다/-습니다.

The question form: 입니까?

To ask a yes/no question in 합니다체, the ending changes from -ㅂ니다 to -ㅂ니까. The copula's question form is therefore 입니까? Notice that Korean marks the formal question with an actual ending change — this is the one speech level where a question is not signaled by intonation alone (as it is in 해요체), but by a distinct morpheme.

Like the statement form, 입니까 attaches identically to any noun — 학생입니까, 도서관입니까, 의사입니까 — with no batchim-driven change.

Where you actually hear it

합니다체 is not "polite Korean" in general — it is a register, and using it in the wrong place sounds as odd as reading a menu order like a press release. You meet 입니다 in scripted, public, or ceremonious speech: broadcasts, announcements, presentations, the military, customer service, and formal first introductions.

And the set greeting every learner should own — the first-meeting formula, which lives entirely in 합니다체:

Because these situations are formal from start to finish, the register has to be consistent: a self-introduction that opens with 입니다 should not slip into 이에요 two sentences later. Mixing them mid-speech is the single most common register error, and it reads as sloppy rather than friendly.

The pronunciation trap: it's 임니다, not 입니다

Now the trap. 입니다 is written with ㅂ but pronounced [임니다]. The ㅂ batchim sits directly in front of the ㄴ of 니, and in Korean a stop before a nasal assimilates to a nasal of its own place: ㅂ → ㅁ before ㄴ/ㅁ. So the spelling 입 is realized as [임], and the whole word comes out [임니다].

This is why its Revised Romanization is imnida, never ×ipnida. English speakers, seeing the letter ㅂ = b/p, want to say and spell "ip-ni-da," but no Korean ever pronounces it that way — the nasalization is automatic and obligatory. The same change hits every -ㅂ니다 form: 갑니다 [감니다] gamnida, 없습니다 [업씀니다], and the question 입니까 [임니까] imnikka.

Common Mistakes

1. Pronouncing or romanizing it "ipnida." The ㅂ nasalizes to ㅁ before ㄴ — the spoken form is [임니다].

2. Making 입니다 change shape for the noun. Unlike 이에요/예요, it never fuses or drops the 이 after a vowel.

3. Mixing 입니다 and 이에요 inside one formal setting. A 합니다체 introduction or speech should stay in 합니다체.

4. Writing a space before the copula. Like all forms of 이다, 입니다 glues onto the noun.

Key Takeaways

• 입니다 is the copula 이다 in the formal-polite 합니다체 — the register of announcements, presentations, and first introductions.
• It attaches identically to every noun, consonant- or vowel-final (학생입니다, 의사입니다), because it is 이 + ㅂ니다 and the stem 이 never fuses away.
• The question form is 입니까? — 합니다체 marks questions with an ending, not just intonation.
• It is pronounced and romanized imnida (the ㅂ nasalizes to ㅁ before ㄴ), never ×ipnida.
• The -ㅂ니다/-습니다 frame is shared by all predicates, so any 해요체 sentence converts to 합니다체 by swapping the ending: 이에요 → 입니다.