Styling
Rethinking CSS Resets for Modern CSS
A practical approach to cleaner, more predictable foundations.
CSS resets have been around forever.
They started as a way to neutralize browser inconsistencies—strip everything down, remove default margins, and build from a clean slate.
And for a long time, that made sense.
But modern CSS has changed. Browsers are more consistent. New layout tools exist. And the platform now gives you more control than it used to.
Which raises a simple question: do we still need to reset everything?
Why traditional resets feel a little outdated
Classic resets were built for a different era of CSS.
Back then, browser defaults varied widely. Margins, font sizes, line heights—everything could behave differently depending on where your code ran.
The solution was to remove as much as possible and start from zero.
That approach worked—but it also came with tradeoffs.
You lose useful defaults. You end up re-declaring basic behavior everywhere. And sometimes you override things that were already correct.
In modern CSS, that “reset everything” mindset can create more work than it saves.
What has changed in modern CSS
The biggest shift is that the platform has become more predictable—and more capable.
Browsers are far more consistent than they used to be, which reduces the need for aggressive normalization.
At the same time, newer features give you more targeted control over layout and behavior. You no longer need to wipe everything out just to get consistency.
Instead of resetting broadly, you can adjust more precisely.
The new mental model
A modern reset is less about removing everything and more about establishing a sensible baseline.
Instead of asking:
“How do I neutralize all browser styles?”
You start asking:
“What defaults do I actually want?”
That leads to a different kind of reset—one that keeps useful behavior and only adjusts what needs to change.
What a modern reset usually includes
Modern resets tend to focus on a few key areas rather than trying to control everything.
One common pattern is normalizing box sizing across elements so layout calculations are predictable.
*, *::before, *::after {
box-sizing: border-box;
}Another is removing default margins in places where they are more likely to cause inconsistency than help.
body, h1, h2, h3, p {
margin: 0;
}From there, resets often shift toward improving defaults rather than removing them.
For example, making images behave more predictably inside layouts:
img, picture {
max-width: 100%;
display: block;
}Or ensuring form elements inherit typography so they feel consistent with the rest of the UI:
input, button, textarea, select {
font: inherit;
}These are not “resets” in the traditional sense—they are small, intentional adjustments.
Modern CSS features that change the approach
Some newer CSS features reduce the need for heavy resets entirely.
Properties like color-scheme let you opt into system-level behavior for light and dark modes, instead of manually overriding everything.
:root {
color-scheme: light dark;
}Layout tools like Flexbox and Grid also reduce the need for older layout hacks that resets used to account for.
And features like @layer give you a structured way to organize base styles, making resets part of a system instead of a standalone file.
@layer reset, base, components;
@layer reset {
/* baseline adjustments */
}The platform is doing more for you—so you do not need to fight it as much.
A more practical approach
In most modern projects, a good reset is small, focused, and easy to understand.
It sets a baseline, then gets out of the way.
Instead of maintaining a long list of overrides, you define a few core rules that make layout and typography predictable—and rely on the browser for the rest.
This makes your CSS easier to read, easier to maintain, and less likely to introduce unexpected behavior.
What to watch for
The biggest risk with modern resets is going too far in the other direction—keeping defaults that do not match your design system.
A lighter reset does not mean no reset. It just means being intentional about what you change.
It is also worth remembering that different projects have different needs. A design system, a marketing site, and an application UI may all benefit from slightly different baseline choices.
Keep the defaults that help you, and override the ones that do not.
Do you still need a reset?
Yes—but probably not the kind you used to use.
A modern reset is less about control and more about clarity. It defines how your project starts, without trying to account for every possible edge case.
In that sense, it becomes part of your system, not a workaround for the platform.
Quick answers
Should I use a popular reset library?
You can—but it is often worth understanding what it does and tailoring it to your needs.
Is normalize.css still relevant?
It can be, especially for broader compatibility. But modern browsers reduce the need for heavy normalization.
What is the biggest shift?
Moving from “remove everything” to “define a baseline.”
Want to go deeper?
As CSS continues to evolve, the need for aggressive resets will likely continue to shrink. The platform is becoming more consistent, and the tools for controlling layout and behavior are more precise than ever.
A reset used to be about fixing the browser. Now it is more about defining your starting point.