Stylix

About

Stylix is a theming framework for NixOS, Home Manager, nix-darwin, and Nix-on-Droid that applies color schemes, wallpapers, and fonts to a wide range of applications.

Unlike color scheme utilities such as base16.nix or nix-colors, Stylix goes further by applying themes to supported applications, following the "it just works" philosophy.

Resources

• Documentation
• GitHub Discussions
• Matrix room

Example configurations

GNOME 46

Try a live demo of this dark theme by running:

nix run github:danth/stylix#testbed:gnome:default:dark:image:scheme:cursor

KDE Plasma 5

Since KDE theming is still a work in progress, some manual steps may be required to properly apply its theme.

Installation

NixOS

You can install Stylix into your NixOS configuration using Flakes. This will provide theming for system level programs such as bootloaders, splash screens, and display managers.

{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    stylix.url = "github:danth/stylix";
  };

  outputs =
    { nixpkgs, stylix, ... }:
    {
      nixosConfigurations."«hostname»" = nixpkgs.lib.nixosSystem {
        system = "x86_64-linux";
        modules = [
          stylix.nixosModules.stylix
          ./configuration.nix
        ];
      };
    };
}

Minimal flake.nix for a NixOS configuration.

If you are using a stable release of NixOS, ensure that you use the matching Stylix release. For example:

{
  nixpkgs.url = "github:NixOS/nixpkgs/nixos-24.11";
  stylix.url = "github:danth/stylix/release-24.11";
}

Many applications cannot be configured system wide, so Stylix will also need Home Manager to be able to change their settings within your home directory.

Installing Home Manager as a NixOS module is highly recommended if you don't use it already. This will combine it with your existing configuration, so you don't need to run any extra commands when you rebuild, and the theme you set in NixOS will automatically be used for Home Manager too.

When Stylix is installed to a NixOS configuration, it will automatically set up its Home Manager modules if it detects that Home Manager is available. You can theoretically use it without installing Home Manager, however most features will be unavailable.

nix-darwin

You can install Stylix into your nix-darwin configuration in a similar fashion to NixOS via Flakes.

{
  inputs = {
    darwin = {
      url = "github:LnL7/nix-darwin";
      inputs.nixpkgs.follows = "nixpkgs";
    };
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    stylix.url = "github:danth/stylix";
  };

  outputs =
    {
      darwin,
      stylix,
      ...
    }:
    {
      darwinConfigurations."«hostname»" = darwin.lib.darwinSystem {
        system = "aarch64-darwin";
        modules = [
          stylix.darwinModules.stylix
          ./configuration.nix
        ];
      };
    };
}

Minimal flake.nix for a nix-darwin configuration.

While this won't have an effect on the looks of MacOS, since we don't have the controls to theme it like we do NixOS, it will automatically set up the Home Manager modules for you.

Nix-on-Droid

You can install Stylix into your Nix-on-Droid configuration in a similar fashion to NixOS via Flakes.

{
  inputs = {
    nix-on-droid = {
      url = "github:nix-community/nix-on-droid/release-24.05";
      inputs.nixpkgs.follows = "nixpkgs";
    };
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-24.05";
    stylix.url = "github:danth/stylix";
  };

  outputs =
    {
      nix-on-droid,
      nixpkgs,
      stylix,
      ...
    }:
    {
      nixOnDroidConfigurations.default = nix-on-droid.lib.nixOnDroidConfiguration {
        pkgs = nixpkgs.legacyPackages."aarch64-linux";
        modules = [
          stylix.nixOnDroidModules.stylix
          ./nix-on-droid.nix
        ];
      };
    };
}

Minimal flake.nix for a Nix-on-Droid configuration.

This will apply your configured color scheme and monospace font to the nix-on-droid terminal. If Home Manager integration for Nix-on-Droid is used, Stylix will automatically set up the Home Manager modules for you.

Home Manager

If you would prefer to use the standalone version of Home Manager, you can install Stylix directly into your Home Manager configuration instead. This could be useful if you are on another operating system, or a machine which is managed by someone else.

{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    home-manager.url = "github:nix-community/home-manager";
    stylix.url = "github:danth/stylix";
  };

  outputs =
    {
      nixpkgs,
      home-manager,
      stylix,
      ...
    }:
    {
      homeConfigurations."«username»" = home-manager.lib.homeManagerConfiguration {
        pkgs = nixpkgs.legacyPackages.x86_64-linux;
        modules = [
          stylix.homeManagerModules.stylix
          ./home.nix
        ];
      };
    };
}

Minimal flake.nix for a Home Manager configuration.

If you are using a stable release of Home Manager, ensure that you use the matching Stylix release. For example:

{
  nixpkgs.url = "github:NixOS/nixpkgs/nixos-24.11";
  home-manager.url = "github:nix-community/home-manager/release-24.11";
  stylix.url = "github:danth/stylix/release-24.11";
}

If you choose to use both NixOS and Home Manager but configure them separately, you will need to copy your theme into both of your configurations, as keeping them separate means they cannot follow each other automatically.

Without flakes

If you haven't enabled flakes yet or don't want to use this feature, default.nix re-exports all the flake outputs, without requiring flakes to be enabled. This means that once you have a copy of this repo, using either a local checkout, niv, or any other method, you can import it to get the NixOS module as the nixosModules.stylix attribute and the Home Manager module as the homeManagerModules.stylix attribute.

let
  stylix = pkgs.fetchFromGitHub {
    owner = "danth";
    repo = "stylix";
    rev = "...";
    sha256 = "...";
  };
in
{
  imports = [ (import stylix).homeManagerModules.stylix ];

  stylix = {
    enable = true;
    image = ./wallpaper.jpg;
  };
}

Example usage of the Home Manager module without flakes.

Configuration

Enable

Stylix must be enabled before it will apply any changes to your system:

{
  stylix.enable = true;
}

Color scheme

Handmade schemes

To set a Tinted Theming color scheme, declare:

{
  stylix.base16Scheme = "${pkgs.base16-schemes}/share/themes/gruvbox-dark-hard.yaml";
}

This option also accepts other files and formats supported by mkSchemeAttrs.

Overriding

