MLB DFS Stacking Strategy

Why stack at all

A stack is two or more hitters from the same team in the same lineup. The reason it works: baseball scoring is not independent across a lineup. A home run with runners on drives in everyone who was already on base, and a rally inning tends to put up runs for several consecutive batters at once, not just one. If you own three hitters from the inning that goes 4-run, you collect four run-producing outcomes from one real-world event instead of hoping three unrelated players each have a good day separately. That correlation is the entire case for stacking — it raises your ceiling on the nights a team explodes, at the cost of a worse floor on the nights it doesn't.

Primary and secondary stacks

The optimizer's Force a team stack toggle sets a primary stack size (how many hitters from one team, 0–5) and an optional secondary stack from a second team. A 4-3 build — four hitters from your top team, three from a second — is a common GPP shape: two correlated blocks instead of one, so you're not entirely dependent on a single offense showing up.

Turn on consecutive batting-order stacking and the solver only builds stacks out of hitters who bat back-to-back (e.g. spots 3-4-5-6), using whatever you filled into the Order column. Consecutive spots score together more often than a stack scattered across the order — the #3 and #4 hitters are far more likely to be on base for the same rally than the #2 and #8 hitters are.

Cash games vs. GPPs: the exposure trade-off

The tool's Cash and GPP presets set the exposure rules opposite ways, and the reasoning is worth understanding rather than just clicking the button:

Cash (double-ups, 50/50s): stacking off, exposure caps at 100%, no cooldown. You want your single best lineup repeated with only minor tweaks — you're trying to beat roughly half the field, not hit a ceiling, so concentrating on your highest-projected players every time is correct.

GPP (large-field tournaments): stacking on (4 primary, 0 secondary by default), max player exposure capped near 40%, max stack-team exposure near 35%, and a 1-lineup cooldown on both. In a GPP you're chasing a small number of huge-payout finishes against thousands of entries, so running the same core in every lineup just multiplies your downside without raising your ceiling. Capping exposure and adding a cooldown forces the lineup set to be genuinely different from itself, which is what differentiation in a large field actually requires.

Exposure and cooldown, precisely

Max player exposure % caps how many lineups in your set any one player can appear in. Max stack-team exposure % is the same cap applied to whichever team is anchoring your stack. Stack-team cooldown (last K) stops a team that just anchored a stack from anchoring the very next one or two lineups, so a 20-lineup set doesn't quietly turn into the same 4 hitters wearing 5 different uniforms of randomness around them.

Min unique players is the diversity floor: every lineup must differ from every other lineup by at least this many players. Set to 1, back-to-back lineups can share all but one player; raise it and the set spreads out faster, at the cost of the solver working harder to find each additional lineup.

A worked example

Say the Braves are a heavy favorite at home in a hitter's park. For a GPP: enable the stack, set primary to 4 (Braves), leave secondary at 0 or pick a second game's team for a 4-3, cap max stack-team exposure around 35% so you're not all-in on one offense across your whole set, and set min unique players to 2 so your 20 lineups actually cover different combinations of the supporting cast around that stack. For cash: turn stacking off, leave exposure at 100%, and let the solver reuse your top-projected hitters across every lineup — correlation isn't the point when you only need to beat the middle of the field.

Also free: NFL lineup optimizer and its own stacking strategy — same solver, quarterback correlation instead of batting order.