Counter 1
Loading local counter…
Tally Counter
Start at zero now, or add named counters with a soft goal or a hard cap that stops exactly at the target.
Saved in this browser Counts stay on this device. Private browsing or cleared site data can remove them.
Another tab changed these counters
Choose which version to keep before counting again.
CSV is a readable snapshot of the current counters, not a restorable backup.
Current count
No target
Step, target, and set count
Whole numbers only. Count and target: 0–1,000,000,000. Step: 1–1,000.
Count immediately, then name what matters
The first counter starts at zero with a step of one. Use the large plus and minus controls, focus a counter card and press Space or Arrow Up once, or open its settings to change the step and current count. Add up to nine independent counters for inventory, attendance, repetitions, laps, or any other whole-number tally.
Choose the target behavior before you count
No target counts freely. A Soft goal may be exceeded and shows the amount remaining or over. A Hard cap never exceeds its target: from 18 with a step of 3 and a cap of 20, one press adds only 2 and stops at 20. Lowering a hard cap below the current count requires you to lower the count explicitly first.
Undo, reset, and delete without a workspace-wide wipe
Each counter keeps one undoable value change. Reset and delete use an inline confirmation naming the affected counter, so one action cannot silently erase the full workspace. Names may repeat because each card has its own local identity.
What local saving means
The page stores a versioned snapshot in this browser when localStorage is available. MDN notes that private-session data is cleared when the private session closes, and browser policy can block storage. If saving fails, the page says the session is not saved and keeps counting in memory. When another tab changes the same workspace, this tab pauses edits until you choose which version to keep.
CSV snapshot and privacy
The Download button creates a UTF-8 CSV from the current committed state at click time. Counter names are quoted and protected against spreadsheet formulas. The file contains names, counts, steps, modes, targets, remaining or over values, and an export timestamp. It is not a history report or restorable backup.
Names, counts, targets, steps, saved JSON, and CSV contents stay in the browser and are not sent to a calculation service or included in analytics fields. The counting task, local save, and CSV generation have no backend dependency.
Frequently asked questions
Does the tally counter save automatically?
Yes, when browser storage is available. Your counters are saved only in this browser and are not cloud-synced. Private browsing, browser settings, or cleared site data can remove them. If saving is blocked, the counter keeps working for the current page and shows an unsaved-session warning.
What is a hard cap versus a soft goal?
A hard cap never allows the count to go above its target. If only 2 remain and the step is 3, the counter adds 2 and stops. A soft goal is a marker: the count may go above it, and the page shows how far over the goal you are.
Can I count below zero?
No. Subtracting stops at zero. Counts and targets support whole numbers from 0 to 1,000,000,000, and each step can be from 1 to 1,000.
Does the CSV restore my counters?
No. The CSV is a readable snapshot of the current names, counts, steps, modes, targets, and export time. It is not an import file or a browser backup.
Can I use the tally counter offline?
After the page code has loaded, counting, adding a new counter, changing a target, local saving, and CSV creation run in your browser without a calculation server. Normal site analytics and ads may require a connection, but they do not perform the counting task.