How to Read Football Heatmaps: What They Show and What They Hide
- Primary Signal: How to Read Football Heatmaps: What They Show and What They Hide
- Overview: Heatmaps turn a player's movement into a picture, but the picture can mislead. This guide explains how to read them, what they reveal about roles and tactics, and where they fall s...
- Verification: Analyzed and compiled by 2026 Football Online editorial monitoring desk.
Football heatmaps are everywhere now: in television broadcasts, in post-match analysis, and in every tactical discussion on social media. They turn a player's movement into a colourful picture, showing where he spent his time on the pitch, and they look like they tell you everything about a performance. But heatmaps are one of the most misunderstood tools in football analysis. They show where a player was, not what he did there, and a heatmap without context can be deeply misleading. This guide explains how to read heatmaps properly, what they reveal, and where they hide the truth.
What a Heatmap Actually Shows
A heatmap is a visual summary of a player's position data, collected by tracking cameras or wearable sensors throughout a match. The pitch is divided into a grid, and each cell is coloured according to how much time the player spent there: red or bright colours for the areas he occupied most, blue or dark colours for the areas he rarely visited. A heatmap is not a record of touches, passes or shots; it is a record of presence. A player can have a bright red zone in an area where he never touched the ball, simply because he stood there waiting. That distinction is the first thing to understand about heatmaps.
Reading Roles and Tactics From Heatmaps
Heatmaps are at their best when they reveal a player's role and a team's shape. A full-back's heatmap will show whether he stayed wide or tucked inside, which tells you whether his team used him as an overlapping winger or an inverted midfielder. A striker's heatmap will show whether he stayed central or drifted wide, which tells you how his team attacked. And a team's combined heatmap will show its shape: where it defended, where it attacked, and which areas of the pitch it left empty. Comparing heatmaps from different matches can reveal how a manager changed his tactics, and comparing two players in the same position can reveal how differently they interpret the same role.
The Traps: What Heatmaps Hide
Heatmaps hide as much as they reveal, and the traps are easy to fall into. A heatmap does not show the direction a player was facing, so it cannot tell you whether he was pressing forward or tracking back. It does not show the speed of his movement, so a player who walked around the centre circle looks the same as one who sprinted through it. It does not show the timing of his positions, so a player who spent the first half on the left and the second half on the right looks as though he was everywhere at once. And it does not show what happened when he had the ball, which is the part of a performance that matters most. A heatmap is a map of where a player stood, not of what he achieved.
Heatmaps and Team Shape
The most useful heatmaps are not individual ones but team ones, which show the average positions of all eleven players and the areas the team controlled. A team's average-position map reveals its shape more clearly than any formation graphic: it shows how high the defensive line was, how wide the wingers played, and how compact the midfield was. It also shows the team's weak points: a large empty area on one flank, or a gap between the defence and midfield, is a problem that the opposition will exploit. Analysts use these maps to judge whether a team's shape was disciplined or stretched, and whether its tactics worked as planned.
Using Heatmaps With Other Data
Heatmaps should never be read alone. They are most useful when combined with other data: pass maps, which show where a player passed the ball; touch maps, which show where he received it; and event data, which shows what he actually did. A heatmap that shows a winger spending most of his time in the centre is interesting; a pass map that shows he completed most of his passes from that central area is revealing; and event data showing that he created three chances from there is conclusive. The heatmap is the starting point for a question, not the answer to it. Always ask what the player did in the areas where he spent his time.
A Heatmap Reading Checklist
Before drawing conclusions from a heatmap, ask five questions. First, what does the heatmap show: presence, not actions. Second, what is the player's role, and does the heatmap match what that role should look like? Third, what does the heatmap not show: direction, speed, timing and on-ball actions. Fourth, what do the other data sources say: do the pass maps and event data agree with the heatmap? And fifth, is the sample big enough: a single match can be misleading, while a heatmap built from ten matches reveals a player's true habits. Read heatmaps with curiosity and with scepticism, and they will teach you a great deal about the game.