To get started with a people counter, open the local People Counter, optionally set a whole-number capacity reminder, and manually record every entry and exit as it happens.
People Counter is a private, local browser tool for a simple two-way flow: record an arrival, record a departure, and read the current net count without losing the direction of either movement. The page keeps Entered and Exited totals separately for each local calendar day, then presents their net as Current people.
This guide covers that manual product rather than a camera, sensor, badge reader, location feed, or computer-vision system. Start by deciding whether your task needs a current headcount based on events a person can actually record.

Confirm that a manual headcount fits the task
Use the tool when the required output is a current headcount created from two-way movement and someone can capture each crossing. It is a manual operational aid, not an observer of the room. Compare the job with the tool’s actual scope before counting begins.
| Part | What it does | Important boundary |
|---|---|---|
| Record entry | Adds one arrival to the manual count | Does not detect arrivals automatically |
| Record exit | Removes one departure from the manual count | Cannot take Current people below zero |
| Current people | Shows the net of the entered and exited records | Represents only movement that was recorded |
| Capacity alert | Displays an alert when the net reaches or exceeds your threshold | Serves as an operational reminder only |
| Daily history | Shows entered, exited, and net totals by local date | Uses the device’s local calendar date |
A staffed doorway or small controlled session can fit this method because the person at the door can press a button as movement occurs. If nobody can reliably observe every entrance and exit, the tool cannot identify people who were missed. If you have not yet chosen between manual and sensor-based methods, compare manual versus sensor people-counter approaches before adding equipment.
Set up and run the counter
Use this sequence for your first counting session and for each later session.
- Open the tool and identify the controls. Open People Counter in the browser you intend to use. Locate Record entry, Record exit, and Current people. No sign-in or account is required, and the tool is designed to keep its state in that browser rather than on a server.
- Set a threshold if an operational reminder will help. Enter a whole-number capacity threshold before counting starts. The page will display a clear alert when Current people reaches or exceeds your selected number. Leaving the threshold unset is also supported when you only need the headcount.
- Record arrivals as they happen. Press Record entry whenever someone is added to the manual count. Enter the event when it occurs instead of trying to reconstruct it later from memory; the direction of movement remains visible in the separate Entered and Exited totals.
- Record departures as they happen. Press Record exit whenever someone leaves the manual count. The exit control is disabled when Current people is zero, and the underlying logic rejects a repeated exit that would otherwise create a negative number. This zero floor protects the displayed count but does not correct a missed or duplicated event.
- Review the current and daily figures. At a natural review point, check Current people and the Daily history row for that local date. The history separates the entered total, exited total, and net total, making it easier to see whether a change came from arrivals or departures. Do not treat the sum of button presses as the number currently present.
- Export a file when the record must leave the browser. Use PNG for a visual summary or CSV for a spreadsheet file. Choose the format based on how you need to retain or share the information, and save the resulting file if it will be needed after the browser session.
Keep the buttons in use as movement occurs. Every 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. When a new local day begins, the visible current count starts at zero, while earlier nonzero days remain in Daily history. For teams that need a repeatable written handoff, use this simple procedure for documenting People Counter use.
Read the current and daily totals
Current people is the number represented by the manual record, not a sensor reading and not a total of every tap. Entered shows how many arrivals were recorded, while Exited shows how many departures were recorded. Keeping both directions visible makes it easier to investigate a surprising change without guessing which movement produced it.
The capacity alert is an on-screen prompt for the person maintaining the count. It does not replace trained staff, determine legal occupancy, establish compliance with fire code, certify safety, or control access. Use it to prompt a review under your own procedures.
| Export | What it contains | Practical use | Limit |
|---|---|---|---|
| PNG | A 1080 by 1350 summary image with the Lizely mark, a total, and recent date rows | Creates a visual snapshot | Includes no URL and omits the optional custom label |
| CSV | Date, Entered, Exited, and Net people columns with one data row for every saved local date | Can be opened in a spreadsheet and retained as a file | Reflects the dates already saved in the browser |
| Browser-generated exports | Files created locally with native canvas and Blob APIs | Keeps the export workflow in the browser | No count or export file is uploaded for processing |
Choose CSV when you need the entered, exited, and net figures in a spreadsheet. Choose PNG when a compact visual summary is enough. You can keep either file privately, open the CSV in a spreadsheet, or discard it when the record is no longer useful.
Keep the record in the browser
State is stored only under the tool’s local browser key. It is not posted to a server, connected to a sign-in, synchronized with another device, or used as an attendance database. Another browser begins with an independent empty record, so opening the tool on a second device does not reproduce the first device’s history.
Clearing browser data removes the saved history. If browser storage is unavailable, the page can still show an interaction during the current session, but it reports that it cannot retain the record. That behavior makes People Counter a personal local aid rather than a durable facility system. If the count must be retained, export a file and keep that copy separately.
Use a consistent browser profile or device for an operational record, and make sure the person closing the session knows whether an export is required. These are working practices around the tool, not extra functions it performs automatically.
Understand what the tool cannot establish
The most important limit is that the tool records only the entries and exits you manually choose to enter. It has no camera, microphone, sensor, badge reader, location feed, or AI model to discover movement. A missed arrival, missed departure, or extra press can therefore affect the manual total even though the displayed count cannot fall below zero.
Set a threshold only as an internal operational reminder. It is not a safety certification, legal occupancy calculation, fire-code determination, access-control system, or substitute for trained staff and site procedures. If a count affects a decision with legal, safety, or access consequences, use an appropriate system and qualified procedures instead of this browser tool.
People Counter answers how many people are currently represented by the manual record. It does not independently prove how many people are physically inside. Keeping that distinction clear prevents a useful local record from being treated as more authoritative than it is.
Close each counting session consistently
Finish the setup with a short, repeatable close-of-session routine:
- Confirm that Current people and the day’s Entered and Exited totals agree with what the recorder observed.
- Check the local date, especially for a session that crosses midnight.
- Export CSV for detailed figures or PNG for a visual snapshot, then retain the file if it is needed later.
- Document who maintained the record, what threshold was used, and any known manual omissions under your site’s procedures.
- Do not use the threshold alert as proof of legal capacity, and do not rely on browser history as the only retained record.
Getting started is therefore straightforward: choose the reminder, record the two directions as they happen, review the local-day totals, and export when the result needs to outlive the browser session. The value comes from a consistent manual routine, not automatic detection.