Way 1: fix it and let the car turn it off
After a repair, the computer runs the test that failed again. Once it passes on enough trips, often about three, the light goes out on its own. Shops usually clear the code after a repair anyway, so you can see right away whether it returns.
Way 2: clear the code with an adapter
An OBD2 adapter can send the clear command. It erases the stored codes, the snapshot of what the engine was doing when the fault happened, and the readiness monitors. Good reasons to do it: a repair is done, or you want to see whether a fault comes back.
In our app, Clear codes sits behind a plain warning first, because it does not fix anything.
Way 3: disconnecting the battery
On many cars this clears the codes too, but it also resets the radio, the clock and the engine's learned settings, and some cars then need a relearn procedure. We do not recommend it as a way to turn off a light.
Why the light comes back
If the fault is still there, the car finds it again. Some faults return within minutes, others after the next cold start or a few days.
Cars from model year 2010 on also keep permanent codes that no adapter can erase. They clear only after the car confirms the repair itself. That is one way an inspection station can tell a code was cleared recently.
Clearing and inspections
Clearing sets every readiness monitor back to not ready. Many emissions inspections turn away a car with too many monitors not ready, so a freshly cleared car can fail even with no light on. Most monitors finish after a few days of mixed city and highway driving. See our guide to the check engine light and inspections.
This is also why our Used-Car Check shows how long ago codes were cleared: a seller can clear them right before your test drive.
Estimates only. A mechanic should confirm. If the car shows a hot temperature gauge, an oil pressure warning, smoke or a burning smell, stop as soon as it is safe.