decoder.tools

OBD-II Trouble Code Decoder

Look up OBD-II diagnostic trouble codes and understand what each one means.

live · client-sideHardware, Radio & Telecomfree · no sign-up
RAW INPUT
DECODED

Output appears here as you type — decoded on your device.

Input is processed on your device. Nothing you paste is sent anywhere.

What is the OBD-II Trouble Code Decoder?

An OBD-II diagnostic trouble code is a five-character identifier such as P0420 that a vehicle's engine control unit sets when it detects a fault, where each character encodes the affected system, whether the code is standardised, and the specific fault.

The structure is fixed. The first letter is the system: P for powertrain, B for body, C for chassis and U for network and communication. The second character is 0 for a generic code defined by the SAE standard and shared across manufacturers, or 1 for a manufacturer-specific one. The third indicates the subsystem — fuel and air metering, ignition, emissions, speed control, computer output — and the last two are the specific fault number.

So P0420, the most-searched code in existence, reads as a generic powertrain emissions fault: catalyst system efficiency below threshold, bank 1. And, importantly, it names a symptom rather than a part. That reading — 'the sensors downstream and upstream look too similar' — has many causes: a failed catalytic converter, but equally a worn oxygen sensor, an exhaust leak or a lingering misfire.

That gap between code and cause is the single most useful thing to understand about OBD-II. A code narrows the search; it does not identify the part to replace.

OBD-II Trouble Code Decoder at a glance

Standard
OBD-II · SAE J2012 · mandatory on US cars from 1996
First letter
P powertrain · B body · C chassis · U network
Second digit
0 = generic SAE · 1 = manufacturer-specific
Connector
16-pin DLC, within reach of the driver's seat

How to use the OBD-II Trouble Code Decoder

  1. 1Enter the code exactly as your scanner reported it, for example P0301.
  2. 2Read the system, standardisation and subsystem breakdown along with the fault meaning.
  3. 3Treat the result as a starting point for diagnosis, not a parts order.

When you would reach for it

  • Understanding a check-engine code before booking a garage visit.
  • Deciding whether a fault is emissions-related and will fail an inspection.
  • Learning what an inherited scan-tool report actually said.

OBD-II Trouble Code Decoder — frequently asked questions

Last reviewed · questions or corrections: contact@decoder.tools