Water Parameter Checker

Tank type

Targets are the site's own recommendations: ammonia 0, nitrite 0, nitrate under 40 ppm (under 20 for shrimp and sensitive fish). Temperature and pH never drive the verdict on their own — temperature is a band check, and pH matters through ammonia toxicity.

Is my water OK?

Enter at least one reading — ammonia, nitrite or nitrate is enough for a verdict — and the result appears here, with what to do about each reading.

Why use this calculator?

  • Judges your readings against the site's own targets — ammonia 0, nitrite 0, nitrate under 40 ppm (under 20 ppm for shrimp and sensitive fish).
  • Gives a concrete next step for every off-target reading, not just a pass or fail.
  • Treats a borderline ammonia reading of 0.25 ppm with care — it is often a test-kit phantom, so the tool says to test your tap water and retest before a panic water change.
  • Keeps temperature and pH in their place: temperature is a band check and pH matters through ammonia toxicity, so neither drives the verdict on its own — and at pH 7.5 and above, ammonia is more toxic, so it is flagged as urgent.

Test kits vary — a reading that doesn't match how your fish look deserves a second test, not panic. This tool checks water, not fish: if fish look sick, see the disease guide and find a fish vet. Full explanations live in the testing guide and the parameters guide. · Back to Water Chemistry

Enter your latest test-kit readings and get a verdict against the site's own targets — ammonia 0, nitrite 0, nitrate under 40 ppm (under 20 for shrimp and sensitive fish) — plus exactly what to do next. No account, no data saved: everything runs in your browser.

How it works

The checker judges each reading against the site's own published targets, then gives one verdict for the whole tank. Ammonia, nitrite and nitrate are the readings that drive the verdict; pH and temperature never do — they are context, not pass/fail.

Ammonia: 0 ppm. Any reading above 0 is a problem. 0.25 ppm is a caution, not an emergency — it is often a test-kit phantom, or a false positive within 24–48 hours of dosing Prime. Above 0.25 ppm is action needed, and at pH 7.5 and above ammonia is more toxic, so it is flagged as urgent.

Nitrite: 0 ppm. Any reading above 0 is action needed — nitrite is as toxic as ammonia.

Nitrate: under 40 ppm for a community tank, under 20 ppm for shrimp and sensitive fish. 20–40 ppm in a community tank is a caution — within the limit, but watch the trend. Over the limit is action needed.

pH: context only. pH is a stability number, not a pass/fail — compare it with your species' range. It matters through ammonia toxicity: raising pH turns harmless ammonium into toxic ammonia, so never adjust pH during an ammonia spike.

Temperature: a band check. The community band is 72–76°F. Outside it, the checker says so and points at your species' own range — bettas run warmer, goldfish cooler — but it never changes the verdict on temperature alone.

Worked example

Ammonia 0, nitrite 0, nitrate 10 ppm, pH 7.2, 75 °F, community tank.

Inputs

Ammonia 0 ppm, nitrite 0 ppm, nitrate 10 ppm, pH 7.2, temperature 75 °F, community tank type.

Formula

Each reading against its target: ammonia 0, nitrite 0, nitrate under 40 ppm (community). pH and temperature are context only.

Calculation

Ammonia 0 = on target. Nitrite 0 = on target. Nitrate 10 < 40 = under the limit. pH 7.2 is recorded, not judged. 75 °F is inside the 72–76 °F community band. No action, no caution.

Result

"Water looks good" — all tested readings are on target. Keep the routine: 25–30% weekly change, retest before the next one.

The opposite case shows what action looks like. Ammonia 0.5 ppm at pH 7.8, nitrite 0, nitrate 10 ppm: ammonia is over 0.25 ppm, so the verdict is "Action needed", and because pH is 7.8 — above 7.5 — the ammonia row adds that it is urgent. And a stubborn 0.25 ppm ammonia on its own gives "Mostly OK — one reading needs a second look": test your tap water first, and retest before a panic water change.

How to read your results

The verdict word is the headline, and the stat grid shows the three nitrogen readings that decided it. Under it, the rows are grouped: "Needs action" first, then "Caution", then "OK". Each row names the parameter, its reading, and what it means.

"Water looks good" means every tested reading is on target — keep the 25–30% weekly change and retest before the next one. "Mostly OK — one reading needs a second look" means nothing here is an emergency, but do not ignore the flagged reading: retest before acting, and watch the trend. "Action needed" means at least one reading is over the site's target — work the "What to do" checklist, then retest.

