Multi Counter keeps your counter names, values, and daily history only in your browser's localStorage on the device you are using right now. There is no account, no upload, no cloud sync, no shared board, and no API request that sends your labels or numbers anywhere off the device. When you rename a counter, add a comparison column, or remove an obsolete one, those changes are written to a local storage key that belongs to this tool on this browser. Clearing the browser's site data, switching to a different browser, or opening the page on another computer gives you an empty comparison, because nothing has been pushed to a server to retrieve later. The two available export buttons, PNG and CSV, are also produced entirely by the browser, using its own canvas and Blob APIs, and nothing about those files is transmitted through any external service.
Where Multi Counter Actually Keeps Your Counter Names and Values
The full record of your counters — every name you typed, every increase or decrease you pressed, and every dated row in the daily history — lives in one place: your browser's localStorage, under a key that belongs to Multi Counter on the current origin. localStorage is a small key/value store that every modern browser exposes to web pages, and it is restricted to the specific site that wrote into it. Another site cannot read it, and Multi Counter on a different domain cannot read it either.
The tool does not infer what a label means, does not collect sensor data, and does not claim that a user-entered number has been independently verified. It simply holds the strings and integers you entered and the calendar dates those values are attached to. There is no background beacon, no telemetry ping, no analytics endpoint, and no third-party widget that copies your data off the page. If you want to confirm this for yourself, you can open the browser's developer tools, look at the Application or Storage tab, and inspect the localStorage entry that this tool writes — you will see only the names, values, and dates you put in.
What Happens When You Open Multi Counter on Another Device
Because nothing is sent to a backend, opening Multi Counter on a second device — your phone, a work laptop, a tablet — produces a fresh, empty comparison. The counters that already exist on your home computer are not mirrored there. Each browser maintains its own record, and there is no cross-device merge step that combines them. If you want to keep a record outside this browser, you can export it as PNG or CSV and then manage the resulting file yourself on your own storage.
This separation is deliberate. A manual split count, a small comparison exercise, a side-by-side inventory check, or another neutral multi-label task does not need a shared account, and the privacy profile of a tool that runs entirely inside one browser tab is much easier to reason about. You can close the tab, shut the laptop, or shut down the browser without worrying that the comparison has been archived somewhere external to the device.
Compare Several Counters Side by Side in Multi Counter
The workflow for a side-by-side comparison is straightforward and stays within the browser tab.
- Rename the two starting counters so each panel describes the value you want to compare. Use clear, short labels such as North queue and South queue, Front door and Back door, or Cash and Card.
- Add another counter only when needed. The page keeps at least one counter and permits up to twenty named counters, which is enough for an ordinary side-by-side check without turning the tool into a database.
- Use the Increase and Decrease buttons in the matching panel as events happen. The buttons are bounded so a count cannot silently become negative or overflow, and the combined total at the top of the page updates together with the value in that panel.
- Review the daily comparison as the local calendar day progresses. Each named value sits in its own panel, and the combined total reflects only that day's named values, not an unrelated lifetime score.
- When the local day rolls over, the visible panels reset to zero while earlier nonzero days remain available in Daily history. Export the comparison as PNG or CSV before the day ends if you want a private file outside this browser.
For a deeper walkthrough of the comparison workflow and the kinds of tasks it suits, see the guide on how to make a click counter and compare several counts.
How Local Exports Work: PNG and CSV Stay on Your Device
The two export buttons are designed to produce a file you can keep on your own storage without ever sending the data to a remote endpoint.
Export PNG creates a 1080 by 1350 image with the Lizely mark, the combined total, and recent date rows. The image deliberately includes no URL and omits your user-entered counter names, which reduces the chance that a shared image reveals private labels. Export CSV creates a Date column plus one column for each current counter name, with one row per saved local day and the corresponding side-by-side values, so it can be opened in a spreadsheet for a simple review.
Both formats are created directly by the browser with native canvas and Blob APIs. Nothing is sent to an export service. Once the file is on your disk, you decide what to do with it — keep it locally, move it to a folder, or delete it. If you want a snapshot you can email to a colleague, you control that step yourself rather than the tool uploading on your behalf.
| Export type | What it contains | How it is produced |
|---|---|---|
| PNG | 1080 by 1350 image with Lizely mark, combined total, recent date rows; no URL; counter names omitted | Browser canvas API, saved as a Blob on your device |
| CSV | Date column plus one column per current counter name, one row per saved local day | Browser Blob API, saved on your device |
Edge Cases: Disabled Storage, Clearing Data, and Private Labels
A few honest constraints are worth knowing before you commit an important comparison to the tool. If browser storage is disabled, set to clear on exit, or full, the current page remains usable for the interaction that is open and displays that it cannot save history. That visible message is preferable to a silent failure, and it tells you to finish the comparison in one session or export it before closing the tab.
Clearing the browser's site data — through the browser's own settings or a "clear browsing data" action — removes the saved comparison entirely. There is no recovery step, because there is no server copy. The same rule applies if you uninstall the browser profile, switch browsers, or use a private or incognito window, since those sessions start with empty localStorage.
Renaming a counter does not assign an older value to another label. Each counter keeps a stable internal identifier, so a rename preserves its own values rather than migrating them to a different name. Removing a counter removes its stored values from the local comparison instead of leaving a hidden value attached to a recycled name. Those two behaviors protect the integrity of the daily record even as you reorganize the panels.
When Multi Counter Is the Right Tool for Side-by-Side Counting
Multi Counter is the right pick when the value of the work comes from named side-by-side comparison on a single device. Two or more counters, clear labels, and a combined total that you can read at a glance are the shape of the task. It is not the right pick when the task has a different shape — for example, when entries and exits must remain directional and a capacity threshold is useful, the People Counter fits better. For a single general click value, an online tally counter is enough. For a preset label and streak, a daily habit counter is a closer match.
If your concern is whether the comparison will leave the device, the answer remains the same across every choice: nothing is uploaded, no account is required, and any file you produce is made on your machine. Add only the counters you need, name them clearly, change the value in the matching panel, and export the local daily comparison when you want a file outside this browser.