Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Tool · Web DevelopmentFree

Can I Use

Can I use shows browser support tables for front end web features (HTML, CSS, JavaScript APIs and more), with global and per country usage percentages from StatCounter rather than a simple yes or no, plus notes on partial support and known bugs. It answers "can I ship this feature yet?" in seconds, for any front end developer deciding what is safe to use.

Data repo GitHub stars

5.9k

GitHub · Sept 2026

Data licence

CC BY 4.0

GitHub · Sept 2026

Format

Tool

Topic

Web Development

Provider

Alexis Deveria

Time needed

Seconds per lookup

Level

All

Access

Free

What it is

Can I use is a free site created and maintained by Alexis Deveria, with community contributions to its data on GitHub. For each web platform feature it shows which browser versions support it fully, partially or not at all, weighted by real usage data. Browser usage figures come from StatCounter GlobalStats and are refreshed regularly (the site showed August 2026 data in September 2026). It also shows results from MDN's browser compatibility data for many features.

The underlying support data is published on GitHub under a Creative Commons Attribution licence, and powers tools such as Browserslist and Autoprefixer. The data repository has about 5,900 stars (September 2026).

The site is free with ads; a small monthly Patreon contribution removes them.

Why the usage percentage matters most

"Is it supported?" is the wrong question. The right one is "what share of my users lack it?" A feature at 94% global support may be fine for a developer tool and not fine for a government service used on older Android phones. Can I use lets you switch from global numbers to a specific country, so you can check support among users in Pakistan or wherever your audience is.

Features worth knowing

  • Known issues tab: a feature marked supported can still be broken in a specific browser version. The bug is often documented right there, saving you an afternoon.
  • Notes and flags: partial support usually comes with a numbered note explaining what is missing.
  • Comparison and filters: you can choose which browsers and versions to show, and compare features side by side.
  • Import your own analytics: you can import your site's browser usage data to see support among your actual visitors.

How to use it in daily work

  • Before using a new CSS or JavaScript feature, search it here. Five seconds can save a production bug.
  • Check the country view for your target audience, not just the global number.
  • For anything under your comfort threshold, plan a fallback or progressive enhancement.
  • In build tooling, set a Browserslist query (for example "> 0.5%, not dead") so transpilers and autoprefixers use the same data automatically.

Limitations

  • It covers browser support, not API documentation. Use MDN for how a feature works.
  • Usage statistics are estimates from StatCounter's sample and can differ from your own users.
  • Very new or experimental features may not be tracked yet.

Pair it with

  • MDN Web Docs for full feature documentation and its own compatibility tables.
  • Baseline (on MDN and web.dev) for a quick "widely available" signal.

Best for: any front end developer deciding whether a modern feature is safe to ship to their audience.

frontendcssjavascriptfree course

Ready to start?

Opens on Alexis Deveria in a new tab.

Open resource
Link broken or out of date?

Report a problem

With "Can I Use". Only Tauseef reads this.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.