C Reserved Keywords: Complete List and Usage Examples

What Is a Keyword in C?

Akeyword(also called areserved word) is a word the C language has claimed for itself. It has one fixed, built-in meaning, and you arenot allowedto use it as a name for your variables, functions, or anything else you create.

int count = 5;
// ✅ fine — "count" is your own name
int while = 5;
// ❌ ERROR — "while" is reserved

Three golden rules about C keywords:

1. All 32 classic keywords are lowercase.Int,IF, andReturnarenotkeywords — and using them that way is an error.
2. They're case-sensitive like everything in C.Returnis an identifier;returnis a keyword.
3. They cannot be redefined.You can't makeformean anything other than what C says it means.

The Complete List of 32 Keywords in C

Rather than dumping 32 words alphabetically, let's group them byjob— that's how your brain will actually remember them.

🟦 Group 1: Data Type Keywords (12)

These declare what kind of data a variable holds:

Note:_Bool,_Complex, and_Imaginaryarrived with C99 — they're the "new kids," only 25+ years old.

🟩 Group 2: Control Flow Keywords (12)

These controlwhichcode runs andwhen:

🟨 Group 3: Storage Class Keywords (4)

These controlwherevariables live andhow longthey survive:

🟧 Group 4: Type Structure Keywords (4)

These buildnewtypes and change how types behave:

🟥 Group 5: The Special Four (4)

The Newer Keywords: C11 and C23 Additions

C evolves slowly, but itdoesevolve. Two recent standards expanded the reserved list:

C11 (2011) added:_Alignas,_Alignof,_Atomic,_Generic,_Noreturn,_Static_assert,_Thread_local

Notice the pattern? They start with anunderscore and capital letter— deliberately ugly, so they'd never clash with names real programmers were already using. Clever, if not pretty.

C23 (2023/2024) promoted several words to full keywords:true,false,nullptr,constexpr,static_assert, andtypeof, among others. If you're on a modern compiler,bool-style logic now works without any headers:

// C23 — no #include needed for this!
bool isReady = true;
if (isReady) {
    // ...
}

Keywords vs Identifiers: Know the Difference

This distinction confuses many beginners, so let's nail it down:

int return = 10;
// ❌ ERROR — return is a keyword
int returnValue = 10;
// ✅ fine — returnValue is an identifier
int returns = 10;
// ✅ fine — "returns" is NOT a keyword
int printf = 5;
// ⚠️ legal but terrible — printf is an identifier (library function)

Wait — that last line islegal? Yes.printfisnot a keyword. It's just a function name from the standard library — technically an identifier. Youcanreuse it as a variable name, though you'd shadow the function and confuse everyone reading your code. Legal doesn't mean wise.

Quick self-test:which of these are valid variable names?

int float_num;
// ?
int floatNum;
// ?
int float;
// ?

Answers: ✅float_num(fine), ✅floatNum(fine), ❌float(keyword — error).

Why So Few Keywords Is Actually a Superpower

There's a design lesson hiding in C's tiny vocabulary. Most languages bake featuresintothe language — C pushes them intolibrariesinstead. Printing isn't a keyword; it'sprintf()fromstdio.h. Math isn't keywords; it'ssqrt()andpow()frommath.h.

The result: the core language stays small enough to learn completely, stable enough to last fifty years, and flexible enough to extend infinitely through libraries. When you hear that "C is a small language," this is what it means.