High-Speed PCB Layout in KiCad, Step by Step

Controlled impedance is a property of geometry and dielectric, which means your fabricator decides more of it than your router does. Start by pulling the fab's published controlled-impedance stackup for your layer count and their impedance calculator's recommended trace width and pair gap for your targets, typically 90 ohm differential for USB, 100 ohm for Ethernet. Enter that stackup in KiCad's board setup so the documentation matches reality, and treat the fab's numbers as the source of truth. KiCad's built-in calculator is right for sanity checks and first passes; the fab's calculator reflects the materials they will actually laminate.

Two layout rules fall straight out of physics and cost nothing: every critical trace needs an unbroken reference plane directly beneath it, and on a standard 4-layer board that usually means signals on the outer layers referencing the internal planes. If a critical trace must change layers, keep the return path continuous, which on a budget board means changing layers near stitching vias to the reference plane.

Route every differential interface with KiCad's differential-pair mode rather than as two single tracks, so the router maintains the gap your impedance target depends on. Set the pair width and gap in net classes before routing, keep the polarity consistent, and minimize the uncoupled length where the two sides separate to reach pins. Place series elements like AC-coupling capacitors symmetrically so both sides see the same discontinuities.

Order of operations matters more than heroics: place the critical connectors and ICs first, route the constrained interfaces second, and let everything else flow around them. Autorouting, in any tool, is for the everything-else category, not for the pairs.

Close intra-pair skew first with the skew tuning tool, small meanders near the source of the mismatch, because a pair that is length-matched but skewed still radiates and still degrades the eye. Then, where an interface specifies inter-signal matching, use track-length tuning against the budget from the interface specification rather than a folklore number. Mainstream interfaces are more forgiving than the internet suggests: USB 2.0 high-speed tolerates millimeters of mismatch, not micrometers, so spend tuning effort where the spec says it matters.

Everything decided above should end life as a design rule, not a memory. KiCad's custom rules can constrain differential-pair gap and uncoupled length, clearances around critical nets, and via usage in defined areas, which means a violation shows up in DRC instead of in bring-up. A short rule file that encodes your pair gap, your keepouts under connectors, and your clearance to noisy nets converts this guide from advice into an enforced workflow, and it travels with the project for the next revision.

KiCad calculates geometry from formulas; it does not extract parasitics, simulate channels, or verify an eye diagram. That boundary is workable for mainstream interfaces because fabricator impedance control plus conservative layout absorbs the uncertainty. It stops being workable for multi-gigabit serial links, DDR4-class memory, and dense HDI, where constraint-driven enterprise flows and dedicated analysis earn their cost. Order controlled-impedance fabrication for any board where impedance matters, so the fab measures coupons against the stackup you designed to; it is the cheapest verification step in the entire flow.

Where AI fits honestly: the schematic and the non-critical drafting. ProtoFlow generates the schematic from a plain-English description, imports real LCSC, DigiKey, and Mouser parts, runs ERC and DRC, and exports a native KiCad project, so the hours saved land in the phase where automation is safe, and the critical routing stays in your hands inside KiCad with the rules above enforcing the physics.