For convenience, it is possible to override parts of stylix.base16Scheme using stylix.override. Anything that base16.nix accepts as override is valid.

When using both the Home Manager and NixOS modules, both the system overrides and the user-provided one are used in the user configuration if stylix.base16Scheme is not changed in the user config. If that is the case, only the user override is used.

Extending

When passing colors to unsupported targets or creating custom modules, it is possible to access values from the configured color scheme through config.lib.stylix.colors. An overview of the available values is shown below.

config.lib.stylix.colors = {
  base08 = "ff0000";
  base08-hex-r = "ff";
  base08-dec-r = "0.996094";
  # ...
  red = "ff0000";
  # ...
  withHashtag = {
    base08 = "#ff0000";
    # ...
  };
};

This attrset is generated by mkSchemeAttrs from base16.nix. Refer to the documentation for more info.

For more complex configurations you may find it simpler to use mustache templates to generate output files. See base16.nix documentation for usage examples.

Wallpaper

To set a wallpaper, provide a path or an arbitrary derivation:

• {
    stylix.image = ./wallpaper.png;
  }
  

• {
    stylix.image = pkgs.fetchurl {
      url = "https://www.pixelstalk.net/wp-content/uploads/2016/05/Epic-Anime-Awesome-Wallpapers.jpg";
      sha256 = "enQo3wqhgf0FEPHj2coOCvo7DuZv+x5rL/WIo4qPI50=";
    };
  }
  

If stylix.base16Scheme is undeclared, Stylix generates a color scheme based on the wallpaper using a genetic algorithm. Note that more colorful images tend to yield better results. The algorithm's polarity can be schewed towards a dark or light theme with:

• {
    stylix.polarity = "dark";
  }
  

• {
    stylix.polarity = "light";
  }
  

The generated color scheme can be viewed at /etc/stylix/palette.html on NixOS, or at ~/.config/stylix/palette.html on Home Manager.

Fonts

The default combination of fonts is:

{
  stylix.fonts = {
    serif = {
      package = pkgs.dejavu_fonts;
      name = "DejaVu Serif";
    };

    sansSerif = {
      package = pkgs.dejavu_fonts;
      name = "DejaVu Sans";
    };

    monospace = {
      package = pkgs.dejavu_fonts;
      name = "DejaVu Sans Mono";
    };

    emoji = {
      package = pkgs.noto-fonts-emoji;
      name = "Noto Color Emoji";
    };
  };
}

These can be changed as you like.

To make things look more uniform, you could replace the serif font with the sans-serif font:

{
  stylix.fonts.serif = config.stylix.fonts.sansSerif;
}

Or even choose monospace for everything:

{
  stylix.fonts = {
    serif = config.stylix.fonts.monospace;
    sansSerif = config.stylix.fonts.monospace;
    emoji = config.stylix.fonts.monospace;
  };
}

Home Manager inheritance

By default, if Home Manager is used as part of NixOS, then Stylix will be automatically installed for all users, and the NixOS theme will become their default settings.

This is convenient for single-user systems, since you can configure everything once at the system level and it will automatically carry over. For multi-user systems, you can override the settings within Home Manager to select a different theme for each user.

You may prefer to disable inheritance entirely, and set up the Home Manager version of Stylix yourself if required. Refer to the options stylix.homeManagerIntegration.autoImport and stylix.homeManagerIntegration.followSystem to customize this.

Standalone Nixvim

When using a NixOS or home-manager installation of Nixvim, you can use Stylix as normal. However, when using Nixvim's "standalone" configuration mode, you will need to pass Stylix's generated config to Nixvim yourself.

The generated config can be accessed as config.lib.stylix.nixvim.config. You can use this as a module in your standalone Nixvim Configuration or an extension of it.

For example:

{
  inputs,
  config,
  pkgs,
  ...
}:
let
  inherit (pkgs.stdenv.hostPlatform) system;
  nixvim-package = inputs.nixvim-config.packages.${system}.default;
  extended-nixvim = nixvim-package.extend config.lib.stylix.nixvim.config;
in
{
  environment.systemPackages = [ extended-nixvim ];
}

Turning targets on and off

A target is anything which can have colors, fonts or a wallpaper applied to it.

You can discover the available targets and their options by browsing through the module reference at the end of this book. Most targets will be found under a module of the same name, but occasionally a module will serve multiple similar targets. For example, the Firefox module also provides options for other browsers which are based on Firefox.

For each target, there is an option like stylix.targets.«target».enable which you can use to turn its styling on or off. By default, it's turned on automatically whenever the target is installed. You can globally set stylix.autoEnable = false to opt out of this behaviour, in which case you'll need to manually enable each target you want to be themed.

Targets are different between Home Manager and NixOS, and sometimes available in both cases. If both are available, it is always correct to enable both.

Tips and tricks

Adjusting the brightness and contrast of a background image

If you want to use a background image for your desktop but find it too bright or distracting, you can use the imagemagick package to dim the image, or adjust its brightness and contrast to suit your preference.

Here's an example Nix expression that takes an input image, applies a brightness/contrast adjustment to it, and saves the result as a new image file:

{ pkgs, ... }:
let
  inputImage = ./path/to/image.jpg;
  brightness = -30;
  contrast = 0;
  fillColor = "black";
in
{
  stylix.image = pkgs.runCommand "dimmed-background.png" { } ''
    ${pkgs.imagemagick}/bin/convert "${inputImage}" -brightness-contrast ${brightness},${contrast} -fill ${fillColor} $out
  '';
}

Dynamic wallpaper generation based on selected theme

With imagemagick, you can also dynamically generate wallpapers based on the selected theme. Similarly, you can use a template image and repaint it for the current theme.

{ pkgs, ... }:
let
  theme = "${pkgs.base16-schemes}/share/themes/catppuccin-latte.yaml";
  wallpaper = pkgs.runCommand "image.png" { } ''
    COLOR=$(${pkgs.yq}/bin/yq -r .palette.base00 ${theme})
    ${pkgs.imagemagick}/bin/magick -size 1920x1080 xc:$COLOR $out
  '';
in
{
  stylix = {
    image = wallpaper;
    base16Scheme = theme;
  };
}

Which is neatly implemented as a single function in lib.stylix.pixel:

