FC/CYA Explained: Salt vs Liquid — Practical Targets for Clear Water
If you’re ranking well but getting zero clicks, the fix is usually clarity: tell the reader exactly what they’ll get in the first screen. Here’s the operating model in one glance — then the page explains the “why” and the salt-vs-liquid control differences.
| CYA (ppm) | Minimum FC (ppm) | Everyday operating band (ppm) |
|---|---|---|
| 30 | ~2–3 | 4–6 (stable daily band) |
| 50 | ~4 | 6–8 (common “sun + normal use” zone) |
| 70 | ~5–6 | 8–10 (often used for SWG stability) |
If FC can drift to near-zero between tests, you’re not “fine” — you’re operating below your FC/CYA lane and relying on yesterday’s clarity.
The thinking error: “FC 1–3 is always enough”
“FC 1–3 ppm” sounds tidy, but it ignores the one variable that decides how aggressive (and how fast) chlorine works outdoors: CYA (cyanuric acid, stabiliser). CYA protects chlorine from UV burn-off — but it also “buffers” active chlorine. The more CYA you have, the more FC you need to keep the same sanitising strength.
Treat FC as a ratio target relative to CYA — not a standalone number. When you do that, the same pool can be “safe and stable” at FC 3 ppm or “barely hanging on” at FC 3 ppm, depending on CYA.
Here’s what the “1–3 ppm always” shortcut typically causes:
- Evening looks fine, morning is zero: UV and daily demand eat FC faster than you replace it.
- “I shocked and it came back” cycles: you spike FC once, but your day-to-day target is still too low for your CYA + sun.
- Salt pool frustration: an SWG makes chlorine slowly; if your target is wrong, you chase it with runtime and % without a plan.
FC/CYA as a control model (normal / load / post-storm)
Think of pool care like steering a car: you don’t set one number forever. You keep the vehicle in the lane by making small corrections. FC/CYA is the lane. The “modes” are the road conditions.
Your goal is a stable daily FC band that doesn’t crash overnight or under sunlight. If FC drifts down over several days, your daily replacement rate is lower than your daily consumption.
Expert clue: clarity is a lagging indicator; FC stability is leading. Clear water can still be under-target.
More swimmers = more organics, sunscreen, sweat, and micro-debris. Demand rises fast. Don’t wait for CC or smell — pre-load or same-day top-up is usually cleaner than “fixing it later.”
In salt pools, “just increase %” can react too slowly for same-day spikes. A measured liquid top-up can bridge the gap.
Storms are two events at once: dilution (FC and CYA can drop if you overflow/backwash/top up) and contamination (demand jumps from debris). The response is not “shock blindly” — it’s test → restore FC first → then re-check CYA.
Expert shortcut: estimate whether your SWG can keep up
The fastest way to stop guessing is to translate “chlorinator output” into a simple question: How many ppm of FC can my system add per day? Then compare that to your observed daily drop.
To raise FC by 1 ppm, you need about 1 gram of available chlorine per 1,000 litres of pool water.
Example: a 50,000 L pool needs ~50 g to rise by 1 ppm.
If your SWG produces X grams per hour, then daily FC added ≈ (X × runtime hours) ÷ pool litres × 1,000.
Table 1 — Scenario → Tests → Action order
Use this like a checklist. The “Action order” is sequenced to avoid chasing numbers in the wrong order.
| Scenario | Tests (first) | Action order (do this, then that) |
|---|
Salt vs liquid: where people misread “production” as “instant FC”
A salt chlorinator (SWG) doesn’t “dose” chlorine like pouring liquid. It produces chlorine gradually while water is flowing. That means you can be doing everything “right” (pump on, % set) and still see FC lag behind a sudden demand spike — especially after storms or heavy swimming.
Treating SWG output % like a “dose button”. Turning 40% → 90% is not the same as adding a measured amount of liquid chlorine today. It changes your rate, not an instant level.
The practical approach is to separate two jobs:
- Job A (baseline stability): set SWG % and pump runtime so a normal day stays inside your FC band.
- Job B (spike response): use a one-time correction (often liquid chlorine) when demand suddenly jumps.
Table 2 — Salt pool vs Liquid pool: control levers / drawbacks
Both systems can run crystal clear. What changes is how you control FC day-to-day and how fast you can respond when demand spikes.
| System | Control levers (what you adjust) | Typical drawbacks (what trips people up) |
|---|
Even in salt pools, a small amount of liquid chlorine is a useful “tool” for storms and parties. It’s fast response while the SWG handles the baseline.
After rain or overflow: why FC and CYA can both drop (and what to test first)
Melbourne-style rain, wind, and storms can change pool water fast. Two things often happen together: (1) dilution and (2) higher chlorine demand.
- Test FC first (and CC if you have it). If FC is low, restore it before interpreting the rest.
- Then test pH (especially if you’ll add chlorine or run equipment longer).
- Then test CYA once water is mixed and FC is back in a normal band.
The goal after storms is to return to your FC/CYA lane quickly and remove what’s feeding demand: skim, brush, clean baskets and filters, and restore circulation.
Timers and circulation: how schedule affects stability (no “magic hours”)
Your schedule matters because it decides when chlorine is produced (salt) or mixed (both), and how well the pool handles sunlight and bather load. There are no universal “magic hours”, but there are reliable principles:
- Mixing beats guessing: if you add liquid, run long enough to distribute it before re-testing.
- Sunlight is predictable: UV load peaks mid-day; having production/circulation during daylight helps stability.
- Skimming is demand control: removing organics early reduces the chlorine you must “burn” later.
- SWG needs flow: salt systems only generate chlorine while water is moving through the cell.
If FC drifts down day after day, you need more daily production (increase pump time, SWG %, or both). If FC climbs over several days, you need less daily production. Change one lever at a time, then observe for 2–3 days.
Key idea: you’re tuning a daily balance (production vs demand). Don’t overreact to a reading taken right after swimming or rain.
Concept chart — Daily FC stability: under-stabilised vs stabilised
This is a conceptual picture of what many owners observe: with low/insufficient stabiliser (or a too-low FC target for existing CYA), FC falls sharply through the day. With a stabilised, correctly-targeted system, FC stays inside a narrower band.
FAQ
ORP can be a helpful trend signal in automated systems, but it’s not a clean replacement for FC/CYA thinking. ORP is influenced by multiple factors (including pH, water chemistry, and sensor condition), so two pools with the same FC can show different ORP.
Practical approach: use ORP as an additional dashboard input if you have it — but keep FC/CYA as the primary sanitation lane.
The most common reason is that your daily replacement rate is lower than your daily consumption (sun, swimmers, debris). It also happens when the FC target is too low for your CYA, so you’re operating close to the minimum.
Fix the operating model: confirm CYA, set a realistic FC band, then tune production (SWG % / runtime) or dosing frequency so FC doesn’t crash.
Use the mini table at the top as a starting point: CYA 30 often runs well around 4–6 FC, CYA 50 around 6–8, and CYA 70 around 8–10, while keeping above the minimum for each zone.
The right number is the one that stays stable day-to-day without drifting toward zero.
If CYA is moderately high but stable, running the correct FC band for that CYA is often the simplest solution. Lowering CYA becomes more valuable when you need impractically high FC to stay stable, or when dosing/production becomes inefficient.
Make the decision operational: if your system can’t keep FC stable at your current CYA without constant “rescues,” CYA reduction can restore headroom.
It depends on pool volume, cell output, and runtime. The key is to treat SWG as a rate device: it adds chlorine gradually over hours, not instantly like liquid.
Use the conversion: ~1 ppm needs ~1 g per 1,000 L. Compare your cell’s grams/hour × runtime to your pool litres to estimate ppm/day.
Yes. It’s a common “spike response” tool for storms, parties, or when FC falls below target. The SWG then maintains the baseline once you’re back in range.
Hybrid control is normal: SWG for steady production, liquid for fast corrections.
CC is a signal that chlorine is reacting with nitrogenous contaminants. A small CC reading can happen after heavy swimming, but persistent CC suggests ongoing contamination or insufficient oxidation at your current operating level.
Practical approach: stabilise FC first (relative to CYA), improve circulation/filtration, and reassess trend rather than chasing one number.
Often yes, because demand usually drops with lower water temperature and lower UV. That typically means you can reduce production or dosing while still respecting the FC/CYA relationship.
Reduce gradually, watch the trend over several days, and avoid letting FC hit near-zero — that’s when small problems start quietly.
Want your FC/CYA targets set correctly (and stay stable day to day)?
We’ll test FC, pH and CYA, then set a practical operating band for your pool — plus a simple “storm/party” mode so you stop chasing zero → shock → zero cycles. Works for salt chlorinators (SWG) and liquid chlorine pools.
- FC/CYA baseline band + “minimum” safety floor
- SWG tuning: runtime/% + cell output & scaling check
- Post-storm sequence: test order + fast stabilisation steps
- Liquid “bridge dose” plan for heavy load days