Dracula for JetBrains: a dark theme plugin with a one person maintenance history
🧛🏻♂️ Dark theme for JetBrains IDEs
At a glance
- What is it?
- The dracula/jetbrains repository builds the Dracula dark theme for JetBrains IDEs as a Gradle plugin project in Kotlin, published to the JetBrains plugin marketplace under the id com.vermouthx.idea. The README is thin, the maintenance is carried by one named person, and the paid Dracula PRO tier covers the theme outside the IDE.
- Who is it for?
- Dracula for JetBrains fits a developer who already uses the Dracula palette elsewhere and wants the JetBrains IDEs to match without hand-editing colour schemes, and who is comfortable installing a plugin from the marketplace. It does not fit a team that needs a theme maintained under a support contract, or anyone who wants to change the palette rather than accept it.
- 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 22 days ago.
- What is it written in?
- Mainly Kotlin, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 22, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What the repository actually is
The dracula/jetbrains repository is a Gradle project in Kotlin that produces a plugin for JetBrains IDEs, and the top-level entries give the shape of it.
There is a build.gradle.kts and a settings.gradle.kts, which is the Kotlin DSL form of the Gradle build, plus gradle.properties, a gradle directory and both gradlew and gradlew.bat wrapper scripts, so the project builds with a checked-in Gradle version rather than whatever Gradle happens to be on the machine. The source lives in a src directory, and there is a docs directory holding a screenshot of the paid tier.
The documentation set is small and worth reading as a signal about the project's maturity. There is a CHANGELOG, a CONTRIBUTING guide, an AGENTS.md and a CLAUDE.md, both of which are instructions for coding agents rather than for human contributors, an INSTALL.md, and a screenshot image at the root.
The plugin identity is visible in the badges. The marketplace badge points at the plugin id com.vermouthx.idea, which is the string the JetBrains plugin repository knows this plugin by, and the release badge points at the GitHub releases. The build workflow is a GitHub Actions build workflow with a status badge.
So the shape is: a colour scheme and theme packaged as a JetBrains plugin, built from source with Gradle, released to both the marketplace and GitHub releases.
Install and where the instructions actually live
The Install section of the README is three lines long, and the whole of it is a link. All instructions can be found at draculatheme.com/jetbrains, which tells you two things at once: the project expects the website to be the canonical documentation, and the repository itself is not where a new user is meant to start.
That is a reasonable division for a theme. The install path for a JetBrains plugin is a few clicks through the marketplace, and the settings the theme exposes depend on the IDE version, which is a moving target for a project that supports many IDEs at once. A website that can be updated without a release cycle is the right place for that.
The INSTALL.md file at the repository root is the other half of the story, and the README does not point at it directly. That is the file to read before installing, since it is the version that lives with the code rather than on a site that can drift from it.
The repository is MIT licensed, with the licence file at the root. The homepage is draculatheme.com/jetbrains, and the last push to the repository was on 2026-10-01, with the most recent release v2.3.1 published on 2026-09-05.
Release cadence and the versioning
The release history is short and recent. Version 2.3.1 was published on 2026-09-05, version 2.3.0 on 2026-08-08 and version 2.2.0 on 2026-07-02, and the last push was on 2026-10-01.
The pattern is worth reading: a minor version roughly every month over the summer, with patch releases following, and a push about three weeks after the most recent tag. That is the profile of a small theme that is still being adjusted, and it is also a warning that a theme you like today may look slightly different next month.
For a theme, the interesting question is what drives a version bump at all. A theme has no API to break, so the releases are almost certainly visual: adjusting a colour, adding a key for a new language definition, or updating support for a new IDE version that changed its theme API. The CHANGELOG at the repository root is where that history lives, and it is the file to consult if you want to know whether a bump will change how your editor looks.
The absence of GitHub releases for older versions in the visible history is not a gap so much as a reminder that the marketplace is the distribution channel, and the tags are the source of truth for what went into each build.
Who maintains it and what the community channels are
The README states that the theme is maintained by the following person or persons and a bunch of awesome contributors, and then names exactly one person in the table, Zihan Ma, linking to a GitHub profile. There is a contributors graph linked alongside.
So this is a single-maintainer project with a wider contributor base behind it, and the README credits that base explicitly rather than listing a team. That is the honest picture and it is worth weighing before you depend on it.
The community channels are listed in three lines, one per medium, with a recommendation for each. Twitter is described as best for getting updates about themes and new stuff, the GitHub discussions area of the main dracula/dracula-theme repository is best for asking questions and discussing issues, and Discord is for hanging out with the community. The GitHub discussions living in a different repository tells you the theme is one part of a wider Dracula project with its own community space.
The AGENTS.md and CLAUDE.md files at the root indicate that contributions are expected to come through coding agents as much as by hand, which is a newer norm for small open source projects and a sign that the maintainer is trying to widen the contributor funnel.
The free theme, the Pro tier and what each covers
The README separates the JetBrains theme from a paid product called Dracula PRO, and the descriptions of the two are different in kind.
The JetBrains project is described plainly as a dark theme for JetBrains IDEs, and its scope is the IDE colour scheme and UI. That is the free thing, and it is what the repository builds.
Dracula PRO is described as a color scheme and UI theme tailored for programming, made for terminal emulators, code editors and syntax highlighters, and designed to be aesthetically pleasing while keeping you focused. It is sold through Gumroad as an upgrade, with the documentation hosting a screenshot of it.
The distinction is worth holding on to, because the two are easy to conflate. The Pro tier is the general Dracula palette packaged for many tools, while the JetBrains plugin is the specific integration for the IDE family. Buying Pro does not obviously include the JetBrains plugin, and the plugin does not obviously require Pro. The repository itself does not say one way or the other, which is exactly the kind of thing the FAQ on the website would answer and the README does not.
For a developer deciding whether to use the theme, the practical question is narrower: do you want the Dracula palette in your IDE, and are you willing to accept the palette as given rather than as something you tune.
Where Dracula for JetBrains is the wrong choice
The first limitation is that a theme is a preference, and preferences are not worth much operational effort. A colour scheme can make long editing sessions more comfortable, but it does not change what the IDE does, and no amount of theme work will compensate for a slow build or a confusing framework.
The second is the single maintainer. A theme that a person maintains in their own time, with a roughly monthly release cadence, is fine until it is not, and there is no support contract and no response time to plan around. The community channels are real, but they are the same channels any hobby project has. If your team's editor theme is a shared standard, an IDE vendor theme or a theme with an organisation behind it is a safer dependency than a personal project with a monthly release rhythm.
The third is the mismatch risk. A JetBrains plugin is coupled to the IDE versions it supports, and the plugin id in the marketplace is the thing you are trusting to stay installable and compatible. The README does not document which IDE versions a given plugin version supports, so a team that standardises on a specific IDE version has a question the repository does not answer and the marketplace listing might.
The fair comparison is with the built-in themes. Every JetBrains IDE ships with a dark theme, and the vendor themes are updated with the IDE itself and are guaranteed to cover every new UI element. Choosing Dracula is a choice about palette consistency across your toolchain, including terminals and editors outside the JetBrains family, and it is a reasonable thing to want. It is just a preference, and the alternatives are free and already installed.
Editorial conclusion
Dracula for JetBrains fits a developer who already uses the Dracula palette elsewhere and wants the JetBrains IDEs to match without hand-editing colour schemes, and who is comfortable installing a plugin from the marketplace. It does not fit a team that needs a theme maintained under a support contract, or anyone who wants to change the palette rather than accept it. Before installing, read INSTALL.md in the repository since the README delegates every installation instruction to the website, check the plugin marketplace entry for the id com.vermouthx.idea rather than trusting a third party download, and note that the JetBrains theme and the separately sold Dracula PRO are different products with different scopes.
Frequently asked questions
What is the dracula/jetbrains repository?
It is a Kotlin and Gradle project that builds the Dracula dark theme for JetBrains IDEs as a plugin, published to the JetBrains plugin marketplace under the id com.vermouthx.idea, with releases also tagged on GitHub. The theme itself is MIT licensed.
How do I install the Dracula theme for JetBrains?
The README does not list the steps itself and instead directs you to draculatheme.com/jetbrains, stating that all instructions can be found there. The repository also contains an INSTALL.md file, which is the version kept alongside the code and worth reading before installing.
How often is the Dracula JetBrains theme updated?
Version 2.3.1 was published on 2026-09-05, 2.3.0 on 2026-08-08 and 2.2.0 on 2026-07-02, with the last push to the repository on 2026-10-01. A CHANGELOG at the repository root records what changed in each version.
Who maintains the Dracula theme for JetBrains?
The README says the theme is maintained by the listed person or persons and a bunch of awesome contributors, and names one person in its table, Zihan Ma, alongside a link to the contributors graph. The repository also carries AGENTS.md and CLAUDE.md files for coding agents.
Is Dracula PRO the same thing as the JetBrains plugin?
They are separate products. The plugin is the free dark theme for JetBrains IDEs, while Dracula PRO is a paid colour scheme and UI theme made for terminal emulators, code editors and syntax highlighters, sold through Gumroad as an upgrade.
Official sources
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.
[](https://hysenlabs.com/projects/dracula-jetbrains)Was this useful?