OBD codes: how to read them without jumping to conclusions

An OBD code is a note the car made about a reading outside its expected range. It tells you where to look. It almost never tells you what to buy.

Understanding the structure helps you interpret one sensibly rather than ordering the part named in the description.

Diagnose my car

Common symptoms

  • A code read at a parts shop with no explanation
  • Several codes stored at once
  • A code that keeps returning after being cleared
  • A pending code that has not yet lit the dashboard

Simple checks you can do safely

  1. 1

    Read the code structure

    The first letter gives the area: P for powertrain, B for body, C for chassis, U for network and communication. The digits narrow it down within that area.

  2. 2

    Note freeze-frame conditions if your reader shows them

    The engine speed, temperature and load recorded when the fault was stored tell you whether it happens cold, hot, idling or under load.

  3. 3

    Treat circuit codes as wiring suspects

    Codes describing a circuit as open, low or high frequently come down to a connector, a chafed wire or a poor earth rather than the component itself.

  4. 4

    Deal with the earliest code first

    When several are stored, one root fault often triggers the rest. Fixing the first can clear the others.

  5. 5

    Record before you clear

    Write the codes down first. Clearing wipes the evidence, and if the fault is intermittent you may wait weeks for it to return.

Do not buy or replace parts until the fault is confirmed, and never work under a vehicle supported only by a jack.

Warning signs: do not drive

  • A code accompanied by a flashing engine light and rough running
  • Codes relating to braking or steering assistance together with a change in how the car handles

You can enter a stored code in AutoFix AI alongside your symptoms, and it will be used as one piece of evidence rather than a verdict.

Common questions

What does my OBD code mean?

The first letter gives the area — P for powertrain, B for body, C for chassis, U for network — and the digits narrow it within that area. The code describes a reading outside the expected range, not the part that failed.

Does a sensor code mean I need a new sensor?

Often not. Codes describing a circuit as open, low or high frequently come down to a connector, a chafed wire or a poor earth. Check the wiring before ordering the component.

I have several codes — which do I fix first?

Usually the earliest one. A single root fault commonly triggers others downstream, and resolving it can clear the rest.

Do I need an expensive reader?

A basic reader is enough to get the codes. Freeze-frame data, which records the conditions when the fault was stored, is a useful extra if your reader offers it.

These describe what a symptom commonly suggests. They are not a confirmed diagnosis of your vehicle.

Related guides

Still not sure what's wrong?

Describe the symptoms, add photos, video or an engine sound, and work through the likely causes with the checks that separate them.

Diagnose my car