You built a DraftKings lineup with the highest-projected QB. His receivers were too expensive, so you went with cheaper WRs from three different teams. Your QB threw for 350 yards and 4 TDs. You scored 155 points.
The guy in first? He had the same QB — plus two of his receivers. He scored 210. Same QB performance. Sixty more points.
Those four touchdowns scored for the QB in both lineups. But in the winning lineup, they also scored for the receivers who caught them. That's the double-dip. That's stacking. That's the entire game.
Stacking is not a preference in NFL DFS tournaments. It's a requirement. If you analyze the first-place lineups from large-field GPPs across any full NFL season, the overwhelming majority feature a QB paired with at least one of his pass catchers. The ones that don't are statistical outliers — the equivalent of winning the lottery. Possible, but not a strategy.
The reason is structural. DraftKings NFL scoring creates a built-in correlation between a QB and his receivers. Every completed pass generates points for both players. Every passing touchdown generates a massive double-scoring event. When you stack, you capture both sides of these events. When you don't, you're leaving half the points on the table and hoping your unrelated players independently have great games at the same time — which is a much less probable outcome.
WHY QB-WR CORRELATION
IS THE FOUNDATION
Let's quantify exactly what stacking gives you. Consider a single passing touchdown: the QB throws a 25-yard TD pass to his WR1.
WHAT BOTH PLAYERS SCORE
QB scores: +1 point (25 passing yards) + 4 points (passing TD) = 5 points
WR scores: +1 point (reception) + 2.5 points (25 receiving yards) + 6 points (receiving TD) = 9.5 points
Combined: 14.5 DraftKings points from a single play. If both players are in your lineup, you get all 14.5. If only the QB is in your lineup, you get 5. If only the WR is in your lineup, you get 9.5. The stack captures 14.5. An unstacked lineup captures at most 9.5 from that play.
Now multiply across a game where the QB throws 3 touchdowns to stacked receivers. That's roughly 40-45 combined points from touchdown plays alone — plus all the yardage and receptions accumulated throughout the game. A QB who throws for 320 yards, 3 TDs, and rushes for 30 yards might score 28 DraftKings points. His WR1 who catches 7 passes for 110 yards and 2 of those TDs scores 30 points. Together, that's 58 points from two roster spots. Without the stack, you'd have the QB at 28 and some random WR from another team at 14. That's 42. Same QB, 16 fewer points.
The correlation coefficient between a QB and his WR1 is typically 0.7 or higher — meaning their DraftKings scores move together roughly 70% of the time. That's an extremely strong statistical relationship. By contrast, two random WRs from different teams have a correlation near zero. Stacking is simply exploiting the strongest correlation in all of DFS.
THE STACK TYPES
THAT WIN TOURNAMENTS
Not all stacks are created equal. The number of pass catchers you pair with your QB, and who else you include from the game, creates meaningfully different lineup structures with different risk-reward profiles.
QB + 1 WR (SINGLE STACK)
The simplest stack: your QB and his top receiver. This captures the core correlation while leaving the rest of your roster flexible. You have 7 remaining slots to fill with the best available players from other games.
Pros: Maximum salary flexibility. You can afford premium players at other positions. Works well when only one receiver on the team is a clear target hog.
Cons: You're only capturing one side of the passing game. If the QB throws 3 TDs and your stacked receiver catches 1, the other 2 TDs scored for players not in your lineup. Ceiling is lower than double stacks.
Best for: Cash games. Slates where you want a specific QB but his receiving corps is expensive or unclear. When you need salary to pay up at RB.
QB + 2 PASS CATCHERS (DOUBLE STACK)
The tournament standard: your QB plus two of his pass catchers (two WRs, or one WR and the TE). This captures a larger share of the passing game. When the QB has a big day, you're catching more of the touchdowns and yardage across two correlated players.
Pros: Higher ceiling than a single stack. Two receivers means you're more likely to capture the majority of the QB's touchdown passes. In a 4-TD game, having two receivers makes it likely you caught 2-3 of those TDs in your lineup.
Cons: More concentrated salary in one team. If the game goes low-scoring or the QB struggles, three roster spots underperform simultaneously.
Best for: GPP tournaments, especially in games with high over/unders (48+) where the passing game is expected to be active. This is the default tournament stack structure for most winning lineups.
GAME STACK (QB + WR + OPPOSING WR BRING-BACK)
The advanced structure: your QB and his receiver, plus a pass catcher from the opposing team. This creates game-level correlation on top of team-level correlation. You're not just betting on one passing offense — you're betting on the entire game being high-scoring.
Why it works: When a game goes 35-31, both passing attacks are producing. Your QB and WR capture the 35 side. Your bring-back WR captures part of the 31 side. A game that totals 60+ combined points fills your lineup with fantasy production across three or four correlated roster spots.
The bring-back logic: If your QB's team is winning, they might run more in the second half — but the opposing team is throwing to catch up. Your bring-back benefits from that desperation passing volume. If your QB's team is losing, the opponent is running with a lead — but your QB is throwing to catch up. Either way, one side of your game stack is producing.
Best for: GPP tournaments with projected shootouts. Games where both teams have strong passing offenses and the over/under is 48+. This is the highest-ceiling stack structure in NFL DFS.
A GAME STACK DOESN'T NEED ONE TEAM TO DOMINATE. IT NEEDS THE GAME TO EXPLODE.
THE OPPOSING PLAYER
THAT COMPLETES YOUR STACK
The bring-back is the most underappreciated piece of NFL DFS stacking. A lot of players understand QB-WR stacking but treat the rest of their roster as unrelated picks. The bring-back ties your stack to a specific game environment instead of just a specific team.
Who makes a good bring-back? The ideal bring-back is the opposing team's WR1 or a high-target pass catcher. You want someone who benefits when the game script forces their team to throw. If your QB stack is from the favored team, the bring-back is from the underdog — and underdogs throw more when trailing. If your QB is the underdog, the bring-back might be a receiver from the favorite's offense that's putting up points.
Can a running back be a bring-back? Yes, but with nuance. An opposing RB works as a bring-back when the opposing team is expected to play with a lead and run the clock. If your QB stack is on the underdog and the game goes as expected — the favorite builds a lead and runs — your opposing RB gets 25+ carries and your QB gets garbage-time passing volume. Both sides produce. However, RB bring-backs have lower correlation with high-scoring games than WR bring-backs, so they're best used situationally.
Bring-back ownership is typically low. This is a leverage opportunity. Most of the field stacks a QB and his receivers but doesn't add a bring-back from the opposing team. When your bring-back has a big game, you're one of the few lineups that captured both sides of the scoring. The first-place lineup in a big GPP often has a bring-back that nobody else thought to include.
WHEN BREAKING THE RULES
IS THE RIGHT PLAY
A "naked" quarterback is a QB rostered without any of his own pass catchers. This violates the core stacking principle, so why would you ever do it?
Contrarian ownership. If a QB is projected at 25% ownership and his WR1 is at 30%, stacking them creates a highly duplicated combination. Half the field has the same stack. If you play the QB naked and use different receivers from other teams, you differentiate from the 30% of lineups that have the obvious stack. When the QB goes off but his WR1 has a modest game (maybe the TE and WR2 got the touchdowns), your naked QB lineup climbs while the stacked lineups don't get the full double-dip.
Mobile QB in a rushing game script. If your QB's projected value comes largely from rushing — a dual-threat who's expected to run for 50+ yards and a rushing TD — the correlation with his receivers is weaker. His rushing production is independent of his passing production. A naked rushing QB with stacks from other games can be viable when the game environment projects as low-passing-volume.
The caveat: Naked QBs should be the exception, not the rule. Over a full season, stacked QBs outperform naked QBs in GPP finish rates by a significant margin. Use naked QBs as a deliberate contrarian lever in specific spots, not as a default approach.
HOW TO PICK THE
RIGHT GAME TO STACK
The stack structure is the framework. Picking which QB and which game to stack is where the weekly edge lives.
WHAT TO LOOK FOR EVERY WEEK
Vegas over/under above 47. High-total games project more combined scoring, which means more passing touchdowns and more fantasy points for both offenses. Games with over/unders of 50+ are premium stacking environments. Games below 42 are typically avoid-for-stacking territory.
Implied team total above 24. The team you're stacking should be expected to score at least 24 points. Below that and the passing volume might not support a ceiling game for your QB-WR combination.
Pace and pass rate. Some teams throw 65% of the time. Others throw 50%. QBs on pass-heavy teams in neutral or negative game scripts see 35-40 attempts per game. That volume is the engine that drives stacking ceilings. Check the team's season-long pass rate and whether the game environment supports passing (trailing, dome, good weather).
Opposing pass defense. A QB facing a bottom-10 pass defense has a higher ceiling than the same QB facing a top-5 unit. This is obvious but often underweighted — weak secondaries allow more completions, more yards, and more touchdowns.
Receiver target concentration. A team where one WR sees 30% of the targets is easier to stack than a team where targets are split evenly across four receivers. Concentrated target shares make your stacked WR more predictable and more correlated with the QB's production.
Ownership. If everyone is on the same stack, the leverage disappears. Check projected ownership and look for spots where the game environment supports a stack but the field is looking elsewhere. These are the highest-value stacks in any given week.
BUILDING A PORTFOLIO
OF STACKS
If you're entering multiple lineups into a GPP — and you should be if your bankroll supports it — your stacking strategy becomes a portfolio decision. Instead of picking one game and one stack, you're allocating across multiple game environments.
Vary your primary QB across lineups. If you build 10 lineups and 7 have the same QB, you're not diversified. You're just praying for one game outcome. Spread your exposure across 3-4 QBs from different games to cover multiple scenarios.
Vary your bring-backs. Even within the same QB stack, you can diversify by using different bring-back receivers across lineups. Lineup 1 has Allen + Diggs + opposing WR1. Lineup 2 has Allen + Diggs + opposing TE. Same core stack, different game-stack variations.
Mix single and double stacks. Some lineups in your portfolio should be QB + 1 WR (allowing premium spend elsewhere). Others should be QB + 2 WRs (maximizing passing game ceiling). This gives you structural diversity — different ways to win depending on how the week plays out.
Use exposure limits. Even your favorite stack shouldn't appear in every lineup. Cap player exposure at 50-60% across your portfolio. This protects you from a single bad game destroying your entire night.
WHAT GOES WRONG
AND HOW TO AVOID IT
Stacking a low-total game. A QB-WR stack in a game with a 40 over/under has a much lower ceiling than the same caliber stack in a 50-total game. Game environment matters more than player talent for stacking purposes. A mediocre QB in a shootout can outscore an elite QB in a grind-out game.
Stacking the wrong receiver. If a team has three receivers and one sees 12 targets per game while the other two see 5 each, stack the 12-target guy. Stacking a secondary receiver increases your bust rate because his involvement is less predictable. Unless the secondary receiver is significantly cheaper and you're making a deliberate contrarian play, default to the primary target hog.
Ignoring the bring-back. Stacking QB + WR without a bring-back leaves value on the table. The bring-back is what turns a team stack into a game stack, and game stacks have higher ceilings because they capture scoring from both sides of a high-total game.
Same stack in every lineup. If the chalk stack this week is Mahomes + his WR1 and 40% of the field is on it, you need some lineups without that stack. Having it in 3 of your 10 lineups is fine. Having it in 9 of 10 means you're just the field with a different name.
Stacking a run-first team. A team that runs the ball 55% of the time has a lower passing volume ceiling, which means your QB-WR stack has a lower ceiling regardless of opponent. Stack pass-first offenses. Use the RBs from run-first teams as standalone plays in your remaining roster spots.
YOUR QB DETERMINES
YOUR ENTIRE LINEUP
In MLB DFS, stacking is about picking the right team. In NFL DFS, stacking is about picking the right QB — because the QB determines which receivers you stack, which game you're exposed to, and what game script you're betting on. Every other decision in your lineup flows from the QB selection.
Pick the QB first. Stack his top pass catchers. Add a bring-back from the opposing team. Fill the remaining slots with the best available values from other games. That's the structural framework that wins GPP tournaments week after week.
DFS Only's optimizer builds NFL stacks using the same Monte Carlo simulation engine that powers our MLB tools. Correlated QB-WR scoring, game-level correlation, leverage scoring against projected ownership, and automated multi-lineup generation with exposure controls. You pick the game environments. The math builds the stacks.
STACK THE PASSING GAME.
WIN THE TOURNAMENT.
Correlated QB-WR stacks. Game-level simulation. Bring-back logic. Ownership leverage. First day free.
Build Your NFL Stacks →