The CSS backdrop-filter property works in Chrome 76+, Edge 17+, Firefox 103+, Safari 9+ (prefixed), Opera 64+, and Samsung Internet 12+. See full browser support.

Prince Dewani
May 6, 2026
CSS backdrop-filter is a W3C Filter Effects Module Level 2 property that applies graphical effects, such as blur or saturation, to the painted area behind an element. It works in Chrome 76+, Edge 17+, Firefox 103+, Safari 9+ on macOS and iOS with the -webkit- prefix, Opera 64+, and Samsung Internet 12+, while Internet Explorer never added support.
This guide covers what backdrop-filter is, the browsers that support it, the filter functions it accepts, the use cases, and the known issues.
backdrop-filter is a CSS property defined by the W3C in the Filter Effects Module Level 2. It applies graphical effects, such as blur, brightness, or saturation, to the painted area behind an element. The element itself must be partially transparent for the effect to show through.
backdrop-filter ships in every modern engine, but the path to unprefixed support was uneven. The Web Platform Baseline marks it as Newly Available, with Safari the last engine to drop the -webkit- prefix and Internet Explorer the only major engine that never added the property.
Chrome supports backdrop-filter unprefixed from Chrome 76 on Windows, macOS, Linux, ChromeOS, and Android. Chrome 47 to 75 had the property behind the Experimental Web Platform features flag at chrome://flags, so it was disabled by default. Chrome 4 to 46 did not support backdrop-filter at all.
Microsoft Edge supports backdrop-filter from Edge 17 on Windows. Edge Legacy 17 and 18 shipped it through the EdgeHTML engine, and the Chromium-based Edge 79+ inherits Chrome's full unprefixed support across Windows, macOS, and Linux. Edge 12 to 16 did not support the property.
Firefox supports backdrop-filter unprefixed from Firefox 103 on Windows, macOS, Linux, and Android. Firefox 70 to 102 had the property behind the layout.css.backdrop-filter.enabled flag in about:config, so it was disabled by default. Firefox 2 to 69 did not support the property at all.
Safari supports backdrop-filter from Safari 9 on macOS and from Safari 9 on iOS and iPadOS, but only through the -webkit-backdrop-filter prefix until Safari 18. From Safari 18 the unprefixed property works on macOS, iOS, and iPadOS. Safari 3.1 to 8 on macOS and Safari 3.2 to 8.4 on iOS did not support the property.
Opera supports backdrop-filter unprefixed from Opera 64 on Windows, macOS, and Linux through its Blink engine. Opera 34 to 63 had it disabled by default behind the experimental features flag. Opera Mobile picks up support from Opera Mobile 80 on Android, and Opera 9 to 33 dropped the declaration as unrecognized syntax.
Samsung Internet supports backdrop-filter unprefixed from Samsung Internet 12 on Galaxy phones and tablets. Samsung Internet 5 to 11.2 had the property disabled by default behind the Chromium experimental flag, and Samsung Internet 4 did not support it at all. The current Samsung Internet builds inherit every backdrop-filter fix from upstream Chromium.
Modern Chrome for Android supports backdrop-filter from Chrome 76, and the legacy stock Android Browser picks up unprefixed support from Android Browser 147+. Android Browser 2.1 to 4.4.4 did not support the property, so any pre-Chromium WebView fallback has to use a translucent background-color without the blur effect.
Internet Explorer 5.5 through Internet Explorer 11 never added support for backdrop-filter. Microsoft has retired Internet Explorer, so legacy intranet pages that still need a frosted overlay have to fall back to a static translucent background-color, a pre-blurred image asset, or a Microsoft Edge IE Mode tab where the modern Chromium engine takes over rendering.
Note: backdrop-filter behaves differently across Safari prefix builds, flagged Chrome and Firefox versions, and Edge Legacy. Test it on real browsers and OS with TestMu AI. Try TestMu AI free!
backdrop-filter accepts the same filter functions as the filter property, plus url() for an SVG filter reference. You can chain several functions in one declaration, and the browser applies them left to right to the painted area behind the element.
/* 1. Frosted glass card. The translucent background lets the blurred backdrop show through. */
.glass-card {
background-color: rgba(255, 255, 255, 0.45);
-webkit-backdrop-filter: blur(12px) saturate(180%);
backdrop-filter: blur(12px) saturate(180%);
border: 1px solid rgba(255, 255, 255, 0.2);
border-radius: 12px;
padding: 24px;
}
/* 2. Sticky header with a darker tint over scrolling content. */
.app-header {
position: sticky;
top: 0;
background-color: rgba(20, 20, 20, 0.55);
-webkit-backdrop-filter: blur(8px) brightness(80%);
backdrop-filter: blur(8px) brightness(80%);
}
/* 3. Modal overlay that desaturates the page behind it. */
.modal-overlay {
background-color: rgba(0, 0, 0, 0.35);
-webkit-backdrop-filter: grayscale(60%) blur(4px);
backdrop-filter: grayscale(60%) blur(4px);
}
/* 4. Detect support before shipping a fallback. */
@supports not ((-webkit-backdrop-filter: blur(1px)) or (backdrop-filter: blur(1px))) {
.glass-card {
background-color: rgba(255, 255, 255, 0.9);
}
}backdrop-filter replaces a stack of older techniques such as duplicating an image and blurring it under a clipped element, blurring with SVG filters, or shipping a pre-rendered noise texture. Most teams adopt it on translucent UI surfaces where the content behind has to stay legible without disappearing.
backdrop-filter ships widely now, but several rendering quirks still bite teams. Most issues come from the -webkit- prefix gap on Safari, parent transforms that break the backdrop root, and the limited reach of the opacity() and drop-shadow() filter functions on backdrops.
In my experience, the trap that bites teams hardest is shipping a glassmorphism card inside a parent that adds will-change: transform for animation, then wondering why the blur silently disappears on the production build but worked fine in the isolated component preview.
All backdrop-filter version numbers and platform notes in this guide come from these primary sources:
Did you find this page helpful?
More Related Hubs
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance