Knitting gauge adjustment calculator
If the pattern says 100 stitches at 20 per four inches and your swatch gives 22, cast on 110 to keep the same width. Enter both gauges and the stitch count to get the whole-stitch total and the adjustment. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Pattern gauge
- 20
- Actual gauge
- 22
- Pattern stitch count
- 100
- Gauge ratio
- 1.1
- Adjusted stitch count
- 110
- Adjustment
- 10
A knitting pattern only reaches its intended measurements when your stitch gauge matches the designer's gauge. If your swatch has more or fewer stitches across four inches, following the original stitch count will change the finished width. This calculator converts the pattern's stated stitch count using the pattern gauge and your actual blocked gauge. It returns a practical whole-number stitch count, the gauge ratio, and the size of the adjustment, helping you preserve the pattern's intended width before you cast on.
Measure both gauges on the same basis
Start with the pattern's stated stitch gauge and a properly prepared swatch of your own fabric. Both values must represent stitches across four inches; do not mix stitches per inch, stitches per ten centimeters, or row gauge with the requested four-inch stitch gauge. Knit a swatch larger than the measurement area, wash and block it as you will treat the finished project, let it dry, and count across the calm center rather than an edge.
The stitch count might be a sweater body cast-on, a flat panel width, or the number present after a shaping row. A larger actual gauge means your stitches are narrower, so you need more of them to preserve the same width. A smaller actual gauge means your stitches are wider, so you need fewer.
Both gauges must be positive because zero or negative stitches cannot describe a physical swatch and cannot form a valid conversion ratio.
Understand the conversion and rounding
The calculator divides your actual gauge by the pattern gauge, multiplies that ratio by the pattern's stitch count, and rounds the result to the nearest whole stitch. For example, a pattern calling for 100 stitches at 20 stitches per four inches describes a width of 20 inches. If your blocked swatch measures 22 stitches per four inches, the same width requires 110 stitches: 100 multiplied by 22 and divided by 20.
Ordinary nearest-integer rounding is suitable for a neutral mathematical answer, but a real pattern may require a multiple for ribbing, cables, lace repeats, or paired shaping. If a repeat requires a multiple of six plus two edge stitches, use the calculated total as your target and choose the nearest structurally valid count. That pattern-specific decision is intentionally left to the knitter because the three numeric inputs alone do not identify repeat constraints.
Apply the result without changing the design accidentally
Use the adjusted count only where width is controlled primarily by stitch gauge. This capability does not convert row counts, recalculate armhole or neckline shaping, estimate yarn, choose needles, or rewrite every instruction in a garment pattern. When changing a large cast-on, review all later directions that refer to fixed stitch totals, repeat counts, centered motifs, decrease placement, and sleeve or body joins.
The output preserves the mathematical finished width implied by the original gauge and count, but it cannot know whether a designer built ease into that width or whether the chosen size already matches your body. Confirm the original implied width by dividing the pattern stitch count by the pattern gauge and multiplying by four. After conversion, divide the adjusted count by your actual gauge and multiply by four; the result should be very close, with only a small difference caused by whole-stitch rounding.
Make a fresh swatch if yarn, needles, stitch pattern, knitting style, washing method, or working in the round changes.
What you can do with it
Resize a sweater body cast-on
Convert the pattern's body stitch count when your blocked stockinette swatch differs from the stated stitch gauge.
Adjust a scarf or blanket panel
Preserve the planned panel width with a different yarn, needle, or personal knitting tension.
Check a pattern modification
Compare the calculated gauge ratio and stitch adjustment before adapting repeat or shaping instructions.
FAQ
Why do I need more stitches when my actual gauge number is higher?
More stitches within four inches means each stitch is narrower, so more stitches are needed to cover the pattern's intended width.
Should I measure my swatch before or after blocking?
Measure after washing and blocking the swatch in the same way you intend to treat the finished item.
Does the result account for stitch-pattern repeats?
No. Treat the result as a target, then select a nearby count compatible with the pattern's repeat, edge, and shaping requirements.
How do I resize 100 stitches if my swatch gives 22 instead of 20?
Cast on 110 stitches. Divide your gauge by the pattern gauge, 22 by 20 gives 1.1, multiply that by 100 and round to the nearest whole stitch. That keeps the 20-inch width the pattern intended.
Can I enter my gauge in stitches per inch or per 10 cm?
No. Both gauges must count stitches across four inches. Mixing in stitches per inch, stitches per ten centimeters or row gauge makes the ratio wrong, so convert your measurement first.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/misc2/knitting-gauge-convert \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"pattern_gauge":20,"actual_gauge":22,"pattern_stitch_count":100}'const res = await fetch("https://api.kit.forhosting.com/misc2/knitting-gauge-convert", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"pattern_gauge": 20,
"actual_gauge": 22,
"pattern_stitch_count": 100
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/misc2/knitting-gauge-convert",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"pattern_gauge": 20,
"actual_gauge": 22,
"pattern_stitch_count": 100
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/misc2/knitting-gauge-convert", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"pattern_gauge":20,"actual_gauge":22,"pattern_stitch_count":100}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"pattern_gauge":20,"actual_gauge":22,"pattern_stitch_count":100}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/misc2/knitting-gauge-convert", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"pattern_gauge": 20,
"actual_gauge": 22,
"pattern_stitch_count": 100
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "misc2.knitting_gauge_convert",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Measure both gauges on the same basis
Enter that result as actual_gauge. Then enter the pattern's published number as pattern_gauge and the original stitch count for the section you want to resize as pattern_stitch_count.
Understand the conversion and rounding
The response includes gauge_ratio so you can see the scale factor, adjusted_stitch_count for the usable whole stitch total, and adjustment to show how many stitches were added or removed.
Apply the result without changing the design accidentally
The browser calculator is free, while automated successful API requests use the published base price of $0.002.
Technical questions
What formula does the calculator use?
It rounds pattern_stitch_count multiplied by actual_gauge and divided by pattern_gauge to the nearest whole stitch.
What happens if either gauge is zero or negative?
The request fails with invalid_input because both the pattern gauge and actual gauge must be greater than zero.
What does the API request cost?
Each successful API request costs $0.002; the calculator can also run free in the browser.