Loading CSS Autoprefixer...
Please wait a moment

How to Use the CSS Autoprefixer

Step 1

Paste or upload your CSS

Start with any CSS: a whole stylesheet, one rule, or minified output from a build.

•
Paste CSS: Drop your code into the input editor
•
Upload: Pick a .css or .txt file from your computer
•
Try sample: Click Sample to load a small rule with flexbox, transform and transition
Step 2

Check the prefixed result

The page adds vendor-prefixed copies above these properties. It works from this fixed list, not from live browser data, so check Can I Use if you need to know which browsers still want a prefix.

PropertyCopies added
transform-webkit-, -moz-, -ms-, -o-
transition, animation-webkit-, -moz-, -o-
box-shadow, border-radius-webkit-, -moz-
display: flexdisplay: -webkit-box, -webkit-flex, -ms-flexbox
flex-webkit-, -ms-
flex-direction, flex-wrap, justify-content, align-items-webkit-
user-select-webkit-, -moz-, -ms-
appearance, backface-visibility, perspective, box-sizing-webkit-, -moz-
filter, backdrop-filter, clip-path-webkit-
Step 3

Copy or download it

Copy the result to your clipboard or save it as prefixed.css. Everything you typed is still there, unchanged; only the prefixed lines are new.

Frequently Asked Questions

Which properties get prefixes?

A fixed list: transform, transition, animation, box-shadow, border-radius, flex and the flexbox alignment properties, display: flex, user-select, appearance, backface-visibility, perspective, box-sizing, filter, backdrop-filter and clip-path. Each one only gets the vendor forms that actually shipped in some browser, so you will see -ms-user-select but never -o-user-select. Anything not on the list, including grid, gradients inside values and custom properties (--name), is left alone.

Is this the same as Autoprefixer from PostCSS?

No. The PostCSS Autoprefixer reads Can I Use data and your browserslist settings and adds only what your target browsers need. This page has no browser data at all; it applies the same fixed list every time. That makes it handy for a quick snippet or an old project, but for a real build pipeline the PostCSS plugin is the better choice.

Will it change any of my CSS?

No. Your declarations, comments, strings, url() paths and numbers are copied exactly as typed, so 14.50px stays 14.50px. The page only inserts prefixed copies right above the declaration they come from, using the same value. If a rule already has, say, -webkit-transform, it is not added a second time.

Do modern browsers still need these prefixes?

Mostly not. Current Chrome, Edge, Firefox and Safari handle transform, transition, animation, box-shadow, border-radius, flexbox, box-sizing and filter without a prefix. The ones that still matter in practice are -webkit-backdrop-filter for Safari before version 18, -webkit-user-select for Safari, and -webkit-appearance on some form controls. The rest only help very old browsers, so you can delete them if you do not support those.

What happens if my CSS has a mistake?

If a string, comment or url( is never closed, or a { or } has no partner, nothing is prefixed and you get the line and column of the problem instead, so you can fix it first. Mistakes inside a value, such as a misspelled color, are not checked.

Is my CSS sent anywhere?

No. The prefixing runs in your browser, and an uploaded file is read locally. Nothing is uploaded to a server.