An auto counter is a tool that increments a running total on a fixed time interval you choose, rather than waiting for a manual click for each item. Auto Counter, a private browser tool, adds exactly one count at the end of every whole interval you set, from 1 to 3,600 seconds, for as long as the page remains open. Each count is recorded under the device-local calendar day on which the interval actually completed, so a callback that finally fires after a long pause is reconciled against elapsed time instead of being treated as a single tick. The session is started and stopped with explicit Start and Pause buttons, and the interval control is locked while running so a change cannot reinterpret counts already in progress. Saved counts, your chosen label, and your interval preference stay under one browser-local key and never sync to a server. When you want a file outside the browser, you can export a CSV with Date and Automatic increments or a 1080 by 1350 PNG share image, both generated locally with native Blob and canvas APIs.
When a Time-Driven Count Beats Manual Tapping
Some counting work is driven by the event itself — you tap a button each time you see one. Other work is driven by elapsed time: a production line moving at a fixed cadence, a recurring observation you want to record, a station check on a timer, a quiet reminder to glance at something every few minutes. In those cases, the count is the time, not the action, and a manual tally counter forces you to be the timer. That is the gap an auto counter is designed to fill — it does the incrementing so you can keep your eyes on the process itself.
The tool is intentionally small. It does not run in the background, it does not pretend to be a server process, and it does not need an account. The boundary is the open tab, and the boundary is visible. The real task it is built for is a neutral process where the count is driven by elapsed time rather than repeated taps, and where a button press for every item would be the wrong interaction.
How to Run an Auto Counter Session
Open the Auto Counter page in your browser. The whole session is built around three interactions: pick a label, choose an interval, and start the timer.
- Enter a short label that describes what you are counting — a station name, a process step, an observation tag, or any neutral reminder phrase.
- Choose a whole-number interval, anywhere from 1 to 3,600 (one hour).
- Press Start and keep the page open while the counter runs. Leave the tab in view if you can; a backgrounded tab can delay callbacks.
- Press Pause when the session ends. The pause reconciles every whole interval already completed and stops further automatic changes.
- Review the local daily history on the page, then export PNG or CSV if you want a file outside the browser.
Start always begins a new active session from the current moment. The interval control is locked while the counter is running so a change cannot reinterpret the time already in progress. If you need to change the cadence, pause first, edit, then start a fresh session so the new boundary is clear. Restarting makes the new session boundary visible and prevents the tool from quietly replaying a long stretch of stored ticks.
How Delayed Browser Ticks Are Reconciled
Browser timers are not metronomes. A busy computer, a hidden tab, or an operating system suspend can delay a callback for tens of seconds or longer. If the tool simply added one count for every callback, a delayed tick would silently undercount the real passage of time.
Auto Counter keeps an elapsed-time anchor instead. When a callback finally runs, it calculates how many full chosen intervals have actually passed and records those completed increments together. Any partial interval remains as a remainder for the next callback, so a pause action does not duplicate a count or throw away an almost-finished interval. If a tab has been inactive for an unusually long time, the tool stops rather than attempting an unbounded replay of old ticks, and restarting makes the new session boundary clear.
Under the hood, the running session uses Date.now() only inside browser event and timer callbacks (per the WHATWG HTML Timers specification), then applies floor(elapsed / chosen interval) and preserves the unfinished remainder. The count is anchored to elapsed wall-clock time rather than callback frequency, which is the only way to keep the daily total honest when the browser hands back control late.
Daily History, Local Days, and Midnight Crossings
The displayed count is grouped by the device-local calendar day. The tool uses Intl.DateTimeFormat to map each completed interval to its applicable local day, which matters if a delayed callback crosses midnight while the page remains open. The completed intervals are split between the two real calendar days rather than forced into one UTC date, so the daily total reflects the actual day each increment landed on.
Daily history is a durable local record for every increment that was saved. Every nonzero date appears in reverse order with its automatic increment total. Your label, interval preference, and saved counts are stored under the browser-local key counter:auto-counter, as described in the WHATWG HTML Web Storage specification. Nothing is sent to Lizely, synchronized to another device, or joined to a user profile. Clearing site data removes the record, and a different browser starts empty. If storage is disabled or full, the page still shows the current interaction and states that it cannot retain history rather than claiming a backup that does not exist.
Picking a Whole-Second Interval That Fits Your Process
The interval field accepts whole seconds from 1 through 3,600. The tool does not claim that any particular value is better, safer, or more productive — only that the value should describe the rhythm of your own process. Use the table below to match common situations to a starting interval; you can always adjust after a first trial run.
| Situation | Starting interval | Why this range |
|---|---|---|
| Slow paced observation (every few minutes) | 120 to 600 seconds | Long enough to span a real change, short enough to keep a visible cadence |
| Station check or glance reminder | 60 to 300 seconds | Matches a typical work rhythm and stays easy to scan in the daily history |
| Production line pace (units per minute) | 30 to 60 seconds | Captures steady throughput without piling up noisy counts |
| Fast visual sweep | 5 to 15 seconds | Used when the event is short and a dense record is helpful |
| Long quiet reminder (per hour) | 3,600 seconds | One count per hour, the upper bound of the interval field |
Exporting a PNG or CSV Record
When the session is done and you want a file outside the browser, Auto Counter generates two formats directly in the page using native Blob and canvas APIs. There is no upload queue, no image processor, no account, and no outside API in the export path.
- Export CSV creates a simple two-column file with Date and Automatic increments rows, ready to open in a spreadsheet or archive.
- Export PNG creates a 1080 by 1350 share image with a total and recent day rows. The image deliberately contains no web address and no custom counter label, so a visual summary does not reveal an unnecessary personal note.
Both files are produced locally. If you close or reload the page, the running session ends and the next session starts clean — the tool never pretends a server process is continuing elsewhere. Privacy is part of the functional design, not a separate promise layered on top.
Auto Counter vs Manual Tally vs Stopwatch
Three related tools solve three different problems. Picking the right one keeps the data shape honest. The table below summarizes where each tool fits.
| Tool | Best for | What it tracks | Session boundary |
|---|---|---|---|
| Auto Counter | Time-driven automatic increments | One count per completed interval, grouped by local day | Runs only while the page is open; Pause reconciles completed intervals |
| Online Tally Counter | Manual adjustable-step events | One count per click, grouped by local day | Local browser history persists; counts are driven by the operator |
| Online Stopwatch | Elapsed time and lap splits | Milliseconds and lap order | Pause-and-resume session with a lap list |
Use Auto Counter when time-driven automatic increments are the real task. Use the Online Tally Counter for manual adjustable-step events where each click is the event. Use the Online Stopwatch when you need elapsed time and lap splits rather than a daily count. The product is intentionally narrow so the boundary matches the actual job.