No, the current people count in People Counter cannot go below zero. The tool treats entry and exit as separate movements, then displays their net as the current number of people represented by your manual record. When Current people is already zero, the Record exit control is disabled, so an extra exit cannot lower the count. The underlying counter logic also rejects an exit that would create a negative net count if the interaction is repeated. This two-part safeguard keeps the displayed occupancy at zero rather than turning an extra departure into a misleading minus figure. The zero-floor behavior does not mean the tool automatically knows how many people are in a room. People Counter has no camera, microphone, occupancy sensor, badge reader, location feed, or computer-vision model. You decide which entries and exits to record, and the displayed number is a local operational record of those choices. Recording an exit at zero therefore does not change the current count. To make the current figure useful, record each actual arrival and departure as it happens, keep the Entered and Exited totals separate, and use the net total as the current people count. An optional whole-number capacity alert can add a reminder when the current net reaches your chosen number, but it does not change the counting controls or make the result an official occupancy determination.
The safeguard behind Current people
People Counter is designed for two-way movement rather than a one-direction tally. Entered and Exited remain separate, while Current people represents their net. Conceptually, the current net is Entered minus Exited, but the result has a zero floor: exits reduce the current number only until it reaches zero, never below it.
| Situation | How the current count behaves |
|---|---|
| Press Record entry | The entry is added to Entered and the net current count increases. |
| Press Record exit while the count is positive | The exit is added to Exited and the net current count decreases. |
| Current people is zero | The Record exit control is disabled because no additional exit is valid. |
| A zero-floor exit interaction is repeated | The underlying logic rejects it, so the count remains zero. |
| The net reaches or exceeds the selected threshold | People Counter displays a capacity alert as an operational reminder. |
The alert does not alter the zero-floor rule. A threshold can signal that your manual count has reached a number you want to notice, but it cannot create a negative figure, certify a safe occupancy, or override the manual record.
Use People Counter to keep the count at zero or above
Follow this flow when you want a current count that cannot accidentally become negative:
- Open People Counter and choose a threshold. Optionally enter a whole number in the capacity alert field. Leave it unset if you only need the manual count. When Current people reaches or exceeds the number you select, the page displays an alert. Treat that number as an internal operational reminder, not a safety, legal, or fire-code limit.
- Record movement in the correct direction. Press Record entry when someone is added to the manual count and Record exit when someone leaves. The buttons let you preserve the direction of each movement instead of combining arrivals and departures into an unexplained total.
- Watch the zero-floor behavior. While the current net is above zero, an exit lowers it. Once it reaches zero, the exit control is unavailable. A repeated action that would cross the zero boundary is also rejected by the counter logic.
- Check the local date. Each interaction is attached to the calendar date used by the device. A record made near midnight remains on that local date rather than moving to a different date because of a UTC boundary. When a new local day begins, the visible current count starts at zero.
- Export the saved history if needed. Use PNG for a visual summary or CSV for date-based columns that can be opened in a spreadsheet. The exported record preserves the available entered, exited, and net information without changing the current count.
Read totals by the correct local date
Use Current people when you need the present net figure. Use Entered and Exited when you need to understand how that figure changed. Keeping the two movement totals separate makes it possible to see whether a change came from arrivals or departures instead of treating every button press as an identical event.
Saved dates remain available in Daily history after the visible current count starts a new day at zero. Each saved date retains its own Entered, Exited, and Net totals. A person viewing the history can therefore inspect a prior day without carrying its nonzero total into the current day’s visible figure.
Date handling depends on the device’s local calendar, not a remote clock or location service. If you monitor movement across midnight, review the local date attached to each saved record. This also prevents a count made just before or after midnight from being assigned to the wrong operational date.
Export a copy for your files
Exports are useful when a browser-session record is not enough for the file you want to keep. Both formats are produced in the browser, and neither the count nor the resulting file is uploaded for processing.
| Export | Contents and best use |
|---|---|
| PNG | A 1080-by-1350 summary image containing the Lizely mark, a total, and recent date rows. It 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. |
Choose PNG when a compact visual summary is more useful for your files. Choose CSV when you want to sort, filter, or inspect the saved dates in spreadsheet software. In either case, the export reflects the records retained by the browser and does not add automatic detection or perform a new count.
Keep the manual record within its limits
People Counter records only the entries and exits you manually choose to enter. It does not observe a doorway, identify faces, read badges, or connect to a sensor. That makes it suitable as a simple local operational aid, but the current number is only as complete as the movements you record. A displayed zero is not proof that a real-world space is empty.
The capacity alert has the same manual boundary. It can flag a user-selected operational threshold, but it is not a safety certification, legal occupancy calculation, access-control system, fire-code determination, or replacement for trained staff and site procedures.
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. Clearing browser data removes the history, and another browser begins with an independent empty record. If browser storage is unavailable, the page can show an interaction during the current session but reports that it cannot retain the record.
For a broader assessment of manual and automatic methods before changing an operating process, this manual versus sensor people counter guide explains the practical choice. People Counter’s narrow manual scope is important to understand: preventing a negative count protects the consistency of the record, but it does not verify the number of people physically present.
Choose the counter that matches the movement
People Counter is the appropriate tool when the need is two-way movement, a current net number, and an optional manual capacity reminder. Other local counters serve different record shapes:
- Online Tally Counter fits a general repeated event when the direction of movement does not need to be separated.
- Multi Counter fits several side-by-side labels that need to remain distinct.
- Daily Habit Counter fits a personal streak rather than entries and exits in a shared operational count.
For the specific concern behind the question, the result is direct: Record exit can reduce Current people, but it cannot make the figure negative. Record each movement in the proper direction, keep the device’s local date in mind, and export saved daily totals when a file is needed.