The most complete CSS support for Sublime Text 3
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
completions Add <aspect-ratio> type to align-content, justify-content Jul 5, 2018
messages Remove misleading install message for version 2.1.18 Aug 19, 2018
tool Add newprop and newfunc snippets to tool/ Jul 31, 2016
.gitignore gitignore Jul 31, 2016 Remove reference to develop branch from Apr 13, 2018
CSS3.sublime-syntax Remove 'include: properties' from rule-list-body Aug 19, 2018
Commands.sublime-commands Merge branch 'new' into dev Jun 30, 2016
Comments.tmPreferences Remove -text.html from Comments.tmPreferences Apr 13, 2018
Default.sublime-keymap Update for Fonts Level 4 Jul 30, 2017
LICENSE Mention CSS Modules support in the README Jun 24, 2017
Symbol Index.tmPreferences Remove unnecessary "source.css" from Symbol List selector match Jul 17, 2016
Symbol List.tmPreferences Remove unnecessary "source.css" from Symbol List selector match Jul 17, 2016 Update for Fonts Level 4 Jul 30, 2017
messages.json Remove misleading install message for version 2.1.18 Aug 19, 2018 merge changes from dev branch Oct 12, 2014


Join the chat at

The most complete CSS and PostCSS-cssnext support for Sublime Text.


  • Absurdly Complete: I mined the entire set of draft specs and supported everything. Some of this stuff won't be implemented in browsers for years. If it's in the spec, it's supported.
  • Future Proof: PostCSS-cssnext is fully supported. If you use cssnext, you can use futuristic CSS like...
    • nesting
    • custom selectors
    • custom properties
    • custom media queries
    • @apply
    • CSS Modules
    • lots more
  • Productive: Offers a full set of completions for properties, descriptors, @-rules, functions, and selectors. The completions are highly specific to what you're writing.
  • Modern: Bad, old CSS is flagged. Unnecessarily prefixed properties aren't highlighted. Catches lots of mistakes. Encourages best practices.
  • Faithful: Follows the W3C specs extremely closely.
  • Fast: CSS3 has been designed for Sublime's new custom regex engine, which is crazy fast. The syntax highlighting typically takes less than 100ms, even for very large CSS files.

Before & After

before and after


  1. Install Package Control

  2. Install CSS3

    Platform Install Command
    Mac cmd+shift+p   → Package Control: Install Package → CSS3
    Linux/Windows ctrl+shift+p → Package Control: Install Package → CSS3
  3. (Required) Disable the default CSS package

    Platform Disable Command
    Mac cmd+shift+p   → Package Control: Disable Package → CSS
    Linux/Windows ctrl+shift+p → Package Control: Disable Package → CSS

    disabling the default CSS package

    Make sure you don't have any open files set to the default CSS syntax (bottom-right) or you may get an error message.

  4. (Strongly Recommended) Enable completions inside completions

    By default, Sublime will not offer completions inside completions. In other words, the completions menu is suppressed when you're tabbing through a snippet. This prevents a lot of CSS3 completions from appearing. Add these keys to your User Settings to fix this:

    "auto_complete_commit_on_tab": true,
    "auto_complete_with_fields": true,
  5. (Recommended) Hide CSS completions from Emmet

    If you have Emmet installed, its completions will drown out the carefully researched, standards-based completions offered by this package. You can hide Emmet completions without disabling them by adding this line to your Emmet package settings.

    "show_css_completions": false
  6. (Recommended) Set CSS3 as the default language for .css files

    • Open a .css file.
    • View → Syntax → Open all with current extension as... → CSS3

    setting CSS3 as default

Best Practices

Help Me Out!

If you think something's missing, make sure you're not asking for something on this list of bad CSS properties. If it's not on that list, open an issue and I'll investigate. Definitely check out the CONTRIBUTING guidelines before submitting your PR. It could save you a lot of time. I'll be monitoring the specs as they're updated on this W3C feed, but I still need your help. Let's keep bad code out of the Web!