Search an OBD-II trouble code, symptom or component and get a clear diagnostic overview: meaning, severity, drivability, symptoms, likely causes, test steps, common fixes, repair range and related codes.
Try a code like P0300 or a broader term such as misfire, EVAP, sensor, ABS, lean, rich or communication.
An OBD2 trouble code is a clue from your vehicle's onboard diagnostic system. It tells you which system detected a problem, but it does not automatically prove that a particular sensor, valve, module, or other part has failed. Use the OBD2 code lookup tool above to decode a code, check its system and severity, review common symptoms and likely causes, and build a sensible diagnostic plan before spending money on repairs.
The tool is designed for drivers, DIY mechanics, technicians, and used-car shoppers who need a fast explanation of common check engine light codes, powertrain codes, chassis codes, body codes, and network communication codes.
For the most useful result, start with the exact five-character diagnostic trouble code shown by your scan tool. Codes usually look like P0300, P0420, C0035, or U0100. You can also search by a symptom or component when you do not know the exact code.
Type the code exactly as it appears on your OBD2 scanner. The tool accepts standard P, B, C, and U code families.
Year, make, model, engine, and check-engine-light status can help you interpret the result. These fields are optional because not every code needs vehicle-specific context.
Do not jump directly to the most expensive possible repair. Compare the code with the way the vehicle is actually behaving.
Inspect simple causes first, check related codes and freeze-frame data when available, and test the circuit or component before replacing parts.
After correcting the root cause, clear the code only when appropriate and confirm that it does not return after the relevant drive cycle.
The first letter of a diagnostic trouble code identifies the broad vehicle system that reported the fault. This makes it easier to understand where to begin diagnosis.
| Code family | System | Typical examples | What it can involve |
|---|---|---|---|
| P | Powertrain | P0300, P0420, P0455 | Engine, transmission, ignition, fuel, emissions, air metering and related controls. |
| B | Body | B0001 and manufacturer-specific B codes | Airbags, restraints, climate, lighting, seat or body-electrical systems depending on the vehicle. |
| C | Chassis | C0035, C0040 | ABS, wheel-speed sensing, steering, stability control and other chassis-related systems. |
| U | Network | U0100, U0121 | Communication between control modules over the vehicle network. |
Generic OBD2 codes use standardized meanings across many makes and models. They are especially common in emissions and powertrain diagnosis. A code such as P0300 generally describes the same broad fault category across compliant vehicles.
Some DTCs are defined by the vehicle manufacturer. The same-looking code can have a different exact meaning or diagnostic procedure depending on make, model, engine, model year, or control module. Verify these codes against reliable service information for the specific vehicle.
Important: A code definition is the starting point of diagnosis. Do not replace a component only because its name appears in a code description. Wiring faults, vacuum leaks, low voltage, connector problems, mechanical faults, or another system can trigger the same DTC.
Severity depends on more than the code itself. A vehicle with a minor evaporative-emissions leak may drive normally, while a severe misfire, overheating condition, oil-pressure warning, braking fault, or network problem can require immediate attention. The diagnostic tool gives an urgency estimate, but you should also consider warning-light behavior and real-world symptoms.
The vehicle drives normally, no critical warning is present, and the fault is unlikely to cause immediate damage. Diagnosis should still be scheduled because emissions, fuel economy, or reliability can be affected.
There may be rough running, reduced performance, hard starting, ABS or stability-control limitations, or another condition that should be diagnosed soon.
Strong misfiring, stalling, overheating, abnormal noises, serious transmission behavior, braking concerns, or other major symptoms can justify limiting or stopping driving until the vehicle is checked.
If you have an oil-pressure warning, overheating, smoke, fuel smell, brake-system warning with reduced braking, or another obvious safety hazard, respond to that condition rather than relying only on the OBD2 result.
A solid check engine light usually means the engine computer has stored a fault that needs diagnosis. Depending on the code and symptoms, the vehicle may still be driveable for a limited period.
A flashing check engine light is more urgent. It often appears when the engine is misfiring severely enough that unburned fuel may overheat and damage the catalytic converter. Reduce load and avoid continued driving when the engine is shaking, losing substantial power, or the light keeps flashing. Have the vehicle diagnosed promptly.
Codes such as P0300–P030x can point toward ignition, fuel, air, compression, timing, wiring, or control issues. Spark plugs and ignition coils are common possibilities, but they should be tested rather than assumed.
Lean/rich conditions and airflow faults may involve vacuum leaks, intake plumbing, MAF/MAP sensors, fuel pressure, injectors, exhaust leaks, or oxygen-sensor feedback.
Evaporative-emissions codes can be caused by a loose or damaged fuel cap, leaking hoses, purge/vent faults, or leaks elsewhere in the sealed fuel-vapor system.
Catalyst-efficiency and oxygen-sensor codes require careful diagnosis. Exhaust leaks, fuel-control problems, misfires, sensor faults, and an aging catalytic converter can all be relevant.
Transmission DTCs may relate to solenoids, speed sensors, fluid or pressure problems, wiring, mechanical wear, or module communication. Some codes simply tell you that another transmission module has stored more detail.
Chassis and U-codes can involve wheel-speed sensors, wiring, low battery voltage, grounds, CAN-bus faults, connectors, or control modules. A network code does not automatically mean a module has failed.
A good diagnostic process moves from evidence to testing. Before ordering a sensor or module, review the complete scan and the conditions under which the fault occurred.
Most scan tools can clear many stored OBD2 codes, but clearing a code is not the same as fixing the fault. If the underlying problem remains, the code will usually return after the system runs its monitor again.
Clearing codes can also erase useful freeze-frame information and reset emissions readiness monitors. That matters if the vehicle is about to undergo an emissions or inspection test. In many cases, it is better to record the codes and diagnostic data first, repair the cause, then clear the code and verify the repair with an appropriate drive cycle.
An OBD2 code, also called a diagnostic trouble code or DTC, is a standardized five-character code stored by a vehicle control module when its diagnostic logic detects a fault or an operating condition outside the expected range.
No. A DTC identifies a detected problem, circuit, system, or operating condition. The named component may be functioning correctly while wiring, connectors, air leaks, mechanical issues, voltage problems, or another system causes the code.
Sometimes, but it depends on the code and symptoms. A solid light with normal operation may allow limited driving while you arrange diagnosis. A flashing light, severe misfire, overheating, stalling, smoke, unusual noises, or another safety-related symptom should be treated much more urgently.
The vehicle runs self-tests called monitors. If the fault condition still exists when the relevant monitor runs again, the control module can set the code again. Repeatedly clearing the code does not repair the underlying cause.
A pending code generally means the system detected a fault but the criteria for a confirmed code may not yet have been met. A stored or confirmed code has met the module's criteria for recording the fault. Exact behavior varies by monitor and vehicle.
The OBD2 standard reserves portions of the code range for manufacturer-defined faults. Those codes may require the exact year, make, model, engine, transmission, or module information to interpret correctly.
Yes. Low or unstable system voltage can contribute to communication, sensor-reference, actuator, or module-related DTCs. Battery condition, charging-system performance, and grounds are worth checking when multiple unrelated electrical codes appear together.
No. A scanner is extremely useful, but proper diagnosis may also require a digital multimeter, smoke tester, fuel-pressure gauge, oscilloscope, wiring diagram, compression or leak-down testing, manufacturer scan functions, or other specialized equipment.
This tool provides educational diagnostic guidance and common repair possibilities. Trouble-code definitions, test procedures, specifications, and component locations can vary by vehicle. For manufacturer-specific codes, safety-critical systems, or repairs requiring specialized procedures, confirm the diagnosis with reliable service information or a qualified automotive professional.
