Someone asks "what's the best AI PCB design tool" in a forum, and the replies name a chatbot, a KiCad plugin, an editor with a copilot, and a router that finishes a whole board. All six get called "AI PCB design software." They are not doing the same job, and I think that mismatch is why so many "AI designs PCBs now" claims read as either hype or a demo that never becomes a real board.
I build PCBEditor, which is one of the six. Here's the honest map, including where mine stops.
Six kinds, one label
Chat assistants — ChatGPT, Claude, Gemini — are good at the judgement part: choosing a regulator, explaining why an LDO beats a buck converter here, drafting a netlist as text. They can't operate on a board, because they never had one. They write a description of a design, not the design.
AI add-ons for desktop EDA — MCP servers, plugins that let a model drive KiCad — let a model click the buttons you'd click. The routing and the checks are still whatever KiCad's router and DRC already do. A better operator isn't a different router.
Editor copilots, the way Flux.ai does it, layer an assistant over a traditional schematic and PCB canvas. You're still working in a manual editor with the AI alongside rather than doing the whole thing — a real product decision, not a lesser one.
Schematic and BoM automation — Circuit Mind, ProtoFlow — turns a prompt or a requirement into a schematic, a BoM, sourced parts, sometimes an analysis report. The emphasis is the front end; whether it carries into placement and routing varies a lot between them.
Autonomous place-and-route, like Quilter, starts from a schematic you already have and produces placement and routing from it, usually with real rigor on high-speed work. It starts from a finished schematic. It doesn't write one.
Prompt to board is what I build. A plain-English description goes through parts, a netlist, placement, routing and a design-rule check, out to fabrication files. Dense fine-pitch parts, BGAs especially, are where it's weakest, and you still review the result before ordering. I'd rather say that than not.
The question that actually sorts them
None of the six kinds is "the best." They answer different questions. But there's one distinction that tells you something true about any of them: is the physical part of the board measured, or asserted?
A language model is good at judgement and has no way to measure whether a trace clears a pad by 0.15 mm. That's not a training problem, it's a category problem — the same way a calculator is the wrong tool for writing a poem. So whichever of the six you're looking at, the useful question isn't "how smart is the AI," it's whether the physical output came from something that can measure, or from something that's estimating.
Four checks answer that in about ten minutes, on any of the six: ask for real export files (Gerber, drill, pick-and-place, a BOM — a picture isn't something a fab can build); open them in a viewer the vendor didn't write; take the board file into KiCad, or your fab's own checker, and run the rules again somewhere the vendor doesn't control; and run the same design twice, not a fresh prompt — the same input should give the same board, and it won't if the layout comes from a language model that drifts every time it's updated.
What this looked like on mine
One prompt — "Design a compact 4-layer microcontroller breakout board (approx 45x45mm)…" — produced a 47.51 × 45.00 mm board: 16 parts, all 33 nets routed with 0 unrouted, a design-rule pass reporting 0 errors and 0 warnings. Worth reading critically rather than taking at face value: Quality Gate was off for this run (you can see "QG Off" in the panel), so this is the raw baseline, not the best case. One board is an example, not a proof that every board finishes this cleanly — dense fine-pitch parts are exactly where I'd expect that to break. And the interface has moved on since I took this screenshot on 11 September 2026; the board and the numbers are what matter here, not the UI chrome.
So which one do you actually want
Mostly this comes down to where you're starting from, not which is "most AI." If you already have a finished schematic and need serious high-speed constraint work, an autonomous router built for that is the right tool, not a prompt-to-board one that's still drafting your netlist. If you lay out in KiCad and mainly want better schematic capture and part sourcing, an add-on or a schematic-automation tool fits better than replacing your whole flow. If you want to think out loud about a topology or sanity-check a power budget, a chat assistant is genuinely good at that — I still use one for exactly this. And if you want a first board out of a description with nothing installed, that's the case I built PCBEditor for, free in the browser.
Which of the four checks would your current tool fail? If you've run any of them and one held up better — or worse — than the label suggested, I'd like to know which, and what you tested.
Top comments (0)