Tap water calculator
A kitchen tap at 8 liters per minute running 15 minutes a day uses 120 liters daily and 43,800 liters a year. Enter flow and open-tap minutes for any faucet or shower to see your yearly volume. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Flow rate
- 8
- Minutes per day
- 15
- Days per year
- 365
- Daily liters
- 120
- Yearly liters
- 43,800
Household tap water is easy to underestimate because faucets and showers do not report liters the way a utility meter does. Daily liters equal flow rate times usage minutes; yearly liters scale that product by three hundred sixty-five. Zero is valid and returns zero liters.
How daily and yearly tap water use is calculated
If a kitchen faucet is rated at eight liters per minute and it runs fifteen minutes a day, daily use is one hundred twenty liters; over a three-hundred-sixty-five-day year that is forty-three thousand eight hundred liters. Aerated bathroom faucets often sit near five to eight liters per minute, kitchen taps near six to nine, and showers commonly nine to fifteen depending on the head and local plumbing codes.
Usage minutes should reflect actual open time, not time spent standing at the sink; washing dishes for twenty minutes with the tap off between rinses might be only four minutes of flow. Zero flow or zero minutes is allowed and returns zero volume; a negative value on either field is rejected because it cannot describe a real tap.
Where a tap water calculator earns its keep
Sustainability dashboards and household water audits need a deterministic, auditable line item for open-valve use that does not depend on a spreadsheet cell someone can overwrite by accident. Property managers batch the same two fields across unit types to rank buildings for retrofit programs. Classroom environmental science courses need an oracle that multiplies liters per minute and minutes correctly and scales to a year for grading rubrics.
Failed validation does not consume balance. Keep requests small, pin the rounded daily and yearly liters in tests, and you get reproducible estimates for audits, LMS plugins, and edge workers without standing up a full water-modelling stack of your own.
What you can do with it
Shower and faucet retrofit savings
Compare yearly liters of an old 15 L/min shower against a 9 L/min head using the same daily minutes to justify the upgrade.
FAQ
How do I estimate tap water use from flow rate and minutes?
Daily liters equal flow rate times minutes; yearly liters equal daily liters times 365.
What flow rate should I use for a typical tap?
Use the rating on the aerator or shower head, or meter it with a jug and a stopwatch. Bathroom faucets often sit near 5–8 L/min, kitchen taps near 6–9 L/min, and showers commonly 9–15 L/min.
Should I count the time I stand at the sink or only when water runs?
Count only the minutes the water is actually flowing. Washing dishes for 20 minutes with the tap off between rinses might be just 4 minutes of flow, and that smaller figure is the one to enter.
How do I compare an old shower head with a water-saving one?
Run the calculation twice with the same daily minutes: once at the old flow, such as 15 L/min, and once at the new one, such as 9 L/min. The gap between the two yearly totals is your saving.
What is the most minutes per day I can enter?
Up to 1440, the number of minutes in a day. Zero is accepted and gives zero liters, and decimals such as 8.5 minutes are fine, but negative values are refused because no tap delivers negative water.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/eco/tap-water \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"flow_rate":8,"minutes_per_day":15}'const res = await fetch("https://api.kit.forhosting.com/eco/tap-water", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"flow_rate": 8,
"minutes_per_day": 15
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/eco/tap-water",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"flow_rate": 8,
"minutes_per_day": 15
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/eco/tap-water", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"flow_rate":8,"minutes_per_day":15}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"flow_rate":8,"minutes_per_day":15}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/eco/tap-water", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"flow_rate": 8,
"minutes_per_day": 15
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "eco.tap_water",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Negative flow rates and negative minutes are rejected as invalid_input because a tap cannot deliver a negative volume under this linear model.
How daily and yearly tap water use is calculated
The calculator always treats flow_rate as liters per minute and minutes_per_day as minutes of open-valve time in a typical day, then multiplies them for daily_liters and scales by three hundred sixty-five for yearly_liters. Results are rounded to twelve decimal places so automated tests and API clients see stable numbers across runtimes without inventing extra precision beyond what the inputs justify.
Input contract, typical flow rates, and response fields
Minutes per day cannot exceed one thousand four hundred forty, the minutes in a calendar day. Zero is valid on either factor and returns zero liters. Example: eight liters per minute times fifteen minutes is one hundred twenty liters a day and forty-three thousand eight hundred liters a year. Pair the volume with your own water tariff if you need a cost estimate; this capability focuses on liters only so rate tables stay outside the pure parse path. Accepted aliases for the rate are lpm, liters_per_minute, flow, flow_lpm, and flow_rate_lpm. Accepted aliases for the time are minutes, usage_minutes, daily_minutes, and min_per_day. Each field may arrive as a JSON number or as a decimal numeric string. Missing fields, empty strings, non-finite values, and magnitudes beyond the supported ceiling fail with invalid_input naming the field. A negative flow rate or a negative minute count is rejected because a tap cannot deliver a negative volume under this linear model; the error message states that the field cannot be negative and the request is not billed. On success the body echoes the cleaned flow_rate and minutes_per_day, reports days_per_year as three hundred sixty-five, and returns daily_liters and yearly_liters plus a short formula string you can show next to the answer.
Integration use cases
Household water audits
Estimate each tap separately, sum daily liters, and fold fixture use into a broader indoor water budget for leaks and conservation planning.
Automation and sustainability reports
Call the API from a dashboard with flow_rate and minutes_per_day to produce stable yearly liter totals for multi-unit properties.
Technical questions
Should minutes_per_day be time at the sink or time the valve is open?
Use open-valve time only. Twenty minutes of dishwashing with the tap off between rinses might be only a few minutes of actual flow.
What if flow_rate or minutes_per_day is negative?
The task fails with invalid_input. A tap cannot deliver a negative volume under this linear model, so any negative factor is rejected and is not billed. Zero is valid and returns zero liters.
What does the tap water calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.