OBD-II Code Lookup

Look up any OBD-II diagnostic trouble code: what each of its five characters means, whether SAE or the vehicle maker defines it, its SAE J2012 definition, and the two bytes your scan tool actually receives.

Decoder Automotive Updated Oct 5, 2026
Learn how this works
How to Use
  1. Pick Look up a code, then type the code your scan tool shows, such as P0171 or U0100 (upper or lower case).
  2. Read the definition and the breakdown: the system letter, whether SAE or the maker defines it, the system area, and the two bytes the car sends.
  3. Have only raw hex from a terminal or ELM327 adapter? Pick Decode raw bytes and paste the reply, for example 43 01 33 00 00 00 00.
  4. Pick Search definitions to find every generic code that mentions a word such as misfire, EVAP or throttle.
  5. Follow Show Work for each step, and use the definition to decide what to test. A code names a circuit or a condition, not the failed part.
Input
5 characters
Mode 03, 07 or 0A
in the definitions
Presets
Code Anatomy
Code
—
System
—
Defined by
—
Bytes sent
—

Worked Example

P0171. P is powertrain; 0 makes it an SAE-defined generic code that means the same on every make; the third character 1 places it in the fuel and air metering group; 71 picks the fault. SAE J2012 defines it as System Too Lean Bank 1. On the wire the car sends two bytes, 01 71: the top two bits 00 stand for P, the next two 00 for the 0, and the rest is the hex 171.

An adapter reply: 43 01 33 00 00 00 00. This is the example in the ELM327 datasheet. 43 marks a reply to a Mode 03 request (stored codes), and the six bytes after it are read in pairs: 01 33 is P0133, O2 Sensor Circuit Slow Response Bank 1 Sensor 1; the two 00 00 pairs are padding, not codes. On CAN vehicles one extra byte after the 43 gives the number of codes that follow.

The common mistake: reading the raw hex as the code. The ELM327 datasheet’s second example is the pair D0 16. Read literally it looks like “D016”, or P0016 if you drop the D, and P0016 is a crankshaft/camshaft correlation code. The first hex digit actually packs the letter and the next digit into four bits: D is 1101, so 11 = U and 01 = 1, and the code is U1016, a manufacturer-defined network code. Likewise 11 31 is P1131, not P0131.

What a code does not tell you. P0301 is Cylinder 1 Misfire Detected: it says where the computer saw the fault, not which part failed. California’s OBD II rule asks for a code “indicating the likely area of the malfunction”, and a misfire in cylinder 1 can come from the plug, the coil, the injector, the wiring or the engine itself. Test before you buy parts.

Show Work

Type a code to see how it is read, step by step.

How a Trouble Code Is Built

1st character
P · C · B · U
Powertrain, chassis, body, network: bits 00, 01, 10, 11 of the first byte
2nd character
0 · 1 · 2 · 3
Who defines it: P0 and P2 SAE, P1 the maker, P3 shared; B, C, U: 0 SAE, 1 and 2 the maker
3rd character
0–9, A–F
System area, e.g. P03xx ignition and misfire, P04xx auxiliary emission controls
Last two
00–FF
The specific fault: P0301 is cylinder 1, P0302 cylinder 2
Two bytes
byte 1 = ss dd hhhh
2 bits system, 2 bits digit, 4 bits third character; byte 2 = last two characters. P0171 → 01 71
Three bytes
code + failure type
Vehicles using SAE J1979-2 report 3-byte codes: the 2-byte code plus a failure-type byte

Who defines each code

Code startsSystemFirst hex digit sentDefined byGeneric codes in this list
P0xxxPowertrain0SAE-defined (generic)1,461
P1xxxPowertrain1Manufacturer-defined—
P2xxxPowertrain2SAE-defined (generic)867
P3xxxPowertrain3Jointly defined: the published generic list starts at P340098
C0xxxChassis4SAE-defined (generic)261
C1xxxChassis5Manufacturer-defined—
C2xxxChassis6Manufacturer-defined—
C3xxxChassis7Reserved for future use—
B0xxxBody8SAE-defined (generic)359
B1xxxBody9Manufacturer-defined—
B2xxxBodyAManufacturer-defined—
B3xxxBodyBReserved for future use—
U0xxxNetworkCSAE-defined (generic)438
U1xxxNetworkDManufacturer-defined—
U2xxxNetworkEManufacturer-defined—
U3xxxNetworkFReserved in the ELM327 table; later J2012 lists define U3000 up18

P0 codes by system area

