What reads the Browserslist config?

Babel preset-env, Autoprefixer, PostCSS plugins, and bundlers like webpack and Vite all share this config to decide which transforms and prefixes to apply, so one query controls your whole toolchain.

What does not dead mean?

The dead query matches browsers without official support and under two percent global usage. Combining it with not, as in not dead, excludes those abandoned browsers from your target set.

How does last 2 versions work?

It selects the two most recent major versions of each browser Browserslist tracks. Pairing it with a usage threshold prevents niche browsers with tiny share from inflating your output.

Should I support Internet Explorer?

Most projects no longer do, since IE reached end of life. Leaving the IE exclusion on keeps your bundles smaller, but you can add a query for it if a legacy audience still requires it.

rc file or package.json field?

Both work identically. A .browserslistrc file keeps the query out of package.json and supports environment sections, while the package.json field keeps everything in one place for small projects.

.browserslistrc Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Control your build targets with one query

Browserslist is the shared source of truth that Babel, Autoprefixer, and bundlers consult to decide which browsers to transpile and prefix for. Get it wrong and you either ship bloated polyfills for browsers nobody uses or break the experience for a real audience. This builder turns a few choices into a precise query.

How it works

The output is a list of Browserslist queries, combined with the implicit AND that Browserslist applies between lines and the OR within comma lists. A last N versions query selects recent releases, while a > X% query keeps only browsers above a global usage share, narrowing the set. Negative queries like not dead and not ie 11 subtract abandoned or unwanted browsers. The result resolves against the bundled Can I Use dataset at build time, so the same config adapts as browser usage shifts.

Tips and example

A common production query is > 0.5%, last 2 versions, not dead, which targets mainstream browsers while dropping the long tail. Lower the percentage to widen support, or raise it to shrink bundles. For modern-only builds add not op_mini all and drop older version counts. Place the result in .browserslistrc, or use the package.json field to keep configuration centralized for a small project.