Knitting rows for length calculator

Zero or negative gauge or length is rejected with invalid_input rather than inventing fabric.

What row gauge and target length mean for a knit piece

This calculator asks for row_gauge and target_length as strictly positive finite numbers in matching units, and optionally for gauge_length when the pattern quotes rows over a span other than one unit. Density equals row_gauge divided by gauge_length, and gauge_length is one when omitted. Raw row count equals density times target_length. After rounding, actual_length is the knit count divided by density, and length_delta is how far that blocked length sits from the target so you can add or drop a pair of rows before you bind off. Using matching units is essential: if the gauge is per inch, enter the target in inches; if the gauge is thirty rows over ten centimetres, enter the target in centimetres with gauge_length ten.

How to call the API and what the response contains

Values at or below about one times ten to the minus fifteen are treated as non-positive and rejected. POST a JSON body with row_gauge and target_length as required strictly positive finite numbers, plus optional gauge_length when the swatch span is not one unit. Aliases include rows_per, rpi, gauge_rows, rows_per_unit, and pattern_rows for the counted rows; length, height, desired_length, target_height, and finished_length for the finished measure; and gauge_span, swatch_length, per, unit_length, gauge_over, and over for the optional span. Absolute values must stay within one trillion so intermediate products remain finite in IEEE double precision on the Worker and in the browser. On success the body echoes rounded inputs, sets rows_per_unit to density, rows_raw to the unrounded product, rows to the rounded integer knit count, actual_length to the blocked length that integer produces, length_delta to actual minus target, formula to a compact equation string, message to a short English summary, and steps to ordered substitution lines you can assert in tests. Failed validation—missing fields, non-finite numbers, values outside absolute limits, or non-positive gauge, span, or length—returns invalid_input and is never billed. Pricing is a flat $0.002 per successful request with unit item.

Practical planning tips, units, rounding, and related searches

Measure row gauge after the same wash and block you plan for the finished fabric; wet row gauge and dry row gauge often differ, and this tool will faithfully scale whatever density you feed it. Prefer a full four-inch or ten-centimetre swatch rather than counting three rows on a tiny scrap, because small counting errors amplify when you multiply by a long scarf or a sweater body. Prefer sending numbers rather than pre-formatted strings when you control the client; string numbers are accepted only when they match a strict finite numeric pattern. Prefer this capability when you already know row density and finished length and only need the row count; if you also need cast-on stitches from stitch gauge and width, use a gauge-to-cast-on tool instead. When a pattern quotes thirty rows to ten centimetres and you want a forty-two centimetre body, send row_gauge thirty, gauge_length ten, and target_length forty-two; do not convert by hand unless you prefer working in rows per centimetre. When teaching, pair examples: seven point five rows per inch for a twenty-four inch scarf yields one hundred eighty rows; thirty rows over ten centimetres for a sixty centimetre panel yields one hundred eighty rows; seven rows per unit for eleven point two units shows rounding from seventy-eight point four to seventy-eight rows; and row_gauge zero demonstrates the hard invalid_input path. This landing targets people searching for a knitting rows for length calculator, how many rows to knit for a length, row gauge to rows, or rows per inch planner for target length. It is not a stitch cast-on calculator, not a yarn-yardage estimator, and not a full pattern generator with waist shaping. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately send a zero gauge. Round-trip checks are easy: recompute row_gauge over gauge_length times target_length by hand and confirm it equals rows_raw within the same twelve-decimal rounding, then confirm that Math.round of that product equals rows.