Skip to content
Lizely

Auto Counter

Run a private start, pause, and resume interval counter that reconciles delayed browser ticks into local daily history.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Enter a short label and choose a whole-number interval from 1 through 3,600 seconds.
  2. 2.Press Start and keep the page open while the counter runs; press Pause to reconcile completed intervals and stop it.
  3. 3.Review the local daily history, then export PNG for a visual record or CSV for a spreadsheet-friendly file.

About Auto Counter

Auto Counter is a browser-local interval counter for situations where pressing a button for every item is the wrong interaction. Choose a whole-number interval in seconds, give the counter a short label, and press Start. The page then adds one count for every completed interval until you pause it. This is useful for a simple production rhythm, a timed observation, a recurring reminder you want to record, a station check, or any neutral process where the count is driven by elapsed time rather than repeated taps. The product is intentionally not a background service, an alarm, a payroll clock, or a monitoring system. It is a small local tool that makes its boundary visible: it counts while this page remains open in the browser.

A browser timer is not a metronome. 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. 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 and resume action does not duplicate a count or throw away an almost finished interval. The displayed count is grouped by the device-local calendar day. If a delayed callback crosses midnight while the page remains open, the completed intervals are assigned to their applicable local days rather than being forced into one UTC date.

The interval field accepts whole seconds from one through 3,600. Pick the interval that describes your own process; the tool does not claim that any particular value is better, safer, or more productive. Start begins a new active session from the current moment. Pause first reconciles every whole interval already completed and then stops further automatic changes. The interval control is locked while running so a change cannot reinterpret the time 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. Restarting makes the new session boundary clear. Closing or reloading the page also ends a running session; it never pretends to have a server process that continues elsewhere.

Daily history provides a durable local record for increments that were saved. Every nonzero date appears in reverse order with its automatic increment total. Export CSV creates a simple Date and Automatic increments file for a spreadsheet or archive. Export PNG creates a natural 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 exporting a visual summary does not reveal an unnecessary personal note. Both files are generated directly in the browser with native Blob and canvas APIs. There is no upload queue, image processor, account, or outside API in the export path.

Privacy is part of the functional design. The label, interval preference, and saved daily counts are stored only under this counter's local browser key. They are not 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; it does not claim a backup that does not exist. Use Auto Counter when time-driven automatic increments are the real task. Use Online Tally Counter for manual adjustable-step events, and use Online Stopwatch when you need elapsed time and lap splits rather than a daily count. Start the interval, leave the page open while the process runs, pause when it ends, and export only when you need a file outside this browser.

Methodology & sources

Auto Counter stores a bounded local JSON record under counter:auto-counter. A running session uses Date.now only inside browser event and timer callbacks, calculates floor(elapsed / chosen interval), preserves the unfinished remainder, and maps completed interval times to device-local calendar days with Intl.DateTimeFormat. It explicitly does not run after a reload or page close.

Frequently asked questions

Does Auto Counter run after I close the page?
No. It is an all-client browser tool and counts only while this page remains open.
What happens if a background tab delays the timer?
The next callback reconciles completed whole intervals from elapsed time, so it does not simply count callbacks.
Does it need an account?
No. Its settings and daily history stay only in this browser and do not sync to another device.

Related tools

Device & Productivity guides

View all