Auto Counter shows your results in a local daily history inside the same browser tab where the counter ran, and you can save those results as a 1080 by 1350 PNG image or a two-column CSV file directly from the page — no account, no upload, and no separate server process required. The history sits right next to the running count, so the moment you pause a session you already see where today's increments have landed. Each saved increment is grouped under the device-local calendar day in which it actually completed, and every nonzero date appears in reverse order with its automatic increment total. The export buttons generate the file locally with native browser Blob and canvas APIs, so the PNG or CSV never leaves your computer until you choose to share it. From there you can open the CSV in any spreadsheet, post the PNG to a chat or document, or simply read the on-page totals for a quick verbal recap without ever leaving the tab.
Where Your Auto Counter Results Appear
Results from an Auto Counter session live in two places: the live count display on the running counter itself and a daily history panel that updates as soon as a completed interval is reconciled. The live count is the running total you see while the page is open and a session is active. The daily history is the durable record — it is the place to look when you close the tab, return hours later, or hand the totals to someone else. Both are produced by the same Auto Counter tool, and you do not need to switch to a separate page or app to read them.
The live count behaves like a familiar tally: it climbs by one each time a whole interval finishes. The daily history behaves like a small private logbook: it stores one row per device-local calendar day that received at least one completed increment, and it stores zero rows for days that did not. Run Auto Counter on Monday for twenty minutes and again on Wednesday for five minutes, and you will see two rows in the history — one for Monday, one for Wednesday — with their respective automatic increment totals.
Steps to Check and Export Your Auto Counter Results
- Keep the Auto Counter tab open until your timed process is finished. The counter only reconciles and saves completed intervals while the page is active.
- Press Pause when the process ends. Pause first reconciles every whole interval that has already passed and then stops further automatic changes.
- Look at the daily history panel on the same page. Each nonzero date appears in reverse order with its automatic increment total.
- Click the PNG export button if you want a 1080 by 1350 visual record showing the overall total and recent day rows.
- Click the CSV export button if you want a two-column Date and Automatic increments file you can open in a spreadsheet.
- Save the file when your browser prompts you, and close or reload the tab only after the export has finished.
Reading the Daily History by Local Calendar Day
Auto Counter assigns each completed interval to the device-local calendar day in which it actually finished, not the day on which you pressed Start. That distinction matters whenever a session straddles midnight: if you begin a session at 11:50 PM and the first interval closes at 12:03 AM, the increment goes into the new day's row, not the previous one. Grouping is handled with the browser's Intl.DateTimeFormat, which uses the calendar and time zone of the device you are currently using.
The history is sorted in reverse chronological order, so the most recent nonzero date sits at the top. Each row shows two pieces of information: the date itself and the count of automatic increments that were saved for that date. There is no separate field for partial intervals, because partial intervals are never saved — only full completed intervals are recorded, and any unfinished remainder is held back for the next callback.
You should think of the daily history as the official count. The live number on screen during a long session can look one interval behind if a tab has been throttled, but the saved daily total reflects every whole interval that actually passed, reconciled together. That is the number to quote when someone asks how many intervals your session produced.
Exporting the Results as a PNG Image
To take a visual record out of the browser, use the PNG export. The image is generated as a 1080 by 1350 share image and contains two pieces of information: the overall total of automatic increments and the recent days with their daily counts. It is rendered locally with the browser's native canvas API, so creating the image never sends data to a server.
The export deliberately omits two things: the web address of the page and the short label you typed into the counter. The intent is that a screenshot of your counts does not quietly leak the description you wrote for your own use. If you want to identify the PNG later, rename the file before sharing it.
The PNG is best when you want a quick visual summary for a chat message, a status update, or a printable page. The CSV is best when you want to do anything else with the numbers.
| Export format | Best for | What it contains | What it deliberately omits |
|---|---|---|---|
| PNG (1080 × 1350) | Visual summary, chat or document screenshot | Overall automatic increment total plus recent day rows | The page URL and your custom counter label |
| CSV (Date, Automatic increments) | Spreadsheet, archive, further analysis | One row per nonzero date with that day's automatic increment count | The page URL, your label, and any partial remainder |
Exporting the Results as a CSV File
The CSV export creates a simple two-column file. The first column is labeled Date and the second column is labeled Automatic increments. One row in the file corresponds to one nonzero date in your daily history, in the same reverse-chronological order. There is no header preamble and no extra metadata beyond the two columns, so the file opens cleanly in Excel, Google Sheets, Numbers, or any text tool.
Because the CSV is produced from the same stored daily history as the PNG, the totals will match exactly. If the PNG shows forty-two increments on a particular Tuesday and the CSV row for that Tuesday reads forty-two, they are reading the same underlying record. This makes the CSV a reliable archive for the same session whose PNG you shared as a screenshot.
How the Count Is Reconciled Before It Reaches History
Auto Counter is built around a simple observation: a browser timer is not a metronome. If you set a 10-second interval and the tab is busy or hidden, the next callback may arrive 14, 23, or 60 seconds after the previous one. Counting each callback as exactly one increment would quietly undercount long sessions. Instead, Auto Counter keeps an elapsed-time anchor and recalculates how many whole intervals of your chosen size have actually passed.
The arithmetic is straightforward. Imagine you set a 10-second interval and let the page run for 47 seconds of elapsed time. Auto Counter divides 47 by 10, which gives 4.7. It records the whole part — 4 — as completed intervals for the current day, and it keeps the leftover 0.7 of an interval (7 seconds) as a partial remainder that will be folded into the next callback. The next callback runs the same division on the new total elapsed, so a pause-then-resume cycle cannot double-count a finished interval or throw away an almost-finished one.
The same reconciliation is what makes the export totals trustworthy even when the live on-screen count briefly looked lower than the number of intervals you expected. The saved daily total is computed from elapsed time at the moment each callback fires, not from the count of callbacks themselves, in line with the behavior described by the WHATWG HTML Timers specification.
Keeping and Clearing Your Saved Results
The label, interval preference, and saved daily history are stored under a single browser-local key named counter:auto-counter. Nothing in that key is sent to a server, joined to a user profile, or synchronized to another device, in line with the WHATWG HTML Web Storage specification. If you open the same browser profile on a different computer, that computer starts empty; if you open a different browser on the same computer, that browser also starts empty.
If local storage is disabled or full, the page still runs the counter and shows the current interaction, but it will tell you it cannot retain history rather than silently failing. Clearing site data for the Auto Counter page removes the saved daily record, and starting a new session after that point begins from a clean slate.
If you want the history to remain useful, follow a small habit: press Pause before closing or reloading the tab. Pause first reconciles every completed interval and then stops further automatic changes. Closing the page without pausing ends the session, and any whole intervals that had already passed remain saved in the daily history for the day on which they completed. Sessions that you simply walk away from are not replayed later — the count only updates while the page is open. For a closer look at where the session ends, see the Auto Counter session boundary guide.