Chicago beat Carolina 59-37 on Sunday in the highest-scoring Week 1 game in NFL history. The two teams combined for 1,030 yards and the lead changed hands at 7-7, 21-21, 24-24 and 31-31 before the Bears finally pulled away.
That makes it sound like a track meet. It wasn't, quite. The Bears scored 59 points while throwing it 29 times. They ran the ball 39 times for 291 yards at 7.5 a carry, scored six times on the ground, held the ball for 34 minutes and converted 10 of 14 third downs. Carolina put up 478 yards of their own and lost by 22 because they turned it over three times and only got 22 carries in while chasing.
So the fantasy takeaways cut differently than the scoreboard suggests. Chicago's biggest number came from its running game, and the receiver room produced almost nothing resembling what people drafted.
Caleb Williams has arrived
Four total touchdowns. Twenty-one of 29 for 269 yards and two scores through the air with no interceptions, a 124.1 rating, 9.3 yards an attempt. Ten carries for 65 yards and two more touchdowns on the ground, including a 29-yard scramble at the end of the first half.
This is the version everyone has been waiting on since he came out of USC, and it didn't look like variance. It looked like a quarterback who has stopped thinking.
The throw people will remember is the 22-yard touchdown to Cole Kmet in the second quarter, where Williams rolled right, saw Kmet get a step on Devin Lloyd up the left sideline, stopped and dropped it over the shoulder. Ben Johnson singled that one out afterward, but he also praised something less glamorous... the speed of the checkdown decisions. That's the part that separates a talented quarterback from a productive one, and it's the part Williams didn't have two years ago.
The rushing is what changes his fantasy profile. Ten carries and 65 yards with two scores is a QB1 floor on its own, and in an offense that also produced 269 passing yards on 29 attempts, the ceiling is a genuinely different tier. If the legs are part of the plan rather than a product of a game that got loose, he isn't a streamer anymore.
The most telling thing about the whole afternoon might be what the Bears said after it. Johnson criticized his own first-half playcalling. Swift talked about how much there was to clean up. Williams predicted it would be their worst game of the season in terms of execution. That's a lot of dissatisfaction to come out of a 59-point day, and it suggests a group that thinks the ceiling is higher than this.
The backfield split isn't a problem, it's a ceiling
D'Andre Swift ran 18 times for 124 yards and three touchdowns, caught his only target, and generally looked like a player who deserved the three-year extension Chicago just handed him.
Kyle Monangai ran 10 times for exactly 100 yards, including a 61-yard touchdown that broke the game open at 45-31, and added two catches for 24.
Nineteen touches to 12. Both over 100 yards. Both averaging north of six a carry.
The instinct after a line like that is to worry about the rookie eating into your first-round back, and I don't think that's the right read. Chicago is clearly trying to get Monangai involved, and they should be. But Swift is really good, and Sunday was the evidence rather than the exception... 6.9 a carry, three scores, the goal line work, and a 28-yard touchdown run to close the game out. A back playing like that doesn't lose his job to a rotational partner.
What the split actually does is cap the top end. Swift is not getting 25 touches in this offense. He's getting 18 to 20 in the good games, and when the offense is producing 59 points, 18 touches turns into three touchdowns anyway. So the floor is fine and the weekly outcomes are still very good. You just shouldn't be projecting the kind of volume that wins you a week by itself.
On the other side of it, Monangai isn't truly emerging while Swift is healthy and playing at this level. He had the biggest run of the game and he's still the second back.
That said, calling him a handcuff undersells it. A handcuff is a player whose only value is insurance on somebody else, and that's not what this is. Monangai is getting ten carries and a couple of targets in a good offense behind a line that's opening holes, and he turned that into 124 total yards. You'd roster him whether or not you have Swift, because that workload produces on its own and because one broken tackle turns it into a week-winning line.
What he isn't is a player you start. Not with Swift healthy. Twelve touches with no goal line role is a bench player in most formats no matter how efficient it looks, and you'd be guessing every week on whether this is the one where he breaks a long one. If Swift misses time he's an immediate every-week start. Until then he's a roster spot you're happy to have used.
Neither of those is a concern. It's just the shape of the thing, and worth knowing before you get frustrated watching Monangai break a 61-yarder off your bench.
Nobody drafted this receiver room
Here's the Bears target distribution, and it's worth reading twice.
Kalif Raymond, in his first game as a Bear, led the team with nine targets and caught eight of them for 84 yards. Luther Burden III saw five and caught all five for 63. Rome Odunze saw three. Cole Kmet saw three. Kyle Monangai saw two. Colston Loveland saw two and caught neither.
Twenty-six targets total, which is what happens when you run it 39 times.
Raymond is the story here and nobody had it coming. He's a career slot and return specialist who came over this offseason, and he spent Sunday making diving chain-movers and finishing with more targets than Odunze and Burden combined. He also had a 23-yard punt return. If that role sticks in Ben Johnson's offense, he's a real PPR asset in deep leagues, and he's presumably sitting on your waiver wire.
Odunze is the one to be careful about. Three targets is a bad number no matter the context, and it would be alarming if not for the fact that he turned two of them into 52 yards including a spectacular 47-yard contested catch where he reached around the defender's head to pull it in. The talent showed up. The volume didn't. In a 26-target game where the offense scored 59 points, three looks is more about the run game than about Odunze's standing, but it's worth confirming next week rather than assuming.
Burden caught everything thrown at him and fumbled on the opening drive, which led directly to Carolina's first touchdown. He recovered fine.
And then there's the tight end situation, which should worry anybody who spent draft capital on Loveland. He ran routes, drew two targets and caught nothing. Kmet drew three, caught two, and scored on the prettiest throw of the game. One week doesn't settle a tight end room, but the direction of it was not what the market expected.
Bryce Young wasn't the problem
Twenty-three of 37 for 361 yards, three touchdowns, one interception, a 110.3 rating, 9.8 yards an attempt, plus a seven-yard rushing score. That's a very good day.
Carolina lost because they gave the ball away three times, because they couldn't get off the field on third down, and because Chicago ran for 291 yards. Young threw for more yards than Williams and averaged more per attempt. Whatever the Panthers' problems are, he wasn't one of them on Sunday.
Coker might be Bryce Young's guy
Jalen Coker caught eight of nine targets for 138 yards and both of his touchdowns, including a 51-yarder. Tetairoa McMillan drew eight targets and turned them into five catches for 75 yards, and lost a fumble.
Coker being good isn't news. Coker being the one Young looks for on third down, in the red zone and on the deep shot, with the high-drafted rookie standing right there, is a different thing.
One game doesn't settle it, and McMillan's eight targets say the offense still wants him. But if this is what the relationship actually looks like, it changes what both of them are worth. Worth watching more than reacting to.
The Brooks situation is the one that surprised me
Jonathon Brooks was supposed to be one of the better stories of Week 1.
Second-round pick in 2024, tore his ACL at Texas, tore it again in December of his rookie year, missed all of 2025. Three games and a dozen touches to show for two professional seasons. He spent the summer looking healthy for the first time, worked with the first team, scored in the preseason, and the reporting around him was that he'd eventually take this backfield from Chuba Hubbard.
Then Sunday happened. Hubbard took 10 carries for 49 yards and a touchdown, plus three targets that he turned into three catches for 38 yards and another score. Thirteen touches, two touchdowns. Brooks got four carries for 14 yards and two targets, one of which he took 48 yards.
A.J. Dillon got five carries. Brooks finished third in the backfield.
The obvious defense is that Carolina was easing him back, and that's a reasonable thing to assume about a player with two ACL tears on his resume.
The wrinkle is that Dave Canales said on the Friday that Brooks would face no limitations, and Brooks carried no injury designation into the game.
Which proves nothing. Coaches say what's useful to say, and a head coach telling you a player has no limitations is one of the least load-bearing sentences in football. Canales may have been telling the truth. He may also have been protecting a competitive edge, or managing a young player's confidence, or simply declining to hand an opponent a target. There's no way to know from the outside and no reason to treat the statement as evidence.
What we can actually observe is the deployment. And the deployment put a fully-cleared second-round back behind both Hubbard and a journeyman on carries.
That leaves two explanations and they both point the same direction. Either Brooks wasn't as available as advertised, in which case the health question is still open on a player with two ACL tears. Or he was fully available and the staff chose Hubbard and Dillon anyway, in which case the trust gap is wider than the offseason reporting suggested. You can't tell which from one game, and for fantasy purposes it doesn't much matter, because both answers say the same thing about the next few weeks.
The one real caveat is game script. Carolina ran the ball 22 times total because they spent the whole afternoon trailing, and a backfield with 22 carries in it doesn't leave much room for a rotation. In a script where the Panthers run 30 times, Brooks probably gets eight or nine instead of four. That's a legitimate argument and it's the only one here that rests on something observable rather than something somebody said.
So the question here isn't really whether Brooks is good. The pedigree is the reason anybody cared in the first place... a second-round back who was the top running back on a lot of boards before the knee, with the size, the patience and the receiving ability to be a three-down player. That version of him is still the highest-upside back in this backfield, and the 48-yard catch was a thirty-second reminder of why.
The question is whether Hubbard ever gets out of the way.
That's the whole thing. Hubbard is the roadblock, not the better long-term player. He took 13 touches and scored twice and did nothing to lose the job, and as long as he's healthy and producing he'll keep getting the early-down work and the goal line looks. Brooks doesn't need to beat him out on talent. He needs Hubbard's grip to loosen, through injury or a cold stretch or the staff simply deciding the upside is worth chasing.
Which makes the roster decision a real one rather than an obvious one. Hubbard is the guy scoring points right now and he's a perfectly fine RB3. Brooks is the guy who could be a weekly starter by November if the situation breaks. In a shallow league you take the production. In anything deeper, or if you have the bench space, Brooks is the more interesting hold, because the ceiling on him is a starting back in a run-heavy offense and the ceiling on Hubbard is roughly what you watched Sunday.
Watch the carry share rather than the press conferences, because the carry share is the only part of this that can't be spun.
The tight end room over there is a mess too
Tommy Tremble drew five targets and caught three for 25. Darren Waller caught both of his for 28. Mitchell Evans caught one of two for nine.
Nine targets, three players, 62 yards. Waller was supposed to be the receiving threat in that room and he's the one who saw the fewest looks. Nobody here is startable until someone separates.
Where this leaves things
Chicago's offense looks like the real thing, and the reason is that it produced 59 points in three different ways... Williams' arm, Williams' legs, and a running game that averaged 7.5 a carry. Teams that can only do one of those things get solved. Teams that can do all three don't.
The caveat is the schedule and the defense. Carolina gave up 478 yards of their own and Chicago's secondary got carved up by Bryce Young. Minnesota comes to Soldier Field next, then Philadelphia on Monday night. We'll learn more in two weeks than we did on Sunday.
For Carolina, the offense was never the issue. Young was sharp, Coker was excellent, McMillan got his looks. They lost because of three turnovers and a defense that couldn't get anybody on the ground.
The fantasy questions that carry forward are narrower than the score suggests. Whether Odunze's three targets were a run-script artifact or something else. Whether Raymond keeps the slot role. Whether Coker is actually Young's guy, which would reshape what McMillan is worth. And whether Hubbard's grip on that backfield loosens at any point, because that's the only thing standing between Brooks and a real role.