Who Should I Drop in Fantasy Football? A Data-Based Decision Guide

We are reader supported. When you purchase through links on our site, we may earn an affiliate commission. Also, as an Amazon affiliate, we earn from qualifying purchases.

The best player to drop in fantasy football is usually the player with the weakest combination of current role, future opportunity, and replacement value—not simply the player who scored the fewest points last week.

Before dropping anyone, check four things:

  1. Is the player actually getting snaps, routes, carries, or targets?
  2. Is their role growing or shrinking?
  3. Would you realistically start them in the next 2–3 weeks?
  4. Is the waiver player you want more valuable than the player you are cutting?

If a player has low usage, no clear path to a larger role, and is easily replaceable on waivers, they are usually your best drop candidate.

Quick Answer: Who Should You Drop First?

When you need a roster spot, evaluate players roughly in this order:

Usually easier to dropUsually harder to drop
Second kickerStarting RB with strong usage
Second defenseWR with high route participation and targets
Backup QB in many 1QB leaguesStarting QB in Superflex
Low-usage TEHigh-usage TE
WR buried on depth chartRookie whose role is clearly increasing
RB needing multiple injuries to matterDirect backup to a high-volume RB
Injured player with no near-term return and no IR spotInjured elite player with a realistic return

This is not a universal ranking. League size, scoring format and waiver depth can completely change the answer.

Step 1: Check Your League Before Dropping Anyone

A player can be droppable in one league and valuable in another.

1QB vs. Superflex

Quarterback value changes dramatically.

In a typical 1QB league with useful quarterbacks available on waivers, carrying multiple mediocre quarterbacks can waste bench space.

In Superflex, starting quarterbacks are much harder to replace. A low-end NFL starter can therefore be worth holding even when his fantasy production is disappointing.

PPR vs. Standard

PPR scoring increases the value of players who consistently earn targets.

A running back catching passes or a receiver earning high target volume can remain useful without scoring touchdowns.

That makes usage particularly important.

Bench Size

A shallow bench means better players remain available on waivers.

That makes aggressive roster churn more reasonable.

A deep league creates the opposite problem: once you drop a player, there may be very little usable talent available to replace him.

Step 2: Look at Usage Before Fantasy Points

This is the biggest improvement you can make to your drop decisions.

Fantasy points describe what already happened.

Usage helps explain whether it is likely to happen again.

Current fantasy analysis routinely tracks metrics including snaps, routes run, targets per route run, carry share and red-zone usage because these reveal how teams are actually using players. PFF’s current Usage and Production Report, for example, explicitly tracks those metrics to identify role changes relevant to waiver and rest-of-season decisions.  

For Running Backs

Look at:

  • snap share
  • carries
  • targets
  • routes
  • red-zone opportunities
  • goal-line work

A running back who scored four fantasy points but handled most of his team’s backfield opportunities may still be a strong hold.

A backup who happened to score a touchdown on five touches may be much easier to drop.

For Wide Receivers and Tight Ends

Look at:

  • routes run
  • route participation
  • targets
  • targets per route run
  • red-zone usage

Targets per route run (TPRR), for example, measures how often a player earns a target when actually running a route.

The Fantasy Footballers’ 2026 TPRR guide uses roughly 20–25% as a fantasy-relevant range, 25–30% as excellent and 30%+ as elite, while explicitly warning that TPRR must be considered alongside total routes. A player earning targets on 25% of routes but barely getting on the field can still have little fantasy value.  

That is exactly why one metric should never determine a drop by itself.

Step 3: Separate Bad Production From a Bad Role

Consider two receivers:

Receiver A

  • runs routes on nearly every passing play
  • continues earning targets
  • has not scored a touchdown
  • produced two disappointing fantasy weeks

Receiver B

  • plays limited snaps
  • runs relatively few routes
  • caught one long touchdown last week
  • rarely earns targets

Receiver B may have scored more fantasy points recently.

Receiver A can still be the better player to hold.

The question is:

Did the player have a bad fantasy week, or did his actual role deteriorate?

