Correct use means setting the pattern's repeat length before recording, adding one row at a time, and using each undo control only in its defined situation. The key is keeping the row count, completed repeats, and position within the next repeat mathematically linked. Knitting Row Counter makes that relationship explicit: today's row count appears beside linked repeat progress instead of relying on a bare total. Choose a whole-number repeat length from 1 through 1,000, then confirm it against your own pattern before saving any row. Press Add row once for each row you want to record; the tool moves the count forward by one and recalculates repeat status. If one entry is wrong, Undo last row reverses that single row. Undo completed repeat serves a narrower purpose: it is available only at an exact completed-repeat boundary and removes the whole repeat while updating row and repeat totals together. After logging, use the local daily history to check dates and progress, or export the record as PNG or CSV. This workflow helps you spot a miscount before it carries into later repeat calculations while keeping the saved project information in this browser on this device.
The four parts of a correct row record
A correct record has four linked signals: today's rows, the chosen rows per repeat, the number of completed repeats, and the rows already worked into the next repeat. They should describe the same current local-day record rather than mixing today's count with an earlier day's total. Use the repeat length stated by your own pattern as the reference; the tool does not judge whether that pattern or repeat length is correct.
| Signal | Correct interpretation | What to verify |
|---|---|---|
| Today's rows | The rows added for the current local calendar date. | Each Add row press represents one row you intend to include. |
| Rows per repeat | A project-defined whole number from 1 through 1,000. | It matches your pattern and is chosen before saved rows exist. |
| Completed repeats | Full repeat-length units linked to the current daily row record. | The figure reflects the linked counting or correction actions. |
| Rows into next repeat | The position reached after the completed repeats. | An exact boundary has no partial repeat, so the next row begins a fresh repeat. |
Read these values as a unit rather than checking the largest number alone. A large row total does not prove that a repeat is complete, and a repeat total is meaningful only when it was calculated from the same saved rows. Protecting that relationship is why the repeat-length field locks after counting begins: changing it later would silently reinterpret the existing progress.
Count rows and correct the record safely
- Open the browser-based Knitting Row Counter and enter a short project label. Use a label that distinguishes this project from another local record without including private pattern details you would not want in an exported summary.
- Set the number of rows in one pattern repeat before recording any work. Enter a whole number from 1 through 1,000 based on your own pattern. Once rows have been saved, this field remains locked until you clear local history, which also removes the saved information.
- Press Add row once for each row you intend to count. The current daily row count moves forward by one, and the tool recalculates the linked completed-repeat and partial-repeat position.
- Check today's row total alongside completed repeats and rows into the next repeat. If the current position is an exact repeat boundary, the next added row starts a new repeat rather than extending the completed one.
- Use Undo last row when one saved row was added incorrectly. It reverses one row and recalculates the linked repeat state, which can move a completed boundary back into a partial repeat.
- Use Undo completed repeat only when the current row count sits at an exact completed-repeat boundary and the entire repeat should be removed. It removes the full repeat and updates both totals together; it cannot remove a partial repeat by mistake.
- Review the local daily history after counting. Export the rows and repeat columns as PNG or CSV when you need a portable record to inspect later.
Recognize an exact repeat boundary
The boundary check protects your pattern record from two different errors: treating a partial repeat as complete and removing several rows with the wrong correction. Whole-repeat undo is deliberately unavailable inside a partial repeat because the tool cannot know whether every row in that section was intended to remain.
Relationship: current daily rows = (rows per repeat × completed repeats) + rows into next repeat. A remainder of zero identifies an exact boundary. Use this relationship to check the displayed values; the tool performs the linked recalculation when you add or undo a row.
For example, with a four-row repeat and ten rows in the same day's record, substitute the values: 10 = (4 × 2) + 2. The linked reading should therefore show two completed repeats and two rows into the next repeat.
- Every Add row press represents one row you intended to record.
- The repeat length was confirmed before any rows were saved.
- Completed repeats and rows into the next repeat describe the same daily record.
- A whole-repeat correction is used only when no partial repeat remains.
If these checks disagree, pause before adding more rows. First confirm the repeat length against your pattern, then inspect recent daily history for an extra or missing row. Correct a single entry with Undo last row rather than repeatedly changing totals by hand.
Check the local-day history before exporting
Every saved row belongs to the local calendar date reported by your device, not a UTC-adjusted date. A row worked late at night remains on that local day. When a new day begins, the new daily record starts at zero while earlier saved days remain in the history list. Each history entry shows that day's rows, completed repeats, and progress into the next repeat, giving you a compact way to review when work happened and whether each day's linked arithmetic is consistent.
The project label, rows, and repeat progress remain in that browser on the current device. They are not uploaded to a server, shared with another browser, or used to build a profile, and the tool requires no project account or cloud dashboard. Clearing browser data or choosing Clear local history removes the saved information. Another device begins separately, so export a record before changing devices if you want to retain the same project history.
Choose PNG or CSV for the final check
Choose the export that matches the record you need. PNG creates a compact image for recent progress, while CSV exposes the dated row and repeat columns for spreadsheet review.
| Format | What it contains | Important detail |
|---|---|---|
| PNG | A 1080 by 1350 image with the Lizely mark, a total, and recent calendar-day rows. | It contains no URL or project label, so the private label is not disclosed in the shareable summary. |
| CSV | Date, Rows, Completed repeats, Rows into next repeat, and Rows per repeat columns, with one row for each saved date. | The structured columns can be opened in a spreadsheet or kept with a paper pattern. |
Both formats are created locally in the browser with native canvas and Blob APIs. After exporting, compare the displayed repeat setting with the repeat column in the CSV, or check that the PNG total and recent daily rows agree with the live page. An export supplements the local history; it does not determine whether your knitting pattern itself is correct.
Run a final audit before putting the project away
A short final pass is more reliable than relying on memory after a session. Confirm the following points:
- The project label identifies the intended local project.
- The repeat length came from your own pattern and was set before the first saved row.
- Every counted row received one deliberate Add row action.
- The completed repeats and rows into the next repeat agree with the row total.
- A single mistake was corrected with Undo last row, while whole-repeat undo was reserved for an exact boundary.
- The dated history and any export contain the rows and repeat information you need to retain.
For a separate pre-start review, mistakes to avoid when using a knitting row counter can help identify setup errors that may undermine later totals. The main rule remains simple: confirm the repeat length first, count one row per action, inspect the linked position after each meaningful change, and use the narrowest correction that fits the mistake. The tool stays neutral about knitting techniques and patterns; it preserves the arithmetic relationship between your rows and repeats without supplying stitch instructions, calculating yarn needs, or diagnosing a project problem.
If you're weighing options, How Do I Get Started With Multi Counter? covers this in detail.