Reference

Can I Use

The browser-support reference for every CSS, HTML, and JavaScript feature shipped on the web.

Can I Use is the canonical browser compatibility reference for the web platform. For any CSS property, HTML element, or JavaScript API you're considering shipping, Can I Use answers one question definitively: which browsers, which versions, and what percentage of your users.

Visit Can I Use ↗Nominate a site →
Pricing · Free (ad-supported)Official site · caniuse.com
— 01 / At a glance

The facts.

Category
Reference
Pricing
Free (ad-supported)
Best for
Frontend developers, Design system maintainers, Tech leads, Anyone shipping production CSS or JS
Where it runs
Browser-based · works on macOS, Windows, Linux, ChromeOS
Official site
caniuse.com
Last reviewed
2026-05
— 02 / What it is

The shape of the tool.

Run since 2008 by Alexis Deveria, Can I Use is one of the longest-running free resources in the web industry, and it's still the single source of truth for compatibility questions. Every feature gets a support table — rows for Chrome, Edge, Firefox, Safari, Opera, Samsung Internet, Android WebView — with green for supported, yellow for partial support, and red for unsupported. A global usage percentage tells you, roughly, how much of the live web audience your decision affects.

What makes Can I Use load-bearing is that the data is curated. Mozilla's MDN compatibility tables, browser-vendor release notes, and community pull requests all contribute. Edge cases — 'supported only behind a flag,' 'supported with a -webkit prefix,' 'partial support in 14.2 and full support from 14.3' — get flagged in the table notes. For a working web designer in 2026, that nuance is the entire point: 'is it supported' is a less useful question than 'is it supported in the versions my users still run.'

The browser landscape in 2026 has narrowed: Chromium (Chrome, Edge, Opera, Brave, Arc) is the dominant family, Safari runs WebKit on every iOS device, and Firefox holds a small but committed share. Even so, Can I Use stays essential. Container queries, view transitions, anchor positioning, CSS nesting, the popover API, scroll-driven animations — every modern feature has a support story that's worth checking before you reach for it.

— 03 / Try it

Use it on the official site.

Open in a new tab
caniuse.com
↗
— 04 / Key features

What it actually does.

  • Support tables for every CSS, HTML, JS, SVG, and Web API feature shipped on the web
  • Configurable usage data (global, regional, or your own browserslist config)
  • Notes column flagging known bugs, flag-gated features, and partial support
  • Search by feature name, by CSS property, or by Bugzilla ticket
  • Linked references to spec status, MDN docs, and original bug tickets
  • Filter by 'usage > 95%' to find broadly-supported features for your audience
  • Embeddable support tables for blog posts and documentation
  • Free, ad-supported, with no rate limits or account required
— 05 / Use cases

When designers reach for it.

  1. 01
    Pre-feature support check

    Before adopting a modern CSS feature in a production codebase, search Can I Use, confirm support in Safari and Firefox (the two most likely laggards), and check the notes for known issues.

  2. 02
    Polyfill scoping

    Decide whether a feature needs a polyfill or a fallback. If global support is above 95% and your audience is Western, you can often ship the feature with a graceful fallback for the long tail.

  3. 03
    Browserslist configuration

    Use Can I Use to translate 'support the last two versions of Chrome, Safari, Firefox, and Edge' into the actual percentage of users you're committing to support.

  4. 04
    Bug triage

    When a feature breaks in one browser version, Can I Use's notes often reveal that it's a known bug with a tracked ticket — saving you the debugging round-trip.

  5. 05
    Educational reference

    Learning a new CSS feature? Read the support story first. It tells you where the feature is on the maturity curve and whether you'll be writing fallbacks for two years or two months.

— 06 / Workflow

A working sequence.

  1. 01
    Search for the feature

    Use the canonical name (e.g., 'container queries' or '@container'). Can I Use handles aliases and prefixed variants.

  2. 02
    Read the support table top to bottom

    Don't skip the right-hand notes. Half the answers live in 'supported only behind a flag' or 'broken in 17.4, fixed in 17.5.'

  3. 03
    Configure usage to match your audience

    Default is global usage. If you ship to a regional audience, configure region-specific data — Safari's share on iOS is much higher in the US than in India.

  4. 04
    Decide: ship, fallback, or wait

    Ship if support is above your threshold. Fallback if you can encode the feature behind @supports. Wait if the feature is a single-vendor experiment.

  5. 05
    Encode the decision in code

    Use @supports for CSS, feature detection (in (...)) for JS. Don't user-agent sniff — it's brittle and discourages browsers from feature parity.

— 07 / Best for

Who it fits.

  • Frontend developers
  • Design system maintainers
  • Tech leads
  • Anyone shipping production CSS or JS
— 08 / Strengths & trade-offs

The balance.

Strengths
  • Authoritative, curated data with deep notes
  • Free and runs without an account
  • Custom browserslist config for accurate per-project usage data
  • Embeddable for blog posts and team docs
  • Maintained for 17+ years; effectively a public utility
Trade-offs
  • Some new features lag the data — verify with MDN's BCD when stakes are high
  • Usage data is global by default; regional accuracy varies
  • Visual design is functional, not editorial
  • Mobile usage data has fewer signals than desktop
Web Design Awards — Verdict
Can I Use is infrastructure. Every working web developer has it bookmarked, and every modern CSS feature gets checked here before shipping. Treat it as load-bearing tooling, not a 'nice to have' reference.
Pricing · Free (ad-supported)
— 09 / Common questions

FAQ

  • Is Can I Use still being updated?

    Yes, actively. New features land in the data within days of browser shipping, and the project accepts community pull requests for corrections and edge cases.

  • How accurate is the global usage data?

    Reasonably accurate for global trends, less precise for regional audiences. If your audience is concentrated in a region, configure regional usage data or supplement with your own analytics.

  • Can I Use vs MDN compatibility tables — which should I trust?

    Both are good and they often agree. MDN's Browser Compatibility Data (BCD) tends to be more granular at the API method level; Can I Use is faster to scan for high-level decisions. Use both for high-stakes calls.

  • Does Can I Use have an API?

    Not an official public API, but the raw data is published as a JSON file at github.com/Fyrd/caniuse, which many tools (browserslist, autoprefixer, postcss-preset-env) consume.

  • How do I check support for features behind feature flags?

    Can I Use marks flag-gated features in the notes column. A yellow cell with a flag icon means 'available, but the user has to enable it' — effectively unsupported for production use.

  • Is it safe to drop IE11 support?

    Yes, in 2026. Microsoft formally ended IE11 support in 2022. Even enterprise IT shops have largely migrated to Edge. Unless your audience is a specific regulated industry, IE11 fallbacks are no longer worth the maintenance cost.

— 10 / Related tools

Or look at the others.

Last reviewed: 2026-05 · 7 tools in the Web Design Awards directory