Brandin Cooks Is Still Hanging Around, but Does He Matter in Deep Dynasty?

By Quan

Brandin Cooks is the NFL’s equivalent of a late-night infomercial knife set. Just when you think you have seen the last of him, he pops back onto the screen, slices through a defensive backfield and demands your attention all over again. You can trade him, waive him or leave him sitting on the open market as an unsigned free agent entering the heart of the 2026 offseason, but the man has never been particularly interested in fading quietly into obscurity.

At 32 years old, Cooks is sitting exactly 189 yards away from reaching 10,000 career receiving yards, which would add another notable milestone to a career that has already included productive stops with six different franchises. He has never been the kind of receiver who inspired widespread loyalty from one organization, but he has been remarkably persistent, producing across different quarterbacks, systems and locker rooms while repeatedly finding his way back into NFL relevance.

Now, after spending the final stretch of the 2025 season with Buffalo, Cooks has made it clear that he would welcome another opportunity to play with Josh Allen and the Bills. That does not suddenly make him a redraft sleeper, nor does it mean dynasty managers should rush to clear a roster spot for him, but his familiarity with Buffalo and the specific role he played there give him a more credible path back onto an NFL field than most unsigned receivers his age.

The question is not whether Brandin Cooks can become a weekly fantasy starter again. He almost certainly cannot. The more useful question is whether he remains worth carrying at the very end of a deep dynasty roster while the rest of the league treats him as though his career is already over.

The 189-Yard Carrot

Motivation is not a fantasy statistic, and managers should be careful not to treat personal milestones as though they automatically create targets. Still, they matter as part of the broader picture when evaluating an aging veteran who has already earned plenty of money and could easily decide that another offseason is not worth the trouble.

For Cooks, the remaining incentive is obvious. He has played 173 regular-season games, catching 734 passes for 9,811 yards and 60 touchdowns. Reaching 10,000 yards would not transform him into a Hall of Fame lock, but it would place a clean numerical capstone on a career that has lasted far longer and traveled much farther than most receivers drafted in his era.

His 2025 production will not convince anyone that a late-career resurgence is coming. Cooks appeared in 15 games, catching 24 of 36 targets for 279 yards without scoring a touchdown. He spent the first 10 games of the season with New Orleans, where he managed 19 receptions for 165 yards before being waived in November.

Buffalo added him for the stretch run, and while the overall volume remained limited, he did show that there was still enough speed and route savvy left to contribute in a specialized role. His regular-season Bills production amounted to only five catches for 114 yards, but almost all of it came in one reminder of what he could still offer. In Week 17 against Philadelphia, Cooks caught four passes for 101 yards on six targets, stretching the field and creating the kind of explosive plays Buffalo had hoped to manufacture when it brought him into the building.

He added three catches for 58 yards in Buffalo’s Wild Card victory over Jacksonville, including a 36-yard reception on the eventual game-winning drive. A week later, his season ended in controversy against Denver when he appeared to secure a 43-yard reception in overtime before Ja’Quan McMillian wrestled the ball away as the two players went to the ground. The play was upheld as an interception, ending what might otherwise have become Buffalo’s best opportunity to move into scoring range.

Cooks has spoken openly about the disappointment of that loss and his desire to return. That does not guarantee the Bills share the same enthusiasm, but it does explain why Buffalo remains the most logical destination if his career continues.

Why Buffalo Still Makes Sense

The most important part of the Buffalo argument is not that Cooks once played in a related offensive system with New Orleans. It is that he spent the final five games of the 2025 regular season and the entire playoff run working directly with Josh Allen, Joe Brady and Buffalo’s offense.

That experience gives him a legitimate advantage over an outside veteran who would be arriving for the first time. Cooks already understands the core terminology, knows how Allen prefers to attack certain coverages and has firsthand knowledge of the role Buffalo envisioned for him. The offense may continue evolving under Brady and offensive coordinator Pete Carmichael, but Cooks would not be walking into the building with a blank playbook and a room full of strangers.

That matters because Buffalo would not be signing him to become a featured receiver. The Bills would be considering him for a narrow, complementary role built around vertical routes, veteran reliability and occasional matchup-specific packages. A player who already spent two months practicing those concepts and developing timing with Allen is easier to plug into that role than another aging free agent who would need to learn everything from the ground up.

Carmichael’s presence only strengthens the connection. Cooks spent the first three seasons of his career in New Orleans, where Carmichael served as offensive coordinator, and he returned to that offense for the first part of 2025. Although Buffalo is not simply importing the old Saints playbook, the shared conceptual background gives Cooks another layer of familiarity that could help him transition into whatever adjustments Brady and Carmichael make this offseason.

The Bills do not need Cooks to teach the offense how to function. They would need him to understand a limited assignment, execute it correctly and provide another receiver capable of threatening defenses vertically when the matchup calls for it. He has already demonstrated that he can do exactly that.

The Buffalo Depth Chart Is Crowded, but Not Closed

Buffalo’s receiver room is deeper than it was when Cooks arrived last November, although the sheer number of names should not be mistaken for an impenetrable wall of proven talent.

The Bills made their largest offseason move at the position by acquiring D.J. Moore from Chicago in exchange for the 60th overall pick, while also receiving the 165th selection in the deal. Buffalo subsequently guaranteed $15.5 million of Moore’s 2028 base salary, further demonstrating its long-term commitment to placing him at the top of the receiver hierarchy.

Moore is coming off a disappointing 2025 season by his standards, finishing with 50 receptions for 682 yards and six touchdowns in a Bears offense that struggled to produce consistent passing-game rhythm. Buffalo is betting that Josh Allen and a more stable offensive environment can restore some of the production Moore displayed earlier in his career, and he should enter the season as the Bills’ primary perimeter receiver.

Khalil Shakir also has a secure role after catching 72 passes for 719 yards last season, while Keon Coleman remains part of the team’s long-term plans despite a quiet sophomore campaign in which he recorded 38 receptions for 404 yards. Joshua Palmer will also compete for snaps after failing to establish himself as a major offensive piece in 2025.

Buffalo then added UConn receiver Skyler Bell in the fourth round with the 125th overall pick. Bell produced 101 receptions for 1,278 yards and 13 touchdowns in his final collegiate season, led the FBS with seven 100-yard receiving games and ran a 4.40-second 40-yard dash during the pre-draft process. His ability to separate and create after the catch gives Buffalo another developmental option who could earn immediate rotational work.

That is a real competition, but it is not a depth chart filled with five established receivers who have already secured their weekly snaps. Moore and Shakir are the safest bets for consistent involvement, while Coleman, Palmer and Bell will compete for the remaining opportunities. The back end of the room still includes players whose primary value may come on special teams or as injury insurance rather than as trusted offensive contributors.

Cooks would not need to leapfrog Moore or Shakir to justify a roster spot. He would need to prove that his experience, familiarity and specialized vertical role offer more immediate value than the final receiver Buffalo would otherwise keep. Given what he showed during the closing stretch of last season, that is at least a plausible outcome.

Bell does not eliminate that possibility simply because Buffalo invested a fourth-round pick in him. The rookie deserves a chance to earn meaningful snaps, but Day 3 draft capital does not automatically guarantee an immediate offensive role, nor does it prevent a contender from carrying a veteran who performs a different assignment. Bell can be part of the future while Cooks serves as a short-term situational option.

The Fantasy Question Is Strictly About Dynasty

There is no meaningful redraft case for Brandin Cooks right now.

He is unsigned, his most likely NFL role would involve limited weekly volume and Buffalo already has several receivers ahead of him in the target hierarchy. Even if he signs before training camp and earns a spot on the final roster, his fantasy production would probably depend on occasional deep receptions rather than steady targets.

That profile does not belong on a normal redraft bench. Managers in standard 10- or 12-team leagues should be using their final roster spots on backup running backs, emerging young receivers or players whose paths to consistent volume are considerably clearer. Cooks would require too many things to break correctly before he became someone you could trust in a weekly lineup.

The dynasty calculation is different, although only at the deepest end of the format.

In leagues with roughly 20 to 25 roster spots, Cooks can still be ignored. The opportunity cost is too high when dynasty managers can instead carry younger players who have a chance to increase in value over multiple seasons. Cooks is unlikely to produce enough to become a meaningful trade asset, and his age places a hard ceiling on whatever market might develop after he signs.

In leagues with 30 or more roster spots, however, the waiver wire often consists almost entirely of players who will never receive an offensive snap. That is where Cooks becomes defensible as a final-bench stash. He already proved last season that he could step into Buffalo’s offense and produce an occasional explosive performance, and his existing relationship with the team gives him a realistic chance of returning if the Bills decide they want another veteran field stretcher.

The upside should not be exaggerated. Cooks is not likely to sign with Buffalo, catch one long touchdown and suddenly command a meaningful rookie pick in trade negotiations. Some contender may eventually view him as a small throw-in or emergency depth option, but his primary value would come from remaining available when injuries or bye weeks create temporary lineup problems.

That is not exciting, but dynasty depth rarely is. The players occupying the final spots on a 30-man roster do not need to have league-winning upside. They need a plausible path to earning snaps, and Cooks still has one.

How Dynasty Managers Should Handle Him

The correct approach depends entirely on roster size.

Managers in standard dynasty leagues should leave Cooks on waivers unless he signs and Buffalo suffers an injury that materially changes the depth chart. There is no reason to sacrifice a younger asset simply because Cooks is close to a career milestone or once produced a 100-yard game with Allen.

Managers in deeper formats can justify adding him now for free, but only if the alternative is another veteran without a roster spot or a developmental player with virtually no chance of seeing the field. Cooks should sit at the very bottom of the bench, and managers should be prepared to release him immediately if he remains unsigned deep into training camp or fails to make an NFL roster.

A return to Buffalo would improve his odds of mattering because he already understands the offense and has shown that he can still contribute there. A contract elsewhere would require a fresh evaluation based on the depth chart and quarterback situation, although most destinations would probably be less attractive than the Bills.

The distinction is important because an inexpensive player is not automatically a good investment. Cooks carries little acquisition cost, but he still consumes a roster spot that could be used on someone with a better chance of gaining long-term value. His case works only in formats where that opportunity cost is minimal.

The Bottom Line

Brandin Cooks is not a hidden redraft sleeper, and he is not one Buffalo signing away from becoming a reliable fantasy starter. His 2025 workload was too limited, his age is too advanced and the Bills have too many receivers ahead of him for that conclusion to hold up.

What he does have is a credible path back onto an NFL roster, particularly in Buffalo. He spent the end of last season working with Josh Allen and learning Joe Brady’s offense, produced when called upon and remains familiar with Pete Carmichael’s broader offensive language. The Bills have added talent, but the bottom of their receiver depth chart is not so settled that a proven veteran with a specialized role would have no chance of making the team.

For most dynasty managers, that still is not enough. Cooks can remain on the waiver wire without becoming the player who comes back to haunt anyone.

In leagues deep enough that nearly every player with a realistic path to offensive snaps is already rostered, however, he remains a reasonable final-bench option. He needs 189 yards to reach 10,000, wants another opportunity with Buffalo and showed last season that there is still enough speed left to punish a defense that loses track of him.

That does not make him valuable, but at the very bottom of a deep dynasty roster, relevance is sometimes all a player needs.

Frequently Asked Questions

Will rookie Skyler Bell keep Brandin Cooks off the field if Cooks signs with Buffalo?

Not necessarily. Bell was selected in the fourth round and offers Buffalo a developmental receiver with separation ability, speed and run-after-catch upside, but his presence does not guarantee that the Bills would avoid adding a veteran. Cooks would be competing for a specialized rotational role rather than trying to take Bell’s place as a long-term piece of the offense.

Is Brandin Cooks worth a roster spot in standard 12-team dynasty leagues?

Probably not. In dynasty leagues with approximately 20 to 25 roster spots, managers are usually better off carrying a younger player with more long-term upside. Cooks becomes a reasonable stash only in deeper formats where the waiver wire contains almost no players with a credible chance of earning offensive snaps.

Does Brandin Cooks have any redraft value?

No meaningful value at the moment. He is unsigned and would likely occupy a low-volume role even if he returned to Buffalo. Standard redraft managers should ignore him unless injuries dramatically alter the Bills’ receiver depth chart.

How would the D.J. Moore trade affect Cooks’ potential role?

Moore would sit well ahead of Cooks and should command a significant portion of Buffalo’s perimeter targets. Cooks would be competing for occasional rotational snaps behind Moore, Khalil Shakir and the rest of the Bills’ receiver group. Any fantasy production would likely come from sporadic deep receptions rather than dependable weekly volume.

Why would Buffalo consider bringing Brandin Cooks back?

Cooks already spent the final portion of the 2025 season and Buffalo’s playoff run working with Josh Allen and Joe Brady’s offense. He also has extensive history with offensive coordinator Pete Carmichael from their time together in New Orleans. That familiarity could make him an inexpensive, low-maintenance option if the Bills want an experienced vertical receiver at the back end of the roster.