The Workout Rep Counter lets you change the reps for any set that you have not yet marked complete, because the tool stores the rep value on the input field for the next set you are about to perform, not on the day record itself. Each saved entry keeps the exact number that was entered at the moment you pressed Complete set, so a workout that mixes a warm-up set of 10 reps with a working set of 8 and a drop set of 12 is recorded exactly the way it happened — three separate sets with three distinct rep counts. The daily total that the page shows is then calculated by adding every set you logged on that local calendar day, regardless of whether the reps matched. Because the field stays editable, you can prepare a different rep target between sets without resetting the page, clearing the history, or signing in to anything. Updates are limited to the moment before you confirm the set with Complete set, because once a set is in the local record it stays there unless you remove it with Undo set. That simple split — editable up front, fixed after save — is what makes the variable-rep workflow work.
How the reps field connects to the next set
Workout Rep Counter treats the input fields above the action buttons as a staging area for the set you have not yet completed. When the page loads, the reps and rest fields hold the values from your most recent interaction, so you can change them again before tapping Complete set on the next set without affecting the sets already saved earlier in the session. The number you see in the field right now is the number that will be attached to your next save, not a number that is applied retroactively to anything already on the day record.
That separation is intentional. A workout that contains different rep targets — for instance, a single warm-up set of 15 followed by four working sets of 8 followed by a back-off set of 12 — would be awkward to log if every set had to share the same value. The rep counter avoids that problem by treating each Complete set press as a snapshot of the field at that exact moment. The first set you save in the morning with 15 reps is permanent in the local record, even if you later type 8 in the field for the working sets. Each set is its own row in the dated history, and the running rep total is the sum of every distinct set you saved on that local day.
How to change reps for a later set
The actual workflow for changing the reps on a set you have not yet completed is short, but it is worth knowing which buttons move data and which only stage it. The Workout Rep Counter opens the page with the field already showing the value from your previous interaction, so adjusting it is just a matter of typing a new number.
- Type a new number in the reps field whenever you want a different rep count for the next set — for example, switching from 10 to 8 before a working set, or from 8 to 12 before a drop set.
- Adjust the rest duration field if you want a different rest interval for the next set; the number there only applies to the next countdown.
- Finish the actual physical set in your workout, then press Complete set on the page once the set is done. The set is recorded with the value that was in the field at the moment you pressed the button.
- Leave the field alone if you want the next set to use the same reps and rest, or change it again before the next Complete set press if you want a different value.
- Repeat for every remaining set in the workout. Each press creates an independent entry with the number that was staged at that moment.
The action above applies to every later set in the same session, and the pattern is the same for the rest of the workout week if you return to the page on a different day, because the daily totals are keyed on the local calendar date, not on a continuous session timer.
What the daily record actually shows for variable rep sets
Once you have logged several sets with different rep counts, the on-page totals and the dated history row both reflect the variable-rep structure directly. Each completed set contributes its own reps to the running day total, and the set count goes up by one for every Complete set press regardless of how many reps were in that set.
If you complete a warm-up set of 10, a working set of 12, and a drop set of 8, the day summary will read 3 sets and 30 reps. The arithmetic is straightforward — 10 + 12 + 8 = 30 — and the Daily history row for that date shows the same three-set and thirty-rep figure so the daily export and the on-page summary stay in sync.
The table below summarizes how each saved set behaves once it is in the local record, and what changes or stays fixed in the same interaction.
| Element of the saved set | Stored behavior | Effect on later sets |
|---|---|---|
| Reps value at the moment of save | Kept as a whole number attached to that set | Other sets can store a different number |
| Set index (1st, 2nd, 3rd…) | Each Complete set press adds one to the set total | Removing a set with Undo set reduces the count by one |
| Rest duration used for that set | The countdown ran with that value, if any | Does not change rest duration for the next set |
| Local calendar date | Set is filed under the device-local day it was logged | Does not move if you keep training after midnight local time |
| Rep field on the page after save | Returns to the staged value for the next set | Editable again before the next Complete set press |
Each row of the dated history shows both the number of completed sets and the total repetitions recorded for that date, so a single day with mixed rep targets still appears as one row when you scroll through the history list or export it.
Limits on the reps and rest inputs
The rep counter is not an open text box. The reps field accepts whole-number repetitions from 1 through 1,000, which is wide enough to cover a single working set in any common strength exercise and still leaves headroom for unusual endurance drills. Non-integer inputs and values outside that range are not what the tool was built to record, and very large rep counts that fit inside the 1 to 1,000 window still keep each set as a single entry rather than a series.
The rest duration field is similarly bounded. It accepts values from 0 through 3,600 seconds, which is a full hour, and 0 seconds is a deliberate option for circuit-style work where a countdown is not wanted. There is no separate cooldown field, no auto-extension, and no warning logic that would block a save on a low or high value — the only thing that changes is whether a countdown starts when you press Complete set.
Neither value is interpreted as a training recommendation. A rep count of 1 is just as easy to save as 20, and a rest of 3,600 seconds simply holds the timer for an hour rather than telling the user that an hour of rest is appropriate for any specific exercise. That neutrality is part of how the tool stays a private log of what you decided to do.
Correcting a set that has already been saved
Because each saved set is its own row, undoing a mistake only requires pressing Undo set, which removes the most recently completed set from that calendar day and recalculates the daily total. If you pressed Complete set too early, the Undo set action deletes that one entry — not the rest of the day, and not any earlier set. The running rep total updates immediately, and the Daily history row for the day shows the corrected figure.
If the mistake was the rep count rather than the set itself, the cleanest path is to undo the affected set, change the reps field to the value you meant, and press Complete set again. The new set is filed under the same local day, so the day totals still reflect one additional set with the corrected rep count. There is no per-set edit button, because the design treats each press of Complete set as a committed entry, but Undo set covers the common case of one wrong tap.
This matters when you are changing reps for a later set too: if you change your mind about a planned drop set after you have already saved the working sets, you can still undo any one of those working sets, adjust the rep count, and re-save it without touching the warm-up or the rest of the workout.
Moving the log to a spreadsheet or image
The dated history that the page builds from your local storage is exportable in two formats when you want a copy outside the browser. The CSV export creates one row per saved day with the columns Date, Sets, and Reps — a flat structure that opens directly in any spreadsheet program without further formatting. The PNG export produces a 1080 by 1350 image with the Lizely mark, a grand total, and recent day rows; the image does not include any URL or workout label, which keeps a shared summary from exposing a personal note.
Both exports happen in the browser through the canvas and Blob APIs, so the file is generated locally rather than uploaded to a server. The day totals that each export contains are the same totals you see on the page at the moment you press the button, which means a day with mixed rep counts exports as a single combined figure per date rather than as one row per set. That level of aggregation is by design — the export is meant for reviewing daily volume, not for reconstructing every set on its own.
If you want to keep a per-set record alongside the daily totals, you can stay on the page until the end of the workout and screenshot the dated history list before exporting. The set count and rep total in the screenshot will match the row that the export contains for that date.
How the local log handles different reps per set
The Workout Rep Counter stores each completed set as a user-entered whole number under the browser localStorage key counter:workout-rep-counter, which means every save is local to that browser profile. The localStorage behavior follows the WHATWG HTML Web Storage specification for the small key-value pairs the tool relies on. Daily totals are calculated from those stored set entries using the device-local calendar date, so a session that crosses midnight in your timezone still keeps each set on the local day where you logged it rather than being moved by a UTC boundary. This is also why running the tool on a second device, or in a second browser on the same device, gives you an independent empty record — there is no account, no sync service, and no hidden upload.
The tool is also deliberately narrow. It does not detect movement with a camera, infer form, estimate calories, prescribe a recovery interval, or make a claim about a health outcome. Those features would need a different evidence model and, in some cases, device permissions that the page does not request. What you see on the screen — the staged reps field, the staged rest field, the Complete set and Undo set buttons, the day totals, the dated history, and the two export buttons — is the full scope of the tool, and every value is one you entered rather than one the tool inferred. For a parallel "can I change it later" question on a similar local-only counter, the guide on changing your daily target later in a water intake counter walks through the same edit-between-sessions pattern for a different kind of record.