What Freeze Frame Data Tells You
When your engine control unit stores a fault code, it also photographs the moment. Engine speed, load, coolant temperature, fuel trims, road speed — all captured at the instant the fault was confirmed. That snapshot is called freeze frame, and it routinely tells you more about where to look than the code does. It is also the first thing destroyed when someone clears the code.
Why a snapshot beats a code
A fault code tells you which measurement failed. It says nothing about the circumstances, and circumstances are how you separate candidate causes.
Consider a lean-running code. That could be a split intake hose, a dirty mass air flow sensor, a leaking injector seal, a weak fuel pump, or an exhaust leak ahead of the lambda sensor. All of them produce the same code. But they do not produce it under the same conditions.
A vacuum leak has its biggest proportional effect at idle and low load, where total airflow is small and a fixed extra leak is a large percentage of it. Fuel delivery problems show up at high load, where demand is greatest and a marginal pump finally runs out. So a lean code frozen at idle with the engine warm points one way; the same code frozen at 3,000 rpm under heavy load points the other. You have just halved the search without touching a spanner.
The rule of thumb
Faults that appear at idle and light load are usually about unmetered air. Faults that appear at high load are usually about fuel or ignition running out of capacity. Faults that appear cold are usually about warm-up enrichment, temperature sensors, or components that only misbehave when cold.
Reading the fields
Exactly which parameters are captured varies by manufacturer, but the standard set covers most of what you need.
| Field | What it tells you |
|---|---|
| Fault code | Which code this snapshot belongs to. If several codes are stored, the freeze frame usually belongs to the first or the highest-priority one |
| Engine speed (RPM) | Idle, cruise or high revs. Combined with road speed, tells you whether the car was moving |
| Vehicle speed | Zero means stationary — idling, or in gear with the clutch down. A road speed with low RPM suggests a high gear and light throttle |
| Calculated load | Percentage of the engine’s available airflow being used. This is the single most useful field. Low load at idle, moderate on a cruise, high under acceleration |
| Coolant temperature | Whether the engine was cold, warming up, or fully hot. Anything well below normal operating temperature changes the interpretation completely |
| Intake air temperature | Ambient conditions, and on a cold start it should be close to coolant temperature |
| Short-term fuel trim | What the control unit was doing to the mixture at that instant |
| Long-term fuel trim | What it had learned to do over time — the more revealing of the two |
| Manifold pressure or MAF | How much air was going in, which is the sanity check on everything else |
| Fuel system status | Whether the engine was in open loop (warming up, or at full throttle) or closed loop (using lambda feedback). This matters enormously for interpreting the trims |
Fuel system status is the field people ignore
It deserves its own paragraph because it changes the meaning of everything around it.
In open loop, the control unit is running from a pre-programmed map and ignoring the lambda sensor. This happens during warm-up, at wide-open throttle, and in certain fault conditions. Fuel trim values recorded in open loop tell you very little, because the control unit was not actively correcting.
In closed loop, it is using lambda feedback and actively trimming. Trim values here are meaningful.
If you read a freeze frame showing a big positive fuel trim and get excited, check this field first. If the car was in open loop, that number is not evidence of anything.
Three worked readings
Misfire code, 2,200 rpm, 74% load, coolant 92°C
Hot and working hard. Cylinder pressure is high, which is when a weakening ignition coil struggles to jump the plug gap — the spark takes the path of least resistance and finds ground somewhere else instead. Fully warm rules out cold-start causes. Look at coils, plug gap and plug condition, and consider fuel delivery if the load figure is very high.
Lean code, 780 rpm, 22% load, coolant 89°C, long-term trim +24%
Warm engine at idle, control unit adding a quarter more fuel than its map calls for. At idle, total airflow is small, so an air leak of fixed size is proportionally huge. This is a vacuum leak until proven otherwise — breather hoses, intake boot, PCV, brake servo hose, inlet manifold gasket. A fuel supply problem would not usually show this badly at idle.
Coolant thermostat code, 68 mph, 41% load, coolant 71°C
Motorway speed and the engine still has not reached operating temperature. That is a thermostat stuck open letting coolant circulate through the radiator constantly. The road speed matters: at 68 mph there is a lot of air through the radiator, which is exactly when a stuck-open thermostat shows itself most clearly.
What freeze frame will not do
Three honest limitations.
It is one moment, not a recording. It cannot show you a trend, a sensor dropping out intermittently, or the sequence of events leading up to the fault. For that you need live data while driving.
You usually get one frame. Most cars store the snapshot for the first or highest-priority fault and overwrite as codes come and go. If five codes are stored, you will not get five frames.
The fields vary. Manufacturers must supply a standard minimum but may add more, and some supply little beyond it. What you get depends on the car.
How to use it in practice
Read it before anything else. It is the most fragile piece of information in the car and it is gone the instant a code is cleared — including when someone else clears it, which is worth remembering if a garage has already “had a look” or if you are buying a used car.
Then use it for the most valuable thing it offers, which is reproducing the fault deliberately. If the snapshot says 2,200 rpm at 74% load fully warm, you know exactly what drive to do with live data running. Being able to watch the parameters at the moment the fault occurs, rather than hoping to stumble across it, is what turns a two-hour investigation into a twenty-minute one.
Take a photograph
Before you clear anything, photograph the freeze frame screen. It costs nothing and you will want those numbers again three weeks later when the code comes back.
Getting at it
Freeze frame is part of standard OBD2 — mode 2, if you want the technical name — so any car that supports OBD2 supports it. What varies is whether your tool reads it. Plenty of basic free tools skip it or show only a couple of fields, which is a shame, because it is one of the highest-value things in the whole standard.
In AutoScan, freeze frame comes with the Enhanced edition and above, alongside live data from over 90 sensors. The Standard edition reads and clears codes but does not include the snapshot — worth knowing before you choose, because for diagnosis rather than identification the snapshot is often the thing you actually wanted.
Get the snapshot before it disappears
Freeze frame is the closest thing to a witness statement your car will give you, and it survives exactly until someone clears the code.
Read it yourself
Stop guessing at the code
AutoScan reads the fault straight out of your car and tells you what it means in plain English, on your own Windows laptop. The trial reads real codes before you pay anything.
Keep reading
Related guides
P0455 Large EVAP Leak: Start With the Fuel Cap
A large evaporative leak is the one EVAP fault you can often find yourself in five minutes, and the fuel cap is…
P0301 Cylinder 1 Misfire: Find the Cause Before Buying Parts
How to use the coil and injector swap test to prove which part is faulty on cylinder one, so you replace the…
MOT Emissions Failure: Find the Cause Before the Retest
An emissions fail tells you the numbers were wrong but not why. Here is how to read the failure sheet, work out…