Counting people at an event works by recording an entry every time someone crosses the door in, recording an exit every time someone crosses it out, and treating the difference between those two running totals as the number of people currently inside. A single click counter that only tallies arrivals cannot answer the question "how many are in here right now," because it cannot see the departures. At any event with moving crowds — a wedding reception, a small conference, a pop-up shop, a community hall meeting — the operationally useful number is occupancy, and occupancy needs two-way movement. People Counter is a private browser tool designed for exactly that pattern: it keeps separate Entered and Exited totals for the local calendar day, shows a Current net count that cannot drop below zero, lets you set an optional capacity alert threshold, and saves per-date history that you can export as PNG or CSV when the event ends. Nothing is uploaded; the entire record lives in the browser tab on the device that did the counting.
Two Numbers Tell You More Than One: Entries and Exits
The most common reason people lose track at an event is that they only count one direction. Someone stands at the door with a tally clicker and taps once per arrival, then hands the total to a manager at the end of the day. That number tells you how many people entered, not how many are still inside. As soon as ten people leave early and twenty more walk in, the clicker cannot tell the difference between a busy moment and a thinning room.
People Counter separates the two directions on purpose. Record entry increases the Entered total and increases Current people by one. Record exit increases the Exited total and decreases Current people by one. The Current people number is always Entered minus Exited for the visible local date, so you are looking at the occupancy you actually care about, not just traffic past the door. As a worked example, after recording 47 entries and 19 exits, Current people reads 28 — 47 minus 19 equals 28 — and that is the figure to use for planning, staffing, or telling the next arrival whether there is room.
This two-way design also prevents a misleading result if you accidentally double-tap exit. The exit control is disabled when Current people is already zero, and the underlying logic rejects any interaction that would push the count below zero. An extra stray exit cannot create a negative occupancy and force you to remember whether the room is at minus two or minus three. It simply does not register.
Counting People at an Event Step by Step
Open the tool on the device that will stay at the door. The whole workflow lives in a single browser tab, so a laptop or tablet on a small stand at the entrance is enough; you do not need a scanner, badge, or camera.
- Open People Counter in your browser on the device you will keep at the door.
- If you want an internal reminder of when the room is getting busy, type a whole number into the capacity alert threshold field. Skip this step if you only want a clean running total with no flag.
- As each person crosses the threshold into the event space, press Record entry. Watch Entered and Current people both increase by one.
- As each person leaves, press Record exit. Watch Exited increase and Current people decrease by one.
- If someone passes back and forth — say a parent stepping outside briefly — press the matching exit and entry so Current people stays accurate.
- If you set a threshold, the page shows a clear on-page alert when Current people reaches or exceeds your number. Treat that alert as your cue, not as a hard stop.
- At any point, glance at Daily history to compare Entered, Exited, and Net people for the local calendar day.
- When the event ends, export a PNG summary or a CSV spreadsheet if you need a file outside the browser.
Each tap is attached to the device's local calendar date. A count recorded near midnight stays on that local date rather than shifting because of a UTC boundary, and when a new local day begins, the visible Current people resets to zero while the prior day's totals stay visible in history.
Setting a Capacity Threshold Without Confusing It With Code
The capacity alert is the most misunderstood part of any two-way counter, so it is worth being explicit about what it does and what it does not do.
| The capacity alert is | The capacity alert is not |
|---|---|
| A user-set whole number you choose yourself | A legal or fire-code occupancy limit |
| An internal operational reminder for your own workflow | A safety certification of the venue |
| A trigger that shows a clear on-page notice when Current people meets or exceeds your chosen number | A replacement for trained door staff or site procedures |
| Stored locally with the rest of the count | An access-control system that locks or blocks a door |
| A calculation based on square footage, exits, or building code |
Use the threshold the way you would use a sticky note on the door: as a personal signal that the room is getting busy, so you can pause new entries, open a second check-in lane, or ask a colleague to help. If your venue has a real legal maximum, treat that as a separate, authoritative number set by the venue operator, the fire marshal, or local code — not by the browser tool.
Reading the Daily History at a Multi-Day Event
If your event runs across two local calendar days — a Friday evening into a Saturday morning, for example — the tool does not blend them together. The count you record before midnight belongs to Friday, and the count you record after midnight belongs to Saturday. When Saturday begins, the visible Current people starts at zero, and Friday's totals remain in Daily history as Entered, Exited, and Net.
This separation matters when you are reviewing what happened. A jump in Net from one day to the next is easier to interpret when you can see Entered and Exited separately: if Entered doubled on Saturday but Exited stayed flat, you know the room filled up; if Exited jumped but Entered did not, you know people left. A single unexplained number would hide that direction, which is exactly the limitation a one-way click counter has.
If you clear your browser data, the history is removed along with it. Another browser on another device starts with an independent empty record. If browser storage is unavailable, the page can still show an interaction in the current session but cannot retain the record. That is why it is worth exporting a CSV at the end of each day if you want a durable file outside the browser.
Exporting Your Event Count as PNG or CSV
Both export options are generated in the browser using native canvas and Blob APIs, so no count is uploaded for processing. You keep the file privately on the device that did the export.
Export PNG creates a 1080 by 1350 summary image with the Lizely mark, a total, and recent date rows. It does not include a URL and omits the optional custom label, which makes it suitable for a printed handout, a slide in a recap deck, or an internal message where the focus is the number rather than the link. Open the file after exporting to confirm it shows the dates and totals you expect.
Export CSV creates a plain file with the columns Date, Entered, Exited, and Net people, with one row per saved local date. That structure makes it easy to open the file in any spreadsheet program, sort or filter by date, or paste the Net column into a post-event report. Because the export is local, you decide where the file lives — email it to yourself, save it to a folder, or discard it when the record is no longer useful.
When People Counter Is the Right Tool (and When It Isn't)
People Counter is a good fit when the question is "how many people are in the room right now" and the only way to know is to count arrivals and departures by hand. It is the wrong fit when the question is "how many taps happened" or "how many separate items did I handle" — those are one-direction counts.
| If your task is | A closer fit is | Why |
|---|---|---|
| Tracking occupancy with separate in and out at an event | People Counter | Two-way totals, capacity alert, per-date history |
| Counting repeated taps of the same kind | Online Tally Counter | General repeated event count |
| Tracking several unrelated counts side by side | Multi Counter | Several side-by-side labels |
| Following a personal habit streak | Daily Habit Counter | Personal streak tracking |
If you want a fully automated headcount — say, a camera that detects bodies in a doorway — that is a different category of tool entirely, with its own hardware, calibration, and privacy considerations. People Counter does not pretend to do that. It records only the entries and exits that you manually choose to enter, which is also why its limits are visible: there is no sensor to fail silently, no badge reader to misread, and no cloud service that holds your attendance data. The number on the screen is the manual record you made.