A quick tallying aid for the host or teacher standing at the front of the room during a show-of-hands or verbal vote. This is a counter for one person to operate manually โ it is not a multi-device online voting system.
Like every other tool on this site, this page is pure front-end code โ all the tallying logic runs as JavaScript inside this one browser tab, with no connection to any database or server. That means if 30 people each open this page on their own phone, you get 30 completely separate, unconnected counters. Tapping +1 on your phone never shows up on anyone else's screen, and vice versa. Building a "multiple people vote on separate devices, results combine live" system requires a server that everyone's device can connect to โ one that collects votes in real time, tallies them, and broadcasts the result back to everyone. That's deliberately not what this tool does: it was designed from the start for a single host or teacher standing at the front of the room, not as a replacement for a real online polling system.
Good fit: a small-to-medium meeting room or classroom, where a single host or teacher visually counts raised hands, or listens to people call out "yes" or "no," and taps the matching card once per hand or voice. That's exactly the scenario this tool is built for โ one person doing the visual counting while everyone else just raises a hand or speaks up, no link to distribute, no setup for attendees. Poor fit: large meetings, or remote/hybrid meetings (some attendees online, some in the room), because those usually need every attendee to cast their own vote on their own device with the system tallying everyone's input in real time โ that requires a proper online polling platform with server-side synchronization (often account-based), which is a fundamentally different tool from this single-device counter.
Say a teacher wants a quick read on which project topic 30 students prefer. They enter "Option A" and "Option B" under "Option Names" and click "Start Tallying." The teacher says "raise your hand for Option A," visually counts 18 hands, and taps the "Option A" card 18 times. Then "raise your hand for Option B" gets 11 hands (maybe 1 student abstained), so the teacher taps "Option B" 11 times. "Total Votes" now shows 29, and the "Option A" card shows the "๐ Currently Leading" badge since it has more votes. If the teacher accidentally over-taps โ say Option A actually only had 17 hands but got tapped 18 times โ a single tap of "โ Correct -1" on that card fixes it without needing to start over.
Because the whole tool runs purely on the front end, there's no code anywhere that writes vote counts to a database or cloud storage. Refresh the page, close the tab, or click "โ๏ธ Edit Options," and the current tally is gone for good โ there's no way to recover it. If a particular result matters (say, it needs to go into meeting minutes), take a screenshot or manually copy the numbers down somewhere else (minutes, a chat thread, a spreadsheet) as soon as "Total Votes" shows the final count, before leaving the page or starting the next round.
No. This tool has no backend server โ every phone or computer that opens this page runs a completely separate, disconnected counter. There is no way to combine votes tapped out on different devices in real time. It's designed for one person standing at the front of the room, visually counting raised hands or listening to verbal votes, and tapping the cards themselves. If you need multiple people to vote on separate devices with results merged automatically, you need a proper online polling platform with server-side synchronization instead.
No, nothing is kept. This tool runs 100% locally in your browser with no database or cloud storage of any kind. Refreshing the page, closing the tab, or switching back to "Edit Options" clears the current counts permanently. Take a screenshot or write down the numbers as soon as "Total Votes" shows the result you need, before leaving the page.
No. The tool automatically clamps every option's count at a minimum of 0 โ even if you click "โ Correct -1" many times in a row, it will never go negative. This is a deliberate safeguard against accidental over-correction.
No. The entire tallying process runs as JavaScript inside your browser โ there's no code on this page that sends any data out, and no backend API is involved. Everything exists only in this tab's memory while it's open.
There's no hard limit โ you can technically keep adding options indefinitely. In practice, though, keep it to what's workable in the room: too many options makes the cards small and cramped, which slows down quick tapping. Most meetings and classroom votes work well with 2 to 6 options.