My personal Sublime Text 3 syntax for Markdown, Liquid, and plaintext.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Markdown Liquid.sublime-settings
Markdown Liquid.sublime-syntax


Markdown Liquid syntax for Sublime Text 3

I use always use Jekyll which uses Liquid for static sites and blogs.

Jekyll uses the Rouge highlighter by default. Not Pygments.

With the additional features of Liquid, Markdown syntax highlighting alone just doesn’t cut it.

Siteleaf have made an excellent Liquid HTML syntax package, but any writing I do is Liquid Markdown.

Here is how you install my “package” via GitHub:

  1. Install Package Control
  2. CTRL+Shift+P/CMD+Shift+P: Add Repository
  3. Enter
  4. CTRL+Shift+P/CMD+Shift+P: Install Package
  5. Select the package to install
  6. Select your new Markdown Liquid syntax


You may have to run Upgrade Package for this, but I honestly have no idea how it works.

If you want to test your own syntax locally, I was able to test mine by saving my .sublime-syntax file to:

~/Library/Application Support/Sublime Text 3/Packages/Liquid/


%APPDATA%\Sublime Text 3\Packages\Liquid\

Remember quotes to cd on UNIX/macOS.

As of now, the default associations are:

- markdown
- md
- mdown
- txt

Currently, the default <pre> syntax is {% highlight lang %} and {% endhighlight %} from Liquid. I have only set up syntax highlighting inside to work with JavaScript, R, Shell, and YAML code. (Rouge’s console highlighter is pretty useless so I haven’t included it.) This is to avoid having a major list of supported programming or markup languages I won’t be using anyway.

You can fork the project to edit the list and just add that repo instead of mine and use that. It’s way easier than demanding I change it in a pull request. The fairly short and simple source code should make it a lot easier for you than starting from scratch; I haven’t bothered to use any complex regex either. I found the official documentation to be beyond awful; it doesn’t even have bloody pagination.

After all, editors setups are very personal things; I just found the experience of making a ST3 syntax to be an absolute pain, so here’s a template you can use to add and edit to your own liking.

I’ve also included a settings file because, for one, I hate not having line wrap. Second, it sets the file associations so you shouldn’ve have to fiddle with syntax settings yourself. Here is what it looks like:

    "extensions": [
    "wrap_width": 78

For more on customizing Sublime Text 3 and your editor and programming experience, check out my style repo with my other configs.

A better Markdown lexer

The default Markdown lexer in Sublime Text 3 has a few issues, especially abbreviation tags. You should download MarkdownEditing through the package manager; it should automatically become your default Markdown lexer, but you may have to pick it as the syntax highlighter and go back to Markdown Liquid again right afterwards.

Your syntax highlighting should look a lot better now.