-prefix-free lets you use only unprefixed CSS properties everywhere. It works behind the scenes, adding the current browser’s prefix to any CSS code, only when it’s needed.
“[-prefix-free is] fantastic, top-notch work! Thank you for creating and sharing it.”
— Eric Meyer
<link> or <style> elements and adds a vendor prefix where neededstyle attribute and adds a vendor prefix where needed<link> or <style> elements, style attribute changes and CSSOM changes (requires plugin).css() method get and set unprefixed properties (requires plugin)@import-ed files is not supportedstyle attribute) won’t work in IE and Firefox < 3.6. Properties as well in Firefox < 3.6.Check this page’s stylesheet ;-)
You can also visit the Test Drive page, type in any code you want and check out how it would get prefixed for the current browser.
Just include prefixfree.js anywhere in your page. It is recommended to put it right after the stylesheets, to minimize FOUC
That’s it, you’re done!
The target browser support is IE9+, Opera 10+, Firefox 3.5+, Safari 4+ and Chrome on desktop and Mobile Safari, Android browser, Chrome and Opera Mobile on mobile.
If it doesn’t work in any of those, it’s a bug so please report it. Just before you do, please make sure that it’s not because the browser doesn’t support a CSS3 feature at all, even with a prefix.
In older browsers like IE8, nothing will break, just properties won’t get prefixed. Which wouldn’t be useful anyway as IE8 doesn’t support much CSS3 ;)
Test the prefixing that -prefix-free would do for this browser, by writing some CSS below:
A file is a "package" format. Unlike a raw disc image, a package is an installer. It contains compressed files, installation scripts, and metadata that tell an operating system—such as macOS, PlayStation 4/5, or various Linux distributions—where to place files and how to configure them. Why Convert BIN to PKG?
Bin was nervous. "You mean... I have to follow rules?"
The files are reorganized into a directory structure that the target system recognizes.
Your binary works on your dev machine, but after packaging, it fails. Why? Your .bin might expect libfoo.so in /usr/local/lib . The target machine doesn't have it.
Converting transforms a raw tool into a first-class macOS citizen. The process isn't magic—it's a deliberate, scriptable wrapping of binaries with metadata, permissions, scripts, and signing. Whether you're a solo developer distributing a CLI tool or an IT admin packaging internal software for thousands of Macs, pkgbuild and productbuild give you the power to deliver reliable, uninstallable, and professional-grade installers.
A file is a "package" format. Unlike a raw disc image, a package is an installer. It contains compressed files, installation scripts, and metadata that tell an operating system—such as macOS, PlayStation 4/5, or various Linux distributions—where to place files and how to configure them. Why Convert BIN to PKG?
Bin was nervous. "You mean... I have to follow rules?" bin to pkg
The files are reorganized into a directory structure that the target system recognizes. A file is a "package" format
Your binary works on your dev machine, but after packaging, it fails. Why? Your .bin might expect libfoo.so in /usr/local/lib . The target machine doesn't have it. Why Convert BIN to PKG
Converting transforms a raw tool into a first-class macOS citizen. The process isn't magic—it's a deliberate, scriptable wrapping of binaries with metadata, permissions, scripts, and signing. Whether you're a solo developer distributing a CLI tool or an IT admin packaging internal software for thousands of Macs, pkgbuild and productbuild give you the power to deliver reliable, uninstallable, and professional-grade installers.