
QR Code Patches and Woven Labels: What Thread Can Actually Hold
A supplier sends back the first embroidered sample and the code looks right from a metre away: a 60 mm square of black thread, three corners where they belong. No phone reads it. Under a loupe every dark module has grown about a third of a millimetre in one axis and shrunk in the other, so the light modules between them have closed into thin grey seams. The digitizing file was correct. Thread did the rest.
Putting a QR code on clothing is a manufacturing problem. Between the file you approve and the object that comes back sits a needle, a loom, a heat press or an inkjet head, and each has a smallest feature it can hold. The general case of curvature and fabric covers what a substrate does to a code. This is what the decoration process does to it first.
A stitch is not a pixel
A filled square becomes a satin column or a tatami fill, and both have a width floor set by the thread, which on standard 40-weight polyester is around a third of a millimetre laid flat and wider once tension pulls on it. Then comes pull compensation. A needle entering fabric drags the material toward the stitch, so a shape comes out narrower than drawn along the pull direction and wider across it, and digitizers correct for that by widening shapes before stitching, usually by a few tenths of a millimetre.
On a logo this is invisible. On a QR code it is fatal, because the grid depends on dark and light modules having the same nominal width. Widen every dark module by 0.3 mm in one axis and the light modules between them lose 0.3 mm in the same axis. At a 1 mm module you have turned a 50/50 grid into roughly 65/35, and the decoder's sampling grid, which assumes an even pitch, starts landing on the wrong side of module boundaries as it works outward. So the module has to be large enough that a fixed compensation error is a small fraction of it, and the digitizer has to be told this is a machine-readable grid: compensation at zero or negative, every module stitched as a discrete block, no auto-merging of adjacent same-colour blocks.
The module size embroidery actually holds
The smallest module most embroidery shops will guarantee as a clean, square, independently visible block sits between 1.5 and 2 mm. Below that, adjacent dark modules merge and touching corners fill in.
A version 1 symbol is 21 modules across plus the four-module quiet zone on each side that ISO asks for, so 29 module widths of footprint: 43.5 mm at 1.5 mm modules, 58 mm at 2 mm. And version 1 at the highest error correction level holds seven bytes, which is not a URL. A 35-character redirect needs version 5 at that level, which is 37 modules plus the margin, so 45 module widths: 67.5 mm at 1.5 mm and 90 mm at 2 mm. That is a patch between seven and nine centimetres square.
Somebody specifies a 40 mm badge, the code turns out to be version 5, and the modules come out at 0.9 mm. Small codes also carry the least structural help: version 1 has no alignment patterns at all and version 2 has one, so the interior reference points that let a decoder resample a warped grid are precisely what a small embroidered code lacks, on the substrate that warps most.
Woven labels hold finer detail than thread
A woven label is made on a loom rather than by a needle, so the unit of resolution is a crossing of warp and weft. On a fine damask label those sit far closer together than embroidery stitches, and a module around 0.8 to 1 mm is realistic, which takes that version 5 code from a 90 mm patch down to nearer 45 mm.
The catch is anisotropy. Warp and weft do not behave identically, so edges running one way come out crisper than the other, and a code rotated to fit the label shape will not behave like the proof. Send the mill the code at the exact orientation it will be woven in. Labels also fold, which embroidery does not, and a crease across a finder pattern is a failed detection rather than a degraded read, so if the label must be sewn in, sew it flat on a flat panel, on all four sides.
Film, vinyl and ink
- Cut vinyl is out. Heat transfer vinyl is cut and then weeded by hand, and a QR code has hundreds of independent light squares. Nobody is weeding those.
- Printed transfer film is the best route. Direct-to-film prints at print resolution onto a carrier, powders it with adhesive and presses the whole image, so module size is limited by adhesive spread rather than by a cutting or stitching floor.
- Screen print and direct-to-garment both work on light cloth. Screen print holds the crisper edge at a fine mesh. Direct-to-garment ink wicks along fibres, so it is acceptable near a millimetre on combed ringspun cotton and poor on slub and blends.
The dark-garment trap is registration. Both processes lay down a white underbase so dark ink reads on a dark shirt, and if that underbase is generated per module, every module edge depends on two passes lining up. Misregistration then shows as a white halo on one side of every dark square and a bleed on the other. Print the underbase as one solid light rectangle covering the code and its full margin, then print the dark modules on top. That also handles the quiet zone honestly, because the garment colour never acts as a light module.
The patch wins because it is stiff, which also answers the sleeve
A patch has a backing: twill, a fusible interlining, a laser-cut edge, a moulded silicone or thermoplastic body. All of them are stiffer than the fabric around them, and stiffness is what keeps the module grid planar while the garment does not. Moulded patches go further: modules formed in a tool have mechanical edges and can drop below a millimetre. Keep them matte, because a glossy moulded patch under a ceiling light behaves precisely like a laminated print. And watch the edge finish, because a dark satin or merrow border two millimetres from the symbol has eaten the quiet zone.
Stiffness is also the answer to a sleeve, the request that comes up most and works least. A bicep circumference near 35 cm gives a radius around 5.5 cm, so a 60 mm patch wraps roughly 60 degrees of arc, well past what alignment patterns correct for. Make the patch rigid enough to hold its own plane and mount it on a hook-and-loop base, which is why tactical patches sit flat on curved sleeves while embroidery on the same sleeve does not. Failing that, move the code to a flat panel: upper back, a woven pocket flap, a tote face.
What to put in the order
Send the decorator four things: the code at final size in vector, with the four-module margin drawn as an explicit light rectangle so nobody trims into it; a written module size in millimetres plus a note that this is a machine-readable grid rather than artwork; the orientation it will be stitched or woven in; and one sample on the real base material, washed three times first.
Then scan that sample on two phones, on a hanger, at the distance somebody would actually stand, and check it against the size guide rather than against how it looks on screen. Keep the payload short, because every character you cut is module width you get back, and a dynamic redirect stays at a low version no matter how long the destination grows behind it.

