Set the rows-per-repeat value before the first row, then repeat the same starting state and the same ordered Add row and Undo actions to reproduce the same row and repeat totals.
The important distinction is between reproducing the arithmetic and reproducing the dated history. The Knitting Row Counter links each saved row to a fixed repeat length and keeps a local calendar-day record, so identical actions can produce different daily breakdowns when they occur on different dates.

Fix the Repeat Length Before the First Row
Give the project a short label and choose how many rows belong in one pattern repeat. The available setting is any whole number from one through one thousand, chosen before recording begins. This number is a deliberate project setting: the tool stays neutral about patterns and techniques and does not claim that a particular repeat length is correct for your knitting.
The repeat-length field locks after rows have been saved. That protection is important when repeating a result because changing the setting would cause the same rows to represent a different pattern unit. If you need another repeat length, export the record you want to keep, choose Clear local history, and then enter the new setting. Clearing removes the saved information and unlocks the field.
For a reproducible run, treat the project label and rows-per-repeat value as part of the setup rather than incidental details. The label identifies your local project record, while the repeat length controls the arithmetic. The label itself does not change the row or repeat calculation.
Reproduce the Same Row-and-Repeat Count
- Decide whether you need a fresh run. If so, export any existing PNG or CSV record you want to preserve, then choose Clear local history. This removes the saved project information and allows you to configure the project again.
- Enter the same project label and set the same number of rows per repeat that you used in the original run. Set the value before recording any new rows.
- Press Add row once for every row you want recorded, using the same order as the earlier run. Each press moves the count forward by one and recalculates the linked repeat position.
- Make corrections with the appropriate undo control instead of manually trying to adjust the displayed total. A single mistaken row calls for Undo last row; a completed repeat can be removed with Undo completed repeat only at the required boundary.
- Check the total rows, completed repeats, and rows into the next repeat before exporting. For an identical daily breakdown, the actions must fall under the same local calendar dates; otherwise the cumulative totals can match while the dated rows differ.
For example, with six rows per repeat, fourteen recorded rows gives 14 = (6 × 2) + 2, resulting in two completed repeats and two rows into the next repeat. Repeating that setup and row sequence reaches the same arithmetic state.
Correct Results Without Breaking the Repeat Link
Use Undo last row when only one recorded row is wrong. It reverses one row. Use Undo completed repeat only when the current row count is exactly at a completed-repeat boundary; that action atomically removes the full repeat and updates the row total and repeat total together. A partial repeat remains protected from accidental bulk removal.
| Control | When it fits | Verified effect |
|---|---|---|
| Add row | Recording each row as you work | Moves the count forward by one and recalculates the linked repeat state. |
| Undo last row | Correcting one mistaken row | Reverses one row. |
| Undo completed repeat | The count is exactly at a completed-repeat boundary | Atomically removes the full repeat and updates both totals together. |
| Clear local history | Starting over or deliberately changing the repeat length | Removes saved information and unlocks the repeat-length field. |
After a correction, read the displayed totals again before continuing. If you are recreating a previous outcome, reproduce the same starting point and final sequence of additions and removals. A full-repeat undo changes several rows at once, so it should not be treated as equivalent to an accidental button press in the middle of a partial repeat.
Match Daily History and Export Output
Every saved row belongs to the local calendar date reported by your device. A row worked late at night remains on that local day rather than moving to a UTC date. When a new day begins, the new daily record starts at zero while previous saved days remain in the history list. Each history entry shows that day's rows, completed repeats, and progress into the next repeat.
This date grouping matters when checking repeatability. The same setup and row sequence can reproduce the cumulative row and repeat totals on another day, but the saved rows will then belong to a different date. Compare the grand totals and repeat state when dates differ; compare the complete daily entries only when the local-date grouping also matches.
| Export | Best use | Included output |
|---|---|---|
| PNG | A quick visual summary of recent activity | A 1080 by 1350 image with the Lizely mark, a total, and recent calendar-day rows. It contains no URL or project label. |
| CSV | A detailed spreadsheet record or run comparison | Date, Rows, Completed repeats, Rows into next repeat, and Rows per repeat, with one row for each saved date. |
Both exports are created locally in the browser. PNG gives you a compact visual reference without exposing the private project label. CSV provides the complete dated fields in a format you can open in a spreadsheet. Because the project label is not part of the CSV columns, preserve the label separately if you need it to identify the file later.
Keep a Reproducible Record on One Device
The project label, rows, daily counts, and repeat progress stay in the browser on the current device. There is no project account, cloud dashboard, profile, or cross-browser sharing, and another device begins with a separate record. Repeating a setup on another device therefore requires transferring your setup details and any saved export separately.
Clearing browser data or choosing Clear local history removes the saved information. To preserve a result for later comparison, export the CSV and keep it with your pattern or project notes. Also record the project label and repeat length separately, since neither export uses the label as a field. This creates a practical record of the setup, actions, corrections, and dated output needed to reproduce the arithmetic.
Separate Repeatable Math from Pattern Advice
The counter preserves the relationship between rows and pattern repeats, but it does not supply stitch instructions, calculate yarn requirements, diagnose a project problem, or confirm that a repeat length is correct. You choose the rows-per-repeat setting for your own pattern. A repeatable counter result confirms that the same setup and actions produce the same recorded arithmetic; it does not certify that the knitting technique itself is identical.
When comparing two runs, check the setup, starting state, ordered Add row actions, undo boundaries, local-date grouping, and export fields. If those elements match, the displayed row and repeat totals will match. If only the dates differ, the cumulative totals may still match even though the daily history and CSV rows are organized differently.
Check the Final Result Against This List
- Use the same project label for identification.
- Keep the same rows-per-repeat value throughout the run.
- Start both runs from the same local saved state.
- Record rows in the same order with Add row.
- Use Undo last row for one correction and Undo completed repeat only at an exact completed-repeat boundary.
- Use the same local calendar dates when an identical daily record is required.
- Export CSV for the dated fields and PNG for the visual summary before clearing local history.
The simplest repeatable procedure is therefore: configure once, record in a consistent order, correct only through the appropriate undo action, verify the displayed repeat state, and preserve the export. That process reproduces the counter’s row-and-repeat totals without implying capabilities the tool does not provide.
Related reading: Planning the Steps Needed to Use Multi Counter.
Related reading: How Do I Get Started With a People Counter?.