Designing Balanced D&D Subclasses for 5e and 2024 Rules

D&D 2024 arrived with one of the biggest overhauls to character classes and subclasses the game has seen. The new Player's Handbook contains 12 character classes, each with 4 subclasses, making 48 in total. That's the official baseline you're designing against. Whether you're a DM cooking up a bespoke archetype for your table, a third-party creator publishing on DMs Guild, or a hobbyist dropping homebrew PDFs on Reddit's r/UnearthedArcana, the rules have shifted under your feet — and so have the design expectations.

Start With the Right Question: Subclass or Full Class?

Before writing a single feature, ask yourself whether your concept even needs to be a full new class. If your idea is just going to replace some elements of a core class, it may work as a subclass — this allows you to flavor a class mechanically in all sorts of ways without resorting to the onerous task of building a balanced and meaningful class. A "shadow hunter" concept? That's a Ranger or Rogue subclass. A "blood mage who spends HP to fuel power"? That's a bloodmage subclass for Sorcerer, which lets you sacrifice HP or HD, or take ranks of exhaustion, in exchange for sorcery points or spell slots. Fitting your concept inside an existing chassis is almost always less work and produces more reliable balance.

The Level 3 Shift: What 2024 Changed for Designers

The single biggest structural change the 2024 rules made to subclass design is the entry level. All classes now get their subclasses at level 3, which required some movement in feature placement for anyone adapting or designing for the updated rules. In the previous 5e rules, Clerics chose their subclass during level one character creation, but the 2024 rules have moved this to a level 3 feature, meaning the player has two levels to experience and grow. For homebrew designers, that means any subclass feature that used to fire at levels 1 or 2 needs to be redesigned or redistributed. 2024 characters are also noticeably more powerful than 2014 characters, which raises the baseline you're competing against. A subclass that felt appropriately powerful under 2014 Fighter may read as underpowered once the base Fighter is already carrying Weapon Mastery and improved Second Wind.

Map Your Feature Slots First

The core design of D&D 5th edition ensures that there is a balance of features at each level for a player. What this means is that each core class has gaps in their features, and these gaps are where subclasses provide their features. Your job is to fill those gaps, not create new ones or double-stack on levels that already deliver class features. When making a subclass, every class has an order and purpose by which subclass features are granted. The Fighter, which gets its subclass at level 3, receives new archetype features at levels 3, 7, 10, and 15. Meanwhile, the Cleric, under old 5e rules, received archetype features at levels 1, 2, 6, 8, and 17. Pull up the class table for whatever base class you're designing for and place your features *only* in the correct slots. Anything else is a red flag — for D&D Beyond publishing especially, it is important that you adhere to this philosophy if you want to be able to publish the homebrew for public use.

Design Philosophy: Sidegrades, Not Upgrades

The point of a homebrew class should be to create a unique experience that isn't already found in the base game. Dungeon Masters and players who are creating new classes and subclasses should think of their new content as a sidegrade, not an upgrade to the existing game. An upgrade is adding raw attack damage or hit points with no cost attached. A sidegrade trades one capability for another. A sidegrade is when one thing improves at the expense of another. For example, a class that is significantly faster than average may also be vulnerable when hit or unable to do much damage. Adding weaknesses alongside strengths keeps a class from becoming too overpowered.

This framework has a practical consequence: if you're giving a martial subclass access to spellcasting, it should cost something elsewhere. The Eldritch Knight and Psi Warrior both do this within their Fighter chassis, keeping action economy tight.

Two Structural Approaches to Feature Design

There are two valid ways to structure how your subclass features relate to each other, and knowing which one you're building toward will save you from incoherence mid-design.

The first approach chains features together, where each new ability improves or builds on what came before. It's easier to balance one prominent ability with minor buffs than five separate abilities that don't build off each other. This works especially well for martial subclasses where a single combat identity needs to scale cleanly.

The second approach uses thematic clustering: a subclass can be homebrewed in a way where the abilities don't improve upon each other. Instead, the archetype features provide the class with separate abilities that build up thematic relevance when looked at as a whole. Spellcaster classes more commonly feature class archetypes designed in this format. These archetypes have features that all stem from a theme or concept that sometimes don't scale with level but become more prominent with each feature gained. Think Circle of the Moon Druid — each feature adds a new dimension to the "shapeshifter" identity rather than stacking the same bonus.

