A people counter is the right tool when you need to record two-way movement — entries and exits — and see a current net count plus a user-set capacity threshold, all from a browser with no sensors, no sign-up, and no data leaving your device. The People Counter fits this exact niche: it tracks entries and exits as separate totals, derives the current number of people represented by the manual record, and displays an alert when the count reaches a threshold you choose yourself. It is not a camera, not an AI vision model, not a badge reader, and not a motion sensor — every number on the page is something you choose to record by clicking. The local-only design keeps the record in your browser, so the decision to use one is really a decision about whether your situation needs a manual two-way movement record rather than a simple one-way click counter or an automated sensor system.
What a People Counter Actually Does (and What It Doesn't)
A people counter in this category is a manual browser tool designed for two-way movement. You press a button when someone arrives and another button when someone leaves. The page keeps the two totals separately and shows a net "current people" number derived from them. Optionally, you can type a whole-number threshold that the page uses as a reminder — when the current count reaches or exceeds that number, a clear alert appears on the page.
What it does not do is just as important. It does not watch a room. It has no camera, microphone, computer vision model, or motion sensor. It does not pull from a badge system, a Wi-Fi probe, or a phone location feed. The current count cannot fall below zero — the exit control is disabled at zero, and the underlying logic rejects any exit that would create a negative net count. State lives in this browser only, under the tool's local storage key, and clearing your browser data removes the history. If browser storage is unavailable, the page still works in the current session but reports that it cannot retain the record.
This narrow scope is the point. The tool stays useful by being honest about what it measures: a manual operational record of the movements you choose to enter, with the direction of those movements preserved.
Signs You Need a Two-Way Movement Record
A one-way click counter — the kind that simply adds one each time you tap — fits when you only need to count repeated events in a single direction. A people counter fits when your question is different. You are looking at a manual two-way flow if any of the following apply:
- People can both arrive and leave while you are tracking, and you need both totals separately rather than a single running number.
- You care about the current number of people represented by the record, not just how many taps have happened.
- You want a soft internal reminder when the count crosses a level you set yourself.
- The site is small enough that a person can press a button at the door reliably, and you do not have — or do not want — a sensor system.
- You need a per-day history of entered, exited, and net totals for review or audit.
A small meeting room, a private studio session, a guided tour group, a classroom check-in, a pop-up shop, or a workshop at a single entrance are situations where a manual record of arrivals and departures answers a question a one-way tally cannot. If you need the same kind of tracking for a permanent installation with cameras or sensors, you have moved into a different product category entirely.
Signs a Different Tool Fits Better
The decision to use a people counter is also the decision not to use something else. A few clear alternatives cover the cases where this tool is the wrong fit:
| Your situation | Better fit | Why |
|---|---|---|
| One repeated event, single direction | Online Tally Counter | Simpler model, fewer controls to press |
| Several parallel counts in one view | Multi Counter | Side-by-side labels and direct comparison |
| A daily personal streak or habit | Daily Habit Counter | Streak framing, habit-specific labels |
| Automated real-world detection | Sensor or camera system | Out of scope for any browser button |
| Legal or fire-code occupancy | Trained staff and certified procedures | A manual browser record is not a code calculation |
A capacity alert in a browser tool is an operational reminder, not a safety certification, a code determination, or an access-control system. If your situation requires a certified occupancy limit, that answer comes from trained staff and the relevant procedures — not from a button on a webpage.
How to Set Up and Use People Counter in Your Browser
Once you have decided the manual two-way fit matches your situation, the setup is short:
- Open the People Counter page in your browser. No sign-up, account, or installation is required.
- If you want a soft internal reminder, type a whole-number capacity threshold into the threshold field. Leave it blank if you do not need the alert.
- Press Record entry each time someone arrives at the door you are tracking. Press Record exit each time someone leaves.
- Watch the page update the Entered and Exited totals and the Current people net. The exit control is disabled at zero, so an accidental extra exit cannot create a misleading negative occupancy.
- If the current net count reaches or exceeds your threshold, the page shows a clear alert. Treat it as the reminder it is — not a code determination or a safety verdict.
- At the end of the day, the entered, exited, and net totals are saved under the local calendar date. When a new local day begins, the visible current count starts at zero, and earlier nonzero days remain in the daily history.
Each interaction is attached to the device's local calendar date, so a count made near midnight stays on that local date rather than shifting because of a UTC boundary. If you want a file outside the browser, export a PNG summary or a CSV record — both are produced in the browser with native canvas and Blob APIs and are not uploaded for processing.
A worked example: imagine you set the threshold to 5, then record 7 entries and 2 exits during the first hour. Entered = 7, Exited = 2, Current = 5. The moment Current reaches 5, the page shows the alert — a plain reminder that you have hit the level you chose. A few minutes later, one person leaves: Entered = 7, Exited = 3, Current = 4. The alert clears. That arithmetic (7 − 2 = 5, then 7 − 3 = 4) is the full logic the page runs; no other math is hidden.
Reading Daily History and Exporting Your Record
The history panel shows entered, exited, and net totals for each saved local date. That three-number view is more useful than a single unexplained total because it tells you whether a change came from arrivals or departures. A date with high Entered but low Net suggests steady arrivals with even steadier exits; a date with high Net and low Entered suggests most people stayed. The separation between entered and exited is what makes the daily review possible, rather than leaving you with a single unexplained number.
If you need a file outside the browser, two formats are available. Export PNG produces a 1080 by 1350 summary image with the Lizely mark, a total, and recent date rows. The PNG omits your optional custom label and includes no URL. Export CSV creates a file with Date, Entered, Exited, and Net columns, with one data row for every saved local date. You can open the CSV in a spreadsheet, keep the files privately, or discard them when the record is no longer useful.
Because state lives only in this browser's local storage, clearing your browser data removes the history, and a different browser on the same device begins with an independent empty record. That is an important limitation for any operational count: this tool is a personal local aid, not a durable facility system. If you need durability across devices or staff handoffs, a central database belongs in the design — but that is a different decision from whether to use a people counter at all.
Make the Decision in Three Quick Checks
A short framework helps when you are on the fence. Run through these three questions; the answers usually make the choice obvious.
- Direction: Do arrivals and departures both matter, or is it a single-direction repeat? Two-way movement points to a people counter; single-direction points to a tally.
- Threshold need: Do you want a soft internal alert at a number you set yourself? If yes, a people counter is built for that. If not, a simpler counter may be enough.
- Privacy and place: Does the record need to stay in this browser with no upload, no sign-in, and no shared server? A browser-based manual counter handles that; a sensor system does not.
If two out of three point to manual two-way tracking, the People Counter fits. If only one or none do, you are probably looking at a tally, a multi counter, a habit counter, or a fully different hardware category.
When you compare manual browser tracking with sensor-based systems, the practical choice is rarely about which one is "better" in the abstract. A monthly footfall report tolerates small errors; a live occupancy limit does not. For a certified limit, the answer has to come from trained staff and the relevant code — not from a button on a webpage. For an internal record of who has come and gone, the People Counter gives you a private, manual, two-way view that a sensor system and a one-way tally both miss. A closer look at the trade-offs between these two paths is laid out in the manual versus sensor people counter guide, which walks through where each option earns its keep.
A few quick cautions often decide the question on their own: the threshold alert is an operational reminder and not a safety or legal occupancy limit; the count cannot go below zero because of how the controls are wired; and the record is local-only, which means clearing browser data removes it. Knowing those three limits up front usually tells you whether the tool fits your situation — and if it does, opening the page takes less time than reading this paragraph did.