How it works
The workflow, examples and limits behind every tool.
Pattern editor ↗
Each cell holds a palette index. Square and pointy-top hexagon layouts use the same row-and-column data.
Example: Paint a 12 × 12 motif; switch geometry to compare its appearance.
Up to 40 × 40 cells. Changing dimensions clears the grid only after confirmation. No automatic photo conversion.
Tile counts ↗
Required tiles per colour = painted count + ceiling(painted count × spare percentage / 100). Empty cells are excluded.
Example: Ten blue tiles with 10% spare require eleven blue tiles.
Counts do not optimize cuts or estimate adhesive. Hexagon size uses the entered corner-to-corner dimension.
Placement guide ↗
The palette legend and grid share stable numbers. Empty cells show no number.
Example: A blue tile marked 2 corresponds to palette colour 2 in the printed legend.
The page is a placement reference, not a certified full-size cutting pattern.
Pattern export ↗
JSON preserves dimensions, geometry, palette, settings and cell colours. Imports validate every index before replacement.
Example: Export JSON, import it in another browser and continue the same motif.
Local-only autosave. Clearing browser site data removes the saved pattern unless you export it.
Local work, explicit limits
Each workspace reports its input and file limits. Imports validate the supported format before asking to replace saved work. Plain text is displayed as text, never executed as markup. Both languages use the same tools; the root address always opens in English, with Chinese under /zh/.