An online counter with nothing to install
An online counter is the fastest way to start counting when you do not have a dedicated gadget at hand. Open this page in any browser — Safari on an iPhone, Chrome on an Android, Firefox on a laptop — and you have a working digital counter in about two seconds. No app store, no download, no permissions dialog, no account.
Because it is a web page rather than an app, the counter updates for free and behaves identically on every device. The layout adapts to your screen: full-width buttons on phones, a centered card on desktops. The current number is rendered in a large monospace font so digits do not visually jump as they change.
Private by design, practical by default
Every count is stored only in your own browser's local storage. There is no account system, no cloud sync, and no analytics attached to your numbers — which makes this counter suitable for sensitive counts like event attendance or client traffic. If you clear your browser data, the count clears with it; nothing survives anywhere else.
Day-to-day conveniences are all here: the count survives refreshes and reboots, a long-press undo fixes miscounts, CSV export hands the number to your spreadsheet, and sound plus vibration settings are remembered between visits. It is a plain, dependable online counter that does exactly one job well.
One page, every browser, no exceptions
Web tools are only useful if they open when you need them, so this counter is built to run on anything with a browser: aging Android phones, school Chromebooks, locked-down office laptops, and every modern desktop. There is nothing to configure and nothing that breaks when an IT department blocks installations, because nothing is installed.
The page also respects the way you work. It follows your system's dark mode automatically, keeps its buttons above comfortable touch-target size, and never puts an advertisement within reach of a control you are tapping. An online counter should disappear into the task — this one does.
Online counter vs. manual tally: which is actually more accurate?
The honest answer depends on which failure modes concern you more. A physical tally sheet or hand counter is immune to software bugs, dead batteries (unless it is a clicker), and the distraction of a notification landing mid-count. It also creates a paper trail — a crossed-out digit with a correction written beside it is evidence that a count was revised, which matters in any context where auditability is required.
An online counter removes a different class of error. Handwritten tallies are misread — a hasty four looks like a nine, a sheet gets wet, a page tears along a fold. Digital display eliminates transcription ambiguity: the number is either 847 or it is not. The undo button provides one level of protection against the most common mistake — an accidental double-tap — without requiring you to cross anything out. Neither medium prevents counting the same item twice, and neither medium notices when you skip one.
Where the online counter has a clear and measurable edge is in long sessions. Research on manual data entry consistently shows error rates climbing after about 20 minutes of monotonous work. A physical clicker doesn't fight this; it just clicks. A browser-based counter with sound and vibration confirmation creates a second sensory channel — you hear the beep and feel the buzz — which keeps a distracted counter slightly more anchored to the task. Over hundreds of tallies, that feedback loop matters.
The category where paper genuinely wins is power failure. If the room loses electricity, a sheet still has a number on it. A phone dies when it dies. If you are counting anything where a power cut mid-session would be catastrophic, keep a running pencil mark alongside the digital count as a fallback — the two together beat either one alone.
Multi-person counting and event check-in
Most online counters, including this one, are designed for a single operator. That is the right default: one phone, one thumb, no coordination overhead. But a surprising number of real counting jobs involve two or more people working a single door, gate, or queue at the same time — a volunteer event, a club night, a conference registration desk.
The cleanest approach when two people need to tally into one total is to split the counting period, not the counter. Person A counts arrivals from 7 to 8 pm, exports the CSV, notes the number, then hands the phone to Person B for 8 to 9 pm. At the end you add the two subtotals. This works because each operator has a clear start and end point and the numbers never compete. The CSV export includes a timestamp, so you have a defensible record of each handoff.
A second pattern that works well for high-throughput check-in is parallel counting on separate devices. Two volunteers each run the counter on their own phone and count roughly every other person in the queue. At the end of the event they each export a CSV. You sum the two final counts. This introduces the risk of overlap — two volunteers both clicking the same person — but in practice, if each person is assigned a clear lane or physical side of a door, overlap is rare and the combined count lands within 2–3 percent of the true total.
For formal event check-in with named attendees, a spreadsheet and a barcode or QR scanner beats any tally counter. But for headcount-only situations — how many people are in the room right now, are we over capacity, how many have arrived by noon — the online counter is genuinely the fastest tool to pick up, hand to a colleague, and start using without any explanation. The interface is three buttons. There is nothing to learn.
One wrinkle worth planning for: if the venue has unreliable WiFi and you are relying on a browser-cached page, make sure you have loaded the counter page on each device before you lose signal. The page runs entirely in the browser with no server calls after the initial load, so once it is open it works offline — but it needs that initial load to happen on a connected network.
How to save your count before closing the page
The counter saves automatically to your browser's local storage after every single tap. You do not need to press a save button. If the page crashes, if the browser crashes, if you accidentally navigate away, the number is still there the next time you open the same page on the same device in the same browser. The save is silent and immediate.
That said, local storage is not a backup. It is a cache. Three things delete it without asking: clearing your browser history and site data, uninstalling the browser, and switching to a different browser or a different device. If any of those scenarios are plausible before your count is finished or handed off, export it first.
The CSV export button writes a file with three columns: the label, the current count, and the timestamp of the last change. Open that file in Notes, Excel, or Google Sheets and the number is permanently outside the browser. This is also the right move before clearing the counter for a new session — export the old data, then reset.
A less formal but very fast alternative is a screenshot. On iOS, press the side button and volume-up together; on Android, press the power and volume-down buttons simultaneously. The screenshot goes to your camera roll, which is synced to iCloud or Google Photos on most phones, so the number is backed up without any action on your part. Screenshots are fine for a number you just need to remember; use the CSV export for anything you might need to share or justify later.
One scenario that catches people out: the counter is open in a browser tab and the phone is about to run out of battery. Local storage is already saved — the number is not going to disappear because the battery dies — but if you want the count somewhere accessible from a laptop or a second device right now, that is the moment to tap the export button or take a screenshot before the phone shuts off. After it charges and the browser reopens, the number will be back exactly as it was.