A knitting row counter that links every row to a pattern repeat is started by naming the project, choosing how many rows belong in one repeat, and only after that pressing Add row as you work. The rows-per-repeat setting is the foundation: it is selected as any whole number from one through one thousand before any row is saved, and once rows exist the field locks to keep the saved record honest. The counter then shows two values together on the same page: today's running row total and the linked repeat position, expressed as completed repeats plus the number of rows into the next repeat. That pairing is what makes the tool different from a generic tally. A plain tally only climbs. A repeat-aware counter tells you whether the next click completes a repeat, whether the one after begins a fresh repeat, and whether a whole completed repeat can be reversed as a single atomic step. Starting it correctly means setting the repeat length first, then counting, then trusting the dated local history and the in-browser export when a snapshot is needed. Open the Knitting Row Counter in any modern browser and the page itself is the workspace, with nothing to install and no account to create.
What "getting started" really means for a repeat-aware counter
Getting started is not the same as opening the page. With a plain tally, opening the page and pressing the button is the whole setup. With a repeat-aware counter, opening the page is just the door. The actual setup is two deliberate decisions: the project label you want to see at the top of the record, and the rows-per-repeat value that matches the pattern in your hands. Until both are entered, the counter is in a pre-flight condition. The fields are not cosmetic labels. The repeat value is the rule the rest of the session will obey, because every Add row press is interpreted through it. Setting four and then logging rows produces a record that completes a repeat every four rows. Setting six produces a record that completes a repeat every six rows. The two records describe the same knitting in two different languages, and the tool cannot translate between them. That is why the field is locked once a row is saved rather than left open as a casual edit.
For this reason, getting started is best done away from the knitting. Read the pattern, count the rows inside one repeat block, write that number down, and only then open the tool and enter it. Knitters who try to set the repeat length mid-row usually discover that the value they remember is off by one, and an off-by-one repeat silently makes every later decision about undo, completion, and history a little wrong. A small pause before the first click protects the integrity of the entire record.
Set the project label and rows-per-repeat before your first row
- Open the Knitting Row Counter in your browser so the project fields appear above the row controls.
- Type a short project label you will recognize when you come back to the page tomorrow. The label is a private note and is not included in the shareable PNG image.
- Enter the rows-per-repeat value as a whole number from 1 through 1000 that matches the pattern block in your hands. For a four-row lace repeat, enter 4. For a six-row cable repeat, enter 6.
- Confirm the field is still editable. The rows-per-repeat field stays editable only until the first row is saved, after which it locks to protect the meaning of any saved history.
- Finish the row you are on in the real world, then press Add row for the first time. That first press fixes the repeat length, so make it on purpose.
These five steps are the minimum. If you are switching from an earlier project whose history is still on the page, clear the local history first so the new label and new repeat length are not mixed with the old record. A fresh start is the only way to be sure that what you see on screen describes the piece in your hands.
Count rows and undo the right amount
Counting is the easy part. Press Add row once at the end of each finished row and watch two numbers update together: today's row count and the linked repeat state. The repeat state is shown as completed repeats and the rows counted into the next repeat, so a record that reads "3 completed repeats, 0 rows into the next" on a four-row pattern means twelve rows have been logged with the last press landing exactly on a boundary.
Undoing is where a repeat-aware counter earns its keep. There are exactly two undo controls, and they are not interchangeable.
- Undo last row reverses a single row, whatever the current repeat position is. Use it for a single miscount, a stray tap, or any one-row correction.
- Undo completed repeat is available only when the current row count lands exactly on a repeat boundary, for example row 4, 8, 12, or 16 on a four-row pattern. When that condition holds, the button reverses the full repeat as one atomic action and updates both the row total and the repeat total in the same step.
The boundary check is deliberate. A partial repeat stays protected from a bulk undo, because removing a partial repeat would silently reinterpret the rows already knit. If the button is greyed out, you are inside a repeat and should use Undo last row the appropriate number of times instead. Treating the two undo controls as one merged control is the single most common beginner mistake, and it is the reason the repeat-aware counter splits them in the first place.
Read the linked repeat state at a glance
The page shows three numbers together: today's rows, completed repeats, and rows into the next repeat. Reading them as a pair is faster than reading them as three independent tallies. The table below shows what each linked state means on a four-row pattern and whether the bulk undo control is available at that moment.
| Linked state shown | What it means on a 4-row pattern | Undo completed repeat available? |
|---|---|---|
| 0 completed repeats, 1 row into the next | You are inside repeat 1, one row in | No |
| 1 completed repeat, 0 rows into the next | You are exactly on the first repeat boundary | Yes |
| 1 completed repeat, 3 rows into the next | You are three rows into repeat 2 | No |
| 4 completed repeats, 0 rows into the next | You are exactly on the fourth repeat boundary | Yes |
A pattern with a different rows-per-repeat value produces the same shape but with boundaries at that value's multiples. For a walk-through that ties each on-screen number to a specific moment in the pattern, see the guide on how to check your knitting row counter results.
Use the local daily history to see when work happened
The calendar history is the second layer of the tool, and it is what makes the counter useful for a project that spans more than one sitting. Every saved row is filed under the local calendar date reported by the device, so a row worked at 11:40 PM stays on that day rather than silently rolling to a UTC date in the early hours of the next morning. When a new day begins, the on-page daily record starts at zero while prior days stay visible in the history list above.
Each row in the history list shows that day's row total, the completed repeats on that day, and the progress into the next repeat at the end of the day. Together those three numbers answer two questions knitters ask most often after a break: how much did I knit on that day, and where in the pattern did I stop. Because the history is keyed to the local date, switching time zones does not move old rows to a different day; the only thing that can move a row to a different history entry is a deliberate press of Add row on the new local day.
Export the project record when you need a snapshot
Exports are produced in the browser with native canvas and Blob APIs, so the file is built locally and no upload happens. There are two formats, and they serve different needs.
| Export | File format | Best for | What it includes |
|---|---|---|---|
| PNG | 1080 x 1350 image with the Lizely mark | Sharing a quick visual summary | Total rows and recent calendar-day rows; project label is intentionally excluded |
| CSV | Spreadsheet-ready text | Keeping a full record with the paper pattern or in a spreadsheet | One row per saved date with Date, Rows, Completed repeats, Rows into next repeat, and Rows per repeat columns |
The PNG omits the project label on purpose, so a shared image does not disclose a private project note. The CSV includes every saved date and is the format to keep when the project record needs to survive a browser reset, a new device, or a long gap between sittings.
Keep the record private on this device
The project label, the daily rows, the repeat progress, and the dated history all live in this browser on this device. They are not uploaded, not sent to a server, not shared with another browser, and not used to build a profile. Clearing browser data, or using the Clear local history control, removes the saved information, and another device begins a separate record. The privacy story is simple enough to state in one line: the tool keeps what you record and nothing you do not record.
For knitters who also need a plain click counter without repeat logic, an unrelated adjustable tally lives at the Online Tally Counter. For daily streaks with label templates, the Daily Habit Counter is the closer match. For comparing several named values at once, the Multi Counter keeps each value in its own row. None of those tools link rows to a pattern repeat, which is the specific job the Knitting Row Counter exists to do.
For a deeper look, see Fix a Result That Looks Wrong in Multi Counter.