Last updated: July 6, 2026. To clear OBD2 codes safely, scan all codes first, save freeze frame, check pending and permanent codes, record readiness monitor status, repair or inspect the cause, then use the scanner’s clear-code function. Do not clear codes first. Clearing codes can erase useful diagnostic data and reset emissions readiness monitors.
Clearing codes turns off the check engine light only if the fault is no longer active. It does not fix the problem. If the same fault returns, the light can come back quickly. If you are still learning scanner basics, read how to use an OBD2 scanner before clearing anything.
Before You Clear OBD2 Codes
| Before clearing | Why it matters |
|---|---|
| Save stored codes | Shows confirmed faults |
| Save pending codes | Shows early or intermittent faults |
| Check permanent codes | Some emissions codes will not clear immediately |
| Save freeze frame | Shows conditions when code set |
| Record readiness monitors | Important before emissions inspection |
| Note symptoms | Shaking, fuel smell, overheating, or flashing light changes urgency |
If your scanner shows stored, pending, and permanent code statuses, read stored vs pending vs permanent OBD2 codes first. Those statuses tell you whether the vehicle has a confirmed fault, an early warning, or an emissions code that must clear through monitor testing.
How to Clear OBD2 Codes Step by Step
- Park safely. Set the parking brake and turn off accessories.
- Plug in the scanner. Connect to the OBD2 port under the dashboard.
- Turn ignition ON. Use key-on engine-off unless your scanner or test requires the engine running.
- Read all codes. Record stored, pending, and permanent codes.
- Save freeze frame. Photograph or export the data if possible.
- Check readiness monitors. Record complete or incomplete status.
- Inspect or repair the cause. Do not clear only to hide the light.
- Choose erase/clear codes. Confirm the scanner warning if you are ready.
- Restart and rescan. Confirm codes do not return immediately.
- Drive and recheck readiness. Monitors may need drive cycles to complete.
What Happens When You Clear Codes?
Clearing codes usually removes stored and pending codes from current scanner view, turns off the check engine light if no active fault remains, and resets freeze frame for those codes. It can also reset readiness monitors to incomplete. That matters for emissions inspection.
Permanent codes work differently. A normal clear command may not remove them. The vehicle must run the required monitor and confirm the repair. If this happens after repair, use the OBD2 permanent codes guide instead of repeatedly pressing clear.
Should You Clear Codes Before Repair?
Usually no. Clear codes after saving data and after inspection or repair. Clearing first can hide the condition that caused the code. For example, freeze frame data can show whether a fault happened at idle, cold start, highway speed, or heavy load. Once cleared, that clue may be gone.
If the check engine light is flashing, do not clear and keep driving. A flashing light often means active misfire. Read check engine light flashing and diagnose before catalyst damage happens.
Clearing Codes Before Emissions Test
Do not clear codes right before an emissions test. Clearing codes often resets readiness monitors. The vehicle may show “not ready” even if the light is off. In many areas, incomplete monitors can cause inspection rejection or failure.
Before inspection, check OBD2 readiness monitors. If monitors are incomplete, drive cycles or further repair may be needed. A clean dashboard light is not enough. The scanner must show readiness status.
When Codes Come Back After Clearing
If the code returns immediately, the fault is still active or easy for the computer to detect. If it returns after one or more drive cycles, the monitor likely ran again and failed. Do not keep clearing the same code. Use scan data to diagnose.
| Return pattern | Likely meaning | Next step |
|---|---|---|
| Code returns instantly | Active electrical, sensor, or severe fault | Inspect circuit/data now |
| Code returns after driving | Monitor failed again | Check freeze frame and live data |
| Pending code returns first | Fault is intermittent or not fully confirmed | Use pending-code workflow |
| Permanent code remains | Vehicle has not proven repair yet | Check readiness and drive cycle |
For codes like P0171, P0300, or P0420, clearing without diagnosis often wastes time. Fuel trims, misfire counters, oxygen sensor data, and readiness status usually matter more than the clear button.
Scanner Features That Help
A basic scanner can clear codes, but a better workflow needs freeze frame, readiness, pending codes, permanent codes, and live data. If your scanner only shows code numbers, compare an OBD2 scanner with live data. New users can compare simple tools in the best OBD2 scanner for beginners guide.
Common Mistakes
- Clearing codes before saving freeze frame.
- Clearing codes right before emissions inspection.
- Thinking clear-code button fixes the problem.
- Ignoring pending codes after clearing stored codes.
- Trying to force-clear permanent codes.
- Replacing parts without checking live data.
- Clearing flashing-light misfire codes and continuing to drive.
FAQ
Does clearing OBD2 codes fix the car?
No. Clearing codes only removes stored diagnostic information and may turn off the light if the fault is not active.
How long before codes come back after clearing?
Some return immediately. Others return after the related monitor runs during a drive cycle.
Will clearing codes reset readiness monitors?
Yes, in many vehicles. That can create not-ready status before emissions inspection.
Can any OBD2 scanner clear codes?
Most basic scanners can clear standard engine OBD2 codes. ABS, SRS, and other modules may need enhanced scanner support.
Final Advice
Clear OBD2 codes only after saving data and understanding what you might lose. Record codes, freeze frame, readiness, and symptoms first. Repair or inspect the cause, then clear and rescan. If the code returns, diagnose the system instead of pressing clear again.
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.
