Estimating Thread for a Project
Thread is easy to underestimate because a spool looks like it holds an enormous amount of thread right up until a project with a lot of overlocked seams runs through it faster than expected. How much a seam actually consumes depends far more on the stitch type sewing it than on the seam's raw length — and the thread consumption calculator is built entirely around that difference.
Why stitch type changes consumption so much
A plain lockstitch interlocks a single top thread and a single bobbin thread with a comparatively short loop at each stitch, so it uses only a little more thread than the seam's own length. A chainstitch loops its thread through the previous stitch's loop rather than interlocking with a separate bobbin thread, and that looping structure needs meaningfully more thread per inch of seam to form. An overlock or serger stitch goes further still, wrapping two, three, or four separate threads around the raw edge of the fabric as it sews — needle thread, upper looper, and lower looper working together — which multiplies the thread consumed per inch well beyond either a lockstitch or a chainstitch. None of this is about thread quality or thickness; it's a direct consequence of how much thread each stitch's own geometry needs to form one stitch.
The same seam, five different stitch types
Running an identical 60in seam through each stitch type the calculator supports shows the range clearly. A lockstitch needs about 190in of thread. A chainstitch needs about 345in — nearly double. A 3-thread overlock needs about 483in. A 4-thread overlock (the stronger, safety-stitch version, adding a second needle thread) needs about 621in. A coverstitch — the multi-needle, looper-based stitch used for professional-looking topstitched hems — needs about 828in, more than four times the lockstitch figure for the identical seam length. All of these already include the calculator's default 15% waste and take-up buffer, which covers tension adjustment, the odd broken thread and re-thread, and the thread consumed just testing a stitch on a scrap before sewing the real seam.
A full garment, two different ways
Stitch choice compounds fast once a garment has more than one seam. A garment with eight 40in seams, sewn entirely with a plain lockstitch, needs about 1,012in of thread — a little over 28 yards, comfortably inside a single 120-yard all-purpose spool. Sew the identical eight seams with a 4-thread overlock instead, and the combined thread need jumps to about 3,312in — roughly 92 yards, which is still under a single 200-yard cone, but well beyond what a typical smaller home-sewing spool holds. That's also why serger thread is conventionally sold on cones holding far more yardage than an ordinary sewing thread spool, often running to a thousand yards or more per cone — a serger's own consumption rate would burn through spool-sized quantities of thread implausibly fast otherwise.
When a project genuinely needs more than one spool
Scale the same comparison up to a larger project — twelve 48in seams instead of eight 40in ones — and the gap between stitch types turns into a real purchasing decision, not just an interesting ratio. Sewn with a plain lockstitch, that project needs about 50.6 yards of thread, comfortably inside a single 120-yard spool. Sewn with a 4-thread overlock instead, it needs about 165.6 yards — still under one 200-yard cone, but over a 120-yard spool, meaning the project genuinely needs a second spool if that's the size on hand. spoolsNeededForThread() handles exactly this rounding: it takes the total thread needed and the spool's stated length, and always rounds up, since half a spool isn't a purchasable quantity.
What the combined figure doesn't tell you
The overlock and coverstitch consumption figures above are combined totals across every thread involved in that stitch — needle thread and looper thread together, not a single spool's worth. A real overlock project typically buys needle thread and looper thread separately, sometimes in different colors or weights, and the needle and loopers don't consume thread at identical rates to each other within that combined total. The calculator's total tells you the right amount to buy in aggregate; it doesn't tell you exactly how to split that total between a needle spool and looper cones, which is a decision best made by watching how quickly each specific spool empties on your own machine during a project, rather than assuming an even split.
What the 15% buffer is actually covering
It's worth seeing the waste allowance as its own line item rather than folding it silently into the total. The raw consumption for a 60in lockstitch seam, with no buffer at all, is 60 × 2.75 = 165in. The calculator's default 15% buffer adds another 24.75in on top of that, bringing the total to 189.75in. That extra quarter of the raw figure isn't padding for its own sake — it's a real allowance for tension adjustments made while test-sewing a scrap before the actual seam, thread consumed re-threading after a snap or a jam, and the thread left on a bobbin or spool that's too short to be usable but too long to call fully spent. Skipping the buffer and buying to the bare 165in raw figure works out fine on a good day and comes up short on a day with an ordinary amount of thread-handling friction.
Hand sewing and bobbin winding aren't part of this estimate
Everything above estimates machine-stitched seams specifically; hand sewing consumes thread by a completely different, far less standardized relationship to stitch length, since hand-stitch length, tension, and technique vary enormously from one sewist and one stitch type to the next in a way a single consumption ratio can't usefully capture. Treat any hand-finishing — slip-stitching a hem, hand-picking a zipper, hand-sewing on buttons — as needing its own separate, generously estimated length of thread, cut long enough to finish the task rather than calculated from a formula. It's also worth remembering that winding a bobbin consumes thread from the same spool the needle draws from on most home machines, so a spool's total useful length for a project is effectively split between the needle and every bobbin wound from it — a detail easy to forget when eyeballing whether a spool "looks like enough" for a project's structural seams alone.
Comparing stitch types side by side
Seen together, the five stitch-type figures for the same 60in seam make the pattern clear: lockstitch (190in) and chainstitch (345in) are both single-needle stitches, with the chainstitch's looped structure roughly doubling the lockstitch's consumption for identical seam length. The three overlock-family stitches step up again, each additional thread the stitch wraps around the fabric edge adding a proportional jump — 3-thread overlock (483in), 4-thread overlock (621in), and coverstitch (828in), which uses multiple needles and a looper together and lands as the most thread-hungry stitch type the calculator models. Choosing a stitch type for a seam is usually driven by strength, stretch, and finish requirements first, and thread budgeting second — but on a large or multi-technique project, knowing the consumption gap between stitch types in advance avoids being caught short partway through the more thread-hungry parts of the build.
Common questions about thread consumption
Does a heavier or thicker thread use up more length for the same seam? Not by this kind of estimate, no — the consumption ratios here are about how much thread LENGTH a stitch's geometry consumes per inch of seam, which is governed by the stitch structure, not the thread's weight or thickness. A heavier thread does take up more physical space on a spool and adds more visible bulk to the seam, but it doesn't need proportionally more length to form the same stitch.
Should I buy extra thread for topstitching or decorative stitching on top of the structural estimate? Yes — topstitching, understitching, and any decorative stitching are additional seams in their own right for consumption purposes, even though they don't join two pieces of fabric the way a structural seam does. Add their length as additional "seams" in the calculator rather than assuming the structural estimate already covers them.
Does old thread need to be replaced before starting a big project? Thread does weaken and become more prone to breaking or shredding as it ages, especially if it's been stored somewhere with a lot of light or humidity exposure, and older thread breaking repeatedly mid-seam is a common, avoidable source of exactly the kind of wasted length and frustration a consumption estimate is trying to help you avoid in the first place. For a project where consistent seam strength genuinely matters, starting with fresher thread is worth it even if the old spool still has plenty of length left on it.
Is it worth buying slightly more thread than the calculator suggests? Generally yes, for the same reason it's worth buying slightly more fabric or trim than the bare calculated minimum — a broken thread mid-seam, a redo after unpicking a mistake, or a change of plan partway through a project all eat into the estimate's built-in buffer faster than expected, and running out entirely partway through a long serged seam is a much bigger interruption than a few extra yards of leftover thread at the end.