Last updated: July 6, 2026. An OBD2 permanent code is an emissions-related diagnostic trouble code that stays in vehicle memory until the vehicle confirms the repair through its own monitor tests. A normal scanner clear command may remove stored codes, but it usually will not erase a permanent code immediately. The vehicle must run the right drive cycle and pass the related monitor before the permanent code disappears.
Permanent codes confuse many drivers because the check engine light may be off while the scanner still shows a code. That does not always mean the repair failed. It means the vehicle has not yet completed enough self-testing to prove the fault is gone. If your scanner shows several code statuses, read stored vs pending vs permanent OBD2 codes before clearing anything else.
OBD2 Permanent Codes: Quick Meaning
| Question | Short answer |
|---|---|
| What is a permanent code? | An emissions code that remains until the vehicle confirms repair. |
| Can a scanner clear it instantly? | Usually no. The vehicle must pass its monitor. |
| Does it mean repair failed? | Not always. Monitor may not have completed yet. |
| Does it affect emissions? | It can, depending on local rules and readiness status. |
| Best next step | Check readiness, pending codes, live data, then complete drive cycle. |
Why Permanent Codes Exist
Permanent codes were designed to stop quick code clearing before emissions inspection. Without permanent codes, someone could clear a check engine light, drive straight to inspection, and hide an unfixed emissions fault until the monitor ran again. Permanent codes make the vehicle prove the repair by completing the related self-test.
That matters most for emissions-related faults such as catalyst efficiency, oxygen sensor heater circuits, EVAP leaks, fuel system problems, and misfire conditions. A code like P0420 may require catalyst monitor completion. A code like P0135 may need oxygen sensor heater monitor success. EVAP codes may need specific fuel level, temperature, and driving conditions before the monitor runs.
Permanent Code vs Stored Code
A stored code is a confirmed fault the scanner can often clear after repair. A permanent code is more stubborn. It remains until the onboard diagnostic system runs the required monitor and decides the fault is fixed. You can clear stored codes too early, but you cannot reliably force away a permanent code with a normal scan command.
A pending code is different again. Pending means the vehicle has seen a possible fault but has not fully confirmed it. If this part of scan data is confusing, use the OBD2 pending codes guide before deciding whether a fault is coming back.
Can You Clear Permanent Codes?
Most permanent codes are not cleared directly by the driver. The normal process is repair the cause, clear stored codes if appropriate, complete the required drive cycle, then rescan. If the monitor passes and no related fault returns, the permanent code can clear automatically.
If the permanent code stays after several normal drives, do not keep pressing clear. Check whether the related readiness monitor has completed. If the monitor is still not ready, the vehicle may not have had the correct conditions yet. The OBD2 readiness monitors guide explains why monitor status matters after repair.
Why Permanent Code Still Shows After Repair
| Reason | What it means | What to check |
|---|---|---|
| Drive cycle incomplete | Monitor has not run yet | Readiness status and required conditions |
| Fault still present | Repair did not fix root cause | Live data, pending code, freeze frame |
| Wrong part replaced | Code name was treated as part name | Diagnostic steps for exact code |
| New related fault | Different issue blocks monitor pass | All stored and pending codes |
| Battery/code clearing reset | Monitors started over | Readiness before inspection |
This is common after emissions repairs. For example, replacing a gas cap for an EVAP leak does not make the EVAP monitor run instantly. A thermostat repair for P0128 may need warm-up and driving conditions before the vehicle confirms coolant temperature behavior. A misfire repair may need clean misfire data over enough operation before the system trusts the result.
How to Handle a Permanent Code
- Scan all codes. Record stored, pending, and permanent codes before clearing anything.
- Save freeze frame. Use OBD2 freeze frame data to see when the original fault happened.
- Diagnose root cause. Do not replace parts from the code name alone.
- Repair the fault. Fix wiring, leaks, sensors, ignition, fuel, exhaust, or mechanical problems as testing shows.
- Clear stored codes only after recording data. Permanent code may remain.
- Check readiness monitors. See which monitor is incomplete or failed.
- Drive normally or follow service drive cycle. Conditions vary by vehicle and monitor.
- Rescan. Confirm no pending/stored code returns and permanent code clears after monitor success.
Permanent Codes and Emissions Inspection
Permanent codes can matter before emissions inspection, but exact rules vary by state or region. Readiness monitors are also important. A car with monitors not ready may be rejected or fail even when the check engine light is off. A car with a permanent code may need more driving after repair before it passes local inspection rules.
Do not clear codes right before inspection. Clearing resets monitors and can make the vehicle look unprepared. Instead, scan first, repair faults, complete drive cycles, then check readiness. If you are buying a used car, permanent codes and readiness status can reveal recent code clearing. The OBD2 scanner for used car inspection guide explains what to check before purchase.
Scanner Features That Help With Permanent Codes
To work with permanent codes, your scanner should show stored, pending, and permanent code status separately. It should also show readiness monitors, freeze frame, and live data. For fuel-trim or oxygen-sensor problems, live data matters because it helps prove whether the issue still exists. If your current reader only shows code numbers, compare tools in the OBD2 scanner with live data guide.
Common Mistakes With Permanent Codes
- Thinking permanent code means scanner is broken.
- Trying to force-clear the same permanent code repeatedly.
- Going to emissions inspection before readiness monitors complete.
- Replacing catalytic converter, oxygen sensor, or EVAP parts without testing.
- Ignoring pending codes that show the fault is still active.
- Clearing codes before saving freeze frame and readiness status.
- Assuming check engine light off means the vehicle is ready.
FAQ
What does permanent code mean on OBD2 scanner?
It means an emissions-related fault remains in memory until the vehicle confirms the repair by passing the related monitor.
Why will my permanent code not clear?
The monitor may not have completed, or the fault may still be present. Check readiness, pending codes, freeze frame, and live data.
Can permanent codes fail emissions?
They can affect inspection depending on local rules. Readiness monitors and active stored codes also matter.
How long does a permanent code take to clear?
It depends on vehicle, monitor, fault type, and driving conditions. Some clear after one successful monitor cycle; others need more driving.
Final Advice
Permanent codes are proof-based. Fix the root cause, save scan data, check readiness, complete the right drive conditions, then rescan. If a permanent code remains, do not fight the scanner. Find out whether the monitor has run and whether the fault is still active.
Written by Michael Hayes
Written by Michael Hayes, editor of Best OBD2 Scanner. Michael researches OBD2 scanners, diagnostic apps, trouble codes, live data features, and vehicle compatibility so readers can choose tools with fewer surprises.
