How to Use NBA
Projections for DFS:
Complete Guide

Why DFS Requires Projections

You've been building NBA DFS lineups based on recent stats, matchups, and gut feeling. Some nights you cash, most nights you don't.

The difference between winning and losing DFS players isn't luck. It's projections. While you're manually comparing players based on season averages, winners are using systematic projections that account for minutes, usage, pace, and opponent defense. They know exactly which players are underpriced and which are overpriced.

DFS is fundamentally different from sports betting:

Sports betting: You just need to be right more than 52.4%

DFS: You need to maximize total points within a salary cap AND beat thousands of other lineups

The challenge:

• 10 games = 200+ players available
• Each player has a salary (price)
• You have $50,000 total budget
• Need 8-9 players that score maximum fantasy points

Without projections, you're guessing. With projections, you're calculating value: points per dollar spent.

What DFS Projections Should Include

Core Stats Projections

Points projection: Expected fantasy points for each player. This comes from projected minutes tonight, points per minute rate, rebounds per minute rate, assists per minute rate, steals and blocks per minute, and turnovers (negative points).

Minutes are the foundation. See our guide on How to Make NBA Minutes Projections.

Salary and Value

Player salary: What DraftKings/FanDuel charges for this player

Projected value: Fantasy points per $1000 of salary

Ceiling and Floor

Floor: Worst-case reasonable outcome (injury excluded)
Ceiling: Best-case outcome if everything goes right

Cash games (50/50, double-ups): Prioritize high floor (consistent scorers)
Tournaments (GPPs): Need high ceiling (upside plays)

DFS Scoring vs Sports Betting Props

Key difference: DFS awards points for multiple stats, sports betting is one stat at a time.

DraftKings Scoring

• 1 point: Point scored, rebound, assist, steal, block
• -0.5 points: Turnover
• Bonuses: Double-double (+1.5), Triple-double (+3)

FanDuel Scoring

• 1 point: Point scored, rebound, assist, steal, block
• -1 point: Turnover (harsher than DK)
• No bonuses

Why projections must match the site: A player averaging 1.5 turnovers per game loses 0.75 DK points but 1.5 FD points. Projections need to account for this.

Building NBA Projections for DFS

Step 1: Project Tonight's Minutes

Same as sports betting, but even more critical for DFS.

Factors: Season average minutes, recent trend (last 10 games), injuries to teammates (big minutes increase), back-to-back games (reduced minutes), blowout risk (starters sit if losing big).

For detailed methodology: See How to Make NBA Minutes Projections

Step 2: Calculate Per-Minute Production

For each stat category: Points per minute, rebounds per minute, assists per minute, steals per minute, blocks per minute, turnovers per minute — all calculated from the last 15 games.

Weight recent games more heavily. Last 5 games at 60%, games 6-15 at 40%.

Step 3: Adjust for Opponent and Pace

Opponent defense: Check opponent's ranking vs position. Strong defense = reduce projections 5-10%. Weak defense = increase projections 5-10%.

Pace: Fast-paced game (103+ possessions) = increase all stats. Slow-paced game (96-98 possessions) = decrease all stats.

See our guide: Best NBA Stats for Prop Betting

Step 4: Calculate Fantasy Points

Step 5: Calculate Value

Value = Projected points / (Salary / 1000)

How to Use Projections for Lineup Building

Cash Game Strategy (50/50, Head-to-Head)

Goal: Consistent scoring, beat 50% of field

How to use projections:

1. Filter for players with value >5.0
2. Prioritize high floor (consistent producers)
3. Build balanced lineup (stars + value plays)
4. Avoid high-variance punts

Lineup construction: 2-3 expensive stars ($9000+), 2-3 mid-range ($6000-8000), 2-3 value plays ($4000-6000). Check: does every player project >5x value? If yes, you have a solid cash lineup.

Tournament Strategy (GPPs)

Goal: Unique lineup that scores massive points

1. Identify high ceiling plays (cheap players with 50+ upside)
2. Stack correlated players (same team, benefit together)
3. Fade chalky plays (even if good value)
4. Take calculated risks on low-owned players

Key difference: You need a few players to BOOM. Consistency matters less.

Leverage plays: Backup getting start (low ownership, high ceiling). Player returning from injury (people fade, but healthy). Opponent of team with weak defense (high scoring game).

Injury Impact on DFS Projections

This is where DFS winners make their money.

When Star Sits (Announced 90 Mins Before)

What changes: Direct replacement gets massive value boost. Other starters get moderate boost. Salary doesn't adjust (value spike).

Using SwishLand for DFS Injuries

Manual approach: 30-45 minutes recalculating everything. With SwishLand: Get updated prop projections instantly, convert to DFS in 2 minutes.

