Rainwater Cistern Sizing Calculator
Plan storage around both supply and dry-weather demand
A rainwater cistern is easy to picture but surprisingly easy to size badly. Many quick estimates focus on only one side of the system. A large roof makes the tank seem safe, or a modest daily demand makes the project seem easy. In reality, a useful cistern sits between two moving forces. One force is supply: roof area, rainfall, and collection efficiency determine how many liters can actually reach the tank. The other is demand: the household draws water every day, and the system still has to feel reliable during stretches without useful rain. This calculator brings both sides into the same worksheet so you can compare what the roof can provide with the reserve you want to hold.
That comparison is the whole point of sizing. A bigger tank does not create water. If harvested supply is consistently below use, more storage by itself will not fix the problem. At the same time, healthy rainfall does not guarantee resilience if the cistern is too small to carry the household from one storm to the next. Good planning therefore asks two questions together: how much water can be harvested in an average month, and how much reserve should be available during a dry spell? The results panel on this page answers both instead of hiding the decision inside one opaque recommendation.
What each input means in plain language
Roof catchment area is the portion of roof that truly drains to the cistern. It is not always the full building footprint. Some roof sections may spill to grade, some may feed a separate downpipe, and some may not be connected to storage at all. The calculator expects square meters because that unit lines up neatly with rainfall depth. Once units match, rainwater yield becomes much easier to estimate and sanity-check.
Average monthly rainfall should be a planning value rather than a memorable storm total. Long-term monthly climate data is more useful than an unusually wet weekend because storage design is about repeatable performance. If your local climate has strong seasons, it is smart to run the tool several times. A wet-month case shows how much water could arrive, while a dry-month case tests whether your target storage and demand assumptions still make sense when conditions are least forgiving.
Collection efficiency is the reality filter. In theory, every millimeter of rain over the roof becomes runoff. In practice, some water never makes it into the tank. Leaves and grit may be diverted in a first-flush device, splash and wind can reduce capture, roof drainage may be imperfect, and screens or gutters can hold back part of the total. Efficiency converts the ideal yield into a realistic harvested volume. For many well-maintained systems, a broad planning range around 75% to 90% is common, but the right number depends on roof material, maintenance quality, debris load, and how aggressively you divert first-flush water for quality protection.
Daily household demand is the amount you expect to withdraw from the cistern each day. Sometimes that means total household use. In other projects it means only the uses actually tied to the rainwater system, such as irrigation, toilet flushing, laundry, or emergency backup. Either interpretation can be correct, but you must stay consistent. If the tank serves only selected fixtures, do not accidentally size it from whole-house consumption unless that is truly your design goal. If occupancy or irrigation changes by season, test more than one demand level.
Desired days of autonomy is the dry-weather bridge you want the tank to provide. This is partly a technical input and partly a resilience choice. A property with dependable municipal backup may be comfortable with a short autonomy target. An off-grid home, a preparedness-minded household, or a site with unreliable service may want a much longer buffer. The calculator turns that preference directly into storage liters, so autonomy is the clearest expression of how much protection you want between useful rains.
How the calculator turns those inputs into liters
The most helpful unit relationship in rainwater harvesting is this: 1 millimeter of rain falling on 1 square meter of roof equals 1 liter of water before losses. That is why the monthly harvest estimate is straightforward. Multiply catchment area by rainfall depth, then reduce the theoretical result by the efficiency percentage.
In that expression, A is roof area in square meters, P is monthly rainfall in millimeters, and E is collection efficiency as a percentage. Because the units are aligned, the result comes out directly in liters per month. This is the supply side of the problem.
The second major result is the storage volume associated with your resilience target. If the household needs D liters per day and you want the cistern to cover N days without meaningful refill, the reserve requirement is:
The calculator also reports an average daily surplus or shortfall. To do that, it converts monthly harvest into a daily average using 30.4375 days per month, which is the average month length across a year. That dailyized harvest is then compared with daily demand.
If B is positive, the page reports a daily surplus. If it is negative, the page reports a shortfall. That does not mean every real day behaves like the average; storms arrive in bursts, not in neat daily doses. It does, however, make the underlying balance easy to read. A persistent shortfall says the selected month, roof, or efficiency assumptions do not support the entered demand. A modest surplus suggests the system may be workable, but the cistern still has to be large enough to hold water between rain events.
If you prefer a general mathematical view, the preserved MathML below expresses the same idea in abstract form: the result is a function of several inputs, and many practical calculators combine weighted contributions from those inputs. In rainwater design, the efficiency term acts like one of those weights because it scales theoretical runoff into usable captured water.
Worked example using the default values
Suppose you start with the form defaults: a 100 m² roof, 80 mm of average monthly rainfall, 85% collection efficiency, daily household demand of 200 liters, and a target of 30 days of autonomy. The theoretical roof runoff before losses is 100 × 80 = 8,000 liters for the month. Applying 85% efficiency reduces that to 6,800 liters of usable harvested water. That is the first number the results panel will show.
The storage side is even simpler. A household using 200 liters per day for 30 days needs 6,000 liters of reserve. So the autonomy-based storage target is 200 × 30 = 6,000 liters. When you place the two results next to each other, the picture becomes clearer. The example month yields about 6,800 liters, while the desired dry-weather buffer is 6,000 liters. That does not prove the design is perfect, but it does suggest the entered scenario is at least in a plausible planning range.
To compare supply and use on the same timescale, the calculator converts monthly harvest to a daily average. Dividing 6,800 liters by 30.4375 gives about 223.4 L/day. Subtracting the entered demand of 200 L/day leaves an average daily surplus of about 23.4 L/day. The word average matters here. The household will not literally receive 23.4 extra liters every day. Instead, the number tells you that under the assumed monthly climate and capture conditions, harvested supply is slightly ahead of use.
This example is also a good model for sanity-checking your own entries. The result should feel believable before you trust it. With 80 mm of rain on a 100 m² roof, the upper bound before losses is 8,000 liters, so 6,800 liters after efficiency makes sense. If your result ever seems off by a factor of ten, the most common culprit is a unit mismatch such as entering annual rainfall where monthly rainfall is expected or using a roof area measured in square feet instead of square meters.
Why the results panel shows both harvest and storage
Some tools try to jump directly to a recommended tank size. This page deliberately shows multiple outputs because cistern planning is easier when the tradeoffs are visible. Monthly harvest tells you what the roof-climate combination can realistically provide. Storage for autonomy tells you how much reserve the household wants to keep in hand. Average daily surplus or shortfall tells you whether the selected scenario trends upward or downward over time. Looking at all three together is much more informative than relying on any one number alone.
For example, if the autonomy-based storage target is far larger than the harvested monthly supply, the problem is not just tank size. You may be trying to bridge a dry spell longer than the roof can support, at least with the entered demand. That often points to one of four design responses: increase catchment area, reduce demand, shorten the autonomy target, or accept a backup source for the driest periods. On the other hand, if monthly harvest looks abundant but the storage target is tiny, the system may work, yet you may also be letting useful water overflow during larger storms because there is not enough storage to hold it.
This is why scenario testing is worth a minute. Keep roof area fixed and try a drier month. Or keep climate fixed and lower efficiency to reflect a leafier site and more first-flush diversion. Or raise demand to represent a busier household or summer irrigation. Small, transparent changes tell you which variable is really driving the project. In many real cases, demand and desired autonomy move the recommended storage size just as strongly as rainfall does.
Example scenarios to compare before you commit
The table below changes only the rainfall assumption while leaving the other example values in place: 100 m² of roof, 85% efficiency, 200 L/day demand, and 30 days of autonomy. Because the storage target stays fixed at 6,000 liters, the changing balance is easy to interpret.
| Scenario | Monthly rainfall | Monthly harvest | Average daily balance | Interpretation |
|---|---|---|---|---|
| Dry month | 60 mm | 5,100 L | 32.4 L/day shortfall | The roof still contributes meaningful water, but the month is too dry to fully support the entered demand. |
| Baseline month | 80 mm | 6,800 L | 23.4 L/day surplus | The default example slightly outperforms demand on average and can justify a moderate storage target. |
| Wet month | 110 mm | 9,350 L | 107.2 L/day surplus | Supply is strong, so storage size becomes more about holding stormwater between events than finding enough water. |
The lesson is not that every project should be sized for the wettest or driest month. The lesson is that your answer depends on what kind of reliability you want. A design sized only from wet-month thinking can disappoint during lean periods. A design sized only from the driest month can become expensive and oversized if a backup source is available. This calculator helps you see that range rather than pretending there is only one universally correct tank volume.
Assumptions, limits, and responsible use
This is a compact planning tool, so it uses a simplified monthly water-balance approach rather than a day-by-day simulation. Real rainfall arrives in storms, not averages. Household use can spike during guests, irrigation season, or heat waves. Roofs do not always drain uniformly, and some projects must preserve emergency fire reserve or include treatment losses. None of those details make this tool unhelpful; they simply define what it is best at. It is excellent for checking scale, comparing scenarios, and deciding whether a concept is in the right neighborhood before you move into detailed design.
When choices are hard to reverse, use conservative assumptions first. If you are unsure whether efficiency should be 80% or 88%, start with 80%. If demand varies, run both a typical case and a high-use case. If climate swings sharply by season, test the dry month instead of relying only on an annual average. Conservative runs do not eliminate uncertainty, but they do reduce the risk of false confidence and make it easier to see how much safety margin your plan really has.
There are also factors this page does not explicitly size: first-flush chamber volume, water quality treatment, code-required overflow details, pump cycling, freeze protection, material compatibility for potable use, and local regulations. Those belong in later design stages or professional review when a project is moving from concept to installation. The strongest use of this calculator is as a clear thinking tool. It helps you state assumptions, compare options honestly, and understand whether the real driver is roof area, rainfall, efficiency, daily demand, or the level of autonomy you want.
If you remember one principle, make it this: a good cistern size is not just a container volume. It is a relationship between realistic supply and honest demand, filtered through losses and shaped by the dry spell you want to survive. When those pieces are aligned, the calculator output becomes a practical starting point for selecting storage that is financially sensible and operationally useful.
Mini-game: Storm Routing Challenge
This optional arcade mini-game turns the calculator logic into a fast decision exercise. You control a three-way valve while storm pulses rush down the pipe. Dirty first-flush water belongs in the flush lane, clean water belongs in the cistern, and excess clean water should be sent to overflow only when the reserve is already comfortably high. Household demand drains the tank throughout the round, so the best strategy is not grabbing everything at all times. The real goal is balance: keep reserve near the green target band that represents useful autonomy.
Controls: tap a lane button, tap or click the left-center-right thirds of the canvas, or use keyboard 1-3 and the arrow keys.
Educational takeaway: cistern sizing is a balance problem. Supply, efficiency, demand, and desired autonomy all matter together, and the smoothest game runs keep reserve near the useful target zone.