Perler Bead QR Code Pattern Maker

How to make a Perler bead QR code

For a link sign or a text message, plan the whole square before laying out beads. You need the two listed bead colors, compatible pegboards, placement tweezers and your manufacturer's fusing supplies. Use this workflow with the local maker above.

1. Choose the exact content

   Enter the final link or text in the maker above. Open a web address yourself to check its destination; this tool encodes it without visiting it. Shorter content may need fewer modules. Prefer a durable address you control, and remove tracking parameters only if the destination still works. Spaces, capitalization and line breaks are preserved.

2. Plan the bead size and colors

   Start with Perler P18 Black and P01 White, or choose two clearly separated colors from your bead brand. Keep the same bead size throughout the piece and check your physical stock against the material list. The light cells, including the outside border, are actual beads in this chart, not empty pegboard holes.

3. Set the layout and check the footprint

   Begin with error correction M, one bead per module and a four-module quiet zone. Generate the chart, then read its complete width and board layout. A module is one QR square: at two beads per module, each module becomes a 2 × 2 block of four beads. More error correction can increase the QR version; more beads per module enlarges the same modules.

4. Verify the export before placing beads

   Download Clean QR PNG and read the verification result for that file. The tool decodes the encoded image pixels and compares the recovered content exactly with your input. Use Grid chart PNG or the paged print chart for placement, and Material CSV for shopping. Each PNG is checked separately: a clean-image pass does not prove a heavily labeled chart will decode.

5. Build, fuse and test the real piece

   Place every chart cell, including the continuous light border. Keep the three corner finder patterns and the alternating timing rows intact; add no logo or decorative bead inside the code. Follow your bead manufacturer's fusing instructions. Once the piece has cooled, test it with the intended phones, lighting and distance, and confirm the recovered text or destination. A screen-image pass is not a physical scan guarantee.

Why your QR bead pattern may not scan

First distinguish a failed exported-image check from a failed physical scan. If the export fails, resolve its reported reason before copying beads. If the file passes but the object fails, work through the physical checks below.

• The light border was cropped or decorated

  Keep at least four light modules on every side, beyond the QR's outermost modules. At two beads per module that is eight light beads on each side. A frame, keyring hole or colored edge must sit outside this area. Export the complete square rather than cropping the border to fit a board.

• The colors or labels obscure the pattern

  Try the default dark-on-light colors and a Clean QR PNG without grid labels first. Similar brightness, shiny beads and reflections can reduce separation. A screen contrast ratio is only a planning hint, not a scanner threshold or a guarantee. The decoder also attempts inversion, but a reversed-color image pass does not establish compatibility with every phone.

• Small modules lose their square structure

  Bead holes, gaps, uneven fusing and shadows can change how a camera sees a module. Try two beads per module if the board count and finished size are practical. This doubles each side and quadruples the total bead count. It does not add error-correction data; test the larger real sample rather than assuming it will scan.

• The matrix was edited or copied incorrectly

  Check the three large finder squares first, then compare the printed tile coordinates and module boundaries with the generated chart. L, M, Q and H are recovery levels, not permission to replace a matching percentage of beads. Changing the border or finder patterns may stop detection altogether. Regenerate after changing the input or settings; do not rely on an old pass.

• The image passes but the finished object fails

  Check focus, glare, flatness, the complete border and whether the camera can see the entire code. Move the phone to a few distances in even light. If the code decodes but a link fails to open, check the destination and network separately. This page tests digital exports; it has not measured a universal physical scanning distance, melt depth or success rate.

QR versions, byte capacity and bead sizes

These planning rows include the four-module light border. Each width is the side of a square, not its total bead count. Size uses 5 mm pre-fusing pitch; the live maker recalculates for your brand, quiet zone and module scale. A 29 × 29 count is a bounding-box layout reference: check physical board compatibility.

Byte-mode capacity is the payload in encoded bytes after allowing for mode and length headers. It is not a character limit for Unicode text. Actual segmented encoding can fit some numeric or uppercase text more efficiently; always use the generated version and counts for your own input. The table is a model, not a scan-performance test.

For example, HELLO BEADS at M uses version 1. With one bead per module it is 29 × 29, 841 beads and an estimated 14.5 cm across at 5 mm pitch. With two it is 58 × 58, 3,364 beads, four reference tiles and 29.0 cm. The exact https://example.com/ at M uses version 2: 33 × 33, 1,089 beads, four tiles and 16.5 cm at one bead per module.

Capacity and border background: DENSO WAVE's QR version explanation and four-module margin guidance. Recovery levels: DENSO WAVE's error-correction explanation.