“Increase 8 stitches evenly across the next row.” The pattern moves on. You’re left holding live stitches and doing mental math.

Whether the row needs to add stitches or remove them, the calculation is the same. Divide the current stitch count by the number of changes you want to make, and that result is the interval between each shaping point. That’s the formula. The interesting part is everything around it: which increase or decrease method to use, how to handle the remainders that almost always show up, what to do at the edges, and how to keep the spacing readable in fabric instead of just on paper.

The formula in one line

Current stitch count / number of changes = interval between each change.

For increases, the interval tells you how many stitches sit in each section, with one new stitch worked at the end of the section. For decreases, the interval is the repeat size, and the last two stitches of each repeat are the decrease.

Same math, two slightly different framings.

Worked example: a clean increase

You have 80 stitches on the needle. The pattern asks for 8 increases.

80 / 8 = 10.

The row reads “knit 10, M1” repeated 8 times. That uses all 80 stitches on the needle, adds 8 new stitches from the M1s, and finishes with 88 stitches in the new row. Math holds, increases land on a regular interval, fabric ends up evenly widened.

There’s one cosmetic issue with the edge-to-edge version: the last M1 falls at the very end of the row, with no plain stitches after it. Some patterns are fine with that. Some aren’t. If you want a buffer on both edges, split one interval between the start and end of the row. The row becomes “knit 5, M1, (knit 10, M1) 7 times, knit 5.” Same 80 stitches consumed, same 8 increases worked, same 88 stitches out. The M1s stay away from the edges, which makes seaming and pickup tidier later.

Worked example: a remainder you have to deal with

Real patterns rarely divide cleanly.

Take 75 stitches with 8 increases.

75 / 8 = 9 remainder 3.

That means 5 sections of 9 stitches and 3 sections of 10 stitches. Each section gets one M1 at the end. Five “knit 9, M1” plus three “knit 10, M1” works out to 75 stitches consumed and 8 increases worked, ending the row at 83 stitches.

Where do the longer sections go? Spread them out. Don’t put all three 10-stitch sections at the start of the row and follow with five 9-stitch sections at the end. The eye reads that as uneven even when the math technically adds up.

A workable arrangement: section of 9, section of 9, section of 10, section of 9, section of 9, section of 10, section of 9, section of 10. The longer sections fall at roughly every third interval, which keeps the distribution looking deliberate rather than lopsided.

You don’t have to be precise. Off-by-one stitches in placement won’t show in the finished fabric for most projects. The goal is even-looking distribution, not mathematical perfection.

The decrease side of the same formula

Decreases need one extra bit of framing, because a k2tog consumes two stitches and creates one. The interval is the whole repeat, not the number of plain stitches before the decrease.

Take 90 stitches with 10 decreases.

90 / 10 = 9.

Each repeat covers 9 stitches: the first 7 are plain, the last 2 are worked together. So the row reads “knit 7, k2tog” repeated 10 times. That consumes all 90 stitches and removes 10, ending at 80. No leftover stitches, no edge buffer needed unless you want one.

Remainders work the same way they do for increases. A row with 95 stitches and 10 decreases gives 9 remainder 5: five repeats are 9 stitches and five are 10 stitches. Distribute the longer ones across the row instead of clustering them.

Why patterns ask for even spacing

Bunched increases make one area flare while the rest of the fabric stays the same width. The garment ends up with a visible wedge instead of a smooth transition. Bunched decreases pull the fabric inward at the wrong spot, sometimes visibly enough that the finished piece looks crooked from across the room.

The most common place this comes up is the transition row right after ribbing. Ribbing pulls inward at the same stitch count that the body wants to sit flat at. Adding stitches in that one transition row widens the fabric for the body without re-casting on. Even spacing is what makes that transition disappear into the fabric instead of announcing itself.

Hat crowns are the other classic case. Crown decreases worked at even intervals over a series of rounds produce the tidy spiral or star pattern at the top of a hat. Uneven spacing gives a lopsided crown that’s hard to fix without ripping back. The hat knitting guide walks through crown shaping in more detail.

You’ll also see “increase evenly” in raglan yokes, sleeve cap shaping, and any place a designer needs the stitch count to change without drawing attention to the change itself.

