CSS Autoprefixer screenshot

CSS Autoprefixer

Add the vendor prefixes a stated property list needs: -webkit- and -moz- where they exist, the standard declaration last, no double prefixing.

Privacy First
0 Runs
Updated 2026-11-17
Runs in your browser
No sign-up, no upload

What the CSS Autoprefixer does

Each declaration is read into a property and a value, matched against the list, and written out prefixed then standard. Because a declaration is read as a pair, position: sticky is matched on the value as well as the property.

An already-prefixed property is not prefixed again: -webkit-user-select is not in the list, so it passes through unchanged.

This is not a full autoprefixer and does not claim to be. A property outside the list is left exactly as written, and values are never rewritten — no display: -webkit-box fallbacks. Check a browser-support table for anything outside the list.

How to use it

Paste the stylesheet into the CSS box, or press Run with the example already there.

Read the Prefixed CSS below: each matched declaration is preceded by its prefixed forms, with the standard one last.

Check a property you know needs no prefix in the Prefixed CSS — it appears once, unchanged, because the list is explicit.

Worked example

Input:

.box { user-select: none; color: red; }

Output:

.box {
  -webkit-user-select: none;
  -moz-user-select: none;
  user-select: none;
  color: red;
}

Why it runs in your browser

The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.

Prefixes for the properties that still need them, written before the standard declaration so a modern browser keeps the unprefixed rule.

The list is stated on the page: `user-select`, `appearance`, `backdrop-filter`, `clip-path`, `hyphens`, `text-size-adjust`, `mask-image` and `position: sticky`.

What it does, and what it does not

Each declaration is read into a property and a value, matched against the list, and written out prefixed then standard. Because a declaration is read as a pair, `position: sticky` is matched on the value as well as the property.

An already-prefixed property is not prefixed again: `-webkit-user-select` is not in the list, so it passes through unchanged.

This is not a full autoprefixer and does not claim to be. A property outside the list is left exactly as written, and values are never rewritten — no `display: -webkit-box` fallbacks. Check a browser-support table for anything outside the list.

How to use CSS Autoprefixer

Paste the stylesheet into the CSS box, or press Run with the example already there.

Read the Prefixed CSS below: each matched declaration is preceded by its prefixed forms, with the standard one last.

Check a property you know needs no prefix in the Prefixed CSS — it appears once, unchanged, because the list is explicit.

What to Expect

Best for

  • Adding the prefixes a small stylesheet still needs
  • Checking whether a property is on the list at all

Not ideal for

  • A full browser-support pipeline, which needs a real autoprefixer
  • Value rewrites such as old flexbox syntax

What this tool keeps

  • The standard declaration last
  • One prefix set per declaration, never doubled

What may need cleanup

  • A property outside the list stays unprefixed
  • A value that needs an old syntax needs a hand-written fallback

Common errors

  • The page refuses it: "color red" has no colon

Example use cases

  • Preparing a rule for an older Safari
  • Auditing which declarations still need a prefix

Sample input

CSS: .box { user-select: none; color: red; }

Sample output

Prefixed CSS: .box { …

Who this is for

  • Frontend developers shipping to older browsers
  • Anyone reviewing a prefixed rule

Frequently asked questions

Which properties does it prefix?

user-select, appearance, backdrop-filter, clip-path, hyphens, text-size-adjust, mask-image and position: sticky. The list is on the page; anything else is left alone.

Why is the standard declaration last?

Cascade order: a browser that understands the standard property must win over the prefixed form above it. Writing the prefix last would let an experimental implementation override the standard one.

Is it safe on a big stylesheet?

It is safe syntactically — every block is parsed and a block it cannot read is refused. But it only covers the listed properties, so a large stylesheet still needs a real autoprefixer.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.