Paste a Browserslist query, compare presets and inspect browser or Node.js targets before changing Autoprefixer, Babel or PostCSS configuration. Evaluation runs locally in a worker and blocks project config lookup.
Browserslist controls how tools such as Autoprefixer, Babel, postcss-preset-env and Stylelint decide browser support. This playground turns compact rules like defaults, > 0.5%, not dead and maintained node versions into visible target rows.
The evaluator uses the bundled Browserslist data in a browser worker. It does not read .browserslistrc, package.json, environment variables, custom stats files or browserslist-config packages.
Start from a preset or paste a query. Unsupported project-specific modes are reported as controlled diagnostics instead of resolving files or packages.
The common Browserslist baseline used by many front-end projects.
Coverage uses the caniuse-lite data bundled with this build, not a live remote database.
browserslist@4.28.2 bundled caniuse-lite snapshotand_chr 148and_chrMobile43.340%and_ff 150and_ffMobile0.350%and_qq 14.9and_qqMobile0.110%and_uc 15.5and_ucMobile0.630%android 148androidMobile0.240%chrome 148chromeDesktop0.020%chrome 147chromeDesktop8.550%chrome 146chromeDesktop7.110%chrome 145chromeDesktop0.940%chrome 142chromeDesktop0.780%chrome 112chromeDesktop1.150%chrome 109chromeDesktop0.710%edge 148edgeDesktop0.000%edge 147edgeDesktop2.480%edge 146edgeDesktop2.310%firefox 150firefoxDesktop0.330%firefox 149firefoxDesktop1.090%firefox 140firefoxDesktop0.090%ios_saf 26.4ios_safMobile1.630%ios_saf 26.3ios_safMobile6.250%ios_saf 26.2ios_safMobile1.010%ios_saf 18.5-18.7ios_safMobile2.660%kaios 3.0-3.1kaiosOther0.000%kaios 2.5kaiosOther0.010%op_mini allop_miniMobile0.000%op_mob 80op_mobMobile0.860%opera 131operaDesktop0.000%opera 127operaDesktop0.010%safari 26.4safariDesktop0.320%safari 26.3safariDesktop1.060%samsung 29samsungMobile1.410%samsung 28samsungMobile0.060%# .browserslistrc
defaults
// package.json
{
"browserslist": "defaults"
}
// mobileToDesktop: falseIt is useful as a baseline, but teams should still know which old or mobile targets are included before changing build output.
The number is calculated from bundled usage data. Confirm regional or custom stats in the real repository when support policy is business-critical.
extends, custom stats and config lookup can be powerful in a repo, but a public page should not resolve user-provided packages or files.
Use these when target browser policy touches dependency ranges, build config or JavaScript transforms.