Skip to content
Lizely

Online Tally Counter

Count repeated events by local calendar day, then export a private PNG or CSV 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 the whole-number step for each button press.
  2. 2.Use Increase or Decrease as events happen; the date line shows the device-local calendar day receiving the count.
  3. 3.Review Daily history, then export PNG for a visual record or CSV for a spreadsheet-friendly file.

About Online Tally Counter

Online Tally Counter is a simple click counter for repeated events, with one important difference from a disposable number widget: it keeps a local calendar-day history. Set a short label, choose the step used by each press, and increase or decrease the count as an event happens. The tool is useful whenever the important question is not only how many events happened right now, but also what happened on a particular day. You can use it for a classroom activity, a production check, a personal collection, a game score tally, a visitor estimate, or any other neutral repeated event. The counter does not ask for an account, a name, or an upload. It is designed to open, count, and get out of the way.

Each click is saved under the local calendar date reported by your device. That means a count recorded late in the evening remains attached to that evening rather than being silently moved to a UTC day. When the next local day starts, the displayed count begins at zero while the earlier day remains visible in the history list. You can reduce a count when you tapped too many times, clear the current day without deleting prior days, and review the saved dates in reverse order. A step value is useful when one button press represents a bundle of items instead of one item. The tool accepts whole-number steps and keeps the daily count within a bounded range so an accidental malformed value cannot corrupt the stored record.

The export controls turn the history into portable files without sending it anywhere. Export PNG creates a 1080 by 1350 share image with the Lizely mark, a total, and recent calendar-day rows. The image deliberately contains no web address and does not include the custom label you typed, so a shared image does not expose a personal note or an external link. Export CSV creates a plain two-column file with Date and Count. There is one data row for every day that has a nonzero saved count, which makes the file easy to open in a spreadsheet or archive alongside a project. Both exports are made from a native browser canvas or Blob at the moment you press the button.

Privacy is a product rule, not a promise hidden in a settings screen. The state is stored only in this browser under the counter's own local key. It is not posted to a server, merged with an account, or shared with another device. Clearing this site's browser data removes the history, and a different phone or computer starts with a separate empty record. If browser storage is disabled or full, the current page still shows the number you changed and explains that it cannot retain the history. That limitation is more honest than pretending a count was backed up somewhere.

This tool is intentionally a general tally rather than a page for every possible noun. A click counter does not become a different product because it is called an attendance counter, a coffee counter, an inventory counter, or a reading-page counter. Those labels can be entered by the user when useful, while the product keeps one durable behavior: local daily records plus downloadable evidence. If you need a set-and-rep workflow, use Workout Rep Counter. If you need 33 or 99 round targets and an optional completion signal, use Tasbih Counter. Keeping the differences concrete avoids duplicate pages and makes the related tools more useful.

Start with a clear label, press Increase as events occur, and check the date line before you leave the page. Use Decrease to correct a recent mistake. The daily history will show only dates that still have a saved count, so a fully cleared day does not create misleading empty data. When you are ready to keep a record outside this browser, use CSV for a spreadsheet-friendly archive or PNG for a clean visual summary. The tool remains free, local, and available without sign-in throughout that workflow.

Methodology & sources

The counter stores a bounded JSON record under counter:tally-counter in browser localStorage. Each interaction resolves its device-local YYYY-MM-DD key through Intl.DateTimeFormat, so history is grouped by local calendar day rather than UTC. PNG and CSV exports are created locally from the saved history.

Frequently asked questions

Does this tally counter need an account?
No. It runs locally in the browser and does not require sign-in.
Will my count still be there tomorrow?
Yes, saved nonzero days remain in local browser storage while a new local calendar day starts at zero.
What happens if I clear browser data?
The local history is removed. It does not sync to another browser or device.

Related tools

Device & Productivity guides

View all