That distinction prevents many bad drops.

Step 4: Ask Whether You Will Actually Start the Player

Bench players need a purpose.

For every borderline player, ask:

Under what realistic circumstances would I put this player into my starting lineup?

Good answers include:

  • during my starter’s bye week
  • if the starting RB ahead of him gets injured
  • if his rising role continues
  • in a favorable matchup next week

A bad answer is:

Maybe something happens eventually.

Players without a plausible route into your lineup are roster cloggers.

Those are the players you can replace with higher-upside waiver options.

Step 5: Compare the Drop to the Waiver Addition

Never evaluate a drop in isolation.

You are making an exchange:

Player being dropped → Player being added

Suppose your WR5 has mediocre usage.

Dropping him simply because you are frustrated accomplishes nothing.

But if the waiver wire contains a receiver whose snap share and routes just increased sharply, the comparison changes.

Current weekly waiver analysis follows exactly this logic. FantasyPros’ early Week 5 coverage, for example, evaluates available players based on injuries and the opportunities those injuries could create rather than simply ranking whoever scored the most points the previous week.  

The correct question is therefore not:

Is this player bad?

It is:

Is the player I can add more valuable to my roster?

Players You Can Usually Consider Dropping

Backup Quarterbacks in 1QB Leagues

If you have a reliable starter and comparable quarterbacks remain available, the backup QB can be expendable.

The bench spot may have more upside when used on an RB or WR whose role could grow.

This changes completely in Superflex.

Second Kickers and Defenses

There is rarely a strong reason to hold two kickers.

Many fantasy managers also stream defenses based on opponent rather than holding multiple units.

Those positions are often the first place to look when you urgently need a roster spot.

Players Whose Roles Are Shrinking

A declining role is much more concerning than one bad fantasy score.

PFF’s September 2026 usage report, for example, highlighted several veteran receivers whose playing time declined while younger players gained opportunities. That type of underlying change matters more for future fantasy value than name recognition.  

Watch for:

  • fewer snaps
  • fewer routes
  • loss of goal-line work
  • falling target share
  • another player moving ahead on the depth chart

If the trend persists and there is no obvious reason it will reverse, dropping becomes easier.

Low-Upside Bench Players

A player who gives you eight points when everything goes right but rarely enters your lineup can be less valuable than a volatile backup who could become a major starter after one depth-chart change.

Bench value is not only about current points.

It is also about what could change the player’s value.

Players You Should Be Careful About Dropping

Running Backs With Real Workloads

Running back opportunity is difficult to replace.

If a player continues receiving meaningful carries, routes, targets or red-zone work, do not cut him simply because touchdowns have not arrived.

Receivers Who Continue Earning Routes and Targets

A receiver can go through disappointing fantasy weeks while maintaining a healthy role.

If routes and targets remain strong, investigate before dropping.

Rookies Whose Playing Time Is Increasing

Early-season rookie roles can change quickly.

This is particularly relevant now because weekly usage reports frequently identify young players moving ahead of veterans as teams learn what their new players can handle.  

The direction of the trend matters.

40% → 55% → 70% of opportunities is very different from:

80% → 60% → 40%.

High-Value Handcuff Running Backs

Some backup running backs have little standalone value but enormous contingent value.

If one injury would clearly make the player his team’s primary back, he may deserve a bench spot—particularly when your roster is already strong.

Don’t Drop a Player Because of One Bad Week

Fantasy football contains enormous week-to-week variance.

Touchdowns are especially dangerous to chase.

A player can receive excellent usage and fail to score.

Another can receive poor usage and score on his only major opportunity.

If you swap the first player for the second solely because of last week’s fantasy points, you may be buying yesterday’s result instead of tomorrow’s opportunity.

Use at least:

production + usage + role trend + roster context

before making the decision.

Don’t Let Draft Position Decide Either

The opposite mistake is holding a player because you drafted him early.

Once the season begins, draft cost is sunk.

If a player has clearly lost his role, the fact that you selected him in Round 7 instead of Round 14 does not create future fantasy points.

