Should I Drop Stefon Diggs?

Short Answer

Dropping Stefon Diggs can make sense in shallow redraft leagues if he is no longer startable and clearly better options are available on the waiver wire. In deeper, keeper, or dynasty formats, cutting him is usually a mistake because his long-term trade value and name recognition remain meaningful. Before dropping, evaluate your bench size, league format, injury status, the trade market, and the quality of available replacements.

When It Makes Sense

  • Good fit: In shallow redraft leagues with small benches and active waiver wires, dropping Diggs is defensible when his role, target share, or quarterback situation has clearly declined and he is no longer in your starting lineup. If a reliable replacement — such as a receiver getting steady targets, a running back with an expanded role, or a useful streaming option — is available and you need immediate production, freeing the roster spot can be more valuable than holding a declining name. The key is whether the player you would add projects to outscore Diggs over the next several weeks, not merely one favorable matchup.
  • Good fit: If Diggs is expected to miss multiple games and your league does not offer an injured reserve slot, carrying him can cost you weekly wins during a playoff push. Rebuilding or bubble teams may not have the luxury of stashing an injured bench player, so dropping him to chase short-term points becomes a rational risk. Just be sure you have a clear plan to replace him and accept that he may rebound later in the season.

When You Should Avoid It

  • Warning sign: Do not drop Diggs simply because of a quiet week or two if he still plays a high snap share and draws targets. Wide receivers are notoriously volatile, and poor games can follow a productive stretch due to weather, defensive matchups, or game script. Cutting him during a slump often leads to regret when he returns to WR2 or flex value, and it can hand an opponent a free upgrade.
  • Warning sign: In deeper leagues, keeper leagues, or dynasty formats, Diggs usually carries more value as a trade asset or bench hold than as a waiver-wire donation. His established career production means another manager may still pay something for him during a downturn. Dropping him for nothing forfeits that leverage and can waste future draft capital or keeper rights, especially when your league rewards long-term roster construction.

Pros and Cons

Pros

  • Roster flexibility. Dropping Diggs opens a bench or active spot so you can stream defenses, kickers, quarterbacks, or matchup-dependent skill players. That flexibility is most valuable in leagues with short benches or during bye weeks when every active roster slot matters.
  • Chase upside. If a breakout rookie, a receiver promoted due to injury, or a high-target waiver add is available, dropping a fading veteran can raise your weekly ceiling. The opportunity cost of holding Diggs increases when better options are sitting unclaimed.

Cons

  • Strengthens opponents. In most leagues, dropped players become free agents or enter waivers where a rival can claim them. If Diggs rebounds on another roster, you not only lose his points but may face them in a head-to-head matchup. That hidden cost matters more in competitive leagues with active managers.
  • Loses trade and rebound value. Once a player is dropped, you no longer control him and cannot extract any trade return. A manager thin at wide receiver might have offered a useful piece or future asset. Dropping should be a last resort after the trade market and bench options are exhausted.

Decision Checklist

  • Is Diggs still startable in my format, or is he locked on my bench with no clear path back into the lineup?
  • Does the waiver wire offer a player with a higher projected floor or ceiling over the next two to four weeks?
  • Have I offered Diggs in trade to at least one or two league mates, and would dropping him help a direct rival more than it helps me?

Alternatives to Consider

Before dropping Diggs, consider whether your league has an injured reserve or taxi squad where he can sit without costing a bench spot. Benching him is usually safer than cutting him, especially in leagues with large rosters or Best Ball formats where you do not set lineups manually. Trading is often the best outcome: package him with another piece for an upgrade, or sell him as a buy-low candidate to a manager who believes in a bounce-back. If you must drop, decide whether the replacement is a short-term rental or a long-term add, and plan your next few waiver moves accordingly.

Final Recommendation

In most redraft leagues with shallow benches, dropping Stefon Diggs is reasonable if he has become unstartable, his target share or role has clearly faded, and a better waiver option is available. In deeper redraft, keeper, or dynasty leagues, avoid dropping him unless injuries force your hand; instead, trade or bench him and monitor his usage. The right move depends on your league format, roster size, playoff timeline, and the quality of players on your waiver wire. If your league involves significant entry fees or side wagers, consult current expert rankings, injury reports, and projection models before making high-stakes roster moves.

FAQ

Should I drop Stefon Diggs?

It depends on your league format and roster needs. In shallow redraft leagues with small benches, dropping him is reasonable if he is not startable and a better waiver option exists. In deeper, keeper, or dynasty leagues, you should usually try to trade or bench him instead.

What should I consider before I drop Stefon Diggs?

Check whether Diggs still has a meaningful role and target share, whether your waiver wire offers a higher-floor or higher-ceiling player, and whether a league mate might trade for him. Also consider your league type, playoff timeline, bench size, and any injured reserve rules.

References

  1. NFL.com official player news and injury reports
  2. ESPN Fantasy Football rankings and projections
  3. FantasyPros aggregated expert rankings and waiver-wire advice

Related Terms

Leave a Reply

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