You finish a layout, export the Gerbers, upload them to a fab, and two days later get an email: minimum annular ring violation, silkscreen clipped off pads, a trace too close to the board edge. Now you're re-spinning a revision and waiting another week. Almost every one of those emails is preventable.
Short answer: DFM — design for manufacturing — is the practice of designing a board so it can actually be built reliably at your chosen fab. A DFM checklist is the cheap insurance that catches capability violations before you order, instead of after. The rules are boring, they're finite, and running them every time you save is the difference between a first-pass build and a re-spin.
What DFM actually means
Your PCB design tool will happily let you draw things a fabricator can't make: a 3 mil trace, a 0.1 mm drill, copper hanging off the board edge. DFM is the discipline of constraining your design to what your manufacturer can physically produce — and then verifying it before the order goes out.
The key insight: DFM rules aren't universal, they're per-fab. A 4 mil trace/space is trivial for one house and impossible for another. So the real workflow is: pull your manufacturer's capability table, encode those numbers as your design rules, and check against them. A green DRC only means something if the rules came from your fab's spec sheet.
The PCB DFM checklist
Work through these by area. Values below are illustrative rules of thumb for standard 2-layer fab — always replace them with your manufacturer's actual limits.
Trace and space
Minimum trace width and minimum spacing between copper are the headline numbers. Go below them and you get opens (traces that didn't etch) or shorts (spacing that bridged). Set them in your net classes so the router enforces them as you go, not after.
Annular ring and drill sizes
The annular ring is the copper collar around a drilled hole. Too thin and drill wander breaks out the pad. Check minimum drill diameter, minimum ring width, and via sizes against the fab table.
Clearance to board edge
Copper too near the routed edge can be nicked during depanelization or exposed after milling. Keep copper — and ideally silkscreen — set back from the board outline.
Silkscreen over pads
Silkscreen ink on an exposed pad interferes with soldering and looks sloppy. Fabs either clip it or reject it. Clip silk off all copper openings.
Soldermask slivers and web
Between closely spaced pads, the mask can become a sliver too thin to adhere — it flakes off and invites bridging. Respect the minimum mask web/dam width, especially on fine-pitch parts.
Copper-to-edge and acid traps
Beyond edge clearance, watch for acid traps — acute copper angles under 90 degrees where etchant pools and over-etches the corner. Route corners at 45 degrees or use curved traces.
Thermal reliefs
Pads tied directly to a large copper pour wick heat away during soldering, causing cold joints. Use thermal-relief spokes on through-hole and ground pads so they're solderable.
Testpoints
If the board will be tested, place testpoints with enough exposed copper and spacing for a bed-of-nails or probe, on an accessible side.
Match your fab's capability table
The final and most important step: reconcile every number above against your manufacturer's published capabilities. This is what turns a generic DRC into a real DFM check.
| DFM item | Why it matters | Typical rule of thumb (verify with your fab) |
|---|---|---|
| Min trace width | Too thin etches open | 5–6 mil (0.13–0.15 mm) |
| Min trace spacing | Too tight bridges/shorts | 5–6 mil (0.13–0.15 mm) |
| Min drill size | Below tool limit is unmanufacturable | 0.3 mm finished hole |
| Annular ring | Drill wander breaks out the pad | ≥ 0.15 mm ring |
| Copper to board edge | Nicked or exposed at depanel | ≥ 0.3 mm setback |
| Silkscreen over pads | Blocks solder, gets clipped | 0 mil overlap on openings |
| Soldermask web/dam | Thin slivers flake, cause bridging | ≥ 0.1 mm dam |
| Acid traps | Acute copper over-etches | No copper angles < 90° |
| Thermal relief | Copper pour wicks heat, cold joints | Spoke connection to pours |
Run DRC against fab-derived rules, every time
A checklist you run by memory once before ordering is a checklist you'll eventually skip. The fix is automation.
KiCad ships kicad-cli, a command-line tool that runs the same design-rule check as the GUI — kicad-cli pcb drc produces a full report without opening the editor. The winning move is to encode your fab's capability table into your net classes and constraints (our guide to KiCad net classes and design rules walks through this), then run DRC on every change. When something slips — a via too small, a clearance too tight — you see it immediately, while the context is fresh, not two days after you ordered. If you do hit violations, fixing common KiCad DRC errors covers the usual suspects.
Get a DFM report before you order
The last gate before spending money is a DFM report: a document that says, in one place, which rules passed and which failed against your target manufacturer. It's what lets you order with confidence instead of hoping. Pairing DFM with assembly-side checks — see designing for assembly with JLCPCB — closes the loop on both fab and assembly before a single board is made.
This is exactly the gap GoForFab closes. Connect a KiCad project and every push runs DRC and surfaces DFM issues automatically — Gerbers, drill files, and a DRC report regenerated on every commit, so your board is always checked and always current. It's free forever for solo work, and it means the "will this build?" question is answered before you ever hit order.
DFM isn't glamorous, but it's the cheapest engineering you'll ever do. A checklist run automatically on every save turns a class of expensive, slow re-spins into a non-event.