Which increase method to use

If the pattern specifies an increase, use that one. Designers pick increases for reasons that aren’t always obvious in the moment, and substituting can change the visible result.

If the pattern just says “increase,” the choice is yours. Each method behaves a little differently.

M1L and M1R are common discreet increases for stockinette. They lift the running thread between two stitches and twist it so it doesn’t leave a hole. M1L leans left, M1R leans right. When increases are scattered evenly across a row (rather than arranged as a visible shaping line), the lean direction matters less. For paired shaping along a raglan or v-neck, follow the pattern’s left- and right-leaning directions so the shaping mirrors.

KFB (knit front and back) works the increase into an existing stitch instead of between two stitches. It leaves a small horizontal bar that looks a bit like a purl bump. Fine in garter stitch or in texture patterns where the bar disappears. More visible in plain stockinette, where a row of KFB increases tends to show as a faint line.

YO (yarn over) creates a deliberate hole and is used in lace, eyelet patterns, and as a paired increase with a decrease elsewhere on the row to keep the stitch count balanced. Not usually what a pattern means by “increase evenly” unless it specifies.

Lifted increases pull a new stitch up from the row below. They can be very inconspicuous in stockinette, but stacked lifted increases need care because they can tug at the fabric if placed too close together.

Which decrease method to use

k2tog leans right. It’s the default for most “decrease 1” instructions when the lean doesn’t matter.

ssk leans left. The natural partner to k2tog for mirrored decreases, like at the start and end of a row for symmetrical raglan shaping. Some knitters swap in skp (slip, knit, pass slipped stitch over) instead. The result is visually similar.

k3tog removes two stitches in one action and leans strongly right. Used when the pattern wants a steeper decrease or when stacking decreases in a lace chart.

Central double decrease (CDD), sometimes written S2KP2 or sl2-k1-p2sso, removes two stitches and keeps the center stitch sitting straight up the middle. Common in lace, in chevron patterns, and at hat crowns where the design wants a strong vertical line.

For “decrease evenly across a row” instructions on a plain knit row, k2tog is often a reasonable default unless the pattern specifies something else. The decreases are scattered, so the lean usually matters less than it would on a visible shaping line.

Edge stitches and seam allowance

The formula doesn’t decide what happens at the edges. That part is up to you.

For pieces that will be seamed, keep the first and last shaping points at least a couple of stitches in from the edge. A decrease worked on the edge stitch makes seaming harder and shows up on the finished seam. The same goes for an increase right at the edge: it disrupts the selvage and complicates pickup later if the project needs a button band or a neckband.

The split-first-interval trick (mentioned earlier) handles this without extra thought. Instead of “knit 10, M1” right from the start, the row begins “knit 5, M1, knit 10, M1…” which puts a 5-stitch buffer between the edge and the first M1.

If the pattern gives exact placement, like k2, *M1, k9; rep from * to last 2 sts, k2, the designer has already built the edge buffer in. Follow it as written.

When the shaping point lands on a purl stitch

This comes up in ribbing transitions and in any allover textured pattern.

If the shaping point falls on a knit stitch in the working pattern, work the increase or decrease as written. If it falls on a purl stitch, the cleanest result usually comes from working the purl-side version of the same method. M1 purlwise. pfb instead of KFB. p2tog instead of k2tog. The stitch reads as part of the pattern instead of interrupting it.

Some patterns handle this automatically by shifting the spacing slightly so all the shaping points fall on knit stitches. That’s a designer’s call. You don’t need to second-guess it.

Working in the round

Same formula, but with no edges to worry about. The round circumference in stitches divided by the number of changes gives the interval, and the shaping repeats all the way around.

The one thing to watch for: if a shaping point lands exactly on the round marker, keep the beginning-of-round clear if the pattern allows it. A decrease that crosses the marker is awkward to work and harder to read on the next round. Use a temporary marker for the shaping point if the beginning of the round must stay fixed.

For hat crowns specifically, the decrease rounds are usually spelled out by the pattern (something like “k8, k2tog around, then knit one round plain, then k7, k2tog around”). The formula above handles the first decrease round when the pattern just says “decrease 8 stitches evenly.”

Symmetric and paired shaping

