Auto Counter does not run after you close the page; it is a browser-local interval counter that stops counting the moment the tab is closed, reloaded, or replaced by another page. The tool is intentionally designed as an all-client browser feature, not a background service, alarm, payroll clock, or monitoring system. Every increment is recorded only while this page remains open in the foreground or background tab, and the daily history you see is built from those same browser-side ticks. There is no server process waiting to pick up where you left off, no account that synchronizes a running session, and no hidden queue replaying old ticks after a refresh. Closing or reloading the page ends a running session; Auto Counter never pretends that an interval counter survived somewhere else. That boundary is the core of how it works and why its daily totals stay trustworthy: a count only exists when the page was open long enough for a whole interval to complete, and an export always matches what was visible when you pressed Pause.
Why the Counter Stops When You Close the Page
The closing behavior is a deliberate design choice, not a bug. Auto Counter uses Date.now inside browser event and timer callbacks to figure out how much wall-clock time has actually passed, then writes increments based on that elapsed measure. According to the WHATWG HTML Timers specification, browsers throttle or drop timer callbacks in background tabs, idle tabs, or busy systems, and a tab that is closed or reloaded loses every active timer entirely. Because there is no server queue and no background process listening for the page to come back, any time the tab is gone is time the counter cannot account for. Auto Counter states that boundary plainly: closing or reloading the page ends a running session, and it never pretends to have a process that continues elsewhere. Restarting begins a fresh session from the current moment so the new boundary is visible in your exported record.
How Delayed Browser Ticks Are Reconciled
A naive interval counter that simply increments on every callback will undercount when the browser is busy, when the tab is hidden, or when the laptop sleeps. Auto Counter avoids that trap with an elapsed-time anchor. When the Start button is pressed, the tool records the start moment. Each time a callback finally fires, the page calculates floor(elapsed milliseconds / chosen interval in milliseconds) and saves exactly that many whole intervals. Any leftover remainder is kept for the next callback, so a long pause followed by a resume action does not duplicate a count and does not throw away an almost-finished interval. For example, with a 60-second interval and 175 seconds elapsed since Start, floor(175 / 60) records 2 whole increments and carries 55 seconds of remainder forward to the next callback, so the pause-and-resume boundary still ends on 2 increments rather than 3 or 1. The interval control is locked while the session is running so the value cannot be changed mid-flight and reinterpret an interval that is already in progress. If a tab has been inactive for an unusually long time, the tool stops rather than attempting an unbounded replay of old ticks.
How to Run an Interval Session
Running a session is a five-step interaction. The list below walks through the full flow from label and interval choice to a file on your disk.
- Type a short label into the label field and pick a whole-number interval between 1 and 3,600 seconds.
- Press Start and leave the page open while the counter runs; the displayed count grows as whole intervals complete.
- Press Pause when the process ends; the tool reconciles every whole interval already completed and stops further automatic changes.
- Scroll to the local daily history to see every nonzero day in reverse chronological order with its automatic increment total.
- Choose Export PNG for a 1080 by 1350 share image containing only the total and recent day rows, or Export CSV for a simple Date and Automatic increments file you can open in a spreadsheet.
What Gets Saved and Where
Auto Counter keeps a bounded local JSON record under the localStorage key counter:auto-counter. The label you typed, your interval preference, and the saved daily counts are stored only in this key. Nothing is sent to a server, synchronized to another device, or joined to a user profile, and there is no upload queue, image processor, account, or outside API in the export path. Both PNG and CSV files are generated directly in the browser with native Blob and canvas APIs, as documented by the WHATWG HTML Web Storage specification for local key scoping and capacity. If local storage is disabled or full, the page still shows the current interaction and explicitly states that it cannot retain history; it does not claim a backup that does not exist. Clearing site data removes the record, and opening Auto Counter in a different browser starts with an empty history. The PNG export deliberately contains no web address and no custom counter label, so sharing a visual summary does not reveal an unnecessary personal note.
When Auto Counter Is the Right Tool
Auto Counter fits when time-driven automatic increments are the real task, the count should be driven by elapsed time rather than repeated taps, and you are happy to keep the page open while the process runs. For a simple production rhythm, a timed observation, a recurring reminder you want to record, or a station check that happens every N seconds, Auto Counter records each completed interval against your device-local calendar day. Open Auto Counter directly when you want to start a session without reading further. The table below compares it with the other counting and timing tools in the same category.
| Scenario | Tool that fits | Why it fits |
|---|---|---|
| Time-driven automatic count every N seconds while the tab is open | Auto Counter | Reconciles delayed ticks and groups totals by local day |
| Manual repeatable events with adjustable +1, +2, +3 steps | Online Tally Counter | Records each tap with configurable increments |
| Elapsed time and lap splits during a single activity | Online Stopwatch | Captures cumulative time and lap deltas |
| One-shot countdown to a fixed deadline | Online Countdown Timer | Counts down a fixed duration then stops |
For related reading on how automatic interval counts reconcile in the browser, the guide Auto Counter: Automatic Interval Counts in Your Browser walks through the same product from a different angle. If a delayed callback crosses midnight while the page remains open, the completed intervals are assigned to their applicable local days through Intl.DateTimeFormat rather than being forced into one UTC date, which keeps the day-level history aligned with the device clock the user actually saw.