← All Deep Dives

Harold Fannin Jr.: What David Njoku's Release Actually Cleared Up

WWBy Waiver Wizard Editorial TeamNovember 13, 2026Breakout Candidate5 min read

AI-assisted · Researched and drafted by our automated pipeline, then checked for accuracy before publishing. How we make these

Cleveland released David Njoku during the 2026 offseason. That single transaction is the headline, but it is not the whole story — Fannin had already taken over as the Browns' lead receiving tight end during his first season, before Njoku was ever off the roster. What changed this year is that the last person who could theoretically pull snaps or targets away from him is simply gone. And the early returns back it up: across Weeks 7-8, Fannin caught 16 of 21 targets for 245 yards, including a 10-for-12, 154-yard performance in Week 8 alone.

That is not a modest bump. That is a tight end being fed at wide-receiver volume, in an offense that currently has no wide receiver on the fantasy radar at all.

What Njoku's Departure Actually Removed

Fannin's rookie-year case was already strong on its own terms. In 2025, he played 16 games and caught 72 of 107 targets for 731 yards and six touchdowns, averaging 11.7 PPR points per game and finishing the season as fantasy's TE6. Crucially, he did that while Njoku was still on the roster — Fannin had simply outplayed and out-targeted him. The condition that has now changed is not competition for the starting job; Fannin already won that in year one. What changed is that the backup plan, the injury-replacement outlet, the designed-package complement — all of it — is gone. There is no scenario in 2026 where a snap or a red-zone look that would have gone to Fannin instead goes to Njoku, because Njoku is not employed by this team anymore.

The one condition from 2025 that has not fully resolved is health. Fannin suffered a groin injury during his rookie season that required offseason surgery. That same issue resurfaced in November 2026 — he was limited in practice on November 7 ahead of the New Orleans game and again on November 12 ahead of Houston. Coach Todd Monken's read was unconcerned: "He'll be fine. Just a little sore." Fannin echoed that himself: "I feel good heading into this game. Just a little sore." Soreness that keeps a player on the practice-limited list twice in a six-day window is worth tracking, not dismissing, but it has not yet cost him a game.

Watson, Monken, and an Offense With Nowhere Else to Go

Deshaun Watson is Cleveland's listed 2026 starting quarterback, with Shedeur Sanders behind him. Watson's presence under center matters here less for his individual passing profile than for what it tells us about where the ball is designed to go. Offensive coordinator Todd Monken has built a usage pattern around Fannin that is deliberately flexible — he lines up as a fullback, as a traditional tight end, and as a detached receiver, which is the kind of scheme design teams build around a player they intend to force-feed. Houston coach DeMeco Ryans, previewing a Week 10 matchup against Cleveland, put it directly: Fannin is "a special tight end," and the Browns "create ways to get him targets." That is an opposing coach describing a scheme-level priority, not an incidental usage pattern.

The rest of the depth chart around Fannin confirms the same read. Blake Whiteheart was re-signed and remains the primary rotational tight end behind him, but that is a blocking and depth role, not a competing receiving one. Cameron Brate was added as further tight-end depth, and Joe Royer and Carsen Ryan were both drafted in 2026 — Royer as additional competition, Ryan a seventh-round developmental piece. None of those additions project to meaningfully pull receiving work away from the starter; Cleveland's stated offseason plan was to build quantity and competition behind Fannin, not alongside him. Add in the fact that Cleveland currently has no wide receiver appearing on our team board, and the picture sharpens further: in an offense starting Watson at quarterback with a thin receiver room, Fannin is not just the best option at his position, he may be the best receiving option on the roster, period.

The Week 9 Dip, and Why It Doesn't Change the Verdict

The honest counter-argument starts with Week 9. After the Weeks 7-8 surge, Fannin caught only two passes for 42 yards in Week 9, and both catches came in overtime — meaning in regulation, he was effectively a non-factor. That is a legitimate data point for the skeptical case: perhaps Weeks 7-8 reflected game-script or matchup anomalies rather than a durable role change, and perhaps the groin issue that limited his practice reps in November is already sapping some of his usual involvement. Tight end volume is notoriously spiky even for entrenched starters, and a fact-based case has to acknowledge that one bad week sitting right next to two huge ones is not nothing.

The answer is that role and opportunity are more durable indicators than any single week's box score. Fannin remains atop Cleveland's depth chart, the Njoku competition is permanently removed rather than just managed, and the Browns' own coaching staff and an opposing head coach are both describing him in the language of a focal point, not a complementary piece. A single quiet week inside a stretch that otherwise featured 16 targets in two games is consistent with normal tight end variance, not evidence that the underlying role has reverted. The 2025 track record — a TE6 finish built before Njoku's roster spot was even vacated — was already a ceiling case. Clearing the last internal competitor only raises that ceiling.

⚠️ Note:The groin issue is the one variable that can unwind this case fastest. Two straight weeks of practice limitations in November, on an injury that already required offseason surgery, is worth monitoring every Wednesday injury report the rest of the season.

The Roster Move

Fannin should be rostered and started as a weekly TE1 in all formats, and owners who have been treating him as streaming depth after the Week 9 dip are mispricing the role. The opportunity is not contingent on matchups or game script in the way a committee back or a WR3 might be — it is a function of Cleveland releasing the one player who could have challenged him for it. If there is a buying window, it is now, immediately after a down week when some fantasy managers will overreact to one quiet box score. The health flag is real and worth tracking on the injury report, but on role alone, this is as clean a target-share argument as exists at the position heading into the stretch run.

Get waiver wire alerts built around your actual league

Connect your ESPN or Sleeper league in under a minute. Free to start.

Start for Free