{ pkgs, config, ... }:
{
  stylix = {
    image = config.lib.stylix.pixel "base0A";
    base16Scheme = "${pkgs.base16-schemes}/share/themes/catppuccin-latte.yaml";
  };
}

Completely disabling some stylix targets

Nixpkgs module system sometimes works in non-intuitive ways, e.g. parts of the configuration guarded by lib.mkIf are still being descended into. This means that every loaded (and not enabled) module must be compatible with others - in the sense that every option that is mentioned in the disabled parts of the configuration still needs to be defined somewhere.

Sometimes that can be a problem, when your particular configuration diverges enough from what stylix expects. In that case you can try stubbing all the missing options in your configuration.

Or in a much clearer fashion you can just disable offending stylix targets by adding the following disableModules line next to importing stylix itself:

imports = [ flake.inputs.stylix.nixosModules.stylix ];
disabledModules = [ "${flake.inputs.stylix}/modules/<some-module>/nixos.nix" ];

Extending CSS options

When trying to extend an attrset option, the order does not matter because a declaration can only exist once. This is not the case for an option with the type of lines (most commonly style options in Home Manager). For these options, the order does matter and Nix cannot guarantee that there aren't conflicting definitions. Nix will still merge these options, but it will not warn you if there are conflicting declaration. In order to get around this, you can make sure Nix puts your CSS at the end - and thus prioritizes it - by using lib.mkAfter:

{ lib, ... }:
{
  programs.waybar = {
    enable = true;
    style = lib.mkAfter ''
      #workspaces button {
        background: @base01;
      }
    '';
  };
}

Commit convention

To keep things consistent, commit messages should follow a format similar to Nixpkgs:

«scope»: «summary»

«motivation for change»

Where the scope is one of:

The scope is meant to indicate which area of the code was changed. Specifying the type of change, such as feat or fix, is not necessary. Dependency updates should use whichever scope they are related to.

The summary should start with a lowercase letter, and should not end with punctuation.

Most commits to master will also include a pull request number in brackets after the summary. GitHub adds this automatically when creating a squash merge.

Development environment

Developer shell

To enter the developer shell, run:

nix develop

To automatically enter the developer shell upon entering the project directory with direnv, run:

direnv allow

pre-commit

The default developer shell leverages pre-commit hooks to simplify the process of reaching minimum quality standards for casual contributors. This means applying code formatters, and scanning for things like unused variables which should be removed.

By default, once you have entered the developer shell, pre-commit runs automatically just before you create a commit. This will only look at the files which are about to be committed.

You can also run it manually against all files:

pre-commit run --all-files

This is useful if a commit was created outside of the developer shell, and you need to apply pre-commit to your previous changes.

Note that there is also a flake output, .#checks.«system».git-hooks, which always runs against all files but does not have access to apply changes. This is used in GitHub Actions to ensure that pre-commit has been applied.

stylix-check

When a pull request is opened, we use GitHub Actions to build everything under .#checks. This includes the previously mentioned .#checks.«system».git-hooks, and every testbed.

You might sometimes find it useful to run these same checks locally. The built in nix flake check command does this, however it can be quite slow compared to the script we use on GitHub Actions.

To use the same script that we use, you can run this command within the developer shell:

stylix-check

This is based on nix-fast-build.

Adding modules

Development setup

Currently the easiest way to test Stylix is to use the new code in your actual configuration.

You might find it useful to change the flake reference in your configuration from github:danth/stylix to git+file:/home/user/path/to/stylix so that you don't need to push your changes to GitHub during testing.

Then, remember to run nix flake lock --update-input stylix to refresh the flake each time you make an edit.

Nix only reads files which are tracked by Git, so you also need to git add «file» after creating a new file.

Module naming

Modules should be named like modules/«name»/«platform».nix. For example, modules/avizo/hm.nix is a Home Manager module which themes Avizo.

The following platforms are supported:

• NixOS (nixos)
• Home Manager (hm)
• Nix-Darwin (darwin)
• Nix-on-Droid (droid)

Correctly named modules will be imported automatically.

Other files needed by the module can also be stored within the modules/«name» folder, using any name which is not on the list above.

Module template

All modules should have an enable option created using mkEnableTarget. This is similar to mkEnableOption from the standard library, however it integrates with stylix.enable and stylix.autoEnable and generates more specific documentation.

A general format for modules is shown below.

{ config, lib, ... }:
{
  options.stylix.targets.«name».enable =
    config.lib.stylix.mkEnableTarget "«human readable name»" true;

  config =
    lib.mkIf (config.stylix.enable && config.stylix.targets.«name».enable)
      {
        programs.«name».backgroundColor = config.lib.stylix.colors.base00;
      };
}

The human readable name will be inserted into the following sentence:

Whether to enable theming for «human readable name».

If your module will touch options outside of programs.«name» or services.«name», it should include an additional condition in mkIf to prevent any effects when the target is not installed.

The boolean value after mkEnableTarget should be changed to false if one of the following applies:

• The module requires further manual setup to work correctly.
• There is no reliable way to detect whether the target is installed, and enabling it unconditionally would cause problems.

Overlays

If your module is provided as an overlay it uses a special format, where config is transparently passed to the platform (e.g. nixos) and overlay is a function taking two arguments and returning an attrset:

{
  lib,
  config,
  ...
}:
{
  options.stylix.targets.«name».enable =
    config.lib.stylix.mkEnableTarget "«human readable name»" true;

  overlay =
    final: prev:
    lib.optionalAttrs
      (config.stylix.enable && config.stylix.targets.«name».enable)
      {
        «name» = prev.«name».overrideAttrs (oldAttrs: {

        });
      };
}

How to apply colors

Refer to the style guide to see how colors are named, and where to use each one.

The colors are exported under config.lib.stylix.colors, which originates from mkSchemeAttrs.

You can use the values directly:

{
  environment.variables.MY_APPLICATION_COLOR = config.lib.stylix.colors.base05;
}

Or you can create a Mustache template and use it as a function. This returns a derivation which builds the template.

