Skip to main content
parlae.ioBeta
Sign in

NFL depth charts, Week 6

All 32 NFL depth charts for Week 6, ordered by who actually played each club's last three games: weighted snap share for quarterbacks, receivers and tight ends, snaps and touches for running backs, with injury designations and the club's own listed order beside every name. 14 clubs have a new leader at a position by usage since the game before. Kyle Pitts moved up to TE1 from TE2 for the Falcons; Tyler Huntley moved up to QB1 from QB2 for the Ravens; Dalton Kincaid moved up to TE1 from TE2 for the Bills.

Advertisement

League depth charts by position

Common questions

  • How are these NFL depth charts ordered?

    Each slot is ordered by the club's last three games played, a bye skipped: the newest game counts three times, the one before twice, the one before that once. Quarterbacks, receivers and tight ends are ordered by their weighted share of the club's offensive snaps. Running backs blend that snap share half and half with their share of the backfield's touches (carries plus targets), because a back's snaps include pass protection. The newest game also counts on its own: a player's place is the higher of his weighted share and his share of that one game, so a starter back from a missed game, or a back who just took the job, is not held under by the games before it. A game a player missed counts as zero for him. Players with no snaps in the window follow in the club's own listed order, and players on injured reserve, PUP, NFI or a suspension are listed apart.

  • How often do they update?

    Every 15 minutes for injury designations, and the morning after each game for snaps and touches. Week 6 charts use games through Week 5.

  • Why not just use the team's official depth chart?

    Official charts are a statement of intent and they lag, sometimes by weeks. Every team page here prints the club's own order beside the usage order, so you can see where the two disagree.

By the Parlae deskDepth charts updated Oct 14, 2026 at 6:39 PM ETHow this is builtReport a wrong number