Open-source project
dempfi/ayu avatar
dempfi/ayu

ayu for Sublime Text: three colour schemes, one settings file

🎨🖌 Modern, bright color theme for Sublime Text

4,429 stars338 forksJupyter NotebookMIT

At a glance

What is it?
ayu ships dark, mirage and light Sublime Text themes that install through Package Control and are activated by two keys in user settings. The last push was on 2026-10-08, and the release before v6.2.0 (2026-09-27) dates from September 2021.
Who is it for?
Adopt ayu if you live in Sublime Text full time and want one palette across the syntax scopes and the editor chrome, with icon artwork that matches it. Leave it alone if you still need Sublime Text 3, since that path stops at v5.1.0, or if you would rather own every line of your own user settings.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 38 days ago.
What is it written in?
Mainly Jupyter Notebook, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • dempfi/ayu4,429 ★ · +13
Star history
Repository2026-09-302026-11-15
dempfi/ayu4.4k4.4k

13 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One palette, three variants, split across six root files

The repository root holds a matched pair for each variant: ayu-dark.sublime-theme next to ayu-dark.sublime-color-scheme, and the same for mirage and light. That pairing is the mechanism to understand before anything else. Sublime Text reads the .sublime-theme file for the shell, the tab strip and the sidebar, and reads the .sublime-color-scheme file for the editor surface and syntax scopes. Set both and the panels agree with the syntax colours.

Three other root files explain how the package behaves inside the editor. Default.sublime-commands is what puts the theme activation entry into the command palette, so a package missing that file cannot be switched by name at all. Preferences.sublime-settings is the settings the package ships, and activation.py handles the palette side. The primary language is listed as Jupyter Notebook, although no notebook appears in the file list: package.json builds with tsx ./src/build.ts, and the root holds Python files such as activation.py and Icons.py.

Package Control is the only scripted install path

No shell command installs this theme. Installation runs through the Sublime Text command palette: open it with cmd or ctrl plus shift and P, type `install package`, press enter, then search for `ayu`. Everything given for this path is a keyboard sequence rather than something to paste into a terminal.

The manual path exists for machines where Package Control is not an option. You download the newest tag from the repository, extract it, rename the directory to ayu, and move that folder into the editor's Packages directory, reachable through Preferences and then Browse packages. The rename matters, because the color_scheme keys point at the package as Packages/ayu/..., and a folder extracted under its archive name will not resolve.

Activation is two keys, and they have to match

The palette command works, and the README offers user settings as the alternative. Preferences, then Settings takes you to the JSON file where the variant is pinned. Three variants are shown with their exact key names:

json
// Light
"theme": "ayu-light.sublime-theme",
"color_scheme": "Packages/ayu/ayu-light.sublime-color-scheme",

// Mirage
"theme": "ayu-mirage.sublime-theme",
"color_scheme": "Packages/ayu/ayu-mirage.sublime-color-scheme",

// Dark
"theme": "ayu-dark.sublime-theme",
"color_scheme": "Packages/ayu/ayu-dark.sublime-color-scheme",

Pick one pair and comment out the rest. If theme names one variant and color_scheme another, the chrome and the editor surface come from different variants.

ui_separator is the switch the screenshots keep returning to

Three settings carry the visible layout changes, and one of them, ui_separator, appears in two of the three screenshot labels:

json
"ui_native_titlebar": true,   // native titlebar on macOS
"ui_separator": false,        // hide separators between panels (shown by default)
"ui_wide_scrollbars": true    // wider scrollbars

ui_separator controls the separators between panels, and they are shown by default. Setting it to false removes them, which is why the light and dark captures are both labelled with that option. ui_native_titlebar affects macOS only and does nothing on Linux or Windows. ui_wide_scrollbars changes scrollbar thickness and nothing else.

Icons need A File Icon, and gaps fall back to it

ayu ships its own icon artwork, the same set used by the VS Code port, but Sublime Text has no native hook for it. The repository makes the dependency visible at the root with a file named .supports-a-file-icon-customization, and the artwork itself sits under icons/. Without the A File Icon package installed, those files are dead weight and your editor shows the editor's own defaults.