{
  environment.variables.MY_APPLICATION_CONFIG_FILE =
    let
      configFile = config.lib.stylix.colors {
        template = ./config.toml.mustache;
        extension = ".toml";
      };
    in
    "${configFile}";
}

Setting options through an existing NixOS or Home Manager module is preferable to generating whole files, since users will have the option of overriding things individually.

Also note that reading generated files with builtins.readFile can be very slow and should be avoided.

How to apply other things

For everything else, like fonts and wallpapers, you can just take option values directly from config. See the reference pages for a list of options.

Metadata

Metadata is stored in /modules/«module»/meta.nix. The following attributes are available under meta:

• maintainers: required list of maintainers. See Maintainers section.
• name: required human-readable string name.

Maintainers

New modules must have at least one maintainer.

If you are not already listed in the Nixpkgs /maintainers/maintainer-list.nix maintainer list, add yourself to /stylix/maintainers.nix.

Add yourself as a maintainer in one of the following ways, depending on the number of maintainers:

• { lib, ... }:
  {
    maintainers = [ lib.maintainers.danth ];
  }
  

• { lib, ... }:
  {
    maintainers = with lib.maintainers; [
      danth
      naho
    ];
  }
  

The main responsibility of module maintainers is to update and fix their modules.

Documentation

Documentation for options is automatically generated. To improve the quality of this documentation, ensure that any custom options created using mkOption are given an appropriate type and a detailed description. This may use Markdown syntax for formatting and links.

For modules needing more general documentation, create modules/«module»/README.md:

# Module Name

Consider describing which applications are themed by this module (if it's not
obvious from the module name), how the applications need to be installed for the
module to work correctly, which theming items are supported (colors, fonts,
wallpaper, ...), and any caveats the user should be aware of.

This will be inserted before the automatically generated list of options.

Testbeds

Adding testbeds for new modules is encouraged, but not mandatory.

Common Mistakes

home.activation Scripts

Any script run by home.activation must be preceded by run if the script is to produce any permanent changes. Without this run wrapper, the script is run in dry-run mode.

Testbeds

Stylix provides a suite of virtual machines which can be used to test and preview themes without installing the target to your live system.

These can be particularly helpful for:

• Working on targets before the login screen, since you can avoid closing your editor to see the result.
• Developing for a different desktop environment than the one you normally use.
• Reducing the risk of breaking your system while reviewing pull requests.

Testbeds are also built by GitHub Actions for every pull request. This is less beneficial compared to running them yourself, since it cannot visually check the theme, however it can catch build failures which may have been missed otherwise.

Creation

Testbeds are defined at /modules/«module»/testbeds/«testbed».nix and are are automatically loaded as a NixOS module with options such as stylix.image already defined. The testbed should include any options necessary to install the target and any supporting software - for example, a window manager.

If the target can only be used through Home Manager, you can write a Home Manager module within the NixOS module using the following format:

{
  home-manager.sharedModules = [
    {
      # Write Home Manager options here
    }
  ];
}

Using home-manager.sharedModules is preferred over home-manager.users.guest since it allows us to easily change the username or add additional users in the future.

Once the module is complete, use git add to track the file, then the new packages will be available to use.

Usage

You can list the available testbeds by running this command from anywhere within the repository:

user@host:~$ nix flake show
github:danth/stylix
└───packages
    └───x86_64-linux
        ├───docs: package 'stylix-book'
        ├───palette-generator: package 'palette-generator'
        ├───"testbed:gnome:default:dark:image:scheme:cursor": package 'testbed-gnome-default-dark-image-scheme-cursor'
        ├───"testbed:gnome:default:dark:image:scheme:cursorless": package 'testbed-gnome-default-dark-image-scheme-cursorless'
        ├───"testbed:gnome:default:dark:image:schemeless:cursorless": package 'testbed-gnome-default-dark-image-schemeless-cursorless'
        ├───"testbed:gnome:default:dark:imageless:scheme:cursorless": package 'testbed-gnome-default-dark-imageless-scheme-cursorless'
        ├───"testbed:gnome:default:light:image:scheme:cursorless": package 'testbed-gnome-default-light-image-scheme-cursorless'
        ├───"testbed:kde:default:dark:image:scheme:cursor": package 'testbed-kde-default-dark-image-scheme-cursor'
        ├───"testbed:kde:default:dark:image:scheme:cursorless": package 'testbed-kde-default-dark-image-scheme-cursorless'
        ├───"testbed:kde:default:dark:image:schemeless:cursorless": package 'testbed-kde-default-dark-image-schemeless-cursorless'
        ├───"testbed:kde:default:dark:imageless:scheme:cursorless": package 'testbed-kde-default-dark-imageless-scheme-cursorless'
        └───"testbed:kde:default:light:image:scheme:cursorless": package 'testbed-kde-default-light-image-scheme-cursorless'

(This has been edited down to only the relevant parts.)

To start a testbed, each of which is named in the format testbed:«module»:«testbed»:«polarity», run the following command:

user@host:~$ nix run .#testbed:«module»:«testbed»:«polarity»:«image»:«scheme»:«cursor»

Any package with a name not fitting the given format is not a testbed, and may behave differently with this command, or not work at all.

Once the virtual machine starts, a window should open, similar to the screenshot below. The contents of the virtual machine will vary depending on the target you selected earlier.

If the testbed includes a login screen, the guest user should log in automatically when selected. Depending on the software used, you may still be presented with a password prompt - in which case you can leave it blank and proceed by pressing enter.

Style guide

The base16 style guide is generally targeted towards text editors. Stylix aims to support a variety of other applications, and as such it requires its own guide to keep colours consistent. Towards this goal we will define several common types of applications and how to style each of them using the available colours.

Please keep in mind that this is a general guide; there will be several applications that don't fit into any of the groups below. In this case it is up to the committer to make sure said application fits in stylistically with the rest of the themed applications.

It is also important to note that this is a growing theming guide and when theming an application and you find the guide to be lacking in any way in terms of direction, you are encouraged to open an issue regarding what you would like to see added to the style guide.

Terms

Alternate

An alternate color should be used when something needs to look separate while not being drastically different. The smaller or less common element should use the alternate color.

For example, each section in this settings menu uses the alternate background color to separate it from the rest of the window, which is using the default background.

On/Off

