How to Invisible Decrease (Crochet)

The invisible decrease is a modified single crochet decrease developed specifically to solve a real, visible problem with the standard method: an ordinary sc2tog decrease leaves a small but noticeable bump or gap on the front of tightly worked fabric, which matters far more in amigurumi (worked at a deliberately tight gauge, with every stitch visible against a small, dense surface) than it does in a looser, larger project where the same bump gets lost in the fabric's overall texture.

The standard decrease it's replacing

A standard single crochet decrease (often written sc2tog) inserts the hook into both loops of two consecutive stitches, pulls up a loop from each, then pulls through all three loops on the hook at once. This is mechanically simple and works fine for most projects, but at amigurumi's characteristically tight gauge, it produces a small, distinct bump on the right side where the two stitches merge — cosmetically undesirable on a small toy where every stitch is individually visible.

The invisible decrease's modification

Rather than inserting into both loops of each stitch, the invisible decrease inserts only into the front loop of the first stitch and the front loop of the second stitch, pulls up a loop through both front loops together, then completes the stitch as normal (yarn over, pull through both loops on the hook). Skipping the back loops specifically is what removes the visible bump — the resulting decrease sits flatter and blends into the surrounding stitches far more convincingly than the standard method does at tight gauge.

The steps

1. Insert the hook through the front loop only of the next stitch.
2. Without yarn-overing yet, insert the hook through the front loop only of the following stitch as well, so both front loops sit on the hook together.
3. Yarn over and pull through both front loops — two loops now remain on the hook.
4. Yarn over and pull through both remaining loops to complete the stitch, exactly as a normal single crochet finishes.

Where it goes wrong

Accidentally catching both loops of a stitch instead of the front loop only. The single most common mistake, and it fully defeats the point of the technique — take a moment to visually confirm you're seeing the front loop's strand under the hook, not both, especially while the front-loop-only insertion is still an unfamiliar motion.

A decrease that still looks bumpy despite using the invisible method. Usually means overall tension across the decrease is too tight — even the invisible method benefits from working the actual stitch slightly looser than the surrounding fabric, since a decrease inherently compresses more material into one stitch regardless of which insertion method is used.

Losing track of which loop is "front" on a stitch that's rotated or twisted from handling. Amigurumi pieces get turned and handled a lot mid-project; if a stitch's orientation looks ambiguous, checking it against a clearly unambiguous neighboring stitch first helps confirm which loop is actually the front one before inserting.

When the trade-off isn't worth it

The invisible decrease is a genuinely slower, fussier motion than a standard sc2tog — for a project where the bump wouldn't be individually visible anyway (a looser-gauge project, a larger piece, anything not worked at amigurumi's characteristically tight, stuffing-concealing tension), the standard decrease is faster to work with no real visual cost. The invisible decrease earns its extra care specifically where amigurumi's tight gauge and small scale make every individual stitch's appearance matter.

Where invisible decrease shows up beyond amigurumi

Anywhere else a project is worked at an unusually tight gauge with individual stitches highly visible — a small tightly worked coaster, a doll's clothing worked to matching scale — the same visible-bump problem and the same invisible-decrease fix apply, even outside amigurumi specifically. The technique is really about gauge and visibility, not about amigurumi as a category on its own.

Invisible increase as the counterpart

There's no widely standardized "invisible increase" the way there's an invisible decrease, mainly because a standard crochet increase (working two stitches into one) doesn't create the same kind of visible bump problem that a decrease does — increases distribute extra fabric rather than compressing it, which reads far less distinctly even at tight amigurumi gauge.

Marking decrease rounds on a pattern

Because amigurumi shaping sequences often mix plain rounds with decrease rounds in a specific, sometimes irregular order, it's worth marking each decrease point directly on a printed pattern (or noting it in a digital pattern's margin) as you work it, rather than relying on memory to track which rounds still need a decrease — a missed or doubled decrease round is one of the more common causes of an amigurumi piece coming out a noticeably different size than the pattern intended.

FAQ

Does the invisible decrease work for stitches taller than single crochet, like half double or double crochet? The front-loop-only principle can be adapted to taller stitches, but the invisible decrease is overwhelmingly associated with single crochet specifically, since amigurumi (its main use case) is almost always worked in single crochet for its dense, stuffing-concealing fabric — taller-stitch amigurumi is uncommon enough that a taller-stitch invisible decrease rarely comes up in practice.

Is the invisible decrease harder to learn than a standard decrease? It has a small learning curve around correctly identifying and isolating the front loop, but once that click happens, it's not meaningfully more difficult to execute — most amigurumi crocheters adopt it as their default decrease fairly quickly.

Does the invisible decrease change the total stitch count differently than a standard decrease? No — both methods reduce two stitches to one, identically affecting your total stitch count; the difference is purely in the visual and structural result at the decrease point, not in the arithmetic of counting stitches.