After you save a start date in the Days Since Counter, the tool displays the number of whole Gregorian calendar days between that date and the device's current local day, then keeps a dated snapshot every time you press Save today's snapshot. That single number on the screen is the result: it is not a live ticker, not an elapsed timer, and not a countdown to a future event. The Days Since Counter reads the date you saved, validates the year, month, and day against the Gregorian calendar (including the century and 400-year leap-year rules per the U.S. Naval Observatory's leap-year reference), converts both dates to UTC midnight timestamps as defined by ECMA-262 Date.UTC, and subtracts the integer day count. Using UTC midnight for the math prevents a daylight-saving boundary from shifting your gap by an hour, so a start date of 2024-02-28 always reports 2 days on 2024-03-01, while the non-leap-year 2023-02-28 reports 1 day on 2023-03-01. The display is still anchored to the device's local calendar day, which is the date stamped on a saved snapshot.
What the Days Since Counter Result Actually Shows
The number you see is a single integer — whole calendar days, not hours and not working days. That integer changes only when the device's local calendar day changes, which means re-opening the page on a later day shows a higher value, but leaving the tab open across midnight does not tick the result up by one every minute. The tool does not auto-increment while you watch; it reads the current local day and recalculates against your saved start date when the page renders.
If you want the underlying distinction between a calendar-day count and an elapsed 24-hour duration spelled out, the Days Since Counter: Calendar Days vs 24-Hour Periods guide covers it in depth. For the on-screen workflow, the practical takeaway is that the displayed integer is the same on every device viewing the same local day, regardless of the user's time zone, because the math runs on UTC midnight anchors rather than wall-clock hours.
How to Enter Your Start Date and Read the First Result
- Open the Days Since Counter in your browser and locate the milestone name field.
- Type a short, descriptive label such as "Project kickoff" or "New routine." The label is purely descriptive and never appears in PNG exports, so keep any personal context here if you intend to share the image.
- Pick a current or earlier date using the YYYY-MM-DD field. Years from 1900 through 9999 are accepted, and a future date is rejected so the tool does not silently turn into a days-until timer.
- Press Save. The tool validates the month length and the Gregorian leap-year rule, converts both dates to UTC midnight timestamps, and subtracts them.
- Read the integer that appears on the page. That value is the result for the device's current local day and the first snapshot of your history.
If the start date is today, the result is zero. Zero is a real calendar answer, not an error or a placeholder, and the history list will keep the zero-day entry visible alongside later non-zero snapshots.
Saving Snapshots to Build a Dated Local History
Each time you press Save today's snapshot, the tool appends a row containing the snapshot date, your saved start date, and the days-since value for that day. Snapshots are stored in your browser only, under the key counter:days-since-counter, and they are what you export when you need a file outside the browser. A snapshot can be zero on the day the milestone begins, and the history list keeps those zero-day entries visible rather than hiding them, because they document the actual start point.
Worked example for a leap-year start. Using the formula (Date.UTC of end − Date.UTC of start) ÷ 86,400,000, with start = 2024-02-28 and a snapshot date of 2024-03-01:
- Date.UTC(2024, 2, 1) = timestamp for March 1, 2024 UTC midnight
- Date.UTC(2024, 1, 28) = timestamp for February 28, 2024 UTC midnight
- (March 1 − February 28) ÷ 86,400,000 = 2 whole calendar days, because 2024 is divisible by 4 and is not a century year, so February has 29 days.
The same calculation with start = 2023-02-28 returns 1, because 2023 is not a leap year and the gap covers only February 28. Re-running the math against the same start date on any later day simply substitutes a new end-date timestamp and returns a larger integer.
Why the Tool Asks You to Clear History Before Changing the Start Date
Saved snapshots carry meaning only in relation to the start date they were created with. The value "37 days" on a row dated March 5 means something specific when the start date is January 27 and means something entirely different when the start date is February 25. To prevent a new start date from rewriting the meaning of old entries, the page asks you to clear local history before replacing a start date that already has snapshots. After clearing, the next Save starts a fresh history tied to the new milestone.
If you simply want to keep an old record and add a new milestone, export the existing history as PNG or CSV before clearing. The export files are independent of the browser key and survive a clear-history step.
Exporting Your Results as PNG or CSV
The export buttons appear in the tool once at least one snapshot exists. Both files are generated in your browser through native canvas and Blob APIs, so no upload step is required and no server processes the data. Use the table below to choose the right format for the job.
| Format | Dimensions or layout | Columns or contents | What it omits |
|---|---|---|---|
| CSV | Plain-text rows, one snapshot per line | Snapshot date, Start date, Days since | Milestone name, web address, branding |
| PNG | 1080 by 1350 image | Total for the active local day, recent snapshots | Web address, custom milestone name |
The CSV is the better choice for a spreadsheet or archive because the three columns give every saved value enough context to interpret it later without relying on a browser-only label. The PNG is the better choice for sharing a quick visual, and its omission of the milestone name and web address limits the amount of personal context that travels with the image.
Where Your Result Lives: Local-Only Browser Storage
The milestone name, start date, and snapshot rows are private local browser data. They are not sent to Lizely, synchronized across devices, or joined to a profile. Clearing this site's browser data removes the record entirely, and a second browser opened to the same URL begins with an empty counter.
If browser storage is unavailable — for example, in a private window that disables local storage — the on-screen calculation still works because the math runs in memory, but the page tells you that it cannot retain snapshots. In that state, export is also unavailable, since both export paths rely on data that the page cannot persist.
When a Different Counter Fits the Task Better
The Days Since Counter answers a calendar question: how many whole days have passed between a named past date and today, with dated snapshots for proof. It is not the right tool when the task is fundamentally about elapsed time or about pressing a button to increment a count.
For a live elapsed timer that ticks while the page is open and supports lap splits, use the Online Stopwatch. For repeated manual events you want to increment one tap at a time and group by local calendar day, use the Online Tally Counter, which also exports a private PNG or CSV history. Choose the Days Since Counter when a named past date and a calendar-day difference are the actual task, and reach for one of the other counters when the work is to time a session or count button presses.