This is for toggles or simple status indicators which have an obvious on and off state.

In the screenshot above the Wired and Night Light buttons are on, Power Mode is off.

Lists and selections

A list of items to select between, such as tabs in a web browser. The selection is the currently active item, or there could be multiple selected depending on the use case.

General colors

• Default background: base00
• Alternate background: base01
• Selection background: base02
• Default text: base05
• Alternate text: base04
• Warning: base0A
• Urgent: base09
• Error: base08

Window Managers

Window Managers arrange windows and provide decorations like title bars and borders. Examples include Sway and i3.

This does not include applications bundled with the desktop environment such as file managers, which would fall into the general category. Desktop helpers such as taskbars and menus are not technically part of the window manager, although they're often configured in the same place.

An urgent window is one which is grabbing for attention - Windows shows this by a flashing orange taskbar icon.

• Unfocused window border: base03
• Focused window border: base0D
• Unfocused window border in group: base03
• Focused window border in group: base0D
• Urgent window border: base08
• Window title text: base05

Notifications and Popups

Notifications and popups are any application overlay intended to be displayed over other applications. Examples include the mako notification daemon and avizo.

• Window border: base0D
• Low urgency background color: base06
• Low urgency text color: base0A
• High urgency background color: base0F
• High urgency text color: base08
• Incomplete part of progress bar: base01
• Complete part of progress bar: base02

Desktop Helpers

Applications that fall under this group are applications that complement the window management facilities of whatever window manager the user is using. Examples of this include waybar and polybar, as well as the similar programs that are part of KDE and GNOME.

Light text color widgets

Refer to general colors above.

Dark text color widgets

These widgets use a different text color than usual to ensure it's still readable when the background is more vibrant.

• Default text color: base00
• Alternate text color: base01
• Item on background color: base0E
• Item off background color: base0D
• Alternate item on background color: base09
• Alternate item off background color: base02
• List unselected background: base0D
• List selected background: base03

Images

For creating modified versions of logos, icons, etc; where we would rather the colors be similar to the original.

Note that the colors provided by the scheme won't necessarily match the names given below, although most handmade schemes do.

• Background color: base00
• Alternate background color: base01
• Main color: base05
• Alternate main color: base04
• Red: base08
• Orange: base09
• Yellow: base0A
• Green: base0B
• Cyan: base0C
• Blue: base0D
• Purple: base0E
• Brown: base0F

Example of a modified systemd logo. The square brackets are using the main color, which is usually be white or black depending on the polarity of the scheme.

Text Editors/Viewers

Text editors are any application that can view or edit source code. Examples include vim, helix, and bat.

For these please refer to the official base16 style guide.

Alacritty

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.alacritty.enable

Whether to enable theming for Alacritty.

false

NixOS options

None provided.

Avizo

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.avizo.enable

Whether to enable theming for Avizo.

false

NixOS options

None provided.

bat

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.bat.enable

Whether to enable theming for Bat.

false

NixOS options

None provided.

bemenu

Module information

This module is maintained by Nathaniel Barragan.

Home Manager options

stylix.targets.bemenu.alternate

Whether to use alternating colours.

false

stylix.targets.bemenu.enable

Whether to enable theming for bemenu.

false

stylix.targets.bemenu.fontSize

Font size used for bemenu.

10

NixOS options

None provided.

bspwm

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.bspwm.enable

Whether to enable theming for bspwm.

false

NixOS options

None provided.

btop

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.btop.enable

Whether to enable theming for btop.

false

NixOS options

None provided.

Cava

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.cava.enable

Whether to enable theming for CAVA.

false

stylix.targets.cava.rainbow.enable

Whether to enable theming for rainbow gradient theming.

false

true

NixOS options

None provided.

Cavalier

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.cavalier.enable

Whether to enable theming for Cavalier.

false

NixOS options

None provided.

Chromium

Module information

This module is maintained by Daniel Thwaites.

Home Manager options

None provided.

NixOS options

stylix.targets.chromium.enable

Whether to enable theming for Chromium, Google Chrome and Brave.

false

kernel console

Module information

This module has no dedicated maintainers.

Home Manager options

None provided.

NixOS options

stylix.targets.console.enable

Whether to enable theming for the Linux kernel console.

false

Discord

This module provides a collection of targets related to Discord. The same theme is used regardless of the method of installation.

Vencord, Vesktop

These targets use the options for Vencord and Vesktop which are built in to Home Manager.

Nixcord

This target leverages the modules provided the Nixcord flake.

Module information

This module is maintained by Erin Pletches.

Home Manager options

stylix.targets.nixcord.enable

Whether to enable theming for Nixcord.

false

stylix.targets.nixcord.extraCss

Extra CSS to added to Nixcord's theme

""

stylix.targets.vencord.enable

Whether to enable theming for Vencord.

false

stylix.targets.vencord.extraCss

Extra CSS to added to Vencord's theme

""

stylix.targets.vesktop.enable

Whether to enable theming for Vesktop.

false

stylix.targets.vesktop.extraCss

Extra CSS to added to Vesktop's theme

""

NixOS options

None provided.

Dunst

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.dunst.enable

Whether to enable theming for Dunst.

false

NixOS options

None provided.

Emacs

Module information

This module is maintained by pancho horrillo.

Home Manager options

stylix.targets.emacs.enable

Whether to enable theming for Emacs.

false

NixOS options

None provided.

Eye of GNOME

Module information

This module is maintained by Daniel Thwaites.

Home Manager options

stylix.targets.eog.enable

Whether to enable theming for Eye of GNOME Image Viewer.

false

NixOS options

None provided.

Fcitx 5

Module information

This module is maintained by Louis Dalibard.

Home Manager options

stylix.targets.fcitx5.enable

Whether to enable theming for fcitx5.

false

NixOS options

None provided.

feh

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.feh.enable

Whether to enable theming for the desktop background using Feh.

false

true

NixOS options

stylix.targets.feh.enable

Whether to enable theming for the desktop background using Feh.

false

true

Firefox and its derivatives

This module supports Firefox, in addition to Floorp and LibreWolf, which are Firefox derivatives.

The same implementation is shared between all of these browsers, but they don't share option values.

