← Engineering blog

Differential pairs in KiCad: naming, coupling, skew and the return path

How KiCad recognises differential pairs, what matters when routing them (impedance, skew, coupling, reference planes) and how to hand them to a router.

Signal integrityKiCad

USB, Ethernet, LVDS, MIPI, PCI Express and most high-speed serial links are differential. Getting the pairs right is most of the difference between a board that works on the bench and one that fails compliance. Here is what we look for, and how to set a KiCad board up so the pairs are routed the way you intend.

1. Let KiCad find the pairs

KiCad treats two nets as a differential pair when their names differ only by a +/- or a P/N suffix: USB_D+ / USB_D-, ETH_TX_P / ETH_TX_N, LVDS0P / LVDS0N. The interactive differential-pair router and the length and skew tuning tools depend on that naming, and so does our router. If your schematic uses DP/DM or other conventions, rename the nets (or add a note listing the pairs) before ordering.

2. Put the geometry in a net class

Create a net class per interface (for example USB, ETH) under Board Setup → Net Classes and set the differential pair width and gap there. Those two numbers, together with the stack-up, set the differential impedance: 90 Ω for USB 2.0, 100 Ω for Ethernet and most LVDS, 85 Ω for PCI Express. Our microstrip worked example shows how to get a first estimate; the fab’s stack-up calculator gives the final numbers.

3. Match the two halves, not every pair to every other pair

What a receiver cares about first is intra-pair skew: the timing difference between P and N. Skew converts part of the differential signal into common-mode noise and closes the eye. Keep the two halves the same length, and fix the mismatch close to where it is created — usually at the connector or a bend — rather than with one large serpentine at the far end.

Matching between different pairs matters only when the interface says so: a parallel bus with a forwarded clock does, while embedded-clock serial links (USB, PCIe, SATA) mostly tolerate large pair-to-pair differences. Check the interface specification and the chip’s layout guide before adding tuning you do not need.

4. Keep them coupled — and don’t over-think it

  • Route the two tracks together at constant gap. Splitting them around a via or a pad changes the impedance for that stretch; short splits are harmless, long ones are not.
  • Keep other signals away by at least a few times the pair gap, so the pair couples to itself more than to its neighbours.
  • Use symmetric transitions: when a pair changes layers, both tracks change at the same place with the same via geometry.

5. The return path is part of the pair

Even a “differential” signal on a PCB carries common-mode current and couples strongly to the nearest plane. Route pairs over an unbroken reference plane, never across a split, slot or plane gap. When a pair changes layers and the reference plane changes too, place a stitching via (or a capacitor between different nets) right next to the signal vias, so the return current has a short path between the planes.

6. Handing pairs to a router

Whether the router is a colleague, KiCad’s interactive tools or our service, it can only honour what is written down. Before you order routing:

  1. Name the pairs so KiCad recognises them, and put them in net classes with width, gap and clearance.
  2. List the targets in the order notes: “USB_D± 90 Ω diff, max intra-pair skew 0.1 mm; ETH TX/RX pairs 100 Ω diff, reference L2”.
  3. Pre-route anything that must follow a specific path (for example a pair under an RF shield), and lock it. Locked tracks are kept exactly as they are.
  4. Say which pairs need matching to each other, if any.

We route pairs coupled at the net-class geometry and fix skew near its source; the evidence dossier lists skew and length results for every pair and group you defined, with pass/fail against your targets. The before/after comparison on your order page lets you check that nothing but copper changed.