The fastest way to fix a result that looks wrong in Workout Rep Counter is to press Undo set, then re-enter the next set with the correct repetitions and an optional rest duration in seconds. A wrong total almost always traces to a rep value that did not match the set you actually performed, an extra tap of Complete set, or a session that crossed your local midnight and split the log between two dates. Undo set removes only the most recently completed entry, recalculates the day's set and rep totals, and does not require you to clear the whole history. If you need to change a different set earlier in the day, there is no in-page edit for older rows, so the supported correction path is to back the log out to that point and re-enter today's sets from there with the corrected numbers. The rest of this article walks through the diagnostic checklist, the exact click order, the date boundaries, and the limits of what the tool will and will not change, so you can recover a tidy daily log without losing the sets you actually performed.
Why the Result You Just Saw Looks Wrong
A wrong-looking total in a workout rep counter almost always traces back to one of four inputs: the reps value you typed before pressing Complete set, an extra tap of Complete set, a session that crossed your local midnight, or browser data that was cleared between visits. Because the tool stores each completed set as its own record with the number you entered, it does not silently merge or rewrite entries behind you. It also does not look at the camera, listen to the microphone, or run any AI model to infer what you performed, so any visible miscount has to come from the value you chose or the moment you pressed the button.
The reps field accepts any whole number from one through one thousand, and the rest field accepts any value from zero through 3,600 seconds. If you finished a set of twelve but typed ten and tapped Complete set, the log keeps ten for that entry. The next clarifying rule is that sets and repetitions stay distinct. The day total combines the values, not the count: log one set of ten reps and then one set of twelve reps, and the day shows two completed sets with twenty-two recorded reps, since ten plus twelve equals twenty-two. Knowing that exact mapping is what turns "the wrong result" from a mystery into a checklist.
Three more scenarios trigger a wrong-looking total that has nothing to do with the addition. Pressing Complete set twice, by accident or because of a touch delay, creates two entries from a single real set, which inflates both the set count and the rep sum. Logging late at night and starting again after midnight splits today's log across two rows in the Daily history list, because the page uses your device's local timezone for the day boundary. And clearing site data, switching to a private window, or opening a different browser starts a fresh empty record, because the tool has no account, no sync service, and no server-side history.
Fix a Wrong Result in Workout Rep Counter
Use this order when you spot a wrong value and want to recover today's log without losing the sets you actually performed.
- Open Workout Rep Counter in the same browser where you saved today's sets, so the local history is still attached.
- Read the today's totals shown on the page: the number of completed sets and the total recorded reps for the local day.
- If the wrong entry is the most recent one, press Undo set once. The latest saved set is removed, the set count drops by one, and the day's rep total drops by the reps that entry had recorded.
- If a different set earlier today is the problem, the page does not expose a direct edit for older rows. The supported path is to remove the most recent entries one by one until you reach the wrong set, then re-log the rest of today with the corrected reps.
- Edit the reps field to the value that matches the next set you are about to perform. Whole-number entries from one through one thousand are accepted.
- Optionally set a rest duration in moments for the interval between this set and the next. Leaving the value at zero skips the countdown, which is useful for circuits and supersets.
- Finish the set in real life and press Complete set. The new entry is saved with the rep value currently shown, and today's totals update immediately.
- Use Skip rest to clear the countdown early if you want to start the next set before the timer reaches zero.
- When the day is right, open the Daily history list to review every saved date. Each row shows the sets and reps logged for that date.
- If you need the corrected record outside the browser, press Export CSV for a one-row-per-day spreadsheet with Date, Sets, and Reps columns, or Export PNG for a 1080 by 1350 image with the Lizely mark, a total, and recent day rows.
How Today's Totals Recalculate After Undo
Today's rep total is the sum of every saved rep value whose local date matches today; today's set count is the number of saved entries for that date. To see the calculation run the other way, Undo set removes the most recently saved set from today's list and subtracts its rep value from the sum. If your day contains a set of ten reps and a later set of twelve reps, the day shows two completed sets and twenty-two total reps before any undo. After one press of Undo set, the same day shows one completed set and ten recorded reps, which matches the entry that was kept.
Every saved set keeps its own number. Changing the reps field before pressing Complete set only changes the next saved set; older entries do not retroactively change. That is the design reason for storing a number per set rather than a single running rep counter: it lets you see which entry carried which value, and it lets Undo set remove exactly one row instead of guessing which row to rewrite.
Daily Date Boundaries and the History List
The day label is taken from your device's local timezone using ECMA-402 Intl.DateTimeFormat conventions, not from a UTC clock. A session that runs from 23:50 to 00:20 on a single calendar night will split into two rows in Daily history: one for the day on which the clock read 23:50 and one for the day on which the clock read 00:20. If that split looks wrong, the supported response is to keep logging on the day where each set actually happened rather than to merge days in the page.
Each row in the Daily history list shows the date, the number of sets logged, and the total recorded reps for that date. The list grows one row at a time as you press Complete set. There is no in-page editor for past rows in that list, so a correction always runs through today's entries and any re-logging you choose to do from there.
| Export | Shape | What you get | When to pick it |
|---|---|---|---|
| CSV | One row per saved day | Columns: Date, Sets, Reps | Spreadsheet review, sorting, custom formulas |
| PNG | 1080 by 1350 image | Lizely mark, a total, recent day rows | Shareable summary without exposing a URL or a custom workout label |
Both exports are produced in the browser using native canvas and Blob APIs, so the file lands on your device without an upload step. The PNG does not include a URL or any custom workout label you typed, which keeps a shared image from exposing a personal note.
Limits That Affect Fixing a Wrong Result
Knowing the bound of the tool keeps a wrong-looking result from being chased in the wrong place. The reps field accepts whole numbers from one through one thousand; the rest field accepts integers from zero through 3,600 seconds, and zero keeps the counter usable when a countdown is not wanted. Undo set removes only the most recently completed set. The tool does not offer a delete-by-date, a bulk edit, or an undo-undo stack, so a correction always runs through the most recent entry or through re-logging from that point.
State is stored in browser localStorage under the key counter:workout-rep-counter, scoped per origin according to the WHATWG HTML Web Storage specification. That is why clearing site data, using a different browser, or opening a private window starts a fresh empty record, and why the page can promise a log that is local to the browser with no account and no upload. If localStorage is unavailable, the page still lets you interact with the controls but reports that it cannot save a durable history, so closing the tab in that state would drop the entry you just made.
The tool also draws a few lines around what it will not try to do. It does not use a camera, a microphone, or an AI model to detect reps. It does not estimate calories, prescribe rest intervals, or make a medical recommendation. If your wrong result came from one of those expectations, the fix is in your assumptions, not on the page.