{
  programs.firefox = {
    enable = true;

    profiles = {
      my-profile = {
        # bookmarks, extensions, search engines...
      };
      my-friends-profile = {
        # bookmarks, extensions, search engines...
      };
    };
  };

  stylix.targets.firefox.profileNames = [ "my-profile" "my-friends-profile" ];
}

Module information

This module is maintained by Erin Pletches and Daniel Thwaites.

Home Manager options

stylix.targets.firefox.colorTheme.enable

Whether to enable Firefox Color on Firefox.

false

true

stylix.targets.firefox.enable

Whether to enable theming for Firefox.

false

stylix.targets.firefox.firefoxGnomeTheme.enable

Whether to enable Firefox GNOME theme on Firefox.

false

true

stylix.targets.firefox.profileNames

The Firefox profile names to apply styling on.

[ ]

stylix.targets.floorp.colorTheme.enable

Whether to enable Firefox Color on Floorp.

false

true

stylix.targets.floorp.enable

Whether to enable theming for Floorp.

false

stylix.targets.floorp.firefoxGnomeTheme.enable

Whether to enable Firefox GNOME theme on Floorp.

false

true

stylix.targets.floorp.profileNames

The Floorp profile names to apply styling on.

[ ]

stylix.targets.librewolf.colorTheme.enable

Whether to enable Firefox Color on LibreWolf.

false

true

stylix.targets.librewolf.enable

Whether to enable theming for LibreWolf.

false

stylix.targets.librewolf.firefoxGnomeTheme.enable

Whether to enable Firefox GNOME theme on LibreWolf.

false

true

stylix.targets.librewolf.profileNames

The LibreWolf profile names to apply styling on.

[ ]

NixOS options

None provided.

fish

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.fish.enable

Whether to enable theming for Fish.

false

NixOS options

stylix.targets.fish.enable

Whether to enable theming for Fish.

false

Fnott

Module information

This module is maintained by awwpotato.

Home Manager options

stylix.targets.fnott.enable

Whether to enable theming for Fnott.

false

NixOS options

None provided.

foot

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.foot.enable

Whether to enable theming for Foot.

false

NixOS options

None provided.

Forge

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.forge.enable

Whether to enable theming for Forge.

false

NixOS options

None provided.

Fuzzel

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.fuzzel.enable

Whether to enable theming for Fuzzel.

false

NixOS options

None provided.

fzf

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.fzf.enable

Whether to enable theming for Fzf.

false

NixOS options

None provided.

gedit

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.gedit.enable

Whether to enable theming for GEdit.

false

NixOS options

None provided.

Ghostty

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.ghostty.enable

Whether to enable theming for Ghostty.

false

NixOS options

None provided.

GitUI

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.gitui.enable

Whether to enable theming for GitUI.

false

NixOS options

None provided.

Glance

Module information

This module is maintained by Louis Thevenet.

Home Manager options

stylix.targets.glance.enable

Whether to enable theming for Glance.

false

NixOS options

None provided.

GNOME

Module information

This module is maintained by Daniel Thwaites.

Home Manager options

stylix.targets.gnome.enable

Whether to enable theming for GNOME.

false

stylix.targets.gnome.useWallpaper

Whether to set the wallpaper for GNOME.

true

NixOS options

stylix.targets.gnome.enable

Whether to enable theming for GNOME and GDM.

false

GRUB

Module information

This module has no dedicated maintainers.

Home Manager options

None provided.

NixOS options

stylix.targets.grub.enable

Whether to enable theming for GRUB.

false

stylix.targets.grub.useWallpaper

Whether to set the wallpaper for GRUB.

false

true

GTK

Module information

This module is maintained by Daniel Thwaites.

Home Manager options

stylix.targets.gtk.enable

Whether to enable theming for all GTK3, GTK4 and Libadwaita apps.

false

stylix.targets.gtk.extraCss

Extra code added to gtk-3.0/gtk.css and gtk-4.0/gtk.css.

""

''
  // Remove rounded corners
  window.background { border-radius: 0; }
''

stylix.targets.gtk.flatpakSupport.enable

Whether to enable theming for support for theming Flatpak apps.

false

NixOS options

stylix.targets.gtk.enable

Whether to enable theming for all GTK3, GTK4 and Libadwaita apps.

false

Halloy

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.halloy.enable

Whether to enable theming for Halloy.

false

NixOS options

None provided.

Helix

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.helix.enable

Whether to enable theming for Helix.

false

NixOS options

None provided.

Hyprland

Module information

This module is maintained by Noah Pierre Biewesch and Zie Sturges.

Home Manager options

stylix.targets.hyprland.enable

Whether to enable theming for Hyprland.

false

stylix.targets.hyprland.hyprpaper.enable

Whether to enable theming for Hyprpaper.

false

true

NixOS options

None provided.

hyprlock

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.hyprlock.enable

Whether to enable theming for Hyprlock.

false

stylix.targets.hyprlock.useWallpaper

Whether to set the wallpaper for Hyprlock.

true

NixOS options

None provided.

hyprpaper

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.hyprpaper.enable

Whether to enable theming for Hyprpaper.

false

true

NixOS options

None provided.

i3

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.i3.enable

Whether to enable theming for i3.

false

NixOS options

None provided.

K9s

Module information

This module is maintained by Chet Luther.

Home Manager options

stylix.targets.k9s.enable

Whether to enable theming for k9s.

false

NixOS options

None provided.

KDE

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.kde.decorations

The library for the window decorations theme.

Decorations other than default org.kde.breeze may not be compatible with stylix.

To list all available decorations, see the library key in the org.kde.kdecoration2 section of $HOME/.config/kwinrc after imperatively applying the window decoration via the System Settings app.

"org.kde.breeze"

stylix.targets.kde.enable

Whether to enable theming for KDE.

false

stylix.targets.kde.useWallpaper

Whether to set the wallpaper for KDE.

true

NixOS options

None provided.

kitty

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.kitty.enable

Whether to enable theming for Kitty.

false

stylix.targets.kitty.variant256Colors

Whether to use the 256-color variant rather than the default combination of colors.

false

NixOS options

None provided.

Kmscon

Module information