Stacking Strategies with Projections

Game Stacking

Concept: Play multiple players from same game. High-scoring games benefit everyone involved. If you project a game to have 240+ total points, stack it.

How projections help: Identify which games have high pace (both teams play fast), weak defenses, injury situations creating opportunities.

Team Stacking

Concept: Play 2-3 players from same team. When a team scores 130 points, multiple players produced. Assists create made baskets.

Correlation examples: PG + Wing scorer (assists feed points). Two forwards on same team (rebounding).

How projections help: Find teams projected to score 120+ points, stack their best value plays.

Ownership Projections and Leverage

Understanding Ownership

Ownership: Percentage of lineups that include a player. High ownership (30%+) = "chalky" — everyone plays them. Low ownership (<10%) = contrarian — few people play them.

Why it matters in tournaments: Playing chalky player who busts = you're fine (everyone has him). Fading chalky player who booms = you're in trouble. Playing low-owned player who booms = massive leverage.

How to Estimate Ownership

High ownership indicators: Star recently announced out (backup is chalk), best value on the slate (obvious play), great matchup + low price, recent hot streak (recency bias).

Low ownership indicators: Back from injury (people fade), bad recent game (recency bias), team on back-to-back (perceived risk), not a "sexy" name.

Projections help: If your projections show a low-owned player has great value, that's leverage.

Common DFS Projection Mistakes

Mistake #1: Using Season Averages

The error: Player averaging 36 fantasy points per game, you project 36.

What you missed: He plays 5 fewer minutes tonight (back-to-back), slow-paced game (fewer possessions), teammate returning from injury (usage down). Actual projection: 28-30 fantasy points.

The fix: Always project tonight specifically, not season average.

Mistake #2: Ignoring Variance

The error: Player projects 40 points, you lock him in. His floor is 22, ceiling is 55. High variance.

For cash games: This is risky. Prefer consistent 38-42 range players. For tournaments: This is fine. You want ceiling.

Mistake #3: Chasing Last Game

The error: Player had 60 fantasy points last night, you must play him. That was an outlier. Regression to mean is real. Tonight projects 38.

The fix: Use 10-15 game samples, not one game.

Mistake #4: Not Updating for Late News

The error: You built lineup at 4pm. At 6:30pm a starter is ruled out. You don't adjust.

The fix: Rebuild lineups 30-60 minutes before lock. The best value often appears in the final hour.

Tools for DFS Projections

Manual Approach

What you need: Minutes projections for all players, per-minute rates for all stats, opponent defense rankings, pace calculations, injury updates, salary data from DK/FD.

Time: 2-3 hours per slate to project 100+ players.

Using SwishLand for DFS

The market price edge: SwishLand shows you two numbers for every prop — the sportsbook's market line and SwishLand's fair value projection. That fair value is your DFS baseline. If the market says a player's points line is 22.5 but SwishLand's fair value is 25.8, you know the market is undervaluing him — and so is his DFS salary.

What SwishLand provides:

• Fair market projections for points, rebounds, assists for all NBA players
• Market line vs fair value comparison (shows where the market is wrong)
• Real-time injury adjustments
• Minutes projections with injury impact

How to use for DFS:

1. Look at SwishLand's fair value projections — these are more accurate than market lines
2. Players where fair value is significantly above market line = undervalued by DFS salaries too
3. Add steals/blocks/turnovers estimates (use player averages)
4. Calculate DFS fantasy points: (28.5 + 9.2 + 6.8 + 1.2 stl + 0.8 blk - 1.5 TO) = 45.0 fantasy points
5. Compare to salary for value calculation

Why the market comparison matters for DFS: DFS salaries are set days in advance based on market expectations. When SwishLand's fair value diverges from the market — because of a late injury, a matchup the market underweights, or a minutes change — the DFS salary hasn't caught up. That's your edge.

Time saved: SwishLand gives you the hardest projections (points, rebounds, assists with injury impacts) AND tells you where the market is wrong. You just add the minor stats.

Conclusion

Using NBA projections for DFS transforms guessing into calculating. Instead of "this player looks good," you have "this player projects 42 fantasy points at $6800 salary = 6.2 points per $1000 value."

What winning DFS players do:

1. Project tonight's minutes (not season average)
2. Calculate fantasy points for each stat category
3. Adjust for pace, opponent, injuries
4. Calculate value (points per $1000)
5. Build lineups around best values
6. Update for late injury news
7. Apply game theory (ownership, stacks, leverage)

Time investment: Manual projections: 2-3 hours per slate. With tools like SwishLand: 20-30 minutes on strategy.

Whether you build projections manually or use tools, systematic projections are the difference between guessing and winning at NBA DFS.