Multi Counter starts with two named counters, supports up to twenty, and keeps each day's values together in one private browser workspace. To get started, open the Multi Counter tool, rename the starting panels with short labels that describe the quantities you want to compare, and add another counter only when your task needs one. Use each panel's Increase or Decrease control as events happen; its value and the combined total update for the device's current local calendar day together. When a new local day begins, the visible panels start at zero while earlier nonzero days remain in Daily history. Review the side-by-side record when you finish, then export PNG or CSV if you want a file outside the browser. No account is needed, the tool does not upload the workspace, and separate phones or computers do not merge their records. The basic routine is to name each panel, make every change in the matching panel, check the current day's comparison, and export a copy only if you need one.

What Multi Counter Keeps Together
Multi Counter is a local browser workspace for comparing several named quantities at once. A short label such as North queue or South queue gives each panel a clear purpose. The panels remain visible together, the combined total stays at the top, and Daily history collects earlier nonzero days. This differs from opening several generic counter tabs: the names explain what is being compared, the layout makes the contrast visible, and one daily record keeps the results together.
- Named panels: Every counter has a display name and its own value.
- Current-day total: The figure at the top is the sum of the named values for the device's current local day.
- Date-based history: Each value is tied to a local calendar date and rolls into a new day when the device's date changes.
- Manual comparison: The tool does not infer a label's meaning, collect sensor data, or verify that an entered number is correct.
Build the First Daily Comparison
- Rename the two starting counters. Multi Counter begins with two panels. Replace their starting names with clear, short descriptions of the values you want to compare, such as North queue and South queue. Add another panel only when the task needs another named quantity; the workspace supports no more than twenty named counters.
- Use the matching panel for every change. Press Increase when that quantity rises and Decrease when it needs to go down. The named counter, its local-day value, and the combined total update together. Increase and Decrease are bounded, so a count cannot silently become negative or overflow.
- Review the day, then decide whether to export. Check the current local date, read the side-by-side values, and confirm that the combined total is intended as the sum for that day. Export PNG or CSV when you want a private file outside the browser.
A rename changes only the display name because each counter has a stable internal identifier. Its values stay attached to the same counter rather than moving to a different label. Keep related labels parallel, and avoid adding a counter merely to make the page look fuller.
Match the Labels to the Task
Choose labels before events begin. Multi Counter does not decide what they represent, so the setup should match the quantity you are manually recording.
| Task | What Each Counter Represents | Useful Starting Layout |
|---|---|---|
| Manual split count | Groups, queues, or locations counted separately | Begin with two group labels and add a panel only for another required group. |
| Small comparison exercise | The separate quantities being contrasted | Use parallel labels that state what each panel measures. |
| Side-by-side inventory check | Manually entered categories or locations | Give each category or location its own clear panel. |
The built-in layout is enough when the comparison has two sides. A later panel is useful only when it represents a quantity you will actually update. If you only need one undifferentiated click value, several named panels do not add a meaningful comparison.
Understand Days, Totals, and Limits
Every value belongs to the local calendar date on the device. The total at the top is the sum of the named values for that date, not a lifetime score. Knowing these boundaries makes the daily record easier to interpret.
| Element | Defined Behavior |
|---|---|
| Starting layout | Two named counters are present when the workspace begins. |
| Available range | At least one counter remains available, with a maximum of twenty named counters. |
| Date assignment | Values are assigned to the device's current local calendar date. |
| Daily rollover | Visible panels start at zero while earlier nonzero days remain in Daily history. |
| Combined total | The current-day sum of the named values, not a lifetime total. |
| Adjustment limits | Increase and Decrease are bounded so counts cannot silently become negative or overflow. |
Renaming and removing counters are more than visual edits. A renamed counter keeps its values because its stable internal identifier does not change. Removing a counter removes its stored values from the local comparison instead of leaving hidden data attached to a recycled name. The page always keeps one counter available, so the workspace cannot be reduced to an empty state.
Check the Current Record
Before treating the daily comparison as final, confirm that the date, labels, and values describe the same task. This review can reveal an update made in the wrong panel, but it cannot confirm the real-world event behind a manually entered number.
- Confirm that the device is on the intended local calendar date.
- Read every panel and make sure each value sits under the correct name.
- Interpret the combined total as the sum of the current named values, not as an independently verified measurement.
- Open Daily history when you need to compare the current record with earlier nonzero days.
Export for Review or Records
Both export formats are created directly by the browser, but they serve different purposes.
- PNG: Creates a 1080 by 1350 image containing the Lizely mark, a combined total, and recent date rows. It includes no URL and deliberately omits user-entered counter names.
- CSV: Creates a Date column plus one column for each current counter name. Each saved local day receives one row with the corresponding side-by-side values, making the file suitable for a spreadsheet review.
Choose PNG when a visual image is more useful than labeled spreadsheet data. Choose CSV when the current counter names and structured daily rows matter. The files are produced with native browser canvas and Blob capabilities, and nothing is sent to an export service.
Protect the Local Saved Record
Counter names, values, and Daily history are kept in browser localStorage under Multi Counter's own key. There is no account, upload, shared board, cloud synchronization, API request, or cross-device merge. Another phone or computer therefore has a separate empty record rather than a copy of the original workspace. Clearing browser data removes the saved comparison, so export a PNG or CSV first if you need a file outside the browser.
If browser storage is disabled or full, the current page remains usable for the open interaction and displays that history cannot be saved. Treat that message as a persistence limit rather than assuming the record will remain available after the interaction ends.
When a Different Counter Fits Better
Multi Counter is designed for value that comes from named side-by-side comparison. Other counter tools serve different structures:
- Use People Counter when entries and exits must remain directional and a capacity threshold is useful.
- Use Online Tally Counter for one general click value rather than several named quantities.
- Use Daily Habit Counter for a preset label and streak rather than a neutral multi-label comparison.
For the intended task, begin with the two supplied panels, name the quantities clearly, update only the matching panel, and review the local daily comparison before deciding whether to export it.