Pathfinder Multiclassing Rules

Multiclassing is one of the most powerful and frequently misunderstood systems in Pathfinder — the rules-dense tabletop roleplaying game published by Paizo Inc. A character who splits their advancement between two or more classes can access a broader toolkit than any single-class build, but the tradeoffs are real and the mechanics have specific constraints worth understanding before a player commits a level. This page covers how multiclassing is defined in Pathfinder's rules, how the mechanics actually function, the most common build scenarios players encounter, and where the genuine decision points sit.

Definition and scope

Multiclassing in Pathfinder (specifically the Pathfinder Roleplaying Game Core Rulebook, published by Paizo) refers to the practice of taking levels in more than one character class as a character gains experience. Unlike some tabletop systems that treat this as an exception, Pathfinder's rules explicitly support multiclassing as a standard option — no special permission from a GM is required unless a table imposes house rules.

The system covered here is the one from Pathfinder First Edition (PF1e). Pathfinder Second Edition (PF2e) replaces multiclassing with an Archetype and Dedication feat structure, which operates on entirely different logic. If a character sheet says "Fighter 3 / Rogue 2," that's PF1e. If it says "Fighter with Rogue Dedication," that's PF2e. The two are not interchangeable, and conflating them is the most common source of table confusion. For a broader orientation to Pathfinder's systems, the Pathfinder overview is a useful starting point.

How it works

When a character gains a level in PF1e, the player chooses which class that level goes into. A character can split levels freely across any classes they qualify for, subject to Experience Point rules under the standard advancement track in the Core Rulebook.

The key mechanical consequences of multiclassing follow this structure:

1. Base Attack Bonus (BAB): Each class has its own BAB progression (Full, 3/4, or 1/2). A multiclassed character adds the BAB from each class separately, then totals them — a Fighter 4 / Wizard 3 has BAB +4 (from Fighter) plus BAB +1 (from Wizard) for a combined BAB of +5.
2. Saving Throws: Good and Poor save progressions stack across classes. The initial "good save" bonus of +2 is only applied once per save, no matter how many classes grant it as a good save — a detail from the Core Rulebook that prevents stacking exploits.
3. Hit Points: Each level grants hit points based on the class taken at that level, plus the character's Constitution modifier.
4. Spellcasting: Spell slots and spells known do not combine across classes unless the character takes the Mystic Theurge prestige class or a similar cross-class bridge. A Cleric 3 / Wizard 3 casts from two entirely separate spell lists with entirely separate slot pools.
5. Class Features: Special abilities, ki pools, sneak attack dice, and similar features advance only within their originating class. A Rogue 2 / Fighter 4 has 1d6 sneak attack damage — not the 3d6 a Rogue 6 would have.

For a deeper look at how these mechanics connect to Pathfinder's underlying design logic, Pathfinder's conceptual framework covers the broader rules architecture.

Common scenarios

Three multiclass combinations appear more often than almost any other at tables running PF1e:

Fighter / Rogue: Fighter levels front-load combat feats and BAB; Rogue levels provide Sneak Attack and skill ranks. The tradeoff is that Sneak Attack scales slowly when Rogue levels are sparse — a Fighter 6 / Rogue 2 has only 1d6 Sneak Attack compared to a Rogue 8's 4d6.

Paladin / Oracle or Cleric: Both classes add their Charisma modifier to saving throws via Paizo's Divine Grace and related abilities, but Divine Grace explicitly applies only to the Paladin class ability — it does not stack with other Cha-to-saves effects from other classes. Players who assume otherwise discover the error at inconvenient moments.

Sorcerer / Dragon Disciple: The Dragon Disciple prestige class (detailed in the Core Rulebook) advances a Sorcerer's bloodline while adding physical combat abilities. This is one of the cleaner prestige class entries because the entry requirements align naturally with a Sorcerer's progression, requiring a draconic bloodline and no levels in a divine spellcasting class.

Decision boundaries

The central tension in any multiclass decision is depth versus breadth. A straight-classed Fighter 10 hits harder, carries more feats, and accesses higher-tier class abilities than a Fighter 7 / Rogue 3. The Rogue levels provide real value — skills, Sneak Attack, Evasion — but they cost three levels of Fighter advancement, including feats like Weapon Training improvements that scale with Fighter level.

Two comparisons frame the decision well:

Dipping vs. full investment: A 1-2 level "dip" into a class to grab a specific feature (such as 2 levels of Paladin for Divine Grace) is a different calculation than splitting levels 50/50. Dips are usually evaluated on a single feature's value. Deep splits require that both class progressions remain functional at lower level totals.

Prestige classes vs. raw multiclassing: Prestige classes in Pathfinder exist specifically to reward multiclass combinations — they advance spellcasting or class features from a previous class while adding new abilities. The Arcane Trickster (requiring Sneak Attack and arcane spellcasting) is one of 6 prestige classes in the Core Rulebook designed around this bridge function. Raw multiclassing without a prestige class destination often plateaus in effectiveness faster.

The general principle, consistent across Paizo's published design notes, is that single-class characters are easier to optimize while multiclass characters reward specific planning around entry requirements and feature interactions.