This module has no dedicated maintainers.

Home Manager options

None provided.

NixOS options

stylix.targets.kmscon.enable

Whether to enable theming for the kmscon virtual console.

false

Kubecolor

Module information

This module is maintained by Igor Rzegocki.

Home Manager options

stylix.targets.kubecolor.enable

Whether to enable theming for kubecolor.

false

NixOS options

None provided.

Lazygit

Module information

This module is maintained by Mateus Auler and Noah Pierre Biewesch.

Home Manager options

stylix.targets.lazygit.enable

Whether to enable theming for lazygit.

false

NixOS options

None provided.

LightDM

Module information

This module has no dedicated maintainers.

Home Manager options

None provided.

NixOS options

stylix.targets.lightdm.enable

Whether to enable theming for LightDM.

false

stylix.targets.lightdm.useWallpaper

Whether to set the wallpaper for LightDM.

true

mako

Module information

This module is maintained by Mateus Auler.

Home Manager options

stylix.targets.mako.enable

Whether to enable theming for Mako.

false

NixOS options

None provided.

MangoHud

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.mangohud.enable

Whether to enable theming for mangohud.

false

NixOS options

None provided.

micro

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.micro.enable

Whether to enable theming for micro.

false

NixOS options

None provided.

mpv

Module information

This module is maintained by awwpotato and Noah Pierre Biewesch.

Home Manager options

stylix.targets.mpv.enable

Whether to enable theming for mpv.

false

NixOS options

None provided.

ncspot

Module information

This module is maintained by awwpotato.

Home Manager options

stylix.targets.ncspot.enable

Whether to enable theming for Ncspot.

false

NixOS options

None provided.

Neovim

This module themes Neovim using the standard Home Manager options.

Related modules

• Vim: themes Vim using the standard Home Manager options.
• Nixvim: themes Neovim using the options provided by Nixvim.
• nvf: themes Neovim using the options provided by nvf.

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.neovim.enable

Whether to enable theming for Neovim.

false

stylix.targets.neovim.plugin

Plugin used for the colorscheme

"mini.base16"

stylix.targets.neovim.transparentBackground.main

Whether to enable background transparency for the main Neovim window.

false

true

stylix.targets.neovim.transparentBackground.signColumn

Whether to enable background transparency for the Neovim sign column.

false

true

NixOS options

None provided.

NixVim

This module themes Neovim using the options provided by NixVim.

Related modules

• Vim: themes Vim using the standard Home Manager options.
• Neovim: themes Neovim using the standard Home Manager options.
• nvf: themes Neovim using the options provided by nvf.

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.nixvim.enable

Whether to enable theming for nixvim.

false

stylix.targets.nixvim.plugin

Plugin used for the colorscheme

"mini.base16"

stylix.targets.nixvim.transparentBackground.main

Whether to enable background transparency for the main NeoVim window.

false

true

stylix.targets.nixvim.transparentBackground.signColumn

Whether to enable background transparency for the NeoVim sign column.

false

true

NixOS options

stylix.targets.nixvim.enable

Whether to enable theming for nixvim.

false

stylix.targets.nixvim.plugin

Plugin used for the colorscheme

"mini.base16"

stylix.targets.nixvim.transparentBackground.main

Whether to enable background transparency for the main NeoVim window.

false

true

stylix.targets.nixvim.transparentBackground.signColumn

Whether to enable background transparency for the NeoVim sign column.

false

true

Nushell

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.nushell.enable

Whether to enable theming for Nushell.

false

NixOS options

None provided.

nvf

This module themes Neovim using the options provided by nvf.

Related modules

• Vim: themes Vim using the standard Home Manager options.
• Neovim: themes Neovim using the standard Home Manager options.
• Nixvim: themes Neovim using the options provided by Nixvim.

Module information

This module is maintained by Adam M. Szalkowski.

Home Manager options

stylix.targets.nvf.enable

Whether to enable theming for nvf.

false

stylix.targets.nvf.plugin

Plugin used for the colorscheme

"base16"

stylix.targets.nvf.transparentBackground

Whether to enable background transparency for the main Neovim window.

false

true

NixOS options

stylix.targets.nvf.enable

Whether to enable theming for nvf.

false

stylix.targets.nvf.plugin

Plugin used for the colorscheme

"base16"

stylix.targets.nvf.transparentBackground

Whether to enable background transparency for the main Neovim window.

false

true

Plymouth

Module information

This module is maintained by 0x5a4 and Daniel Thwaites.

Home Manager options

None provided.

NixOS options

stylix.targets.plymouth.enable

Whether to enable theming for the Plymouth boot screen.

false

stylix.targets.plymouth.logo

Logo to be used on the boot screen.

stylix.targets.plymouth.logoAnimated

Whether to apply a spinning animation to the logo.

Disabling this allows the use of logos which don't have rotational symmetry.

true

Qt

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.qt.enable

Whether to enable theming for QT.

false

true

stylix.targets.qt.platform

Selects the platform theme to use for Qt applications.

Defaults to the standard platform theme used in the configured DE in NixOS when stylix.homeManagerIntegration.followSystem = true.

"qtct"

NixOS options

stylix.targets.qt.enable

Whether to enable theming for QT.

false

stylix.targets.qt.platform

Selects the platform theme to use for Qt applications.

Defaults to the standard platform used in the configured DE.

"qtct"

qutebrowser

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.qutebrowser.enable

Whether to enable theming for Qutebrowser.

false

NixOS options

None provided.

ReGreet

Module information

This module has no dedicated maintainers.

Home Manager options

None provided.

NixOS options

stylix.targets.regreet.enable

Whether to enable theming for ReGreet.

false

stylix.targets.regreet.useWallpaper

Whether to set the wallpaper for ReGreet.

true

Rio

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.rio.enable

Whether to enable theming for Rio.

false

NixOS options

None provided.

river

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.river.enable

Whether to enable theming for River.

false

NixOS options

None provided.

Rofi

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.rofi.enable

Whether to enable theming for Rofi.

false

NixOS options

None provided.

Spicetify

This Stylix module leverages the modules provided by Spicetify-Nix.

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.spicetify.enable

Whether to enable theming for Spicetify.

false

NixOS options

