Course contentsShow
← Web Development
Lesson 134 of 2,9823. CSS FundamentalsFree lesson

!important and When to Avoid It

Learn what !important does, why it causes problems, and the rare cases where it's acceptable.

!important and When to Avoid It

What you'll learn: How !important overrides CSS specificity, why it usually creates more problems than it solves, and the rare situations where it's acceptable.


What is !important?

The !important declaration is a way to force a CSS property value to win, no matter what specificity or source order rules say. It's like shouting in a conversation—it guarantees you'll be heard, but it's disruptive.

.button {
  color: blue;
}

.button {
  color: red !important; /* This wins, even if blue has higher specificity */
}

The Problem with !important

Think of !important as breaking the normal rules of the game. Once you use it, you can only override it with another !important declaration. This creates a "specificity war" where developers keep adding !important to override each other, making your CSS unmanageable.

Issues it causes:

  • Breaks the natural cascade and specificity system
  • Makes debugging harder (styles appear to "not work")
  • Forces you to use more !important to override it
  • Prevents proper code organization

When Is It Acceptable?

There are rare, legitimate uses:

  1. Utility classes that should always apply (e.g., .hidden { display: none !important; })
  2. Overriding third-party CSS you can't edit
  3. User stylesheets for accessibility needs

Better Alternatives

Instead of !important, fix the root problem:

  • Increase specificity properly
  • Reorganize your CSS source order
  • Refactor overly-specific selectors

Key Takeaway: !important breaks CSS's natural specificity system and should be avoided except in rare utility cases—always try to solve specificity problems by writing better selectors first.