What makes neumorphism different
Neumorphism (or neomorphism) describes a UI style that sits between two extremes: the hyper-realistic skeuomorphism of Apple's late-2000s interfaces and the flat minimalism of today's Material Design. The term was coined in a December 2019 UX Collective post; since then the design and development communities have debated it heavily, with Adam Giebl publishing an online generator and plenty of commentary on its aesthetics, usability and practicality.
The defining look is relatively simple to describe: elements appear attached to the surface they sit on, either extruded from it or pressed into it. Soft shadows in two directions create the effect, which is why the style is sometimes called "soft UI." Comparing a card component in Material Design against its neumorphic counterpart shows the gap clearly.
Building the effect in CSS
A single box-shadow is not enough. A convincing neumorphic surface uses several box-shadow and background-color values together, and the details matter.
Shadow basics
The box-shadow syntax:
box-shadow: [horizontal offset] [vertical offset] [blur radius] [optional spread radius] [color];
- Horizontal offset: positive shifts the shadow right, negative shifts it left.
- Vertical offset: positive shifts it downwards, negative upwards.
- Blur radius: longer lengths produce bigger, lighter shadows; negative values are not allowed.
- Spread radius: larger values produce bigger, longer shadows.
- Color: set as with any CSS color.
- Inset: the default gives a drop shadow;
insetmoves it inside the element.
Multiple shadows can be chained with commas, up to four values, one per side of the box:
box-shadow: 20px 20px 50px #00d2c6,
-30px -30px 60px #00ffff;
Two shadows, four light directions
A neumorphic element needs one light and one dark shadow to get its raised look. For that you set two positive and two negative offsets, and moving the light source yields four combinations. Keeping the values in CSS variables makes the variations easier to reason about.
box-shadow: var(--h1) var(--v1) var(--blur1) var(--color-dark),
var(--h2) var(--v2) var(--blur2) var(--color-light);
| Light Source | Positive Values | Negative Values |
|---|---|---|
| Top Left | --h1, --v1 | --h2, --v2 |
| Top Right | --h2, --v1 | --h1, --v2 |
| Bottom Left | --h1, --v2 | --h2, --v1 |
| Bottom Right | --h2, --v2 | --h1, --v1 |
Swapping a drop shadow for inset flips the element from extruded to pressed into the background. Holding the light source at the top left and toggling only the inset option is enough to see the difference.
Background and gradients
The element's own background must be transparent or share (or nearly share) the color of whatever sits beneath it, which is why box-shadow alone determines the edges. A solid color equal to the parent's background produces a flat surface. Subtle gradients change how the surface reads; the gradient angle must match the light source:
- Convex: the surface bulges outward — lighter gradient sections align with lighter shadow sections, darker with darker.
- Concave: the surface curves inward — lighter gradient sections align with darker shadow sections, and vice versa.
.element {
background: linear-gradient(var(--bg-angle), var(--bg-start), var(--bg-end));
box-shadow: var(--h1) var(--v1) var(--color-dark),
var(--h2) var(--v2) var(--color-light);
}
Where the style falls short
Buttons expose the core weakness. A primary call-to-action exists to stand apart, typically through a distinct background color. Neumorphism requires the background to match the surroundings, so that tool is gone. Text color, a border below the label, or an added icon can recover some visual weight; a solid background also reads stronger than a gradient and pairs with an inset shadow to produce a "pressed" state on active.

Nods to physical devices — a router button with a sticker-like label, a car panel button that lights up when pressed — improve the result somewhat, but the conventional button still delivers the better UX with fewer constraints and less implementation work.
State changes and clickability
Inputs, select elements and progress bars need to look different across states:
- User interaction: hover, active, focus, visited
- Validation: error, success, warning, disabled
Accessibility and UX rules demand visible distinctions for each. Neumorphism's restrictions leave little room; variations end up too subtle to cover every case, and it becomes hard to tell which elements are clickable at all. Shadow and rounded corners also consume padding and margin, so small elements suffer disproportionately because the effect overwhelms them.

The suitable targets are cards and other static containers with no interaction or validation states. Michal Malewicz, who helped coin the term, makes the argument in a sharply critical piece: the effect works only on cards whose structure already carries the hierarchy.
It works well when it can be removed without any loss for the product.
Accessibility and restraint
Contrast is the biggest problem. Neumorphic elements deliberately blend into their background, and a contrast checker sees only foreground and background — shadows don't enter the calculation, and even if they did they would be too faint to help. Specific criticisms include:
- Users with color blindness or poor vision struggle with the low contrast produced by soft shadows.
- Overuse flattens page hierarchy; the background color constraint keeps any single element from standing out.
- The extrusion effect obscures which elements are interactive and which are static.
To keep shadows readable, the underlying surface color should not sit near the RGB extremes of white or black. And aesthetically pleasing or not, neumorphism should not dominate a page: overuse yields a plastic look and destroys visual hierarchy.
The workable approach is to treat neumorphism as an accent layered on another system — pairing it with Material Design (one example combines it with Materialize CSS on card elements) so components gain a fresh alternative look without inheriting the style's limits. A full neumorphic design system is too restrictive in color and too soft in contrast for interactive controls, which makes it a poor replacement for current design systems — though it may earn a place inside them as an option for cards and static containers.



