Your pattern, checked in every size.
Paste a written knitting pattern. Stitchwright follows every size through the rows it can read, tells you where the counts stop balancing, and names anything it could not read instead of passing it.
One mistyped number, and the size it breaks
The draft below is real: a sweater graded to four sizes, written row by row, with one number mistyped in the cast-on. Reading it top to bottom in one size would never show you which size the typo breaks. The report beside it is what the checker returns for these lines today, not a mockup.
The written pattern
Sizes: S (M, L, XL)
Cast on 96 (104, 114, 120) sts.
Row 1 (RS): *K2, p2; repeat from * to end.
… 183 more rows: the rest of the rib, the stockinette body, the armhole shaping.
Work even until armhole measures 7 (7.5, 8, 8.5) inches.
Bind off all sts.
Size L's cast-on, mistyped: every count below it is graded from 112 sts, and a k2, p2 rib cannot fill 114.
The checker's report
Not verified: 1 stitch-count error to fix
Some rows don't add up. 3 constructs couldn't be checked automatically.
- 84–184 pattern rows checked, by size
- 1 stitch-count error
- 0 warnings
Row 1, size L: the repeat "*K2, p2*" is 4 sts wide, but 114 sts remain to fill, leaving 2 left over.
S
184
rows
M
184
rows
L
84
of 184 rows
XL
184
rows
Only 84 of size L's 184 rows could be checked. The rest are named as unread, never counted as verified.
Run this example yourself →Then hand it your own draft
Paste what you already wrote: Word, Google Docs, a PDF, or straight typing. The checker carries a running stitch count through each size separately, so a repeat that stops dividing in one size is caught in that size, the way size L was caught above.
Share a read-only report by link today. Studio participants can invite a tech editor to comment on rows after manual paid-pilot activation.
A wrong "verified" is worse than no answer
The report above already shows it: 3 constructs in that draft are named as unchecked and left out of the verdict, not guessed at. Here is the current list of what the checker cannot read, in full, on the page you are deciding from.
The whole list, and why →- Crochet. Stitchwright is knitting-only for now, and says so rather than guessing at sc and dc.
- Charts pasted as images. A chart has to be derivable from rows the checker could read.
- Stitches outside the list above: cables (C4F, C6B), twisted decreases (k2tog tbl), a psso spelled across commas ("sl 1, k1, psso"), German short-row double stitches (DS), and a turn in the middle of an instruction list ("k5, turn, p5"). A row holding one is named as unread rather than counted.
- Bind-off shaping written as prose, such as "Bind off 4 sts at beg of next 2 rows", and the rows that follow once a bind-off splits a piece at a neckline: each side is worked on its own count, so those rows are named as unread rather than checked against both sides at once.
- A parenthesized group its line leaves ambiguous, such as stitches in parentheses with no count after them: "(K2, p2) to end". Parentheses are also how a pattern writes its sizes, and one line cannot be read both ways, so the blurred cases are named as unread rather than guessed.
- Rows whose stitch count cannot be established, usually because an earlier row could not be read. Those rows are named, not skipped silently.
- Prose that changes the fabric without saying by how much. "Work as for the back, reversing shaping" is called out by name, pointing at the section it mirrors, but the mirrored rows stay unread rather than guessed.
- Anything a schematic would need beyond stitch counts: a schematic comes from graded measurements, never from the written rows.
Check the pattern you are working on right now
It takes one paste, and if the checker cannot read it, it says so instead of guessing.
No account. Nothing is saved unless you ask for it.