After you press Complete set in the Workout Rep Counter, the page immediately updates today's set count and total repetitions, and every saved day stays in the local Daily history list until you clear browser data. The result of a workout session is therefore visible in three places at once: the running totals shown above the controls, the per-day row that is added to the history list, and the files you can produce by exporting. None of these views require an account, a sync step, or a network request, because the tool stores every completed set as a single entry under counter:workout-rep-counter in browser localStorage and recalculates the totals from that stored value each time the page loads. Checking the result is a matter of looking at the right field on the same screen, scrolling through the dated history list for an older day, or producing a portable CSV or PNG that you can open outside the browser. The whole flow is built so you can confirm what you logged during the session and walk away with a record that matches the numbers you saw while you were training.
What Shows Up the Moment You Press Complete Set
Each time you tap Complete set, the page records the chosen repetition count for that single set and adds it to the in-memory totals for today. Two numbers update on the same screen: today's completed set count and today's total repetition count. If you finished a set of ten and then a set of twelve, the running totals show two completed sets and twenty-two total reps, because sets and repetitions stay separate in the local record rather than being merged. The repetition value you entered is also saved with the entry, so a later set of eight does not overwrite the earlier set of ten; the history keeps both values distinct. If you only need to confirm a single set, the per-set value is the number you typed into the reps field just before pressing Complete set, and the selected repetitions remain available for the next set. The rules for changing the rep field between sets are explained in the guide on changing reps for a later set in the workout rep counter.
When you also entered a rest duration, completing the set starts a countdown based on those seconds, and Skip rest clears it when you are ready to continue. The countdown is a local convenience rather than a stored result, so it does not appear in the history list or in either export. Its only job is to keep you in rhythm between sets; the actual record of what you did lives in the saved set entries, not in the timer.
Reading the Daily History List Day by Day
The Daily history list is the second view of your result. Each row in the list corresponds to one local calendar date and shows both the number of completed sets and the total repetitions recorded for that date. The date itself is calculated from your device's local timezone, which means a late session that crosses midnight UTC still appears under the local day on which you logged it instead of being shifted to the next row. The list therefore reflects when you trained, not when a remote server received an upload.
Reading the list is straightforward: pick a date, look at the sets column for how many completed sets you logged that day, and look at the reps column for the sum of the repetition values across those sets. There is no aggregation across weeks or months built into the on-screen view, so a long log is read row by row. The Daily history list is also where you can confirm that an Undo set was applied correctly, because removing the most recent set updates that day's row and recalculates the totals without leaving a ghost entry behind.
How to Check Your Results After Each Set
- Open the Workout Rep Counter in your browser so the running totals appear at the top of the page.
- Type the number of repetitions you plan to perform in the reps field, and optionally type a rest duration as a number of seconds between zero and 3,600.
- Finish the set, then press Complete set to save the entry; watch the on-screen set count and total rep count both increase by one set and by the rep value you entered.
- Scroll to the Daily history list and confirm that today's row shows the new set count and the new total reps that match what is shown in the running totals above.
- If the row is wrong, press Undo set to remove the most recent set; the running totals and today's row both update to reflect the corrected state.
- When you want a portable copy, choose Export CSV for a spreadsheet-friendly file or Export PNG for a fixed-size image summary; the exports reflect the same numbers shown in the running totals and the history list.
Exporting Your Record as a CSV File
Export CSV produces one row per local calendar day on which you saved at least one completed set. The file uses three columns with the headers Date, Sets, and Reps, and each row carries the values shown in the Daily history list for that date. The CSV is generated in the browser through native Blob APIs, so the file is created on your device rather than fetched from a server. You can open it in any spreadsheet program and the totals you see there will match the totals you saw on the page because both come from the same localStorage entries.
The CSV is the right export when you want to compare days side by side, calculate your own weekly or monthly totals in a spreadsheet, or keep a backup outside the browser. It does not include per-set rep values, only the per-day sum, so each saved local day appears as a single row with that day's set count and total repetitions. If you need per-set granularity inside the export, you would have to log each set on its own day, which is not how the tool is designed to be used.
Exporting Your Record as a PNG Image
Export PNG creates a single image sized at 1080 by 1350 pixels that contains the Lizely mark, the overall total, and a list of recent day rows. The image is built with native canvas APIs and downloaded as a regular image file, so it opens in any image viewer without needing the original tool. Because the size is fixed, the PNG is the right export for sharing a short summary on social media, attaching a snapshot to a message, or printing a small card without having to format anything yourself.
The PNG intentionally does not include a URL or any custom workout label that you may have written for your own reference. That means a shared image cannot accidentally expose a personal note typed into the page, but it also means the image is a neutral summary rather than a labeled poster. If you want to label the image with the workout name or the date range, add the text yourself after the file is on your device.
CSV vs PNG: Which Export Fits the Task
| Use case | CSV | PNG |
|---|---|---|
| Open in a spreadsheet for math | Yes, three fixed columns ready for formulas | No, image is not a data file |
| Share in chat or on social media | Awkward, raw text file | Yes, fixed-size shareable image |
| Show per-day sets and total reps | Yes, one row per saved day | Yes, recent day rows in the image |
| Include custom workout label | No, columns are fixed | No, label is omitted from the image |
| Back up outside the browser | Yes, small text file | Yes, single image |
| Re-import into this tool later | No, the tool does not read its own exports | No, the tool does not read its own exports |
Pick CSV when your next step is to do math on the record, and pick PNG when your next step is to show a quick visual summary to someone else. For long-term storage, exporting a CSV after each session is the safer habit, because a text file survives browser cache clearing in a way that localStorage does not.
Where the Record Lives, and When It Disappears
Every completed set is stored under the key counter:workout-rep-counter in the browser's local storage area, as defined by the WHATWG HTML Web Storage specification at https://html.spec.whatwg.org/multipage/webstorage.html. The daily totals on the page and the rows in the Daily history list are both calculated from those stored entries each time the page is loaded, using the device's local calendar date through the Intl.DateTimeFormat behaviour described in the ECMA-402 specification at https://tc39.es/ecma402/#sec-intl.datetimeformat. There is no account, no synchronization service, no background upload, and no API request for completed sets; the record stays on the device where you saved it. A second device has an independent empty record.
Clearing browser data removes the history, and so does switching browsers or using a private window that does not persist storage. If local browser storage is unavailable, the page still lets you interact with the controls on screen and reports that it cannot save a durable history, so the running totals you see during the session will not survive a reload. Treat the record as one-device local unless you actively export a CSV or PNG after each session, because the tool never claims a backup that does not exist.
What the Result Does and Does Not Include
The numbers you see are the numbers you entered. The tool records the repetition count for each completed set, the rest duration you optionally entered, and the local date on which the set was saved. It does not detect movement, infer form, estimate calories, prescribe a recovery interval, or make any claim about a health outcome. The selected repetitions and rest duration are saved with the counter for the next interaction, and the page accepts whole-number repetitions from one through one thousand and rest durations from zero through 3,600 seconds, so any total that appears in the running totals or in the export is a sum of values inside those bounds.
If you want to read the result without exporting, the on-screen view is the source of truth. If you want to share the result, the CSV and PNG exports are the only portable form, and they are produced in the browser through native canvas and Blob APIs without a server round trip. For any other interpretation of the data, such as calculating weekly volume or comparing training weeks, open the CSV in a spreadsheet and run the math yourself; the tool stays neutral and never implies a recommendation about exercise volume, rest, or health.