Icon Forge · a 3D workbench · runs in your browser
Build it in blocks. Stamp it flat.
Stack a few bold pieces on the board, cut holes through them, then press Stamp: the camera looks straight down and what you see is the SVG. The real 16px pixels update while you build, so you find out what survives before you fall in love with a detail.
This browser cannot draw the 3D workbench (WebGL is off or unavailable). Everything still works from the panel: add pieces, select them in the layer list, and edit them there.
Drag a piece to move it (Shift: no snap) · drag the board to orbit · Q/E turn · +/− size · [/] layer · D duplicate · M mirror · X cut · arrows nudge · Del remove
Then make it real
The Forge coaches.
The review decides.
The checks here are quick heuristics on your browser’s own rendering. The exported master.svg is an ordinary, editable SVG: hand it to IconFlow, which renders it in a pinned Chromium, compares finalists, and refuses to ship favicon, PWA, desktop and tray files until a six-axis review of that exact file passes.
How the Forge works
- One model, two views. The board and the SVG are drawn from the same list of pieces. Stamp view is an orthographic camera looking straight down, so it matches the master exactly; Orbit is only for building.
- Layers are draw order. A higher piece covers a lower one. A cut piece punches through every piece below it but never through the card, which is how a mark gets the inner holes a menu-bar silhouette needs.
- Nothing leaves your device. The design is kept in this browser and, when you share it, inside the link’s
#fragment, which browsers never send to a server. An opened SVG is read locally; only the design data embedded by the Forge is used. - Few, bold pieces win. Each brief has a piece budget because detail is the first thing 16px throws away. The red lattice in Stamp view is the 16×16 pixel grid.
- The neighbourhood is the CLI’s. The Forge computes the same 16px shape field as
iconflow neighbours, constant for constant, and compares it with the same generic forms: gear, bell, magnifier, bar chart,# πand the rest. A browser test renders every one of them through both and requires them to agree. A clean neighbourhood is not a clearance check, and it is not a score. - The kit is the hand-off. Download project kit writes a folder the CLI runs as-is: an
iconflow.tomlwith the brief’s intent and@collisionin its avoid set, soiconflow checkgates the same generic forms the Forge showed you; the master; the finalists ready foriconflow compare; and a README of the next commands. It is built in your browser. - Diverge, then compare. Keep up to three finalists and see them side by side at 16 and 32 pixels on light and dark tabs, the way
iconflow comparelays out a bake-off. If two of them are the same shape at 16px, the Forge says so: that is one idea in two colours.