The "What to do" list is the action plan for the verdict, not a generic tip sheet. For action it starts with a big water change right now — 30–50%, temperature-matched, dechlorinated — then stop feeding, use Prime as a bridge, do not adjust pH, and find the cause. For caution it starts with retesting before acting.

Common mistakes

  • Panicking over a 0.25 ppm ammonia reading. It is often a test-kit phantom — test your tap water first: if tap also reads 0.25, it is the kit, not your tank.
  • Adjusting pH during an ammonia spike. Raising pH turns harmless ammonium into toxic ammonia — fix the ammonia first.
  • Treating one reading as the whole story. A number climbing week over week matters more than any single reading — watch the trend.
  • Chasing a perfect pH. pH is a stability number; a steady 7.2 beats a 7.0 that bounces. Compare with your species' range, not with a universal ideal.
  • Forgetting the cause. A spike is a symptom — new fish added all at once, filter media replaced, medication dosed. If you do not find the cause, it will be back next week.
  • Trusting a reading that does not match how your fish look. Test kits vary — a reading that disagrees with the fish deserves a second test, not panic.
  • Using a strip test for a decision that matters. Liquid kits and a TDS meter give numbers worth acting on; strips are a rough screen.

Targets table

The site's own recommendations, from the species database. These are the numbers the checker judges against.

ParameterTargetWhat happens over it
Ammonia0 ppm0.25 ppm: caution (often a phantom — retest). Over 0.25 ppm: action needed; urgent at pH 7.5+.
Nitrite0 ppmAny reading over 0: action needed — as toxic as ammonia.
Nitrate (community)Under 40 ppm20–40 ppm: caution, watch the trend. 40 ppm and over: action needed.
Nitrate (shrimp / sensitive)Under 20 ppm20 ppm and over: action needed — water change now.
Temperature (community)72–76 °FOutside the band: check your species' own range. Never drives the verdict alone.
pHSpecies' rangeNot judged as pass/fail. Matters through ammonia toxicity.

FAQ

What should my ammonia, nitrite and nitrate be?

Ammonia 0, nitrite 0, nitrate under 40 ppm — under 20 ppm for shrimp and sensitive fish. Those are the site's own targets, and they are the numbers this checker judges against.

My ammonia reads 0.25 ppm — is that an emergency?

Usually not. 0.25 ppm is often an API kit phantom reading, or a false positive within 24–48 hours of dosing Prime. Test your tap water first: if tap also reads 0.25, it is the kit, not your tank. If the fish look fine, retest before a panic water change.

Why doesn't pH change my verdict?

Because pH is a stability number, not a pass/fail — every species has its own range, so there is no single pH that is right for every tank. pH matters through ammonia toxicity instead: at pH 7.5 and above, ammonia is more toxic, so an ammonia problem at high pH is flagged as urgent. And never adjust pH during an ammonia spike.

What do I do first when a reading is over target?

A big water change, right now: 30–50%, temperature-matched and dechlorinated, then retest. Stop feeding for a day or two, remove anything rotting, and use Prime or equivalent as a bridge — it buys 24–48 hours of reduced toxicity while you fix the cause. It is a bandage, not a cure.

My nitrate keeps climbing between water changes — what is wrong?

Usually feeding or stocking: too much food, too many fish, or both. A routine 25–30% change keeps nitrate down, but if it keeps climbing, feed less and consider fast-growing plants to soak up nitrate — and check whether the tank is overstocked.

How often should I test?

Weekly, before the next water change — weekly testing catches drift early, and a number climbing week over week matters more than any single reading. Test daily while cycling a new tank, or while a reading is over target.

Does this tool diagnose sick fish?

No. It checks water, not fish. If fish look sick, see the disease guide and find a fish vet — this tool gives you the numbers to show the vet, it does not tell you what is wrong with the fish.

Sources

  1. Our recommendation — TheCycledTank species database (data/species-db.json, water_targets). Ammonia 0, nitrite 0, nitrate under 40 ppm (under 20 ppm for shrimp and sensitive fish), community temperature 72–76 °F. Also the note that API kits can show a phantom 0.25 ppm ammonia reading and Prime can cause false-positive ammonia readings.
  2. Our guide — TheCycledTank water-testing guide. How to test, and why a reading that does not match how the fish look deserves a second test.
  3. Our guide — TheCycledTank ammonia, nitrite and nitrate parameters guide. The full explanations behind the targets, including the emergency option for nitrite (aquarium salt at 1 tsp/gal, dissolved, gradual — read its caveats first).

This tool's targets are the site's own published recommendations, not figures taken from a standard or textbook — no external source was used for them. The 25–30% weekly water change is the site's own baseline. Treat the targets as the site's tested practice, and verify against your test kit.

Related tools