OSS TanbouSign in with GitHub

generate only the vendor prefixes required by Browserslist and Can I Use data

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
22,211
Primary language
JavaScript
License
MIT
Repository last updated
Oct 5, 2026
On this page

Overview

Autoprefixer is a PostCSS plugin that parses CSS and adds or removes vendor prefixes according to target browsers and Can I Use data. Browser policy can be shared through Browserslist configuration.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Add and remove prefixes according to Browserslist target browsers

It reads Browserslist configuration and emits only the prefixes required by the selected browser set.

Sources: [1]

Use Can I Use data instead of maintaining prefix rules by hand

Browser support decisions are driven by dependencies such as caniuse-lite and updated support data.

Sources: [2][1]

Integrate through PostCSS loaders, CLI workflows, or Node APIs

It works as a standard PostCSS plugin in bundlers, postcss-cli, and programmatic processing.

Sources: [1]

Best fit

Fits frontend teams that want one browser-support policy instead of handwritten prefixes

A shared Browserslist configuration lets developers author standard CSS while the build determines compatibility prefixes.

Sources: [1]

Before adoption

Autoprefixer is not a polyfill

The README explicitly states that it only adds prefixes. Unsupported CSS features still require a separate transform or polyfill where appropriate.

Sources: [1]

IE Grid translation is opt-in and has limitations

Grid prefixing must be explicitly enabled, such as with grid: autoplace, and translated IE layouts have constraints that should be tested in the target browser.

Sources: [1]

Official sources

  1. [1]Autoprefixer 10.6.1 README(2026-10-05)
  2. [2]Autoprefixer 10.6.1 package metadata(2026-10-05)
  3. [3]Autoprefixer 10.6.1 changelog(2026-10-05)
  4. [4]Autoprefixer 10.6.1 release(2026-10-05)
  5. [5]Autoprefixer MIT license(2026-10-05)
Supplemental curator note

Treat .browserslistrc or the browserslist field in package.json as the source of truth for browser targets. Autoprefixer is a prefixer, not a general CSS polyfill.

Try it in 3 steps

  1. 1

    Install Autoprefixer 10.6.1 with PostCSS

    Pin Autoprefixer and the reviewed PostCSS release in a temporary project.

    demo=$(mktemp -d "${TMPDIR:-/tmp}/autoprefixer.XXXXXX") && cd "$demo" && npm init -y >/dev/null && npm install --save-exact postcss@8.5.29 autoprefixer@10.6.1
  2. 2

    Create a Browserslist target and CSS that needs a prefix

    Target Safari 8 explicitly so the example demonstrates Browserslist-driven prefix generation.

    printf "%s\n" 'Safari 8' > .browserslistrc && printf "%s\n" '.field { user-select: none; }' > input.css && printf "%s\n" "import fs from 'node:fs';" "import postcss from 'postcss';" "import autoprefixer from 'autoprefixer';" "const css = fs.readFileSync('input.css', 'utf8');" "const result = await postcss([autoprefixer()]).process(css, { from: 'input.css', to: 'output.css' });" "fs.writeFileSync('output.css', result.css);" > demo.mjs
  3. 3

    Run Autoprefixer and verify the vendor prefix

    Confirm that the target browser policy adds the expected WebKit prefix to the generated CSS.

    node demo.mjs && grep -q -- "-webkit-user-select" output.css
Check the official README

Growth

Growth trends · Last 30 days

22,211 Stars

Trend data is still being collected.

Built with

Categories and tags

Categories

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • css
  • postcss-plugins
  • prefixer
Stars
22,211
Forks
1,288
Watchers
360
Open issues
38
Owner type
Organization
Primary language
JavaScript
License
MIT
Repository last updated
Oct 5, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?