Evaluate the roster you have today.

Injured Players: Drop or Hold?

Start with IR.

If your league allows the player to be moved to an injured-reserve slot, use that slot before cutting someone useful.

Without IR space, ask:

How long is the expected absence?

How valuable will the player be when healthy?

Can my team survive while waiting?

What player can I add immediately?

A 4–0 team with strong starters can afford more patience than an 0–4 team struggling to field a competitive lineup.

The player’s value has not changed—but the team’s time horizon has.

A Simple Drop Score

You can make this even easier.

Give the player one point for each statement that is true:

  • I probably won’t start him in the next three weeks.
  • His playing time or opportunities are declining.
  • He has no clear path to a larger role.
  • Similar players are available on waivers.
  • The player I want to add has more upside or immediate utility.

0–1 points: Usually hold.

2–3 points: Borderline; compare alternatives carefully.

4–5 points: Strong drop candidate.

This is not a projection model. It is simply a checklist that forces you to evaluate the factors that matter instead of reacting emotionally.

Example: Production vs. Opportunity

Imagine two running backs.

RB ARB B
Last week’s fantasy points614
Carries144
Targets41
Red-zone opportunities31
Role trendStableLimited

RB B looks better if you sort your roster by last week’s fantasy points.

RB A looks better if you evaluate opportunity.

The numbers are hypothetical, but the example demonstrates the decision process:

Do not confuse fantasy results with fantasy role.

Your Weekly Drop Routine

You do not need the dozens of checks in the old version of this article.

Once waivers approach:

1. Check injuries.

An injury can instantly change a backup’s value.

2. Check usage.

Look at snaps, routes, carries, targets and red-zone work.

3. Rank your bench from least to most valuable.

Know your first drop before submitting waiver claims.

4. Compare every drop with the actual player being added.

A roster move should improve either your starting lineup, depth or upside.

5. Check news again before waivers process.

Roles can change quickly after injury updates or coaching announcements.

Where to Check Current Usage

Because player roles change every week, an evergreen article should not pretend that a static list of “drop these players” will remain accurate.

For current decisions, combine the framework above with fresh weekly data.

PFF publishes current usage reports covering snaps, routes, targets, carry share and red-zone involvement.  

FantasyPros publishes weekly waiver-wire coverage including add, stash and drop considerations.  

The Fantasy Footballers also publishes weekly waiver, snap-count and target-trend analysis.  

Use those current inputs with your own league settings.

A generic ranking cannot know whether your league is 8-team PPR or 14-team Superflex.

FAQ

Should I drop a player after two bad games?

Not automatically.

Check whether snaps, routes, carries and targets also declined. Poor production with a stable role is different from poor production caused by losing playing time.

Should I drop my backup QB?

In many 1QB leagues, possibly—especially if comparable quarterbacks remain available.

In Superflex, starting quarterbacks are substantially harder to replace.

Should I drop a defense with a bad matchup?

Streaming D/ST is reasonable when useful alternatives are available. There is usually little reason to sacrifice a valuable RB or WR stash merely to hold multiple defenses.

Should I drop an injured player?

Use IR first when possible.

Without an IR spot, compare the expected absence and post-injury value with your immediate need to win games.

Should I drop a rookie who hasn’t produced?

Look at the role trend.

A rookie earning progressively more snaps and routes can be worth holding even before the fantasy points arrive.

Bottom Line

When deciding who to drop in fantasy football, stop asking:

“Who scored the fewest points?”

Ask:

“Who has the weakest future value relative to what I can add?”

Start with league format and waiver depth. Then examine real usage—snaps, routes, carries, targets and high-value opportunities. Separate temporary poor production from an actual loss of role.

The easiest players to drop are generally those who:

do not enter your lineup, are losing opportunities, have no realistic path to a larger role, and can be replaced easily.

The hardest players to drop are those whose current fantasy points look disappointing but whose underlying opportunities remain strong.

Fantasy football changes every week.

Your decision framework should remain stable even when the names change.

Leave a Comment

Your email address will not be published. Required fields are marked *