A reliable plan for using Multi Counter has six stages: define the comparison, name each counter, follow the device’s local-calendar day, update the matching panel, review the daily values, and export a copy when needed.
Multi Counter is a local browser workspace for comparing several named quantities side by side. It does not infer what a label means, collect sensor readings, or independently verify a number you enter, so the plan must supply the labels and counting rule.

Define the comparison before opening the counters
Write a one-sentence comparison goal before touching the controls. For example: “Compare the number of completed items recorded for North and South today.” That sentence tells you what must be counted, which period matters, and what the review should support.
- Unit: Define what qualifies for an Increase and, if relevant, a Decrease.
- Scope: Decide which events count and which do not.
- Timing: Plan how to handle events near the device’s local-day boundary.
- Review: Decide whether the on-screen comparison is enough or you need a CSV spreadsheet or PNG visual record.
Give every panel a clear, short label, such as North queue and South queue. Multi Counter is not the same as opening several generic counter tabs: its named panels remain visible together in one daily record.
Map names, events, and the local-day boundary
The workspace begins with two counters. Rename each starting counter so its panel describes the quantity you intend to compare, then add another only when the task needs it. Multi Counter can hold up to twenty named counters and always keeps at least one counter available.
- Rename safely: Each counter has a stable internal identifier, so changing its display name preserves the values attached to that counter.
- Remove deliberately: Removing a counter also removes its stored values from the local comparison instead of leaving hidden values attached to a recycled name.
- Match every action: An Increase or Decrease belongs in the panel for the quantity that actually changed.
Every value is attached to the device’s local calendar date. When a new local day begins, the visible panels start at zero, while earlier nonzero days remain in Daily history. The combined total is the sum of the named values for that day, not a lifetime score. If your work period spans midnight, plan around that calendar-day boundary rather than expecting one custom shift total.
Plan and run the Multi Counter workflow
- Open the workspace and inspect the starting panels. Multi Counter opens with two side-by-side counters, providing the starting point for the comparison.
- Rename the counters with specific labels. Make each label describe the value you will compare rather than using a vague label that could be confused with another panel. Add another counter only when the task requires it.
- Set the counting rule before the first event. Decide which events cause you to select Increase, which cause you to select Decrease, and which events should be ignored. Apply the same rule to every named quantity.
- Select Increase in the matching panel as events happen. The panel value, that counter’s local-day value, and the combined total update together.
- Select Decrease in the same panel when your rule calls for a downward value. The controls are bounded, so a count cannot silently become negative or overflow; do not assume the tool can represent an out-of-range amount.
- Check the visible comparison during the day. Read each panel separately, then use the combined total only as the sum of the named values for the current local day.
- Account for the day change. When a new local day begins, the visible panels start at zero and earlier nonzero days remain available in Daily history. Review the old day before treating the new zero values as missing data.
- Review the daily comparison and export when needed. Open the history, check the values for the relevant local date, and download PNG or CSV if you want a file outside the browser.
Review the result without changing what it represents
Use a fixed review order so a labeling error does not become a false comparison.
- Read the counter name and date before judging the value.
- Confirm that the event met the counting rule you defined.
- Check that each change was entered in the matching panel.
- Compare panels for the same day, then interpret the combined total separately.
If a label was changed, its values did not move to another counter. Likewise, removal is not a reset: it deletes that counter’s stored values from the local comparison. For a count that affects an important decision, confirm it against the original source because Multi Counter does not independently verify entered values. For a focused troubleshooting pass, see how to check the result after using Multi Counter.
Choose the export format before the count ends
Treat exporting as part of the workflow rather than assuming the browser will preserve the record indefinitely.
| Format | Best fit | What the file contains | Important detail |
|---|---|---|---|
| CSV | Reviewing named daily values in a spreadsheet | A Date column, one column for each current counter name, and one row per saved local day with the corresponding side-by-side values. | The file contains the counter names, so handle the downloaded copy according to its sensitivity. |
| PNG | Creating a compact visual record | A 1080 by 1350 image with the Lizely mark, a combined total, and recent date rows. | It contains no URL and deliberately omits user-entered counter names. |
Both formats are created directly in the browser with native canvas and Blob APIs, and nothing is sent to an export service. Downloading a file is how you keep a separate copy outside the browser. The CSV is the better choice when names and daily rows matter; the PNG is better when you need a visual summary that does not expose the counter labels.
Plan for local storage, resets, and limited access
Multi Counter keeps counter names, values, and daily history only in browser localStorage under the tool’s key. There is no account, upload, shared board, cloud synchronization, network API request, or cross-device merge.
- Another phone or computer has a separate empty record rather than receiving the current browser’s history.
- Clearing browser data removes the saved comparison from that browser.
- If browser storage is disabled or full, the current page remains usable for the interaction in front of you, but it cannot save history and displays that limitation.
- Values can reach only one local calendar day at a time in the visible panels; earlier nonzero days must be reviewed through Daily history.
If the comparison must survive browser cleanup or be opened on another computer, export the appropriate file and manage it yourself. Multi Counter cannot merge exported records with a different browser’s history.
Use a pre-count checklist to finish the plan
Before the first Increase, confirm that you have answered these points:
- What exact comparison will the daily review support?
- What event triggers each Increase or Decrease?
- Does every panel have a distinct, meaningful label?
- Do you need more than the starting counters?
- How will you handle the local-day boundary?
- Do you need an on-screen review, CSV, PNG, or both?
Following this sequence keeps the workflow focused: manual entries go into named panels, the review uses the current local day, and any outside file is created only when you request it.
Related reading: How Do I Get Started With a People Counter?.