Tabletop RPG Classes and Archetypes: A Reference Guide
Character classes and archetypes are the structural backbone of most tabletop RPG systems — the framework that defines what a character can do, how they grow, and what role they fill at the table. This reference covers the mechanics of class-based design, how archetypes function as secondary specializations, where classification systems diverge across major games, and the genuine design tensions that make class choice one of the most debated decisions in the hobby.
- Definition and scope
- Core mechanics or structure
- Causal relationships or drivers
- Classification boundaries
- Tradeoffs and tensions
- Common misconceptions
- Checklist or steps
- Reference table or matrix
Definition and scope
A character class is a formal category assigned at character creation that determines a character's primary abilities, resource pools, and advancement trajectory throughout play. The term "archetype" functions differently depending on the system: in Dungeons & Dragons 5th Edition (Player's Handbook, Wizards of the Coast, 2014), it refers to a subclass chosen at a specific level — a Fighter choosing Battle Master or Champion at level 3, for instance — while in Pathfinder 2nd Edition (Paizo Publishing, 2019), archetypes are a modular feat-based system that any character can layer onto their existing class.
The scope of class-based design extends well beyond D&D. Call of Cthulhu uses "occupations" rather than classes, defining starting skill packages without locking characters into rigid ability tracks. Powered by the Apocalypse games — explored in depth at /powered-by-the-apocalypse-games — use "playbooks," which are functionally classes but embed personality, narrative role, and mechanical identity into a single document. Understanding how these systems differ is foundational to choosing your first tabletop RPG system.
The class concept traces its functional origin to the 1974 original Dungeons & Dragons boxed set, which offered 3 classes: Fighting Man, Magic-User, and Cleric. D&D 5e launched in 2014 with 12 base classes; subsequent official sourcebooks expanded that to 13 with the addition of the Artificer in Eberron: Rising from the Last War (Wizards of the Coast, 2019).
Core mechanics or structure
Most class systems operate through at least 3 structural layers: the base class (broad identity), the subclass or archetype (specialization), and the advancement table (the schedule of ability unlocks by level or experience point threshold).
Resource pools are the mechanical heartbeat of class design. A Wizard in D&D 5e manages spell slots distributed across 9 spell levels; a Barbarian manages Rage charges — typically 2 at level 1, scaling to unlimited at level 20. These resource pools define pacing: Barbarians tend toward consistent moderate output, while high-level Wizards hold significant power in reserve and release it in concentrated bursts.
Action economy is the second pillar. Classes differ in how many meaningful decisions they make per round of combat. The Fighter's Action Surge (usable once per short rest at levels 1–16, twice per short rest at level 17+) compresses multiple actions into a single turn. A Rogue, by contrast, optimizes a single attack through Sneak Attack — a bonus that scales from 1d6 at level 1 to 10d6 at level 19 (D&D 5e Systems Reference Document, Wizards of the Coast).
Subclass selection introduces the branching structure. In Pathfinder 2e, a Wizard selects a thesis at level 1 — Spell Blending, Spell Substitution, Experimental Spellcasting — which restructures how core class features operate. This is mechanically distinct from D&D 5e's subclass model, where the base class remains largely unchanged and the subclass appends additional features at set levels.
Causal relationships or drivers
The proliferation of class options across major systems is directly driven by two forces: commercial expansion and player demand for identity expression.
Wizards of the Coast has released over 30 official subclasses for the Fighter class alone across D&D 5e sourcebooks and Unearthed Arcana playtest documents. Each new sourcebook — Xanathar's Guide to Everything (2017), Tasha's Cauldron of Everything (2020), Fizban's Treasury of Dragons (2021) — adds subclass options, which expands the design space but also increases the cognitive load for new players navigating character creation basics.
Community homebrew accelerates this further. The DMs Guild platform, which operates under Wizards of the Coast's Community Content Agreement, hosts thousands of custom classes and subclasses. This ecosystem exists because the class system creates a natural template: designers know the mechanical slots that need filling (level 3 subclass feature, level 6 feature, level 10 feature, level 14 feature), making homebrew tractable even for intermediate designers.
The deeper causal driver is that class selection is a proxy for identity at the table. Research in game studies, including work published in the International Journal of Role-Playing (ijrp.subcultures.nl), has examined how players use character class as a framework for self-expression, which explains why class flavor text — the narrative justification for abilities — receives nearly as much design attention as the mechanical content.
Classification boundaries
The hobby's class systems split along a fundamental axis: class as constraint versus class as foundation.
In D&D 5e and Pathfinder 2e, class is primarily constraining — it defines what a character cannot do as much as what they can. A Fighter in 5e has no native access to spell slots without multiclassing, which requires meeting a 13 in the relevant ability score for both the original and destination class. This boundary creates identity clarity but limits flexibility.
Narrative-forward systems reject this model almost entirely. In Blades in the Dark (One Seven Design, 2017), the 6 character types (Cutter, Hound, Leech, Lurk, Slide, Whisper) function less as mechanical restrictions and more as starting statistical profiles and special ability menus. The narrative vs. rules-heavy RPG systems distinction maps almost perfectly onto the class-as-constraint versus class-as-foundation divide.
Multiclassing sits at the boundary of this classification problem. D&D 5e allows characters to split levels across multiple classes, creating hybrid builds — a Paladin 2/Warlock 5 combination, known informally as "Hexadin," is a well-documented optimization for maximizing short-rest spell slot recovery. Pathfinder 2e handles this differently through its archetype feat system, which layers abilities from other classes without splitting the advancement table.
Tradeoffs and tensions
The central tension in class design is breadth versus depth. A class system with broad options distributes choice across the entire player base but dilutes the distinctiveness of any individual class. A system with narrow, sharply defined classes produces clearer identity but frustrates players whose concept doesn't fit the available molds.
A second tension lives in the subclass timing decision. D&D 5e staggers subclass selection: Clerics and Sorcerers choose at level 1, Fighters and Rogues at level 3. Critics of this design — including game designers writing on forums like the EN World design discussion boards — argue that delaying subclass selection forces players to play 2–3 sessions as a generic version of their class before their actual concept comes into focus. Defenders argue the delay gives new players time to understand the base class before adding complexity.
The third tension is between balance and fantasy fulfillment. Optimization communities, including those active on Reddit's r/3d6 subreddit (which had over 210,000 members as of 2023 data), routinely identify mechanical outliers — classes or subclass combinations that dramatically outperform others. The Twilight Cleric's Channel Divinity, which grants temporary hit points equal to 1d6 plus the Cleric's level to every creature in a 30-foot radius, was flagged as overpowered in Tasha's Cauldron of Everything but was never officially revised downward. This reflects a genuine design philosophy tension: nerfing after publication erodes player trust; leaving outliers intact distorts table balance.
Common misconceptions
Misconception: Archetypes and subclasses are synonyms across all systems. They are not. In D&D 5e, "archetype" was used in early sourcebooks but has been largely supplanted by system-specific terms ("Primal Path" for Barbarians, "Sacred Oath" for Paladins). In Pathfinder 2e, an archetype is a distinct mechanical category separate from subclass features. Treating the terms as universal creates confusion when moving between systems.
Misconception: Class determines playstyle more than player skill. Class establishes the mechanical vocabulary, not the sentence. A Rogue can be played as a skulking assassin or a social-facing Arcane Trickster who rarely enters combat. The roleplaying your character effectively dimension is almost entirely independent of class mechanics.
Misconception: Multiclassing always produces stronger characters. Multiclassing delays class feature progression. A character who takes 1 level of Warlock and 19 levels of Fighter receives the Fighter's level 20 capstone (Extra Attack 3 times) — but a character who splits 11 Fighter / 9 Warlock receives neither capstone. The math favors multiclassing only in specific combinations and only when short-rest recovery cycles are available at the actual table.
Misconception: Classless systems have no equivalent structure. Games like Fate Core (Evil Hat Productions, 2013) use aspects and skills rather than classes, but these still function as character differentiation frameworks. The structure exists — it's just distributed rather than categorical.
Checklist or steps
Elements a class system typically defines at character creation:
Elements resolved later during advancement:
For a broader overview of character building from the ground up, the getting started with tabletop RPG section covers the full sequence.
Reference table or matrix
Class System Comparison Across Major TTRPGs
| System | Term Used | Selection Timing | Specialization Layer | Multiclass Mechanism |
|---|---|---|---|---|
| D&D 5e (2014) | Class / Subclass | Level 1 (class), Level 1–3 (subclass) | 1 subclass per character | Level-splitting across classes |
| Pathfinder 2e (2019) | Class / Archetype | Level 1 (class), Level 2+ (archetype feats) | Multiple archetypes stackable | Archetype feat system |
| Call of Cthulhu 7e | Occupation | Character creation only | None (skills are fluid) | N/A — skill-based, not class-based |
| Blades in the Dark (2017) | Character Type / Playbook | Session zero | Crew type adds secondary layer | N/A — advancement is within playbook |
| Powered by the Apocalypse (2010) | Playbook | Session zero | Moves from other playbooks (limited) | Move selection across playbooks |
| Fate Core (2013) | None (aspects + skills) | Session zero | N/A | N/A |
| Shadowrun 6e (2019) | Metatype + Priority | Character creation | Specializations within skills | N/A — resource-based build system |
The tabletop RPG system comparison page extends this analysis across additional mechanical dimensions, including resolution systems and GM-facing design assumptions.
The full range of what class and archetype design makes possible — and impossible — at the table is one of the hobby's most durable design conversations. The complete landscape of RPG play, including how class decisions interact with campaign structure and story type, is indexed at the tabletoprpgauthority.com home.