A manual people counter avoids mistakes when the user treats it as a private tally book with two buttons, a built-in zero-floor guard, and a self-chosen operational reminder, not as a sensor or a legal occupancy certificate. People Counter keeps entries and exits as separate totals per local calendar day, disables the exit button at zero, and lets you set a whole-number capacity alert purely as an internal threshold. Because the tool records only the taps you make, the most common mistakes happen at the keyboard: tapping the wrong direction, pressing the same button twice, trusting the alert as a code-compliant maximum, or assuming the browser will save the record forever. The page stores data only under this tool's local browser key, so clearing browser data or switching browsers silently wipes the history. Treat the tool as a manual operational aid, set a realistic threshold only when it helps, and verify the daily history before exporting. That posture prevents almost every error people run into with a browser-based counter, and it makes the resulting number mean exactly what it is: a manual operational record.
What Can Go Wrong With a Manual People Counter
Most problems with this kind of tool are not bugs. They are mismatches between what a browser button can do and what the user expects it to do. People Counter has no camera, microphone, sensor, badge reader, or computer-vision model, so it cannot detect anyone on its own. Every figure on the screen reflects a Record entry or Record exit press that you or someone at the keyboard chose to make. The first mistake is treating the page as if it were watching a doorway. It is not. It is a manual record, and the record is only as accurate as the hands that fed it.
A second common mistake is losing the direction of movement. A one-way tally button that goes up for everyone who walks in and down for everyone who walks out collapses two different signals into a single net number. People Counter keeps them apart: Entered, Exited, and Net on the current screen, and the same three columns for every saved local date in history. That separation lets you see whether a sudden jump came from arrivals or departures, instead of leaving you with a single unexplained number. If a session ever mixes up the buttons, the daily breakdown is what makes the error visible.
A third mistake is trusting the local total after a browser refresh, a different device, or a cleared cache. State lives under this tool's local browser key only. It is not posted to a server, not connected to a sign-in, and not synchronized to another device. Another browser begins with an independent empty record, and clearing browser data removes the history entirely. If browser storage is unavailable, the page can still show an interaction in the current session and reports that it cannot retain the record. That note is the tool telling you, in plain language, that the number is not durable yet.
Set the Capacity Threshold as an Operational Reminder, Not a Rule
You can optionally enter a whole-number capacity alert threshold for your own operational reminder. The threshold is a self-chosen internal trigger: when the current net count reaches or exceeds that user-selected number, the page displays a clear alert. It is not a safety certification, a legal occupancy calculation, an access-control system, or a fire-code determination, and it does not replace trained staff or site procedures. Treating the alert as a code-compliant maximum is a fast path to a real-world problem, because the page has no way to know what your jurisdiction or venue actually permits.
Avoid another threshold mistake: setting it far above or far below what your space can sensibly hold. The alert exists to nudge you, not to enforce anything, and a poorly chosen number either fires constantly or never fires at all. Pick a figure that matches the routine you are trying to support, leave the field blank when you only need an unfiltered manual count, and remember that the threshold is an operational reminder only. If you need a number tied to a specific code, certification, or audit, that number belongs in your own records, not in this field.
Record Entries and Exits the Right Way
The recording flow has three concrete steps, and following them in order is the simplest way to avoid the mistakes above.
- Optionally enter a whole-number capacity alert threshold for your own operational reminder. Leave it blank when you only need a plain manual count.
- Press Record entry when someone is added to the manual count and Record exit when someone leaves. The two buttons keep their directions separate, so the Entered total and the Exited total never merge on the page.
- Review entered, exited, and net totals by local date in Daily history, then export PNG or CSV if you need a file outside the browser.
The zero-floor guard is built into step 2. The exit button is disabled at zero, and the underlying logic also rejects an exit that would create a negative net count if an interaction is repeated. That protection means an accidental extra exit press cannot produce a misleading negative occupancy on the page. It does not, however, protect against a wrong-direction press that happens while the count is above zero, so the daily review in step 3 is the safety net for everything else. If a number on the current screen does not match what you remember from the room, the daily row usually shows whether the gap came from arrivals, departures, or both.
For a closer look at how the negative-number protection behaves in practice, the guide on whether the current count can go below zero in People Counter walks through the exact interaction rules.
Use Daily History to Catch and Correct Recording Errors
Each interaction is attached to the device's local calendar date. A count made near midnight stays on that local date rather than shifting because of a UTC boundary. When a new local day begins, the visible current count starts at zero, and earlier nonzero days remain in Daily history. The history shows the entered total, exited total, and net total for each saved date. That row-by-row breakdown is the easiest place to spot a recording slip, because an unusual day stands out against the surrounding rows.
| Signal on the daily row | What it usually means |
|---|---|
| Net much lower than Entered | Many of that date's arrivals were matched by departures during the same local date, so only a small residual net remains |
| Net stays at zero while Entered and Exited both grow | The session is balanced and the buttons were used in roughly equal pairs |
| Exited higher than Entered | Impossible under the zero-floor rule, so the row most likely reflects mixed-up dates or a reloaded browser with a partial record |
| Net looks too low for the room | Some arrivals were not recorded, or a busy period used the wrong button |
The point of the table is not to compute exact numbers for you. It is to show how the three-column history turns a single unexplained figure into a question you can answer with the day's own totals. If a row looks off, compare its Entered and Exited figures against what actually happened in the room during that local date, and use that comparison to choose what to fix going forward.
Export PNG or CSV Without Losing Context
Two exports are available, and both are made in the browser with native canvas and Blob APIs. No count and no export file is uploaded for processing, so the file you download is the only copy in existence. If you want the record to survive a cache clear, a new device, or a different browser, you must keep the file yourself.
Export PNG creates a 1080 by 1350 summary image with the Lizely mark, a total, and recent date rows. It is a quick visual snapshot suitable for a printed notice, a clipboard paste, or a chat message. The PNG includes no URL and omits the optional custom label, so it does not leak a destination address or a private annotation.
Export CSV creates a Date, Entered, Exited, and Net people file with one data row for every saved local date. Open it in a spreadsheet to filter by date, sum the columns, or compare two days side by side. Both formats describe what the manual record actually contains, in the order the local calendar dates were saved. If you need a longer-term record, export regularly, store the file outside the browser, and treat the in-page history as a working buffer rather than the final archive.
Understand the Limits of a Browser-Based Manual Counter
The tool is private by design. State is stored only under this tool's local browser key. It is not posted to a server, connected to a sign-in, synchronized to another device, or used as an attendance database. That privacy posture is a feature, not a workaround, but it also means the page cannot recover a record you have lost. Clearing browser data removes the history, and another browser begins with an independent empty record. A second device has its own independent record, even when it is sitting next to the first.
The narrow scope also matters. There is no camera, no sensor, no badge reader, no location feed, and no computer-vision model. The tool records the entries and exits that you manually choose to enter, and the limits of that design are visible instead of pretending a browser button can measure a real-world space automatically. For a side-by-side look at the trade-offs between this approach and a sensor-based system, the guide on manual vs sensor people counters lays out the practical choice in more detail.
Use People Counter when the distinct product need is two-way movement plus a manual capacity threshold. Reach for an Online Tally Counter for a general repeated event, a Multi Counter for several side-by-side labels, or a Daily Habit Counter for a personal streak. Set a threshold only when it is useful as an internal reminder, record entries and exits as they happen, and treat the resulting number as the manual operational record it is. That framing keeps the tool honest and prevents the most common avoidable mistakes.