Documenting your steps in a Water Intake Counter means keeping a private, browser-only record of every cup you decide to count, alongside the whole-number daily target you personally chose. The tool stores that record in local browser storage under a single key, displays today's cup total against your chosen target, and keeps a short history list of past nonzero days. Each cup you record is one entry in your local tally, and each tap to remove a cup is one step backwards in the same tally. Nothing about the documentation is automatic or hidden — every cup must be added by you, every cup can be undone by you, and every export is generated in your browser from the values you typed. The result is a small, plain record that you can read on the page, open in a spreadsheet, or save as a single image, all without creating an account or sending anything to a remote service.
What Documenting Your Steps Looks Like Here
The phrase "document my steps" can mean several different things, depending on the workflow. In a paper log, it often means drawing a tally mark after every glass. In a spreadsheet, it can mean typing a number into the next empty row. In a digital counter, it usually means pressing one button to mark a completed unit and trusting the tool to keep a running count. The Water Intake Counter follows that third pattern: every step you document is one press of Add a cup, and every correction is one press of Undo a cup. There is no auto-detection of how much you have drunk, no estimate based on body weight, weather, or activity, and no hidden sensor import. Your documented steps are exactly the cups you decided to record, in the order you recorded them.
What the Counter Records About Each Cup
When you press Add a cup, the counter writes a small JSON record to your browser's local storage area. According to the WHATWG HTML Web Storage specification, local storage is the named key/value area that persists across page loads on the same origin. That record keeps the local calendar date on which the cup was logged, the running total of cups for that date, and, if a target was set, the target you were aiming at when the date's first cup was saved. The local date is produced by the Intl.DateTimeFormat API, which the ECMA-402 specification defines for locale-aware date formatting; that is why a cup you add late at night stays attached to that date instead of being moved by a UTC boundary.
The target field is documented at the moment a date's first cup lands. If you change your preference afterwards — for example, raising your goal from 6 cups to 8 cups on a Thursday — the new value applies only to days whose first cup is saved from that moment forward. Days that already have saved cups keep the target that was active when they were first written. That detail keeps your history honest: an older day's record cannot appear to have met a target that did not yet exist on the day you actually drank those cups.
Setting Up Your Target Before You Start
You do not need a target to begin documenting your cups, but setting one gives each saved cup a clear meaning against your own plan. Open the Water Intake Counter page and look for the optional label field and the daily target field at the top. The label is a short word or phrase you can type to remind yourself what the counter is for — a project name, a training block, a weekday plan, or anything else. The target accepts a whole number between 1 and 9,999 cups. There is no preset value, no medical recommendation, and no body-weight calculation behind it. The number you type is the number the page will measure you against.
If you leave the target empty, the counter still records every cup you add; the screen simply states that there is no personal progress target to display until you set one. Pressing Add a cup is the only action that locks a target into a date's record. Until you press it for the first time on a given date, the counter does not freeze any preference. That detail matters if you change your mind often: you can experiment with different targets across days, and each day's record keeps the version you had when its first cup was logged.
Recording and Correcting Each Step
Documenting your cups day-to-day is a short two-button loop, and the steps below are the practical workflow.
- Decide you want to record a cup — for example, after finishing a glass.
- Press Add a cup. The total for today increases by one, and the percentage against your target updates on screen.
- Read the plain status message below the total to see whether the day's target has been reached.
- If you pressed Add a cup by accident, press Undo a cup to remove the most recent cup from today's total. This is a single-step undo; it does not step further back.
- Continue adding or undoing cups as your day progresses.
The single undo covers almost every mistake, because the counter moves forward one cup at a time. If you undo when today's total is zero, nothing changes; if you undo by mistake, you can press Add a cup again to restore the value. Undo is not a way to edit an earlier cup from the day — it is a way to fix the very last cup you recorded.
Reviewing Your Documented History
Once you have saved cups on a few different days, the counter shows a history list below the day panel. Each row in the list represents one local calendar date on which at least one cup was recorded. The row displays the date, the total number of cups you saved for that date, and the target that was kept with that date — or a note that no target was set. The history list is read-only; you cannot edit a past day from it. If a past day's total looks wrong to you, the correct response is to add or undo cups on today and let tomorrow's row capture the new state.
The history list is the first place to look when you want to confirm what you actually documented. It does not summarise trends, calculate averages, or compare weeks; it is a literal list of dates and their counts. For any cross-day or cross-week analysis, the CSV export is a better starting point because it puts the same rows into a spreadsheet. For a fuller walk-through of what each field in the history list means, see how to view your Water Intake Counter results.
Exporting Your Documentation Outside the Browser
The counter gives you two export controls so you can take your documented steps somewhere else. Both controls run entirely in your browser using the canvas and Blob APIs; they do not upload anything, and they do not require an account. The table below summarises what each export contains and where it works best.
| Export type | What it produces | Columns or layout | Best for |
|---|---|---|---|
| CSV | A comma-separated text file you can open in any spreadsheet | Date, Cups, Daily target cups, Goal reached | Sorting, filtering, and adding your own formulas |
| PNG | A single 1080 by 1350 image built on a canvas | Total row plus recent day rows | A visual summary you can paste into notes or attach to a message |
Each saved nonzero day appears as one row in the CSV, and the Goal reached column shows whether the day's cups met or exceeded its target. The PNG export does not include the custom label you typed and does not embed a URL, so the image carries less personal context than the CSV. If preserving your own labels is important to you, keep the label inside the counter or note it in a separate document rather than relying on the image alone.
How Local Dates Shape Your Record
Because each cup is attached to the local calendar date your device reports, the documented record follows your day, not the UTC day. Cups logged before midnight on a Tuesday stay on Tuesday even if you continue drinking after the universal clock moves to Wednesday. When a new local day begins, the on-screen total resets to zero, and the previous day appears in the history list with whatever cups you had saved up to that point. The practical effect is small but worth knowing: if you travel across time zones, the date labels in your history reflect the date in each zone you were in at the time. That is rarely a problem for daily cup counts, and it is the reason the counter does not pretend to track drinking time — it tracks the local day on which each cup was logged.
What the Counter Does Not Document
A few limits keep the documented record honest. The counter does not calculate a recommended amount, infer a need based on body weight, apply a default medical target, diagnose hydration, or make a wellness promise. It does not convert cups to millilitres, import data from a wearable, ask for a health profile, or sync to another device. It does not run in the background, and it does not collect analytics about how you use it. The label you type, the target you choose, and the cups you record all stay inside the browser you are using right now.
If your browser blocks local storage, the page still loads and still lets you add cups, but a short on-screen message tells you it cannot preserve a durable history. In that case, your documented steps exist only for as long as the page stays open in that session. Clearing this site's browser data, or using the site in a private window that you later close, removes the stored record. If you want to keep the document, export a CSV or PNG before you clear anything.
Putting the Workflow Together
A short routine is enough to document your cups reliably, and the steps below summarise the full loop from opening the page to exporting a private file.
- Open the Water Intake Counter and type a short label if you want one.
- Enter a whole-number daily target in cups that matches your own plan.
- Press Add a cup each time you finish a glass; press Undo a cup if you tap by accident.
- Glance at the percentage and the on-screen status to see whether the day's target has been met.
- Open the history list to confirm what you have already saved across days.
- Export a CSV at the end of the week if you want a spreadsheet, or a PNG if you want a single image.
That sequence is the full document loop: set a target, record each cup, correct the occasional tap, review the list, and export a private copy when you want a file outside the browser. The counter does not add anything beyond those six moves, and that restraint is what keeps the documentation trustworthy.
If you're weighing options, Document Your Workout Steps in a Rep Counter covers this in detail.