numvana

Knitting Gauge Calculator

Turn a gauge swatch's stitch and row counts into the cast-on stitches and rows needed for a target finished size.

Stitches to cast on
225 sts
Rows needed
360 rows
Gauge (per 10cm)
45 sts x 60 rows

How it works

Every knitting pattern is written for a specific gauge — stitches and rows per unit of fabric. Measuring a swatch gives stitches-per-length (stitches ÷ width) and rows-per-length (rows ÷ height); multiplying those rates by a target width and length gives the stitches to cast on and rows to knit for that size, the standard gauge-scaling method knitting references teach (verified via web search against gauge-substitution guidance rather than relied on from memory).

Because cast-on stitches and total rows are just the target dimension times a rate measured in the same unit system, the calculation is unit-invariant the same way this site's Bicycle Gain Ratio and Guitar Fret Position calculators are — flipping the metric/imperial toggle rescales the swatch and target fields together and the result stays identical.

Gauge is also reported per the conventional standard swatch size (4 inches or 10 cm, matching whichever unit system is active) so it can be compared directly against a pattern's stated gauge, even if the actual swatch measured was a different size.

FAQ

Why does my finished piece not match this calculation exactly?

This assumes your gauge stays constant across the whole piece, which isn't always true in practice — tension can drift over a large project, and many yarns relax or 'bloom' after washing/blocking. Swatching, then washing and blocking the swatch the same way you plan to finish the final piece, gives a far more reliable gauge than an unwashed swatch straight off the needles.

Why is there no toggle just for the stitch/row counts?

Stitch and row counts are plain counts, not a physical measurement, so there's nothing to convert — only the width/height/length fields (real distances) are affected by the metric/imperial toggle.

Related calculators