Homebrewing with thematically clustered features is far more complex than the chained method, requiring much more creativity and balancing knowledge to pull off well. However, when pulled off correctly, this method can make a subclass that comes together to create an experience that is gratifying for roleplay, character design, and combat.

Cover All Three Pillars

One of the most common homebrew failures is a subclass that only does one thing in combat. Have a healthy mix of Combat, Exploration, and Interaction features. Spellcasting can cover for Exploration and Interaction depending on the spell list. Don't make your class only capable in combat. A subclass built purely around dealing damage will feel hollow across an entire campaign. Even a single out-of-combat feature at a mid-level slot — a skill proficiency, a ritual, a passive that affects social encounters — dramatically improves table feel.

Watch Action Economy and Bounded Accuracy

Players get several different types of actions each turn: movement, an item interaction, a bonus action, a reaction, and an action. There are several potential problems when it comes to assigning abilities to different action types. On one hand, you could put too many options on one action type. If every feature in a subclass costs one action, the player has potential bonus actions and reactions they aren't using. Also, if this is a subclass, be aware that you are competing with other features of the base class.

The 2024 rules leaned hard into this. The classes are more flexible and tactical with better synergy between abilities — for example, weapon masteries give martials more tactics in how they approach attacks. There's also been a lot more thought about how abilities might combine, with many abilities now being usable as a bonus action to ensure turns can be more productive. Your subclass features need to fit that action-economy ecosystem, not fight it.

On the math side, respect bounded accuracy. Bounded Accuracy, Advantage/Disadvantage, and Proficiency Bonus were all designed to avoid the inflation problem of 4th edition, where +1s and +2s stacked from so many sources you'd forget they were there. In 5e, such things come in very limited forms. Don't stack static numeric bonuses. A feature that gives +2 to attack rolls indefinitely is doing significant hidden damage to encounter balance, especially at higher levels where it interacts with Extra Attack.

Synergy Within the Subclass (and Internal Conflicts)

Class features, when grouped into a whole, should build a foundation that drives a strong mechanical narrative of play. Some homebrew classes have had no synergy between their features, or even had features that were in direct conflict. One particularly egregious example of conflicting features involved a protective feature that required an Action to use, and a damage-boosting feature that granted additional damage dice to weapon attacks made using a reaction. On paper neither sounds problematic; in practice, one feature constantly undercuts the other's usage. Read your whole subclass out loud as if explaining it to a player mid-session. If you catch yourself saying "but you wouldn't use X and Y together," that's a design signal worth addressing.

Playtesting: The Non-Negotiable Step

To avoid problems arising during a longer campaign, it's important to playtest homebrew creations to ensure they work as intended. The best way to do that is to run short one-shots with friends or ask for input from experienced Dungeon Masters. The more testing that's done, the more improvements can be made.

For classes and subclasses, compare feature timing, action costs, and resource refresh to peers at the same levels. The benchmark is right there in the existing books: ask how your subclass's level 3 feature compares to Battle Master's Combat Superiority or the Totem Warrior's Bear totem. If it's dramatically stronger or more flexible, it needs a cost or constraint. If it's weaker, figure out what it's trading that weakness for.

When designing a subclass for an existing class, you have other existing subclasses against which to compare. There is no shortage of forums where you can gather a large sample of opinions about those preexisting subclasses, posted by a wide variety of people with a vast array of combined experience from which you can learn. What you learn from those sources can help you run your comparisons against the other subclasses.

A Note for Third-Party Creators

If you're publishing for public use rather than just your home table, the compatibility question with 2024 rules is real and ongoing. You can combine a 2024 class with a subclass from the 2014 Player's Handbook, Tasha's Cauldron of Everything, Xanathar's Guide to Everything, and any other book your DM allows. However, you will probably notice that the wording of certain features clashes with the 2024 wording of certain rules. Writing new homebrew subclasses specifically to the 2024 chassis means using updated terminology: "Magic action" instead of "cast a spell," "Origin feat" framing, and updated condition language. Getting this right isn't cosmetic — it determines whether your subclass plays correctly when built on D&D Beyond.

The 2024 revision also brought 15 new or substantially changed subclasses to the official roster. Each of the 12 core classes has four subclasses, including returning favorites from the 2014 Player's Handbook and 15 new or substantially changed subclasses. That means the design space is crowded in some places and still wide open in others. The best homebrew subclasses will be the ones that feel like they were always supposed to exist — filling a mechanical niche or thematic identity that the official books left on the table.