Even spacing across a row is one situation. Paired shaping is a different one and worth distinguishing.

When a pattern says “increase 1 stitch at each end of every 6th row,” that’s paired shaping for a sleeve or skirt taper. The increases live at fixed positions near the edges, and the formula above doesn’t apply. The same goes for “decrease 1 stitch at each end of the next row and every following 4th row” instructions in armhole shaping.

“Increase evenly” or “decrease evenly” specifically means scattered across the row at regular intervals. If the pattern is asking for paired edge shaping, follow the row-by-row instructions instead of doing the math.

A few common intervals worth recognizing

Some divisions show up often enough that knitters start recognizing them on sight.

  • 80 stitches, increase 8 -> “k10, M1” repeated 8 times -> 88 stitches
  • 60 stitches, increase 6 -> “k10, M1” repeated 6 times -> 66 stitches
  • 72 stitches, increase 8 -> “k9, M1” repeated 8 times -> 80 stitches
  • 90 stitches, decrease 10 -> “k7, k2tog” repeated 10 times -> 80 stitches
  • 100 stitches, decrease 10 -> “k8, k2tog” repeated 10 times -> 90 stitches
  • 84 stitches, decrease 14 -> “k4, k2tog” repeated 14 times -> 70 stitches

The numbers won’t always cooperate this neatly. When they don’t, the remainder gets distributed across the row in the longer-section pattern from earlier.

When the math gets annoying

127 stitches, increase 11, with a 6-stitch lace repeat to respect. That’s the kind of row where the arithmetic on live stitches takes longer than the increases themselves, and it’s also where mistakes happen. The Increase & Decrease Calculator in the KnitTools app gives you a worked-out row-by-row instruction instead of leaving you to figure it out from the needle.

For simpler rows, the calculation by hand is fast and reliable. Knowing when to reach for a tool and when not to is part of working efficiently.

A few things that come up

If a pattern says “increase evenly” without giving a number, look at the next stitch count it expects. Subtract what you currently have, and that’s the number of increases. Uncommon, but it happens in older patterns and in self-drafted designs.

If the spacing ends up off by one stitch in a spot or two, don’t rip. The finished fabric won’t show it on most projects. Even-looking distribution is the real target.

Increasing or decreasing on a purl row works the same way. Use the purl-side equivalent of whichever method you’re using. The spacing formula doesn’t change.

For the cast-on count itself, the stitches-to-cast-on guide covers that calculation. If the gauge underlying the whole thing needs a refresher, that’s the gauge measurement guide.

FAQ

Can I eyeball the spacing instead of doing the math? For small adjustments on wide pieces (a blanket, a scarf), eyeballing works fine. For fitted garments or anything where the math affects the final dimensions, do the calculation. Five minutes of arithmetic beats ripping a sleeve cap.

What if the pattern doesn’t tell me which increase to use? M1L or M1R is the safe default for stockinette. KFB if the pattern is in garter stitch or texture where the bar disappears. The increase type matters more when shaping is visible (a raglan line, a yoke shaping) than when it’s scattered evenly across a row.

Why does my math sometimes give me one fewer or one more change than I need? Usually a remainder that wasn’t accounted for, or an off-by-one when deciding whether the first section gets a full interval or a half interval. Walk through the row mentally before knitting and confirm the math by counting the planned shaping points.

Does the formula change if I’m decreasing 2 stitches at a time with k3tog? The number of decrease points stays the same, but each one removes 2 stitches instead of 1. So 90 stitches with 5 k3togs evenly distributed leaves 80 stitches, not 85. Count by the number of stitches removed, not the number of decrease actions.

Can I increase or decrease on the same row as a stitch pattern repeat? Sometimes. If the row is plain (a transition row between ribbing and stockinette, for example), shaping is straightforward. If the row is mid-pattern, the shaping has to respect the repeat, and the placement gets more complex. Most patterns put shaping on transition rows for exactly this reason.

The pattern says “increase evenly” and the number doesn’t divide my stitch count cleanly. Am I doing something wrong? No, that’s normal. The remainder gets distributed by making some sections one stitch longer than others. Spread the longer sections out across the row rather than clustering them, and the finished fabric will look even.