People Counter does not use a camera, microphone, sensor, badge reader, or AI model to detect people. It is a manual browser tool that counts only the entries and exits a user presses, with separate totals for each direction and a net current count that updates on the same page. Because the tool has no live feed and no computer vision, it cannot recognise faces, identify individuals, or measure a real-world space automatically. Every change in the displayed numbers is the direct result of a human clicking Record entry or Record exit inside the browser tab. That deliberate scope is the answer to the question of how it detects people: it does not, in the camera sense; instead it records the manual operator's stated direction of movement and shows that record alongside a user-defined capacity threshold. The rest of this article explains exactly how those controls behave, where the resulting numbers live, and what kinds of situations the tool is built for, and equally important, what it is not built for.
What Detection Technology People Counter Uses
People Counter has no detection technology in the automatic sense. The page contains two record buttons, a current count display, an optional capacity threshold field, and a daily history list. It does not contain a camera permission prompt, a microphone permission prompt, a geolocation request, a Bluetooth handshake, a barcode scanner, or a deep-learning model running on a server. None of those inputs are available to the page and none would change the count even if they were.
The tool's "detection" is the user's button press. Press Record entry when a person is added to the manual count, and press Record exit when a person leaves. The page adds the two streams separately: an Entered total, an Exited total, and a Current people value that is Entered minus Exited. Because the math is one-directional in the exit column, the page prevents an exit from taking the current count below zero. The exit control is disabled at zero, and the underlying logic also rejects an exit that would otherwise create a negative net count if a click is repeated too quickly. That safeguard is the closest thing the tool has to a verification step, and it does not depend on any external signal.
You can see this design clearly in the daily history. Each saved local calendar date has its own Entered, Exited, and Net row, which lets you tell whether a change in occupancy came from arrivals or departures. That separation is the whole point: the question the tool answers is not "how many taps happened" but "how many people are currently represented by my manual record". A plain tally counter cannot answer that question, and neither can a camera-based system that the user has explicitly chosen not to involve.
Why You Might Expect Camera or AI in a People Counter
Outside the browser, people counting is often a hardware problem. Cities have piloted AI-assisted cameras to monitor crowds at large outdoor events, and police forces in several countries have trialled live facial recognition on public streets. Commercial venues install overhead sensors that count heads through a doorway, and retailers use computer vision on closed-circuit feeds to estimate queue length. Those systems do exist, and their visibility in news coverage is one reason someone might assume a tool called People Counter would work the same way.
The Lizely People Counter sits at the opposite end of that spectrum. It is built for situations where the operator is present, the throughput is modest, and the need is to keep a clear record of direction without deploying any hardware. A shop attendant tapping a tablet as customers walk in, a community group leader tracking who is currently inside a meeting room, and a volunteer at a small event door are all examples of where a manual two-way counter is the right scale. None of those users wants a camera pointed at their visitors, and none of them needs sub-second latency. The tool accepts that its numbers are only as accurate as the person pressing the buttons, and is built around that honesty rather than around the appearance of automatic measurement.
Recording Entries and Exits Step by Step
Open the People Counter page in any modern browser. The page loads with both totals at zero and no threshold set. From there, the basic flow is three steps.
- Optionally enter a whole-number capacity alert threshold for your own operational reminder. This is the number at or above which the page will display a clear alert on the Current people value. Leave it blank if you do not want an alert.
- Press Record entry or Record exit as movement happens. Each press increments the matching daily total and updates Current people. If Current people is zero and you press Record exit, the press is ignored by the disabled control and rejected by the underlying logic, so the count cannot drop below zero.
- 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. Counts stay attached to the device's local calendar date, so a record made near midnight stays on that 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 the history.
There is no save button to remember to click, no sign-in, and no online database. Each interaction is added to the device's local calendar date and held under this tool's local browser key. If the browser cannot write to its storage layer, the page can still show an interaction in the current session and reports that it cannot retain the record.
How the Capacity Threshold Works
The capacity alert is one of the most commonly misunderstood parts of the tool. The threshold field accepts a whole number of your choice. Once the current net count reaches or exceeds that number, the page displays a clear alert near the current count display. The alert is purely a visual reminder on your own screen: it does not lock a door, send a notification, restrict access, or contact any other system.
The threshold is not a safety certification, a legal occupancy calculation, an access-control system, a fire-code determination, or a replacement for trained staff and site procedures. If your building has a legally defined maximum occupancy, that number is set by your local authority and enforced by your operational procedures, not by a browser field. People Counter's threshold is best thought of as a personal prompt for the operator: a quick visual cue that the manual count is at or beyond a number you decided matters for your own workflow. Setting it does not make the count authoritative for any purpose beyond the operator's own use of the page.
Where Your Counts Are Stored and How Export Works
All People Counter state lives 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. Clearing browser data removes the history, and a different browser begins with an independent empty record. The tool is private by design: the only places your numbers exist are the browser you recorded them in and any file you choose to export yourself.
Two export formats are available directly on the page. Export PNG creates a 1080 by 1350 summary image with the Lizely mark, a total, and recent date rows. It includes no URL and omits the optional custom label. Export CSV creates a Date, Entered, Exited, and Net people file with one data row for every saved local date. Both files are made in the browser using native canvas and Blob APIs. No count or export file is uploaded for processing. You can keep the files privately, open CSV in a spreadsheet, or discard them when the record is no longer useful.
When People Counter Fits and When It Doesn't
The right way to choose a tool is to match the shape of the question to the shape of the data it records. People Counter is built for two-way movement plus a manual capacity threshold. The table below shows how it differs from three other Lizely counters that share a similar look but answer different questions.
| Tool | Direction tracking | Capacity alert | Best for |
|---|---|---|---|
| People Counter | Two-way (Record entry / Record exit) | Optional, user-set | Tracking current occupancy with a manual threshold |
| Online Tally Counter | One-way (single click up) | None | Counting repeated events by local day |
| Multi Counter | One-way per named label | None | Comparing several counts side by side |
| Daily Habit Counter | One-way per preset habit | None | Personal habit streaks with daily history |
If you need a count that updates by itself when someone walks through a door, People Counter will not do that, and no honest description of a manual browser button can fill that gap. If your question is how many people are currently represented by your manual record, with a friendly alert when that number gets uncomfortable for you, the People Counter page is the right fit. 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.
If you're weighing options, How to Check Results After Using an Online Tally Counter covers this in detail.
If you're weighing options, How Do I Compare Approaches to Use a Tasbih Counter covers this in detail.