Auto Counter is a browser-based interval counter that adds one to your total for every whole interval of seconds you choose, then saves each day's total to a private local record while the page stays open. You start by entering a short label, picking a whole-number interval from 1 to 3,600 seconds, and pressing Start; the counter then increments by elapsed time rather than by taps or clicks, and it pauses by reconciling completed intervals before stopping. Because the count is anchored to elapsed time inside the running tab, a delayed callback that finally fires adds every full interval that has actually passed instead of treating that one callback as a single count. Completed increments are then mapped to the device-local calendar day they belong to, so a session that crosses midnight assigns earlier counts to the previous local day rather than collapsing everything into one date. The label, interval, and saved daily totals live only inside the browser's local storage for this counter, and both a CSV export and a 1080-by-1350 PNG export are generated directly in the browser using native Blob and canvas APIs. That is the entire boundary of the tool: it counts while the page remains open, reconciles delayed ticks by elapsed time, groups results by local day, and produces a local-only export file when you ask for one.
The reason Auto Counter exists is the situation where the count is driven by elapsed time rather than by repeated manual taps. A simple production rhythm, a timed observation, a recurring reminder you want to record, a station check, or any neutral process where the number of items equals the number of intervals that have passed is a good fit. The tool is intentionally not a background service, an alarm, a payroll clock, or a monitoring system; it makes the boundary visible by counting only while this page remains open in the browser. That boundary matters for getting started, because the very first decision is whether your real task is time-driven automatic increments or something else.
What Auto Counter Does and When It Fits
The counter runs a single active session at a time. A session is the span between one press of Start and the next press of Pause. While the session is active, the counter adds one to the running total for every full chosen interval that has elapsed. When you press Pause, the tool reconciles every whole interval already completed and stops further automatic changes, so the displayed total at the moment of pause reflects exactly the elapsed time since Start, interpreted through the interval you chose.
Use Auto Counter when the count is genuinely a function of time. A slow continuous drip into a bucket over a 90-minute window, a queue that is supposed to clear every 20 seconds, or a process step that should happen once per minute are all examples. Do not use it as an alarm (use a browser alarm if you need a sound), as a payroll clock (it does not keep running after you close the page), as a stopwatch (it returns a count, not an elapsed time with lap splits), or as a manual tally (every tap would be the wrong interaction when the count should be time-driven).
The Three Inputs You Need Before You Press Start
There is no account, no signup, and no server configuration. The interaction is a short label, a whole-number interval, and the Start button.
- Short label. The label identifies the counter on your device. It is a private note and never appears in any exported file by design: the CSV only carries the date and the automatic-increment count, and the PNG is intentionally produced without the label so a shared image cannot leak a personal note. Pick something short enough to recognise on your own screen.
- Whole-number interval in seconds. The interval field accepts only whole seconds from 1 through 3,600. There is no preset value, and the tool does not claim that any particular number is better, safer, or more productive. Pick the interval that actually describes your own process: a 30-second check, a 5-minute reminder, a 60-minute observation.
- An open tab that stays in front. The counter lives inside the page. As long as this page remains open in the browser, the count keeps advancing by elapsed time. Closing the tab, reloading the page, or letting the browser discard the tab ends the running session.
If local storage is disabled or full, the page still shows the current interaction and tells you it cannot retain history; it does not claim a backup that does not exist. You can still run a session and still export, but the saved daily history will not persist after the page goes away.
How to Run Your First Auto Counter Session
The first run is intentionally short. The steps below walk you through the same three operating actions every session uses.
- Open Auto Counter in a browser tab and type a short label that describes the process you are timing (for example, "queue check" or "station rhythm").
- Enter a whole-number interval in moments that matches how often your process is supposed to add one count. The field accepts 1 to 3,600 seconds; leave it at the default if you are unsure, then adjust it on a later session once you have seen the pace.
- Press Start. The page is now the active session. Keep the tab open in the foreground while the process runs; the running total updates as whole intervals complete. The interval control is locked while running, so the in-progress session cannot be reinterpreted by a mid-session edit.
- Press Pause when the process you are timing ends. Pause first reconciles every whole interval already completed and then stops further automatic changes, so the displayed total equals the elapsed time since Start interpreted through your chosen interval.
- Open the daily history panel to confirm the local-day total for today. If you want a file outside this browser, export PNG for a visual record or CSV for a spreadsheet-friendly file using the export controls on the page.
For a first sanity check, try a 60-second interval for ten minutes. Ten minutes is 600 seconds, and 600 seconds divided by 60 seconds per interval equals 10 increments. The displayed total at Pause should be 10, and the history row for today should show 10 automatic increments. If your computer is busy and the callback fires late, the next callback will still reconcile to the same total because the count is anchored to elapsed time, not to the number of times the timer was allowed to fire.
How the Count Stays Honest Across Pauses and Background Tabs
Browser timers are not metronomes. A busy computer or a hidden tab can delay an interval callback, and treating each callback as exactly one increment would quietly undercount. Auto Counter instead keeps an elapsed-time anchor from the moment Start was pressed. When a callback finally runs, the tool calculates how many full chosen intervals have actually passed since the anchor and records those completed increments together. Any partial interval remains as a remainder for the next callback, so a pause and resume action never duplicates a count and never throws away an almost finished interval.
The same elapsed-time anchor is what makes pausing reliable. Pause first reconciles every whole interval already completed and then stops further automatic changes, so the number on screen is the same number that becomes the saved daily increment for that local day. If a delayed callback crosses midnight while the page remains open, the completed intervals are mapped to their applicable device-local calendar days rather than forced into a single date. Internally, the page uses Intl.DateTimeFormat to group completed intervals by the device's local day, so a session that started at 11:50 PM and ran past midnight will save its early counts to one date and its later counts to the next.
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. There is no silent replay that would inflate your count when you finally return to the tab. According to the WHATWG HTML Timers specification, browser timers can be throttled or coalesced when their host page is inactive, which is the underlying reason Auto Counter reconciles from elapsed time instead of counting raw callbacks.
Reading Your Daily History and Exporting the Record
Daily history is a durable local record for increments that were saved. Every nonzero date appears in reverse order with its automatic increment total, and the list lives under a local browser key for this counter only. There is no upload queue, no image processor, no account, and no outside API in the export path; both file types are generated directly in the browser using native Blob and canvas APIs, so a clear site-data wipe is the only way the record leaves your device, and a different browser will start empty.
The CSV export creates a simple two-column file with Date and Automatic increments that opens cleanly in any spreadsheet for archiving or further analysis. The PNG export creates a natural 1080 by 1350 share image with a total and the most recent day rows; the image deliberately contains no web address and no custom counter label, so exporting a visual summary does not reveal an unnecessary personal note. If a number in your history looks off, the guide on how to check the result after using Auto Counter walks through the reconciliation logic and what to look for.
Picking the Right Tool for Time-Driven vs. Tap-Driven Counting
Choosing the right tool matters more than picking the perfect interval. The table below summarises the boundary that Auto Counter explicitly draws against its closest neighbours in the productivity category.
| Your real task | Best fit | Why this tool |
|---|---|---|
| Add one count per elapsed interval while a tab stays open | Auto Counter | Count is driven by elapsed time, reconciled by floor(elapsed / chosen interval), and saved by local day. |
| Add one count per deliberate tap or button press | Online Tally Counter | Every increment is a manual event; the count is not tied to a timer firing. |
| Measure elapsed time with lap splits, not a count | Online Stopwatch | Returns a duration and split table rather than a daily total. |
Auto Counter is the right choice when the number you want at the end of the day equals how many whole intervals fit inside the time the page was open. If the count has to follow your fingers, switch to a manual tally counter. If the result has to be a duration, switch to a stopwatch. Picking the wrong shape is the most common reason an auto counter feels off; once the shape matches, the rest is just setting the interval that describes your own process and letting the elapsed-time anchor do the work.
If you're weighing options, How to Get Started With a Chess Clock for the First Time covers this in detail.