The right approach to using a People Counter is a manual two-way flow: record each entry, record each exit, and let the tool show the net current number against an optional capacity threshold you set yourself. That definition matters because it rules out expectations the tool cannot meet — People Counter has no camera, sensor, badge reader, location feed, or computer-vision model, so it cannot detect movement for you. What it does instead is give you a calm, private interface to keep an honest operational record of arrivals and departures, attached to the device's local calendar date. Each interaction is something you choose to enter, the exit button is disabled when the current count is already at zero, and the underlying logic rejects any repeated exit that would push the net below zero. The result is a small set of numbers — entered, exited, and net — that you can read at a glance, set a reminder threshold on, and keep in local browser storage or export as a PNG or CSV file without anything being uploaded.
What "the right approach" actually means for a people counter
An "approach" in this context is not a setting inside the tool — it is the way you decide to work with it. The right approach matches your need to the tool's actual scope, then follows a small set of habits so the numbers stay trustworthy over time. People Counter is built around a very specific scope: a manual record of arrivals and exits, a current net total that cannot go below zero, and an optional capacity alert that you set yourself. Knowing that scope up front is what lets you pick the approach instead of fighting the tool later.
Two questions decide the approach almost on their own. First, do you need to know how many people are currently represented by a manual record, or only how many taps happened? A click counter answers the second question. People Counter answers the first, by keeping entered and exited totals separate and showing their net on the page. Second, do you want the tool to detect movement on its own, or are you willing to record it yourself by pressing a button? If you want automatic detection, you need a camera, sensor, or badge reader; People Counter deliberately has none of those. If you are willing to press a button each time someone enters or leaves, the manual approach fits and gives you a clean record.
Confirm the situation actually calls for a manual two-way flow
The right approach starts by confirming that a manual two-way record is the right fit for the situation. People Counter is a strong match in settings such as a small meeting room where one person watches the door, a classroom or workshop where you want a rough attendance feel without sharing personal data, a club night, a pop-up event, a queue at a counter, or any private setting where the operator is already in the room and can press a button as people come and go.
It is not the right fit when you need an automatic headcount, when the door is unattended, when the count carries legal or fire-code weight, or when you must reconcile the total against an authoritative attendance system. In any of those cases the right approach is to look for a different kind of system, not to push a manual tool past its scope. People Counter is also not a one-way click counter, so if the question is simply how many taps happened, an Online Tally Counter is the cleaner choice.
If you are weighing manual versus automatic detection, the practical trade-offs are worth a closer look — the differences are laid out in Manual vs Sensor People Counter: A Practical Choice.
Set up and run People Counter step by step
Once the situation fits, the approach turns into a short, repeatable workflow.
- Open People Counter in your browser on the device you will keep the record on. State lives in that browser's local storage, so the same record will not follow you to another device or browser profile.
- Optionally enter a whole-number capacity alert threshold. This is the number at or above which the page will display a clear alert. Pick a value that is useful as an internal reminder for your own situation; the threshold is not a legal occupancy figure.
- Press Record entry when someone joins the manual count and Record exit when someone leaves. The two buttons stay independent, so you can record several entries in a row without recording any exits, and vice versa.
- Watch the current count update on the page. The net cannot drop below zero: when the count is already at zero, the exit control is disabled, and even a repeated interaction that would create a negative number is rejected.
- At the end of your session, read the entered, exited, and net totals for the local calendar day. Each interaction is attached to the device's local date, so a count near midnight stays on that date and does not shift because of a UTC boundary.
- When the local day changes, the visible current count starts at zero again, and earlier non-zero days remain available in Daily history with their own entered, exited, and net totals.
- If you need a file outside the browser, export a PNG summary or a CSV of the saved daily history. Both files are produced locally with the browser's own canvas and Blob APIs and are not uploaded for processing.
Read the entered, exited, and net totals correctly
Each saved day exposes three numbers, not one. Entered is the running total of every Record entry you pressed that local day. Exited is the running total of every Record exit. Net is their difference, which the page surfaces as the current count. The separation matters because it tells you whether a change came from arrivals or from departures, instead of leaving a single unexplained number that drifts up and down with no visible reason.
When you spot a number you did not expect, the split usually shows the cause. A net that is higher than expected is almost always an extra entry or a missed exit. A net that is lower than expected is almost always an extra exit or a missed entry, with the lower bound protected by the disabled-at-zero rule. Looking at the two totals side by side also helps during a hand-off: a new operator can read where the day stands without having to watch every movement.
Treat the capacity alert threshold as an operational reminder
The capacity alert is the part of the tool that is easiest to misread, so it deserves its own approach. The threshold is a whole number you choose yourself; the page displays a clear alert when the current net count reaches or exceeds it. That is the whole mechanism — a user-set operational reminder on the page you are looking at. It is not a safety certification, a legal occupancy calculation, a fire-code determination, an access-control system, or a replacement for trained staff and site procedures.
The table below spells out what the threshold is not, so the reminder is used in the right way.
| Common assumption | What the People Counter alert actually is |
|---|---|
| An authoritative occupancy limit | Only a user-set operational reminder on the page |
| A safety or fire-code calculation | Not derived from codes, sensors, or a legal standard |
| An access-control or door-lock signal | Does not control anything; it only displays a notice |
| A replacement for staff judgement | Complements, never replaces, on-site decisions |
Set a threshold only when the number is useful as an internal reminder. Leave it blank if you are only interested in keeping a record. If the count near the threshold is genuinely load-bearing for safety, the right approach is to involve the people and procedures responsible for that decision, not to lean on a browser page.
Export PNG or CSV and keep the record private
People Counter is private by design. State is stored only under the 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. Clearing browser data removes the history, and a different browser begins with an independent empty record. If browser storage is unavailable, the page can still show an interaction in the current session and tells you it cannot retain the record — a useful signal that the count in front of you is not durable.
The two export options both run in the browser. Export PNG produces a 1080 by 1350 summary image with the Lizely mark, a total, and recent date rows. The image includes no URL and omits the optional custom label, so it stays compact and easy to share privately. Export CSV produces a file with Date, Entered, Exited, and Net people columns and one data row for every saved local date. Both files can be kept privately, opened in a spreadsheet, or discarded when the record is no longer useful.
Choose between People Counter and similar browser counters
Part of choosing the right approach is knowing when a sibling tool fits better. The table below compares People Counter with three other local counters on the same site, so you can pick the one that matches the actual question you are trying to answer.
| If the question is | Better fit | Why |
|---|---|---|
| How many people are currently represented by a manual record | People Counter | Keeps entered and exited separate and shows net with a non-negative floor |
| How many times a repeated event happened | Online Tally Counter | A simple one-way click counter for taps, repetitions, or passes |
| How several different things compare side by side | Multi Counter | Lets you name and compare several counters in one daily record |
| Whether a personal habit streak is intact | Daily Habit Counter | Built around preset habit labels and a local-calendar streak |
If two-way movement and a manual capacity threshold are the actual product need, People Counter is the right approach. If the question is one-way taps, several side-by-side labels, or a personal streak, switching tools gives you a cleaner result than stretching People Counter into a role it was not designed for.
If you're weighing options, Fix a Result That Looks Wrong in Daily Habit Counter covers this in detail.