CodesThird characterArea (SAE J2012 grouping)Generic codes listedExample
P0000–P00FF0Fuel and air metering and auxiliary emission controls114P0001 Fuel Volume Regulator Control Circuit/Open
P0100–P01FF1Fuel and air metering117P0100 Mass or Volume Air Flow A Circuit
P0200–P02FF2Fuel and air metering (injector circuit)133P0200 Injector Circuit/Open
P0300–P03FF3Ignition system or misfire94P0300 Random/Multiple Cylinder Misfire Detected
P0400–P04FF4Auxiliary emission controls128P0400 Exhaust Gas Recirculation Flow
P0500–P05FF5Vehicle speed control, idle control and auxiliary inputs109P0500 Vehicle Speed Sensor A
P0600–P06FF6Computer and output circuits148P0600 Serial Communication Link
P0700–P07FF7Transmission123P0700 Transmission Control System (MIL Request)
P0800–P08FF8Transmission123P0800 Transfer Case Control System (MIL Request)
P0900–P09FF9Transmission106P0900 Clutch Actuator Circuit/Open
P0A00–P0AFFAHybrid propulsion252P0A00 Motor Electronics Coolant Temperature Sensor Circuit
P0B00–P0BFFBHybrid propulsion14P0B00 Auxiliary Transmission Fluid Pump Motor Phase U Current

One sensor usually owns a run of codes that differ only in the last word, which tells you what kind of fault the computer saw on that circuit: P0110 Intake Air Temperature Sensor 1 Circuit, P0111 Intake Air Temperature Sensor 1 Circuit Range/Performance, P0112 Intake Air Temperature Sensor 1 Circuit Low, P0113 Intake Air Temperature Sensor 1 Circuit High and P0114 Intake Air Temperature Sensor 1 Circuit Intermittent. The meaning of each word for your vehicle, and the test that follows, is in the maker’s service information.

Where OBD-II Codes Came From

1988: California’s first on-board diagnostic rule, OBD I, makes carmakers monitor a few emission parts. The California Air Resources Board found it limited: few components were checked and the monitors were not tied to emission levels.

1996: OBD II becomes required on all 1996 and newer gasoline and alternative-fuel passenger cars and trucks, and on 1997 and newer diesels; a few 1994 and 1995 gasoline models already had it. The US EPA requires OBD on all 1996 and newer cars and trucks in every state and accepts systems built to California’s rule, so in practice almost every US vehicle is built to it. The codes are the SAE J2012 set, read through the standard 16-pin connector.

2001 and 2004: Europe follows with EOBD for petrol cars first registered from 1 January 2001 and diesel cars from 1 January 2004, under Directive 98/69/EC, using the same connector and code format.

2010–2012: permanent fault codes arrive, on 50 % of 2010, 75 % of 2011 and all 2012 model-year vehicles: a confirmed code that lit the light is copied to memory that no scan tool and no battery disconnect can erase. Newer vehicles using SAE J1979-2 report 3-byte codes.

