Skip to content

Character sheet templates created by the community for use in Roll20 VTT. Submit a ticket at if critical hotfixes are to be requested.


Notifications You must be signed in to change notification settings


Folders and files

Last commit message
Last commit date

Latest commit

Sorry, we had to truncate this directory to 1,000 files. 260 entries were omitted from the list.

Repository files navigation

Roll20 Character Sheets is the easy-to-use virtual tabletop that brings pen and paper gaming to the web the right way. Built on a powerful platform of tools, yet elegantly simple, it focuses on enhancing what makes tabletop gaming great: storytelling and camaraderie.

This repository is the collection of all the community-contributed character sheets that are available for use on Roll20. These are, mostly, created for free, for use by the community, and represent dozens, if not hundreds of hours of effort on the parts of their creators.

This repository consists of over 📜 800 community contributed sheets, from over 🧑 300 contributors, who have written over ⌨️ 400,000 lines of code. This is an 🦦 otter.

Community Conduct

The Roll20 Code of Conduct applies to your participation on this repository.


Following the Roll20 Code of Conduct means no racism, no sexism, no hate speech, no backseat gaming, no personal attacks, no transphobia, no misgendering, no ableism, no anti-LGBTQIA+ sentiments (and so on) are allowed.

Table of Contents


There are many ways in which you can contribute to these sheets, and to the health of the space:

Getting Started

If you are interested in contributing code, fixing issues, or adding content, the Roll20 Wiki: Building Character Sheets documentation is a great place to start familiarizing yourself with the space.

Improving Existing Character Sheets

Before you submit work to the repository, please ensure that there is not already a sheet that covers the game you are intending to create a sheet for. If there is already one, fear not! Be bold and suggest some changes.

In general, this should look something like this:

  • Fork the repository.
  • Make your changes to the sheet in question.
  • Make the Pull Request.
  • Invite previous contributors to review your changes.
  • Once everyone is satisfied with the changes, we can merge the changes into the existing sheet.

We have learned from experience that it is better to have a single sheet that is contributed to by a number of people, rather than perpetuating the cycle of a contributing a sheet, losing interest, moving on, and then the next contributor creating an entirely new sheet. This is a collaborative community, please feel empowered to collaborate!

Beginner's Guide to GitHub - for Roll20 character sheets

Starting a New Character Sheet

If you have a burning desire to start from scratch, and there isn't already an existing sheet for a game or system, then it's time to embark upon a voyage of discovery. ⛵ There is plenty of documentation available on the Roll20 Help Center and on the community wiki, but here's a quick primer to get you started.

A character sheet, at a minimum requires four files in an appropriately named subfolder of the repo:

  • <sheetname>.html - This HTML file describes the structure and functionality of your character sheet. It might consist of inputs to store user data, buttons to make rolls to the VTT, repeating sections to store lists of information (like inventory items), or more advanced elements such as roll templates or sheet workers.
  • <sheetname>.css - This CSS file is primarily responsible for adding styles to your character sheet. However, CSS can be very versatile and such is used for much, much, much more.
  • preview.(jpg/png/gif) - This image file is what users will see as a preview, before selecting your sheet.
  • sheet.json - This JSON file includes metadata about the sheet, including the filenames for your sheet, your credit as author(s), and much more. It's integral to your sheet being implemented correctly that this format is followed. Please see this document for more information.

Submission Guidelines

All contributions to this repository must meet the minimum requirements outlined in this article. We additionally reccomend requesting approvals from a sheet's original author if you are submitting any large overhauls to actively-maintained sheets. This will speed up your approval process.

Release Cadence

Pull Requests are reviewed at least weekly by 00:00 UTC on Thursdays, although cadence is often more frequent.

Once a Pull Request has been merged, changes should be served on within approximately ten minutes. Contributors are encouraged to open a GitHub issue if their changes haven't appeared 24 hours after the Pull Request has been merged.

Internationalization & Translations

We use Crowdin to crowdsource and manage translations for various aspects of our site.

Check out the Help Center articles and Community Wiki documentation below to learn about translations and to help us make Roll20 accessible in as many languages as possible!

Sheet translations submitted outside of Crowdin will not be accepted and/or will be overwritten by Crowdin.

Uploading Sheets

Ensure that you have installed jq before running the following commands:

cd 5eShaped # Change this to your desired sheet directory
cat sheet.json|  jq ". += {\"version\":\"$(date +%s)\"}" | tee sheet.json # This will bump the version field in sheet.json

Commit the change to sheet.json, push your changes to one of the supported branches and watch CircleCI for the branch to which you pushed. The supported branches are:

  • master
  • staging


All of the code (HTML/CSS) of the sheets in this repository is released under the MIT license (see LICENSE file for details). If you contribute a new sheet or help improve an existing sheet, you agree that your contribution is released under the MIT License as well.


For urgent concerns, problems, or hotfixes, please submit a ticket at


Character sheet templates created by the community for use in Roll20 VTT. Submit a ticket at if critical hotfixes are to be requested.




Security policy





No packages published