Can I use Browser Support Tables compared with MDN compatibility tables and BrowserStack| Can I use | MDN compatibility tables | BrowserStack |
|---|
| Question answered: Which browser versions support a web feature, with notes on partial support and known issues. Usage statistics from StatCounter, by country, show whether a feature can ship without a fallback. | Question answered: Which browsers and runtimes implement a given API, CSS property, HTML element or other feature, at fine feature granularity. | Question answered: How a site or web app actually behaves on real browsers and devices, tested interactively. It checks your own pages, where support tables describe features in general. |
| Data source and scope: Tables cover HTML, CSS, JavaScript and web APIs. According to Mozilla, Can I use covers larger features as a whole and adds each feature manually, and it now builds further tables from MDN data. | Data source and scope: Built on the browser-compat-data project, with over 15,000 features across Web APIs, JavaScript, CSS, HTML, HTTP, SVG, WebAssembly and WebExtensions. Flags, UI changes and screen reader compatibility are not tracked. | Data source and scope: Real Windows, macOS, Android and iOS devices with newer and older versions of Edge, Safari, Chrome, IE and Firefox. |
| Openness and local testing: Data from your own Google Analytics account can be imported to see support among your actual visitors. Sister sites cover email clients and WebViews. | Openness and local testing: The underlying dataset is released under the CC0-1.0 licence and distributed as an npm package. It is also used in tools such as Visual Studio Code and WebStorm. | Openness and local testing: Internal development and staging sites, including those behind firewalls, can be tested without extra setup. |
| Access and cost model: Free, financed by ads and Patreon, and no account is needed. | | Access and cost model: Commercial cloud service. A free trial is offered, and plans are listed on a separate pricing page. |