dracula/gtk: a dark GTK theme spread across per-version directories

One palette, many desktops

The Dracula GTK theme is a dark theme for GTK, and the interesting part is the scope it covers. The README states support for GTK-3 and GTK-2 based desktop environments, naming Gnome, Unity, Budgie, Pantheon, XFCE and Mate, and it also says it provides support for KDE Plasma.

That is a wide claim for a colour theme, and it is what shapes the repository. A theme that covers GTK 2, GTK 3, GTK 3.20 and GTK 4, plus a shell theme, plus several window manager directories, is not a single stylesheet. It is the same design decisions expressed again and again in the formats each of those components expects.

The homepage for the theme is draculatheme.com/gtk, and the install instructions live there rather than in the README, which keeps the repository readme short: a screenshot, a description of what the theme supports, a link to the install page, a team section and the licence.

The project is part of the wider Dracula theme family, and the community channels are shared across it: Twitter for updates about themes and new work, GitHub Discussions for questions and issues, and Discord for the wider community. The team section credits Eliver Lara as the maintainer, along with a list of contributors.

The licence is GPL-3.0, with the LICENSE file in the repository root.

The directory layout is the version matrix

The top-level entries of the repository are the best documentation of what this project actually is.

There are four GTK toolkit directories: gtk-2.0/, gtk-3.0/, gtk-3.20/ and gtk-4.0/. GTK 3.20 is the version that introduced the theming changes many of those versions are remembered for, and shipping it as a separate directory rather than as part of gtk-3.0/ shows that the theme keeps the older and newer GTK 3 conventions apart.

Then there is a directory per component that draws its own interface. gnome-shell/ covers the GNOME shell theme, cinnamon/ covers Cinnamon, unity/ covers Unity, kde/ covers the Plasma side, metacity-1/ covers the Metacity window decorations, and xfwm4/ covers the Xfwm window manager theme. Art/ and assets/ hold the artwork, and src/ holds the source the build works from.

An index.theme file at the root is what makes the directory usable as a GTK theme, since that is the metadata file GTK looks for when it scans a theme directory.

The implication for anyone using it is practical. A theme is not a single file you drop in, it is a directory you install and select, and the directory you need depends on the toolkit version and the components your desktop draws. Installing the whole tree and letting the desktop pick up what it understands is the forgiving approach; picking a single subdirectory is the tidy one, and the per-component split is what makes the second option possible.

It is also the maintenance story. A colour change has to be applied in each of these directories, and that is the cost of covering this many toolkits with one design.

Sass and Gulp, and a package manifest with a history

The build tooling is in the package manifest, and it is worth reading because it explains how the theme is put together.

The dependencies are a Gulp pipeline with a Sass compiler:

"dependencies": {
  "gulp": "^4.0.0",
  "gulp-exec": "^2.1.3",
  "gulp-sass": "^4.0.2"
}

gulp-sass compiles the Sass sources, gulp-exec lets the pipeline shell out for the steps Sass does not cover, and the Gulpfile.js at the repository root is the task definition. The src/ directory holds the source that this pipeline consumes.

What is odd, and what a contributor should notice immediately, is the identity of the manifest. The package is named Ant, with the description a flat and light theme with a modern look, its repository points at EliverLara/Ant, its licence field says ISC, and its build script is defined as git push && sh install.sh. That is a template manifest carried over from a different project, and it explains itself once you know it: the Ant theme by the same author provided the starting point that this repository was derived from.

The practical consequence is that the manifest is not a reliable description of this repository. The licence that applies to the theme is the GPL-3.0 file at the root, as the README states, not the ISC string in package.json. The test script is a placeholder that echoes an error and exits, so there is no test suite to run. And the build script as written pushes to git before running an install script, which is not something you want to trigger by accident.

If you are going to work on this theme, the honest starting point is to replace the inherited manifest rather than to trust it.

Installing, and what the install page covers

The README keeps installation to a single sentence, and it is a redirect: all instructions can be found at draculatheme.com/gtk.

The repository does carry an INSTALL.md at the root, so the mechanics are in the tree as well as on the site. The general shape of a GTK theme installation is that the theme directory goes into the user's theme directory, and the desktop environment is then told to use it, and for the shell and window manager components there are additional steps because those are separate theming systems rather than plain GTK.

That last point is the one that catches people out, and it is a consequence of the directory layout. Installing gtk-3.0/ gives you the applications and the toolkit widgets. It does not give you the GNOME top bar, which comes from gnome-shell/, or the window decorations, which come from metacity-1/ or xfwm4/ depending on the window manager you run. On KDE Plasma the relevant piece is the kde/ directory instead.

The multi-version support is also not entirely automatic. GTK 2 and GTK 3 applications are themed by different directories, so a machine running both, which is less common now but was routine when the theme was started, needs both installed to look consistent.

The screenshot at the root of the repository, screenshot.png, shows the intended result, and the screenshot on the theme site shows it in the wild.

A theme that predates the current toolkit

The maintenance picture is the part to weigh, and it is specific.

The tagged releases are old. v2.0 came on 2020-09-19, v3.0 on 2021-12-30 and v4.0.0 on 2023-02-24. The repository is not archived, and the last push was on 2026-08-24, which tells you that work is still landing on the branch even though no new tag has been cut in more than three years.

That gap is the thing to understand about themes specifically. A theme is not code with a stable interface, it is a description of how a toolkit should look, and the toolkit changes underneath it. GTK 4 introduced a different way of styling applications, the GNOME shell reworked its theme format between versions, and Cinnamon, Unity and Plasma each have their own conventions. A theme that was last released in early 2023 and has not been tagged since can still be maintained on the branch, and the pushes since then are the evidence of that, but you have no release artefact to point at and no changelog to tell you what changed.

The GTK 4 directory is a good example of the judgement involved. Having a gtk-4.0/ directory means the author has covered the newer toolkit, but shell theming in particular is tied to specific GNOME versions, and a directory that was correct for the GNOME release current in 2023 is not automatically correct for the one shipping now.

So the honest description is a maintained but slowly released theme. If you want the dark look and accept a little mismatch on the newest toolkit, it does the job. If you need pixel accuracy on the current GNOME or Plasma release, expect to adjust it.

Editorial conclusion

Adopt dracula/gtk if you run a GTK based desktop and want the Dracula palette applied consistently across the shell, the panel, the window manager and the applications, and if you are willing to pick the right directory for your toolkit version. Do not adopt it expecting a theme that tracks every new GTK release, because the newest tag v4.0.0 dates from 2023-02-24 and the toolkit moves faster than that, and do not treat the GNOME Shell directory as a guarantee that current shell themes will render, since shell theming changes with each GNOME version. Before you start, read INSTALL.md and the instructions at draculatheme.com/gtk, check whether your desktop matches one of the covered directories, and look at the uncommitted difference between the last release and the current tree before you copy it into your system.

Frequently asked questions

Official sources

1. dracula/gtk on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases