RB Jeremy Langford - Free Agent

6-0, 208Born: 12-6-1991College: Michigan StateDrafted: Round 4, pick 106 (2015)

Main      Career stats      Game Logs      Game Recaps      Split Stats      Play-by-play      Latest News

Game Recaps

2018 Week 17 vs TB (9 / 25 / 0 rush, 0 / 0 / 0 / 0 rec)

He earned six yards up the left flat in the second half behind decent blocking. He couldn't earn the edge on second and goal, getting stuffed for a yard in the third quarter. He didn't find many cutback lanes and couldn't push through wraps and hits on a handful of runs during the second half. He earned good blocking on a pitch to the left for five yards late in the game. On the next play he broke through a reach for his leg on a toss to right end for 10 yards but a Julio Jones crack-back block nullified the gain just shy of the two-minute warning.

2016 Week 1 vs HOU (17 / 57 / 1 rush, 4 / 2 / 6 / 0 rec)

The second-year rusher out of Michigan State finished Sunday with a very subpar stat line -- 17 carries for 57 yards (3.4 YPC) and one touchdown.   Langford definitely has the skill set to be a bell-cow running back in the NFL, but he still has some learning to do when it comes to his vision out of the backfield. On few occasions did Langford find and exploit a potential hole in the Texans' defensive front. Now, this partially was due to the Bears' offensive line failing to get much of a push after the ball was snapped. But Langford is going to need to be able to play better than he did Sunday if he expects to keep RB1 on lockdown.  Another area in which Langford needs to improve is his blitz pickup. Given how much the offensive line struggled to protect its quarterback, Jay Cutler, the Bears need their best blockers on the field as much as possible, thus taking snaps away from Langford. Ka'Deem Carey will see more action sole for this reason if Langford can't improve in a timely manner. 

2016 Week 2 vs PHI (11 / 28 / 1 rush, 2 / 1 / 6 / 0 rec)

While the box score doesn't exactly tell the full story of Jeremy Langford's performance against the Eagles. Langford only carried the ball 11 times for 28 yards and a touchdown. Of his 28 rushing yards, 16 of them came on one run, meaning his other 10 went for eight yards. Langford's inability to rack up rushing yards should fall at the feet of his offensive line. The second-year running back out of Michigan State made some good moves at the line. His first step is quick. His vision is on par with where it should be for a sophomore back in the NFL. But none of that matters if his offensive lineman can't hold their blocks. As the season goes on and the Bears try to find out what they have at the running back position, we might start to see guys like Ka'Deem Carey and Jordan Howard get more run. It's been an awful season thus far for Chicago, which usually means it's time to throw stuff against the wall to see what sticks.

2016 Week 3 vs DAL (3 / 31 / 0 rush, 3 / 2 / 15 / 0 rec)

Jeremy Langford looked to be on his way to having his best game of the season until an ankle injury forced him off the field. Langford only touched the ball five times before leaving the game entirely -- three runs for 31 yards and two catches for 15 yards. Running the ball, Langford looked to have some bounce in his step. When a hole opened, he hit it. When he needed an extra burst to get through the Cowboys' defensive line, he turned on the jets. While it's definitely a small sample size, the second-year rusher actually looked like a starting running back in the NFL. It could all be for naught, though, as Langford left the stadium Sunday night in a walking boot to protect the injured ankle. What that means for Langford in Week 4 is not yet known. Jordan Howard, Chicago's fifth-round pick in 2016, looked great when he touched the rock. Howard's emergence could allow Chicago to rest Langford until he's 100 percent. Keep an eye out for injury updates on Langford.

2016 Week 16 vs WAS (7 / 19 / 1 rush, 2 / 1 / 4 / 0 rec)

Jeremy Langford made the most of his few touches Sunday against Washington. Despite only carrying the ball seven times for 19 yards, Langford found the end zone on a one-yard run one play after Matt Barkley found Cameron Meredith for 32 yards. As long as Jordan Howard continues to run all over opposing defenses, carries will be few and far between for Langford.

2016 Week 17 vs MIN (10 / 26 / 0 rush, 3 / 3 / 41 / 0 rec)

Langford had a nice move on a screen pass to get the Bears inside the five and set up their only score, but the rest of the day was dim for the one-time starter. His fumble on the second drive helped the early slide as the Bears were never really in this game.

2015 Week 1 vs GB (1 / 1 / 0 rush, 0 / 0 / 0 / 0 rec)

As it stands now, it's hard to tell which running back truly is the Bears' No. 2. While the depth chart says it's Jacquizz Rodgers, conventional wisdom says it's Jeremy Langford, whom first-year general manager Ryan Pace used a fourth-round pick to select. Langford carried the ball only once.

2015 Week 2 vs ARI (6 / 21 / 1 rush, 0 / 0 / 0 / 0 rec)

To the surprise of pretty much everyone, Jeremy Langford saw some decent run Sunday against the Cardinals. The rookie out of Michigan State actually replaced starter Matt Forte for an entire series, one that resulted in Langford's first NFL touchdown. All in all, Langford only carried the ball six times for 21 yards and the aforementioned TD. This Bears coaching staff appears to trust Langford. The kid does a great job of making it hard for only one defender to bring him down. If he can continue to run successfully without giving up the ball, expect him to spell Forte for one or two series a game. That type of usage might not seem like a lot for a backup running back, though it's been Forte and Forte only for the past few seasons.

2015 Week 3 vs SEA (0 / 0 / 0 rush, 0 / 0 / 0 / 0 rec)

Jeremy Langford scored the first touchdown of his short career last week against the Cardinals. This week, however, fared much different for Langford. The rookie back didn't record a run or a catch in the 26-0 loss to the Seahawks. Why? That's a good question. The coaching staff made no mention of Langford's absence from the Bears' offensive gameplan. It likely had something to do with Forte carrying the ball 20 times and trailing by double digits for most of the second half.

2015 Week 4 vs OAK (1 / 4 / 0 rush, 0 / 0 / 0 / 0 rec)

While Jeremy Langford appears to have the confidence of the coaching staff, enough to fall into the backup role, it's highly unlikely he will be playing a key role on any team anytime soon. Langford simply won't see the field enough to make a lasting impact. In the win over Oakland, Langford touched the ball only once, a four-yard rush. There's no doubting the kid's ability, but there is doubting the role of the backup running back within the Bears organization. As long as Matt Forte is around, the backup shouldn't plan on seeing much action.

2015 Week 5 vs KC (2 / -2 / 0 rush, 2 / 1 / 14 / 0 rec)

The rookie running back touched the ball a whole three times in Sunday's 18-17 win over the Chiefs -- two rushes for -2 yards and one catch for 14 yards. Langford saw one series where he was the lone back, giving Matt Forte a brief respite. He didn't make much of it, recording the two carries for negative yards. The only other action Langford saw came out of three-back sets, most of which resulted in screen passes to Forte. Barring a Forte injury, Langford will continue struggling to find a rhythm in this Bears offense.

2015 Week 6 vs DET (5 / 10 / 1 rush, 2 / 1 / 17 / 0 rec)

Jeremy Langford was given an extended look Sunday by the Bears coaching staff. The rookie carried the ball five times for 10 yards and a touchdown, along with one reception for 17 yards. Langford kept Forte on the sideline for an entire series, and was given the ball on a goal line play when Forte was in the backfield. As long as Forte is healthy, Langford will continue to see only one or two series per game, which really limits his value.

2015 Week 8 vs MIN (12 / 46 / 0 rush, 1 / 0 / 0 / 0 rec)

Jeremy Langford might want to forget about his role in Sunday's game. Despite finishing the game as the No. 1 back, after starter Matt Forte exited early with a knee injury, Langford dropped a huge third-down pass that would have given the Bears a first down late in the game. On third and short, Cutler scrambled in the pocket before finding a wide-open Langford crossing the field. The pass hit Langford in the hands and fell to the ground. Langford finished the game with 12 carries for 46 yards. His 12 carries are only three fewer than his season total (15) entering Sunday. This is what running behind a talent like Forte will do to you. As a result, Langford still is somewhat of a mystery. The rookie is a hard-nosed runner who can hit the edge quickly, but the Bears' offense definitely will suffer without the versatility of having a guy like Forte in the backfield. If Forte ends up missing time, look for Langford to be given the lion's share of the carries.

2015 Week 9 vs SD (18 / 72 / 1 rush, 4 / 3 / 70 / 0 rec)

Langford owners were probably very nervous seeing Ka'Deem Carey out there to start the game for Chicago, and look pretty good on a couple of early runs. But by the end of the game, they were likely congratulating themselves on having the foresight to grab Langford. He did a little bit of everything, and looked very much like Matt Forte in piling up the yardage both on the ground and in the air (not to mention converting both a short yardage touchdown run and two point conversion). From the outset, Langford looked the part of a number one type back. And for good measure, he showed remarkable skills in hauling in a deep ball for 32 yards down the left sideline. He actually kind of mis-timed his jump, but still managed to corral the pass with a fantastic diving attempt. In the second half, he again showed excellent hands on a screen pass that kind of went awry. He re-adjusted his hands to snag the ball in front of him, take it in stride, and shoot up the left sideline for a big gain. Another big gain came on a key third down play where he broke out of the backfield and wasn't even touched until he was a good 20 or so yards downfield. And of course, the aforementioned short yardage conversions that resulted in points on the board. On one goal line run, he was tackled just shy of the goal line. But what was very telling is that he didn't carelessly extend the ball out away from his body just to take a shot at scoring. Obviously you want players to try and score, but his focus was on protecting the ball. And on the next play, he ended up getting in anyway. He followed his blockers after a brief hesitation, showing good patience in the process. He just looked like a complete back, and had both announcers talking about how fortunate the Bears were to have a player of this caliber to replace Matt Forte with. Along the way, he impressed in the running game by reading his blocks, showing patience, and hitting the hole and the edge with equal decisiveness and his trademark speed. He even did a nice job in blitz pickup, and commentator Jon Gruden made it a point to illustrate this on several occasions. It was only one game, but the Bears appear to be in good shape to handle the absence of Matt Forte for however long he is out for.

2015 Week 10 vs LA (20 / 73 / 1 rush, 9 / 7 / 109 / 1 rec)

Jeremy Langford deserves an Oscar for playing the role of Matt Forte. The rookie running back out of Michigan State was superb in Sunday's 37-13 win over the St. Louis Rams. Langford carried the ball 20 times for 73 yards and a touchdown, to go along with seven receptions for 109 yards and a touchdown. The Rams did not have an answer for what Langford was able to do in space. No Bear had more catches than Langford's seven. When the Rams threw a double team at Alshon Jeffery, Cutler looked for Langford out of the backfield. It worked time and time again. Look no further than the second-half play that saw Langford catch a pass in the flat and take it 83 yards for a score. After the ball was snapped, one defender went with Jeffery and a second defender shaded his way over the top; the Bears loaded up blockers at the line of scrimmage and the rest is history. As a runner, Langford had to work hard for his 73 yards. While his 3.65 yards-per-carry average isn't going to win any awards, he kept the chains moving enough to make the run game relevant. St. Louis had to respect what Langford and Ka'Deem Carey were doing on the ground. Langford's strong play is giving general manager Ryan Pace all the necessary reasons to move on from Forte once the season ends.

2015 Week 11 vs DEN (13 / 25 / 1 rush, 6 / 3 / 17 / 0 rec)

Jeremy Langford turned in a very average performance Sunday against the Broncos. The rookie tailback gained just 25 yards on 13 carries, by far his worst game since taking over the starting role three games ago. Without Forte, Alshon Jeffery and Eddie Royal in uniform, Denver was able to lock in on Langford and the Bears' rushing attack. The offensive line didn't do Langford any favors, either. Running mostly up the middle, Langford's biggest gain of the day went for only five yards. Whatever offensive coordinator Adam Gase saw on tape in the Broncos run defense wasn't there for Langford. Looking forward, Forte likely will be back for Thursday's game against the Packers. But Langford's open-field speed and pass-catching ability will keep him in the rotation, for sure.

2015 Week 12 vs GB (12 / 48 / 1 rush, 3 / 1 / 5 / 0 rec)

With Matt Forte back in the saddle, Langford found himself splitting carries almost completely down the middle with the veteran back. Forte got a few more carries and Langford got several more targets but the reality was that both players got plenty of work, but sharing limited their overall impact. Langford had a streaky day when he got touches. He ran the ball well on most of his carries, but had two huge drops on passes, one of which was nearly picked off. Langford showed good strength on his 1-yard touchdown run as well, but was stymied late in the game when the Packers loaded up the box on obvious running plays. Overall he played a solid game, showing the speed, vision and quickness which has served him well while he was the starter, but his overall number of carries could hover much lower than they have been with Forte back.

2015 Week 13 vs SF (12 / 59 / 0 rush, 3 / 2 / 9 / 0 rec)

Jeremy Langford looks like a future star for the Chicago Bears, but he still has a long way to go before he'll be as impactful as Matt Forte during his prime. Langford has done a great job running the football, gaining 59 yards on 12 carries in Sunday's loss to the San Francisco 49ers. Offensive coordinator Adam Gase is working hard to keep his backs fresh by giving Langford a series or two each quarter. Where Langford struggles is the pass game. In at least three of the Bears' seven losses, Langford has dropped key third-down passes that could have tilted the result the other way. Langford was targeted three times Sunday, catching two passes for nine yards. This is important because Langford is making a name for himself as a pass dropper. Until Langford can learn how to catch the ball, he won't be trusted in big moments of the game.

2015 Week 14 vs WAS (11 / 37 / 0 rush, 7 / 3 / 27 / 0 rec)

Jeremy Langford really is a mixed bag right now -- some good, some bad. Langford runs the ball extremely hard, and he hits holes much quicker than Matt Forte, who is more of an up-and-down runner. Langford also lends the Bears a lot of versatility in the passing game. The only problem is Langford doesn't catch very well. Frown. Langford carried the ball a team-high 11 times in the 23-20 loss to the Redskins. He gained only 37 yards on those 11 carries, for a 3.4 yard average. Offensive coordinator Adam Gase wasn't willing to commit to the run with any consistency. The Bears as a team only ran the ball 23 times, compared to 31 passing attempts, for Jay Cutler, on 34 total dropbacks. In the passing game, Langford received a good bit of targets. His seven targets were good for second on the team, behind Alshon Jeffery's nine. Langford only caught three of his seven targets for 27 yards. With as much as Gase loves to involve his runners in the passing game, you'd figure Langford would show some signs of improvement when it comes to hauling in passes. Sadly, the drops continue to come, despite the appearance of confidence from the coaching staff. It you want upside as your season winds down, Langford definitely has it. The Bears want to put Langford in as many new situations as possible, which is why he lines up all over the field on Sundays. It's likely going to be the Jeremy Langford show from here on out.

2015 Week 15 vs MIN (11 / 46 / 0 rush, 3 / 1 / 11 / 0 rec)

Jeremy Langford turned in a very average performance Sunday in the loss to Minnesota. The rookie running back carried the ball a team-leading 11 times for 46 yards and added one reception for 11 yards. Minnesota's defensive front was depleted Sunday, taking the field without two of its best run stoppers. Langford wasn't able to get it going with any semblance of consistency, though, partially due to horrible offensive line play. But you have to wonder if the lack of consistent carries has hampered his ability to find a rhythm. Langford hasn't seen more than 13 carries since the Bears' Week 10 win over the Rams. While Langford has shown flashes in his rookie season, he still leaves a lot to be desired, especially his work in the passing game.

2015 Week 16 vs TB (19 / 83 / 0 rush, 2 / 0 / 0 / 0 rec)

Jeremy Langford continues to have a strong rookie campaign. Chicago's running back of the future gained a season-high 83 yards on 19 carries (4.36 yards per carry) in the win over the Buccaneers. We saw a bit more of Langford than we normally do, as Matt Forte exited early after tweaking his back. Langford received eight carries more than Forte. Without Alshon Jeffery on the field to stretch out the offense, offensive coordinator Adam Gase heavily relied on Langford and the run game. The Bears dominated time of possession 37:03 to 22:57, largely because Langford was able to pick up chunks of yards when given the ball. Langford appeared to be more comfortable running to the right side, mainly behind right guard Vladimir Ducasse and right tackle Kyle Long. Ten of Langford's 19 carries went to the right side. We have yet to see Langford truly have a breakout game on the ground. He hit a high-water mark against the Bucs, and he could be in line for more carries in Week 17 if Forte misses the game due to the back injury he sustained Sunday.

2015 Week 17 vs DET (5 / 14 / 0 rush, 0 / 0 / 0 / 0 rec)

This one is going to be short, mostly because Langford barely saw the field in Sunday's 24-20 loss to the Lions. With Matt Forte likely playing his last game as a member of the Chicago Bears, offensive coordinator Adam Gase made sure No. 22 got the ball early and often. Langford saw only five carries against Detroit, while Forte saw 17. Langford received zero targets in the passing game, while Forte received three. Leading up to the game, knowing how depleted the Bears were on offense -- without the likes of Alshon Jeffery, Kevin White, Eddie Royal, Marquess Wilson, Martellus Bennett and Zach Miller -- one would have thought Langford would have played a huge role in the game plan. This would have been the spot for Gase to use Langford as a receiver, as much as he could. You have to wonder if Langford's catching problem was the primary reason to keep him off the field. If you've been following along here week by week, you'd know Langford has a propensity to drop the football when it's thrown his way. Perhaps management was sending him a message, or perhaps not. Barring something completely and utterly unforeseen, Langford will be the Bears starting running back next season.