Homebrew: Overview

From 5etools Community Wiki
Jump to: navigation, search


When we say homebrew in the sense of 5eTools, it's more than what you might be normally be used to, homebrew content effectively means any content that is not WoTC and is also available for use within 5eTools. This will include licensed 3rd party content such as Green Ronin; Kobold Press; Paizo; etc. You can see the list of Offical content [{{ }} here].

When it's used within 5eTools, Homebrew also includes the *means* to take your ideas and use them as part of the site.


That requires some additional work from what you may be familiar with RE: Homebrewry, GMBinder, or just drafting up a thought in a word processor. It helps to have a minor understanding of a data structure called JSON. If you've used Homebrewry or GMBinder, or indeed CritterDB or the like, it's not that different.

To Create Homebrew



Conversion for another site/service.


  1. If what you are trying to create is easily accomplished by reflavoring an existing, official component of the game. Do that. Not only is designing it yourself wasted time and effort, but often will be poorly balanced in comparison.
    Ex: If you’re looking to create a massive serpent that spits poison, simply edit a green dragon and adjust its challenge rating accordingly.

  2. As a rule of thumb, stick to established design format. It’s there for a reason.
    You are free to go against status quo, but keep in mind this will require extensive playtesting, and will generally get your homebrew dismissed by curators.

  3. When formatting your homebrew text, try to find the middle ground between Comprehensive, Traditional and Concise. WotC’s wording of certain spells, classes, etc. is poor. Don’t take their work as gospel, but try to keep your formatting familiar and to the point.

Player options

  1. When designing player options, be extra diligent in your attempt to balance your new material against published works. Aim for below average power, but powerful enough to at least be attractive for a player. It’s easier to give a class or race something extra if it turns out too weak, than it is to take features away if it turns out too powerful. Especially if your players are already using them! Imagine how you would feel getting something extra against having features taken away from you.

  2. A homebrew class should grant proficiency in two saving throws at level one. Choose one from [Strength/Intelligence/Charisma] and [Constitution/Dexterity/Wisdom]. A player character with only one class should never feel pressured to spread its strengths too thin. Beyond the every important Constitution score, a specific (sub)class should never focus on more than 2 ability scores at once. For instance, Rogues tend to perform best on a combination of Dexterity, Intelligence and Constitution, but certain subclasses might substitute Intelligence with Charisma.
    A class’ hit die should be proportionate to both its flexibility and its general approach to combat. Classes designed to be at the front most often have larger hit dice, and classes that focus on staying in the back have smaller ones.
    Constitution is *not* a spellcasting ability.
    Don’t give your class too many resources to pull from. If your character has spell slots, give them one additional resource at most. Ex: Sorcery points.

  3. When creating a subclass, attempt to have the its features fill the same niche as the ones from existing subclasses for the class. If a feature focuses on broadening the player’s options in exploration, consider having your subclass’ feature share that focus.

  4. NPCs have a proficiency bonus related to their challenge rating. Whenever a creature has a feature with a saving throw, that saving throw’s DC equals 8 + the creature’s proficiency bonus + the creature’s relevant ability modifier. Exceptions to this rule exist, but only rarely.

  5. Always ask for input from other experienced homebrewers if you intend on going public with your homebrew creations.