With A File Icon present the division of labour is clean: A File Icon decides which icon each extension receives, ayu supplies the artwork. Any file type ayu has no icon for keeps A File Icon's own, so a tree that mixes two icon styles in one project is expected behaviour rather than a broken install.

UI fonts are patched by hand under /User, and the copy is undoable

Font control is not a settings key here. The documented route is to open the command palette, run `Browse packages`, go to /User, create your own ayu-mirage.sublime-theme (or the light or dark name), and put a rule array in it mapping the class names ayu uses to your font face. Classes such as sidebar_label, sidebar_heading, tab_label, label_control, quick_panel_label and quick_panel_path_label are the ones named.

Because your file sits in the user folder and carries exactly the packaged theme's filename, deleting it hands control straight back to the packaged file. That reversibility is the practical part. Nothing documents how to change syntax colours the same way, so a font override is the only customisation of this kind explained, and the mirroring step is manual: type the filename correctly or your rules never load.

One gap between 2021 and 2026, and two repository URLs

The tags show a pause rather than a steady cadence. v6.1.2, titled for Sublime Text 3 compatibility, landed in September 2021; the next, v6.2.0, arrived on 2026-09-27 carrying the palette and file icons, followed by v6.2.1 on 2026-10-08. Anyone still on Sublime Text 3 is pointed at v5.1.0, and Sublime Text 2 at v3.2.2, so the current line is the only one that moved.

Two smaller details deserve attention. The repository metadata inside package.json sends its repository url to github.com/dempfi/ayu, while every download and legacy tag link in the README resolves to the ayu-theme organisation, so automation following the metadata lands on a different path than a person following the documentation. The build also depends on the ayu npm package (^9.1.0) as a dev dependency, with Node 22.18.0 or newer required. The project site is ayutheme.com, and the licence is MIT.

Where a plain built-in scheme is the better buy

The real alternative for Sublime Text is to keep a built-in colour scheme and change nothing, which makes sense if you already have a workflow you like and dislike the ayu chrome. The difference is in approach rather than colour: a built-in scheme sets syntax scopes through the colour scheme file alone, while ayu ships a .sublime-theme beside it so the sidebar, tabs and quick panel come from the same palette. That is a wider surface to restyle, and it is why ayu needs a two key settings block where a plain colour scheme needs none.

Outside Sublime Text, the same palette exists as a VS Code port, so a team standardising one palette across two editors is not tied to this package. The Sublime build carries the ui settings described above.

Editorial conclusion

Adopt ayu if you live in Sublime Text full time and want one palette across the syntax scopes and the editor chrome, with icon artwork that matches it. Leave it alone if you still need Sublime Text 3, since that path stops at v5.1.0, or if you would rather own every line of your own user settings. Check the two keys first: open Preferences, Settings and confirm that theme and color_scheme both name the variant you chose, because a mismatched pair leaves the sidebar in one palette while the editor surface stays in another.

Frequently asked questions

How do I change the theme in Sublime Text?

Open the command palette with cmd or ctrl plus shift and P and type `ayu: Activate theme`. Alternatively, set the theme and color_scheme keys under Preferences, then Settings.

What is the best Sublime Text theme?

ayu is described as a bright colour theme handcrafted for Sublime Text, available as dark, mirage and light. The documentation does not rank it against other themes.

Which ayu version supports Sublime Text 3?

Sublime Text 3 is covered by v5.1.0, and Sublime Text 2 by v3.2.2. Anything newer targets the current editor line.

Why do ayu file icons not show up in Sublime Text?

Sublime Text needs the A File Icon package to display them. That package decides which icon each file gets while ayu supplies the artwork, and file types ayu has no icon for keep A File Icon's own.

How do I change the UI font in the ayu theme?

Run `Browse packages` from the command palette, go to /User, and create your own ayu-mirage.sublime-theme (or the light or dark name) containing font.face rules for the sidebar, tab and quick panel classes the theme uses.

Official sources

  1. dempfi/ayu on GitHub
  2. License: MIT
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/dempfi-ayu.svg)](https://hysenlabs.com/projects/dempfi-ayu)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/dempfi-ayu.svg)](https://hysenlabs.com/projects/dempfi-ayu)

Was this useful?