stylix.targets.spicetify.enable

Whether to enable theming for Spicetify.

false

starship

Module information

This module is maintained by Chet Luther.

Home Manager options

stylix.targets.starship.enable

Whether to enable theming for Starship.

false

NixOS options

None provided.

Sway

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.sway.enable

Whether to enable theming for Sway.

false

stylix.targets.sway.useWallpaper

Whether to set the wallpaper for Sway.

true

NixOS options

None provided.

swaylock

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.swaylock.enable

Whether to enable theming for Swaylock.

false

true

stylix.targets.swaylock.useWallpaper

Whether to set the wallpaper for Swaylock.

true

NixOS options

None provided.

SwayNotificationCenter

Module information

This module is maintained by Maxim Muravev.

Home Manager options

stylix.targets.swaync.enable

Whether to enable theming for SwayNC.

false

NixOS options

None provided.

sxiv

Module information

This module is maintained by Mateus Auler.

Home Manager options

stylix.targets.sxiv.enable

Whether to enable theming for Sxiv.

false

NixOS options

None provided.

tmux

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.tmux.enable

Whether to enable theming for Tmux.

false

NixOS options

None provided.

Tofi

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.tofi.enable

Whether to enable theming for Tofi.

false

NixOS options

None provided.

Vim

This module themes Vim using the standard Home Manager options.

Related modules

• Neovim: themes Neovim using the standard Home Manager options.
• Nixvim: themes Neovim using the options provided by Nixvim.
• nvf: themes Neovim using the options provided by nvf.

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.vim.enable

Whether to enable theming for Vim.

false

NixOS options

None provided.

VSCode

Module information

This module is maintained by Erin Pletches and Daniel Thwaites.

Home Manager options

stylix.targets.vscode.enable

Whether to enable theming for VSCode.

false

stylix.targets.vscode.profileNames

The VSCode profile names to apply styling on.

[
  "default"
]

NixOS options

None provided.

Waybar

Module information

This module is maintained by awwpotato.

Home Manager options

stylix.targets.waybar.addCss

adds fully functional css (otherwise just adds colors and fonts)

true

stylix.targets.waybar.enable

Whether to enable theming for Waybar.

false

stylix.targets.waybar.enableCenterBackColors

enables background colors on the center of the bar

false

stylix.targets.waybar.enableLeftBackColors

enables background colors on the left side of the bar

false

stylix.targets.waybar.enableRightBackColors

enables background colors on the right side of the bar

false

stylix.targets.waybar.font

The font for waybar to use

"monospace"

"sansSerif"

NixOS options

None provided.

Wayfire

Module information

This module is maintained by 0x5a4.

Home Manager options

stylix.targets.wayfire.enable

Whether to enable theming for wayfire.

false

stylix.targets.wayfire.useWallpaper

Whether to set the wallpaper for wayfire.

true

NixOS options

None provided.

WezTerm

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.wezterm.enable

Whether to enable theming for wezterm.

false

NixOS options

None provided.

wob

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.wob.enable

Whether to enable theming for wob.

false

NixOS options

None provided.

Wofi

Module information

This module is maintained by Mateus Auler.

Home Manager options

stylix.targets.wofi.enable

Whether to enable theming for wofi.

false

true

NixOS options

None provided.

wpaperd

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.wpaperd.enable

Whether to enable theming for wpaperd.

false

true

NixOS options

None provided.

Xfce

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.xfce.enable

Whether to enable theming for Xfce.

false

true

NixOS options

None provided.

Xresources file

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.xresources.enable

Whether to enable theming for Xresources.

false

NixOS options

None provided.

Yazi

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.yazi.enable

Whether to enable theming for Yazi.

false

NixOS options

None provided.

zathura

Module information

This module is maintained by Mateus Auler and Noah Pierre Biewesch.

Home Manager options

stylix.targets.zathura.enable

Whether to enable theming for Zathura.

false

NixOS options

None provided.

Zed

Module information

This module has no dedicated maintainers.

Home Manager options

stylix.targets.zed.enable

Whether to enable theming for zed.

false

NixOS options

None provided.

Zellij

Module information

This module is maintained by Noah Pierre Biewesch.

Home Manager options

stylix.targets.zellij.enable

Whether to enable theming for zellij.

false

NixOS options

None provided.

Home Manager

The following options can only be set in a Home Manager configuration.

If you combined Home Manager with your NixOS configuration, write these options within a Home Manager section, either for all users:

home-manager.sharedModules = [
  {
    stylix.targets.xyz.enable = false;
  }
];

Or for a specific user:

home-manager.users.«name» = {
  stylix.targets.xyz.enable = false;
};

Read more about per-user themes.

Home Manager options

stylix.autoEnable

Whether to enable targets by default.

When this is false, all targets are disabled unless explicitly enabled.

When this is true, most targets are enabled by default. A small number remain off by default, because they require further manual setup, or they are only applicable in specific circumstances which cannot be detected automatically.

true

false

stylix.base16Scheme

A scheme following the base16 standard.

This can be a path to a file, a string of YAML, or an attribute set.

stylix.cursor

Attributes defining the systemwide cursor. Set either all or none of these attributes.

null

stylix.cursor.name

The cursor name within the package.

null

stylix.cursor.package

Package providing the cursor theme.

null

stylix.cursor.size

The cursor size.

null

stylix.enable

Whether to enable Stylix.

When this is false, all theming is disabled and all other options are ignored.

false

true

stylix.enableReleaseChecks

Whether to check that the Stylix release matches the releases of NixOS, Home Manager, and nix-darwin. Checks are only performed if the component in question is used.

If this option is enabled and a mismatch is detected, a warning will be printed when the user configuration is being built.

true

stylix.fonts.emoji

Emoji font.

{
  name = "Noto Color Emoji";
  package = <derivation noto-fonts-color-emoji-2.047>;
}

stylix.fonts.emoji.name

Name of the font within the package.

stylix.fonts.emoji.package

Package providing the font.

stylix.fonts.monospace

Monospace font.

{
  name = "DejaVu Sans Mono";
  package = <derivation dejavu-fonts-2.37>;
}

stylix.fonts.monospace.name

Name of the font within the package.