PCB layout
Multi-layer boards: routing, vias, zones and planes, net classes and design rules.
Move from schematic to board in one step, then place footprints, route copper with real-time clearance checking, switch layers with vias and pour ground and power planes. Unrouted connections stay visible as a live ratsnest until they are done.
What it does
Routing that goes where you draw
Route with X, drop a via with V. A click lays exactly the leg the preview shows; anything it comes too close to is measured on its real shape and marked as you route, and DRC reports it — nothing is silently refused.
Route Assist
Auto-route a net or a bus, reroute tracks, or reroute only the clashing ones — in the background, as one undo step (Ctrl+Shift+W or right-click). Double-click finishes a connection.
Zones and planes
Copper zones with net, layer, priority, clearance and cutouts; same-net pads connect to the fill, other nets keep their gap.
Net classes and design rules
Track widths, clearances and via sizes per net class, set to match your fab.
Board outline and holes
Draw the outline on Edge.Cuts, add mounting holes, and see the board in 3D at any time.
Clearance is measured on the real shape
A pad is not a rectangle, a track with a 45° bend is not two rectangles, and a thermal relief is neither. WireFrame measures clearance on the actual geometry — polygon against polygon, including arcs — rather than on bounding boxes, so what the editor marks as a violation is a violation the fab would also find, and what it allows is genuinely manufacturable. It is slower to compute and it is the only version worth having.
Nothing is silently refused
Some tools will not let you lay a track that breaks a rule. That sounds safe and is how people end up fighting the editor at two in the morning. WireFrame lays the track you drew, marks the clearance it broke, and puts it in the DRC list. You decide whether it is a mistake or a deliberate exception; the board does not get to decide for you.
Zones are poured against the rules, every time
A copper zone takes a net, a layer, a priority, a clearance and a thermal-relief style. Pads on the zone's net connect to the fill — with spokes or solid, your choice — and everything else keeps its gap, including other zones at lower priority. Refill re-pours every zone on the board in one step, so the copper you see is always the fill the rules give.
Net classes carry the intent
Track width, clearance, via size and drill belong to a class, not to each track: POWER at 0.8 mm, DEFAULT at 0.25 mm, FINE at 0.15 mm. Assign a net to a class once and every track you draw on it starts correct. When the fab's capability changes, you change the class rather than reroute.
The details
| Layers | 2, 4, 6, 8, 16 or 32 copper layers, on every plan including Free |
|---|---|
| Units | mm or mil, switched at any time with Shift+U |
| Routing | Tracks with 45°, arc or square corners; through, blind/buried and micro vias; differential pairs and length tuning |
| Zones | Per-net copper zones with priority, clearance, minimum width and thermal relief; isolated islands removed; every zone refilled in one step |
| Rules | Net classes with track width, clearance, via size and drill, assigned by net name or by hand; fab presets Relaxed, Standard, Fine pitch and HDI |
| Shortcuts | X route · V via · Shift+U units · Ctrl+Shift+W Route Assist |
How to start
- From the schematic, use Tools › Update Schematic to PCB.
- Draw the board outline on Edge.Cuts and place footprints.
- Route with X, add vias with V, let Route Assist finish what is left, then pour a GND zone on an inner layer.
Questions
Is the layer count limited on the free plan?
No. Up to 32 copper layers, and no limit on board area or part count, on every plan including Free. The paid plans are about the AI, not about taking layers away.
How big a board does it handle?
The renderer is built for boards of more than 10,000 items — tracks, pads, vias and zones — and stays smooth to pan and zoom at that size.
Can I import my fab's design rules?
Start from a fab preset — Relaxed, Standard, Fine pitch or HDI — and adjust it to your fab's published capability; it is saved with the project. Direct import of a fab's rule file is a partner integration and is on the roadmap rather than in the application today.