Sources

  • SAE J2012 Diagnostic Trouble Code Definitions — SAE International, 2002–2019 revisions. The standard that defines the codes. It is sold by SAE; the wording here is as reproduced in the two open code tables below. www.sae.org/standards/content/j2012_201912/
  • AndrOBD code table (codes.properties) — AndrOBD open-source project, GitHub, 2026. Source of 3,500 of the definitions, after removing reserved entries and fixing spacing typos. Licensed GPL-3.0 — the definitions (and this site's data file built from them, /assets/data/obd-codes.json) are redistributed under the same licence. github.com/fr3ts0n/AndrOBD
  • python-OBD code table (obd/codes.py) — python-OBD open-source project, GitHub, 2026. Cross-check: it carries 2,025 of the same codes with the same meaning; the other differences are later J2012 revisions adding bank and sensor numbers or filling codes that were reserved. github.com/brendan-w/python-OBD
  • ELM327 OBD to RS232 Interpreter datasheet, “Interpreting Trouble Codes” — Elm Electronics, 2014. How the five characters are packed into two bytes, which first digits are SAE- or manufacturer-defined, and what a Mode 04 clear erases. www.elmelectronics.com/wp-content/uploads/2016/07/ELM327DS.pdf
  • California Code of Regulations, Title 13, §1968.2, Malfunction and Diagnostic System Requirements (OBD II) — California Air Resources Board, current text. Pending, confirmed and permanent fault codes; when the light comes on, blinks and goes off; codes that point to the likely area of the malfunction. www.law.cornell.edu/regulations/california/13-CCR-1968.2
  • 40 CFR 86.1806-17, Onboard diagnostics — US EPA, Electronic Code of Federal Regulations, 2026. Adopts the California rule federally; names P0456, P04EE and P04EF as very-small (0.020 inch) EVAP leak codes; P04EE and P04EF are listed from it because the open tables predate them. www.ecfr.gov/current/title-40/part-86/section-86.1806-17
  • On-Board Diagnostic II (OBD II) Systems Fact Sheet — California Air Resources Board, current page. OBD I from 1988; OBD II on all 1996 and newer gasoline cars and trucks (1997 diesel); the blinking light; readiness. ww2.arb.ca.gov/resources/fact-sheets/board-diagnostic-ii-obd-ii-systems-fact-sheet
  • On-board diagnostics: OBD-II diagnostic trouble codes — Wikipedia, 2026. Third-character system groups for P0 codes (citing SAE J2012) and the EOBD start dates (citing Directive 98/69/EC). en.wikipedia.org/wiki/On-board_diagnostics

About This Tool

Reference: Diagnostic & Vehicle Network Protocols Table.

This lookup reads any five-character trouble code, explains each character, shows the two bytes the car sends, and gives the SAE J2012 definition for the 3,502 generic codes in its list (P0, P2, P34xx, B0, C0, U0 and U3). It also turns raw adapter replies into codes and searches the definitions. Manufacturer-defined codes (P1, P30–P33, B1, B2, C1, C2, U1, U2) are decoded for structure only, because each maker writes its own meanings.

The definitions follow J2012 as reproduced in two open scan-tool code tables, checked against each other; J2012 itself is sold by SAE, so treat the wording as a guide and your maker’s service information as the final word, especially for B and C codes. The same dataset feeds Understanding OBD-II & Trouble Codes, so the two pages agree. The definitions load from this site; nothing you type is sent anywhere.

A flashing check-engine light means a misfire that can damage the catalytic converter: ease off and get it seen to, and follow the vehicle maker’s procedures for any repair.

Related tools: VIN Decoder, MAF Sensor Sizing, and Wiring & Electrical.

Frequently Asked Questions

What does P0171 mean?

P0171 is “System Too Lean Bank 1” in SAE J2012. P is powertrain, 0 means an SAE-defined generic code, and the third character 1 puts it in the fuel and air metering group. P0174 is the same condition on bank 2. The code names the condition the engine computer saw, a lean mixture; it does not name the part that caused it.

What do the letters P, B, C and U mean?

P is powertrain, C chassis, B body and U network. The letter is carried in the top two bits of the first byte the car sends: 00 for P, 01 for C, 10 for B and 11 for U, so only these four letters can exist.

What is the difference between P0 and P1 codes?

P0 and P2 codes are defined by SAE J2012 and mean the same on every make. P1 codes are defined by each manufacturer, so P1xxx needs the maker’s service information. P3 codes are shared: the published generic list starts at P3400. For B, C and U, 0 is SAE-defined and 1 and 2 are manufacturer-defined.

Does clearing a code fix the problem?

No. A scan-tool clear (Mode 04) erases the stored codes, the freeze-frame snapshot and the test results and turns the light off, but it does not erase permanent codes. California’s OBD II rule, adopted federally, keeps a permanent code until the car itself confirms the fault is gone, and the light returns if the fault does.

Why is my check-engine light flashing?

A blinking light means misfire bad enough to damage the catalytic converter is happening now. California’s OBD II regulation requires the light to blink once per second while that level of misfire occurs. The California Air Resources Board notes that many makers recommend having the car serviced as soon as possible when it blinks.

How do I use the OBD-II Code Lookup?

Simply type or paste your value and read the result, which refreshes the instant you change something. There is nothing to submit and nothing to wait for.

Do I need to install or sign up for anything?

Not at all — it runs in the browser with nothing to install and no account. After it loads once, it even works without an internet connection.

Is my information private?

Yes. Everything happens in your browser. Nothing you type is sent to a server or saved anywhere.

Common Use Cases

Read a bare-bones adapter

An ELM327 adapter answers a Mode 03 request with 43 01 71 00 00 00 00; the pair 01 71 is P0171, System Too Lean Bank 1, and the 00 00 pairs are padding.

Check which bank

P0420 and P0430 are the same catalyst-efficiency code on bank 1 and bank 2; P0171 and P0174 are lean on bank 1 and bank 2.

EVAP leak codes

P0456 is the very small EVAP leak code; 40 CFR 86.1806-17 sets that leak at 0.020 inch (0.51 mm) for 2017 and later vehicles.

Network faults

166 of the generic U codes (U0100–U02FF) are “lost communication” codes; U0100 is Lost Communication With ECM/PCM A.

Hybrids

The P0A00–P0AFF block holds 252 hybrid codes; P0A80 reads Replace Hybrid Battery Pack.

Last updated: