PCB Via Fencing in KiCad: Using the ViaFence Plugin and Getting the Spacing Right
Why bother with via fencing
If your board runs anything above a few hundred MHz alongside circuitry that needs to stay quiet — an ADC input near a switching regulator, an RF trace threading through a digital field — via fencing is one of the least expensive interventions you can make before layout sign-off. No special materials, no added layers. Just vias in a row, connected to ground.
What makes it work: at high frequencies, electromagnetic fields radiate and couple through the board substrate. A row of grounded vias alongside a trace creates a low-impedance wall. Fields can’t easily propagate through the gaps; they get shunted to ground instead. The result is reduced crosstalk and a tighter, lower-inductance return-current path back to the source.
It’s not a substitute for a machined shield can. Via fencing typically delivers 15–30 dB of isolation. A physical shield can reach 40–80 dB. But fabrication cost is zero — it’s just copper and drill holes — and with the right plugin, placement takes seconds.
The one number that governs via fence design
Keep the via-to-via pitch below λ/20 of the highest frequency of concern. That’s one-twentieth of the wavelength at that frequency. Below this threshold the fence acts as a solid electromagnetic barrier; exceed it and you get slot-mode leakage — the gap between vias becomes a slot antenna that lets fields through.
Some references use λ/10 as a looser rule of thumb. Either way, the arithmetic is simple. At 2.4 GHz, the wavelength in FR4 is roughly 52 mm, putting λ/20 at about 2.6 mm. In practice, most designers target 1.5–2.0 mm pitch for 2.4 GHz Wi-Fi or Bluetooth bands. Via diameter typically runs 0.2–0.3 mm; smaller vias reduce parasitic capacitance on the signal line, though they cost more to drill.
One more constraint: the vias must actually connect to a solid ground plane on every layer they pass through. A fence whose vias float because the footprints aren’t tied to the plane does nothing useful — it just adds copper and confuses anyone reading the layout later.
The ViaFence plugin: what it does differently
KiCad’s built-in via stitching tool places individual vias; it doesn’t automatically follow a selected trace and populate a fence at even spacing. For that you need a plugin.
The long-standing option is the via fence generator in easyw’s RF-tools-KiCAD. It works, but it requires pyclipper — a native C extension that has to be compiled or installed separately. On Windows, where many KiCad users work, getting pyclipper into the right place for KiCad’s bundled Python is a well-documented frustration, with forum threads going back years.
The ViaFence plugin by ozzysv sidesteps this entirely. No external libraries at all — just Python that KiCad already ships with. Install the .zip through the Plugin and Content Manager (or drop it manually into the user plugins directory), restart, and it’s ready.
Beyond the install experience, it handles geometry that older generators struggle with:
- Arcs: the plugin follows true arc geometry rather than approximating curves as coarse polygons
- T-junctions: all branches of a branching trace get fenced, not just the longest run
- Closed loops: useful for shielded rings around sensitive components like oscillators or crystal resonators
- Multiple disconnected selections: fence several separate trace segments in a single pass
Return currents: the less obvious reason to use fences
Most discussion of via fencing focuses on blocking external interference. The return-current angle matters just as much, especially for high-speed digital work.
At high frequencies, return currents take the path of least inductance: directly under the signal trace on the nearest ground plane. This works when the plane is continuous. The moment the plane is interrupted — a connector clearance, a routed slot, a cutout — the return current detours. That detour forms a loop antenna, and loop area is directly proportional to radiated emissions.
Via fences stitched along both sides of a critical trace give the return current a tighter alternative path even across imperfect plane regions. It won’t rescue a badly fragmented ground plane, but it genuinely reduces loop area on runs that cross problematic spots. On anything above a few hundred megahertz, that can be the difference between passing a pre-compliance scan and having to respin.
When to add a fence and when to skip it
Via fences consume board real estate, add DRC items to clear, and aren’t worth adding indiscriminately.
Good candidates:
- RF traces — microstrip, grounded coplanar waveguide (GCPW), or stripline runs going to antennas or RF modules
- High-speed digital — PCIe, USB 3, HDMI, or DDR4/5 at speeds where even a small extra loop area matters
- ADC or DAC input traces routed near switching regulators or digital clock nets
- Traces running parallel to a board edge for more than a centimeter or two, where fringing fields escape easily
Adding a via fence to an I2C bus at 400 kHz or a DC power trace is mostly cosmetic. The wavelengths involved are meters long and the fence contributes nothing measurable.
Quick filter: if the fundamental or a significant harmonic is above roughly 100 MHz and the trace is longer than about a centimeter, the question is worth asking. Below that, route it cleanly and move on.
Sources