Open-source project
necolas/normalize.css avatar
necolas/normalize.css

normalize.css: The Reset That Keeps Useful Defaults

GitHub describes it as A modern alternative to CSS resets. The repository metadata lists CSS as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

53,484 stars10,256 forksCSSMIT

At a glance

What is it?
normalize.css is a CSS file that corrects browser inconsistencies without wiping out every default style. It is a modern alternative to CSS resets, aimed at developers who want a consistent baseline without losing useful defaults.
Who is it for?
Adopt normalize.css if you want a consistent, well-commented baseline that preserves useful defaults and fixes browser bugs, and you support Chrome, Edge, Firefox ESR+, IE10+, Safari 8+, and Opera. Do not use it if you need to strip all default styles for a highly custom design, or if you must support older browsers like IE9.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Probably not. The repository last received commits 29 months ago, on June 12, 2024.
What is it written in?
Mainly CSS, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • necolas/normalize.css53,484 ★ · -53
Star history
Repository2026-08-132026-11-15
necolas/normalize.css53.5k53.5k

-53 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The Problem: Inconsistent Defaults Across Browsers

Every browser ships its own default styles. Margins, padding, font sizes, and element rendering differ. A button in Chrome does not look like a button in Firefox. A heading in Safari has different spacing than in Edge. For years, developers used CSS resets to solve this. Resets work by removing all default styling, forcing you to redefine everything from scratch. That is blunt and often wasteful. normalize.css takes a different path. It does not wipe the slate clean. Instead, it makes default styles consistent across browsers while keeping the useful parts. This matters for anyone building a site where you want a predictable baseline without writing every rule yourself.

How normalize.css Works: Correction, Not Erasure

The README defines normalize.css as a modern alternative to CSS resets. Its stated goals are to preserve useful defaults, normalize styles for a wide range of elements, correct bugs and browser inconsistencies, and improve usability with subtle modifications. The key mechanism is selective rule application. For example, the `pre, code, kbd, samp` rule uses a `font-family: monospace, monospace` hack. The duplication of `monospace` is intentional, fixing inheritance and scaling of font-size for preformatted text. Another example: `sub` and `sup` normally affect line-box height, and normalize.css addresses that. The file is heavily commented, so each rule explains why it exists. That makes it a learning tool as much as a fix. You can read the source and understand the quirks it handles.

Getting It Running: npm, CDN, or Direct Download

Installation is straightforward. The README shows three ways. Via npm: `npm install --save normalize.css`. Via a CDN: the README points to the yarn package page for CDN links. Or download the latest file directly from `https://necolas.github.io/normalize.css/latest/normalize.css`. That last URL is useful if you want a single file to drop into a project. Once installed, you link it in your HTML or import it in your CSS. There is no build step, no configuration, no JavaScript. It is a single CSS file. You include it, and it applies its corrections. The simplicity is a feature: no framework, no dependencies.

Browser Support and What That Means for You

The README lists support for Chrome, Edge, Firefox ESR+, Internet Explorer 10+, Safari 8+, and Opera. That is a broad range, but note the ESR+ on Firefox. ESR means Extended Support Release, so older but still maintained Firefox versions are covered. Internet Explorer 10+ is included, which is surprising in an era where many libraries drop IE. Safari 8+ goes back to 2014. This support list is a double-edged sword. It helps if you need to cover legacy browsers. But it also means the file may contain hacks for old browsers that you no longer need. If you target only modern browsers, you might be carrying dead weight. The README does not mention any conditional loading or versioning for browser-specific rules, so you get everything regardless of your actual user base.

Known Limitations: Where normalize.css Falls Short

The README documents several known issues. For checkbox and radio inputs, it recommends not styling them because Firefox ignores box-sizing, padding, and width. That is a real constraint: if you want custom-styled form controls, normalize.css will not help, and you may need a separate approach. For `[type="number"]`, certain font-size values change the cursor style on the decrement button, a minor but annoying quirk. For `[type="search"]`, the search input is not fully stylable by default in Chrome and Safari on OSX/iOS, and on Windows you cannot control the border properly. The README suggests using `-webkit-appearance: textfield` to fix some of these issues, but that is a manual step. These limitations mean normalize.css is not a silver bullet. It normalizes, but it does not make every element fully stylable. You still need to know the quirks and apply your own fixes.

Alternative: Traditional CSS Resets vs. normalize.css

The main alternative is a classic CSS reset, such as Eric Meyer's reset or a minimal reset like `* { margin: 0; padding: 0; }`. The difference in approach is fundamental. A reset removes all default styling, giving you a blank canvas. You then define every style yourself. That gives you full control but requires more work and can lead to inconsistent typography if you forget to set a font-size on an element. normalize.css, by contrast, keeps useful defaults like heading sizes and paragraph margins, but makes them consistent across browsers. The trade-off is control vs. convenience. With a reset, you own everything. With normalize.css, you inherit a baseline that someone else designed. If you want a completely custom look, a reset might be better. If you want a solid starting point, normalize.css is more efficient.

Maintenance and License: Low Overhead, MIT

normalize.css is licensed under MIT, which means you can use it freely, including in commercial projects, as long as you keep the licence and copyright notice. The README includes a CHANGELOG link, so you can track changes between versions. The project is not archived, but the README gives no cadence, so how often it is updated is up to the changelog alone. The file is small and static, so the upgrade cost is low: replace the file or update the npm package. However, because it targets old browsers, future versions may drop support for IE10 or Safari 8, which could affect your project if you rely on those. The detailed comments in the source make it easy to audit what each rule does, so you can decide if you need to fork or modify it. Overall, the maintenance burden is minimal, but you should check the CHANGELOG before upgrading to avoid surprises.

Editorial conclusion

Adopt normalize.css if you want a consistent, well-commented baseline that preserves useful defaults and fixes browser bugs, and you support Chrome, Edge, Firefox ESR+, IE10+, Safari 8+, and Opera. Do not use it if you need to strip all default styles for a highly custom design, or if you must support older browsers like IE9. Before adopting, verify the latest version's browser list and check the CHANGELOG for any recent changes that might affect your target browsers.

Frequently asked questions

what is normalize css

It is a single stylesheet, version 8.0.1 in its package manifest, described as a modern alternative to CSS resets. It ships as normalize.css with a MIT licence, and the manifest points both the main and style fields at that one file.

what does normalize css do

It preserves useful defaults unlike many resets, normalizes styles across a wide range of elements, corrects bugs and common browser inconsistencies, and improves usability with subtle modifications. Each rule is explained in comments, including the fixes for preformatted text, sub and sup line box height, and form control limits.

how to install normalize css

From npm the command is `npm install --save normalize.css`. For other routes the project points you to a CDN package listing at yarnpkg.com and to a downloadable copy at necolas.github.io/normalize.css/latest/normalize.css, without naming a pinned version for either.

is normalize css still needed

The repository was last pushed on 2024-06-12 and publishes no GitHub releases, so there is no release history to check a current build against. The stated support list is Chrome, Edge, Firefox ESR+, Internet Explorer 10+, Safari 8+, and Opera.

reset css vs normalize css

The project positions itself as an alternative to CSS resets on the strength of preserving useful defaults rather than stripping them. Its stated scope is normalizing element styles, correcting browser inconsistencies, and small usability fixes, and the published files list contains only the stylesheet and its licence, with no design system layer.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/necolas-normalize-css.svg)](https://hysenlabs.com/projects/necolas-normalize-css)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/necolas-normalize-css.svg)](https://hysenlabs.com/projects/necolas-normalize-css)

Was this useful?