Fantasy Baseball Strategy: Categories, Counting Stats, and Ratios

Fantasy baseball scoring breaks into two fundamentally different philosophies — categories leagues that reward breadth across a fixed set of statistical buckets, and points leagues that reduce everything to a single number. This page focuses on the categories format: how counting stats and ratio stats interact, why that interaction shapes roster construction from the first round of a draft, and where managers consistently make mistakes that cost them category standings over a full season.

• 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 categories league — typically called a "roto" or rotisserie league — ranks all teams in a pool from first to last in each statistical category, then assigns points based on rank. A 12-team league playing 10 categories awards 12 points for first place in home runs, 11 for second, and so on down to 1 for last. At season's end, the team with the most cumulative ranking points wins. No single game, no single series, no single week determines anything — the whole season functions as one long, slow argument between rosters.

The categories themselves split into two mechanical types that behave completely differently: counting stats, which accumulate additively over the season, and ratio stats, which are calculated from the relationship between two counting stats and can move in either direction with each new game.

The standard 5×5 roto format — popularized when rotisserie baseball was formalized by the rules codified in the 1984 book Rotisserie League Baseball by Glen Waggoner and colleagues — uses Home Runs, Runs Batted In, Stolen Bases, Runs Scored, and Batting Average for hitters, and Wins, Saves, Strikeouts, ERA, and WHIP for pitchers. Variations expand this to 6×6, 7×7, or custom categories, but the counting/ratio split remains the defining structural feature regardless of format. The fantasy baseball strategy hub covers format selection and league-type tradeoffs in broader detail.

Core mechanics or structure

Counting stats work exactly as the name implies. Each home run adds 1 to the HR total. Each stolen base adds 1. The category standings shift upward when a player contributes and stay flat when he doesn't. Critically, counting stats can never hurt a roster — a player who goes 0-for-4 with no RBI contributes zero to counting categories, nothing more.

Ratio stats operate on a different logic entirely. ERA (Earned Run Average) is calculated as (Earned Runs × 9) ÷ Innings Pitched. WHIP (Walks plus Hits per Inning Pitched) is (Walks + Hits) ÷ Innings Pitched. Batting Average is Hits ÷ At-Bats. These numbers represent a running weighted average across the entire roster.

The consequence is significant: a pitcher with a 7.20 ERA who throws 6 innings doesn't just fail to help the ERA category — he actively damages a roster's ERA. If the rest of a pitching staff has combined for a 3.40 ERA over 600 innings, adding 6 innings of 7.20 ERA work will drag the combined ERA upward. The formula doesn't forgive; it recalculates.

This is why roster construction in rotisserie versus head-to-head formats must account for the distinction explicitly. A deep bench of streaming pitchers who average a 4.80 ERA can erode a season's worth of ratio-category work in a single roster week.

Causal relationships or drivers

Three causal dynamics govern how categories interact across a full season.

Volume amplifies counting stat leads. A team that drafts 3 power hitters who each hit 38 home runs builds a 114-HR contribution from those 3 roster spots. A team that drafts 6 hitters averaging 20 home runs gets 120 — a higher total from less concentrated talent. This matters during the draft because positional scarcity can force managers to reach for position-specific counting stat producers at a cost to depth.

Innings pitched is the hidden multiplier for pitching ratio stats. A staff ERA is not an average of individual ERAs — it is a combined calculation across all innings. A staff that accumulates 1,400 innings over a season has 1,400 units of ERA buffer. A staff that logs only 1,050 innings has less buffer, meaning each bad outing carries proportionally more weight. Streaming-heavy strategies (addressed at streaming strategies) must account for this.

Stolen bases are inelastic. Unlike home runs or strikeouts, stolen base opportunities depend on lineup position, manager tendencies, and player health. A 40-steal player is genuinely rare — Fangraphs' leaderboards from 2023 showed only 8 MLB players reached 40 stolen bases that season — making the category behave more like a fixed supply auction than a market with broad alternatives.

Classification boundaries

Not all categories sit cleanly in one type. Wins is a counting stat, but it depends on run support, bullpen performance, and managerial decisions in ways ERA and WHIP do not. A pitcher can throw 7 scoreless innings and receive a no-decision; the Win never accumulates despite elite ratio-stat contribution. This makes Wins a counting stat with ratio-stat volatility — a quirk that has driven many leagues to replace it with Quality Starts or Innings Pitched as a standalone category.

Holds, where used as a category, behave similarly — a counting stat that depends on leverage decisions made by managers rather than pitcher performance.

Categories can also be positively correlated (high strikeout pitchers tend to have lower WHIPs) or negatively correlated (stolen base specialists often hit in the .260-.270 batting average range, trading contact consistency for speed). Recognizing these correlations shapes draft targeting — a draft strategy overview that ignores category correlation is optimizing in a vacuum.

Tradeoffs and tensions

The ratio/counting divide creates a persistent roster construction tension: depth or ceiling?

In counting stats, more roster slots devoted to a category means more accumulation. In ratio stats, more roster slots devoted to pitching only matters if those pitchers are better than the current roster average. Adding a pitcher with a 4.50 ERA when the resource ERA is 3.60 hurts, even if that pitcher contributes positive counting-stat value in strikeouts and wins.

This creates an asymmetric risk structure. A manager who streams aggressively to chase wins and strikeouts accepts ERA/WHIP variance as a cost of doing business. A manager who locks in a stable, high-quality 8-man pitching staff sacrifices counting-stat accumulation in wins and strikeouts but protects ratio floors.

The points league versus category league comparison makes this tension visible: in a points league, there is no ratio category — a 7.20 ERA outing still generates strikeout points. Category leagues penalize bad ratio stats in a way that points leagues structurally cannot.

A second tension: the value of a category win is always 1 ranking point, regardless of margin. Finishing first in home runs by 12 home runs earns the same 12 ranking points as winning by 1. This creates strategic incentives to abandon hopeless categories and double down on winnable ones — a practice called "punting" that has its own risk profile, explored further in roster construction principles.

Common misconceptions

Misconception: ERA and WHIP can be fixed by adding a good pitcher mid-season.
Reality: The mathematics of a combined ratio stat means mid-season corrections require both a high-quality addition and enough remaining innings for that quality to matter. Adding a 3.00 ERA pitcher in September with 6 weeks remaining, when the resource has already logged 900 innings at a 4.20 ERA, produces a mathematically small ERA improvement — the 900 innings of prior context overwhelm the new contribution.

Misconception: Batting average and on-base percentage are interchangeable.
Reality: In standard 5×5, only Batting Average appears — OBP is not a category. Walks improve OBP but contribute zero to batting average. A player with a .240/.370 slash line is a batting average liability and an OBP asset in the same player. Leagues that add OBP as a 6th category fundamentally change the value of walk-heavy players like a Mike Napoli type.

Misconception: A player who "helps in four categories" is always a good add.
Reality: If that player is a catcher hitting .231 and those four categories include batting average, the addition pulls batting average down while adding counting stats elsewhere. Net category impact depends on current roster composition, not on the player's absolute category count.

Checklist or steps

Category audit process — conducted at any roster evaluation point:

1. For ratio stat categories ranked 9th–12th, calculate the current roster's combined average and identify which active players are below the roster's own ratio average.

Reference table or matrix

Counting Stats vs. Ratio Stats: Behavioral Comparison

The advanced stats for fantasy reference covers how metrics like xERA, xFIP, and Hard-Hit Rate map onto category-league decisions for managers using projection systems to inform roster moves.