Why pH Crashes When KH Runs Out

Written 2026-10-03

A KH (buffering capacity) crash is the cause, and the pH crash is just what follows. Every time nitrifying bacteria break down ammonia and nitrite, they spend a little KH, and only a water change puts it back — it never recovers on its own. We ran a 60cm tank with 10 neon tetras for 180 days in the Water Kiwoogi simulator. With no water changes at all, KH starts at the tap-water level of 4.0, a "KH is depleted and pH has crashed" warning fires on day 63, and from day 70 pH is pinned at 5.0 while ammonia and nitrite climb out of control — fish start dying on day 92, and all 10 are gone by day 144. Add nothing but a weekly 25% water change to the same setup, and KH never drops below 2.4: ammonia stays at zero for all 180 days, and every fish survives.

Nitrification spends KH, a little at a time

The bacteria that turn ammonia into nitrite, and nitrite into nitrate, spend KH every time they do that job. Tap water usually starts around KH 4.0, and as long as bacteria keep processing the nitrogen fish produce, KH drops by an amount too small to notice, day after day. A water change puts that KH back, but skip it and the drop just carries over to the next day. In a plain black-sand tank with no KH-raising substrate or stone (coral sand would do that), this slow drain can build up quietly over weeks or months.

The moment the buffer is gone, pH falls straight down

While KH still has a point or two left, pH holds steady around 7. But once KH drops below 0.25, the water has nothing left to resist acid with, and pH falls straight to 5.0 — what this simulator calls a "KH crash." The catch is that nitrifying bacteria are sensitive to pH too: they work at full speed above pH 7.2 and almost stop below 5.8. So after a KH crash, bacteria can’t keep up with ammonia and nitrite anymore, and both toxins pile up together in a feedback loop. That’s why, in the 10-neon-tetra tank, ammonia (in test-kit ppm) passes 0.5ppm on day 70, then climbs to 5.5ppm by day 90 and 12ppm by day 120.

What to change

Watching pH alone makes it easy to miss KH running out, since pH barely moves while KH still has some left, then drops all at once the moment it’s gone. In the same run, pH held at 7.05 through day 55, eased to 6.67 by day 65, and hit 5.0 by day 70 — a steep fall in just ten days. Test KH separately once in a while, and if it’s down to 1 or 2, don’t wait for the next scheduled water change — do one right away. If pH has already crashed to 5.0, raise KH gradually with small, frequent water changes rather than one big one — a sharp pH swing in a single day is stressful for fish on its own. If you’re not sure, it’s safest to check with a local aquarium shop or an expert.

The button below runs the 60cm standard tank · 10 neon tetras · no water changes at all tank from this guide. Switch the water-change setting to a weekly 25% and run it again to see KH stop draining for yourself.

The numbers in this guide come from the Water Kiwoogi simulator model; real tanks can differ.