Grounding feels like the easiest part of PCB design, since you just connect everything to ground and move on.
But most of what we were taught about ground is a simplification.
It stops being true once your board has high currents, fast-switching signals, or a sensor measuring tiny voltages.
A single grounding mistake can take a board that seems to work perfectly for you and turn it into a product that fails FCC testing, resets when someone touches it, or reads garbage from its sensors.
And when a board fails emissions testing because of a grounding problem, you’re usually looking at another board spin, another round of lab fees, and weeks of delay.
These nine rules start with how to think about ground, and they finish with the one rule that ties all the others together.
Table of Contents
Rule #9 – NEVER Assume Ground Is 0V Everywhere
Ground looks like one perfect connection on a schematic, because every ground pin connects to the same little symbol.
On the actual board, ground is just copper, and copper has resistance and inductance like any other trace.
The ground currents from your regulator, radio, microcontroller, and everything else all flow back through that copper.
Each of those currents creates a small voltage drop as it flows, so two points that are both labeled ground can sit at different voltages.
When your sensor’s ground shares copper with noisy current from another part of the board, that noise ends up in your sensor readings.
A schematic is only an approximation, and the physical board doesn’t care what your schematic says.
So stop thinking of ground as a perfect reference and start thinking of it as a return path.
Every signal on your board travels in a loop, so when one chip sends a signal down a trace, that current flows into the receiving chip, out its ground pin, and back through ground to the chip that sent it.
That current flowing back is called the return current, and at high frequencies it flows through the nearest ground copper, which is usually the ground plane right underneath the signal trace.
That’s because a fast signal isn’t just current moving down the copper, it’s energy traveling in the electric and magnetic fields between the trace and the ground plane below it.
Those fields are why the return current hugs the copper right under the trace, and if anything forces it somewhere else, that bigger loop starts radiating noise.
For every current on your board, ask where it returns and what else is sharing that copper on the way back.
Rule #8 – NEVER Give a Decoupling Cap a Long Path Back to the IC’s Ground Pin
Decoupling caps get a lot of attention for where they’re placed, and most people know to put one right next to the power pin.
But the current from that cap travels in a loop, out of the cap, into the power pin, through the chip, out the ground pin, and back to the cap.
If the ground side of that loop takes a long trace or runs to a via that’s far away, the loop gets bigger, and a bigger loop means more inductance.
That extra inductance slows down how fast the cap can deliver current when the chip suddenly needs it.
The result is a supply voltage that dips during every burst of activity, which can cause random resets, and a loop that radiates noise at your clock frequency and its multiples.
Keep the cap right at the pin like you normally would, but also give its ground pad its own via straight down to the ground plane, right next to the pad.
Rule #7 – NEVER Leave Connector Shields Floating
Connector shields and exposed metal are easy to ignore, because most people never think about how your enclosure and any metal a person can touch connect to ground.
But when someone zaps a USB connector or exposed metal with static electricity, that ESD strike has to go somewhere.
If the shield isn’t connected, the charge can arc into your circuit through whatever path it finds, and that path can run right through your microcontroller.
And if the shield is tied to signal ground at the wrong spot, the ESD current flows across your whole board on its way out, which is how a product ends up resetting when someone touches it.
So the fix is to plan a short, deliberate path for ESD right at the connector, before it can reach the rest of your board.
If your product has a metal enclosure, bond the connector shields to the enclosure with short connections right where the cables enter, and decide on purpose how your circuit ground and mounting holes connect to it.
If your enclosure is plastic, connect the shield to ground right at the connector, and put your ESD protection diodes right there too.
Rule #6 – NEVER Stitch a Multilayer Board Sparsely
Multilayer boards give people a false sense of security, because once there’s a ground plane, the grounding job feels finished.
But most boards have ground copper on more than one layer, like an inner ground plane plus ground pours on the top and bottom.
At high frequencies, two areas of ground copper that only connect in a few places behave like two separate grounds.
When return current needs to move between them and there’s no via nearby, it has to take a long detour to find one.
That detour shows up as noise radiating from the edges of your board, and as crosstalk, which is when one signal leaks into another trace that has nothing to do with it.
Add stitching vias, which are just extra ground vias that tie your ground layers together, along the board edges, around your fast signals, and anywhere a signal changes its reference ground plane.
And a long ground pour with only a few far-apart connections can pick up and radiate noise, so either stitch it down along its length or delete it.
Rule #5 – NEVER Star-Ground a Mixed-Signal Board Because a Textbook Said So
Star grounding means running a separate ground connection from each part of the circuit back to one central point.
It’s classic advice for audio and power electronics, so engineers often carry it over to boards with microcontrollers and radios.
I’ve made this mistake myself, and years ago I even recommended star grounding in one of my own videos.
It sounds like the careful, disciplined way to ground a board, which is exactly why it’s such an easy trap to fall into.
The catch is that those separate ground connections usually end up as long traces, and fast signals need their return path to stay close to the signal.
At high frequencies, return current follows the path with the lowest inductance, and that path is directly under the signal trace on the plane below it.
A star layout takes that path away, so the return current is forced into a long detour back to the central point, and that big loop turns into an antenna.
Star grounding still has its place in audio and power circuits, including small local connections around a switching regulator, but it’s not a replacement for the ground plane under your fast signals.
Instead, use one solid ground plane under all your signal routes, and control noise with where you place your parts and how short you keep the current loops.
Rule #4 – NEVER Let Your Switching Regulator’s Return Path Run Through Sensitive Analog Circuits
Switching regulators and analog circuits both connect to ground, so on the schematic it looks like there’s nothing to worry about.
But a buck converter, which is a switching regulator that steps voltage down, slams current on and off hundreds of thousands of times per second or more.
Those sharp current pulses run through a loop made up of the input capacitor and the switching parts, while the inductor smooths things out on the output side.
If those pulsed currents share the ground path used by sensitive analog circuits like sensors, an ADC, or an audio amplifier, that switching noise ends up in your measurements or your audio.
This is one of the most common reasons sensor readings look clean on a dev board and turn noisy in the finished product.
So keep that input switching loop as tight as you can, and follow the regulator’s recommended layout for the output side.
Then keep the regulator away from your analog section, keep your sensor connections short, and make sure high-current return paths never run through the analog area.
Rule #3 – NEVER Change a Fast Signal’s Reference Ground Plane Without a Nearby Return Via
Layer changes are so routine that most people never think about where the return current goes when a signal switches layers.
Return current flows on the plane right next to the signal, which is called its reference plane, so when a signal moves to a layer with a different reference plane, the return current has to switch planes too.
If there’s no ground via nearby, the return current spreads out looking for one, and that spreading loop radiates and couples noise into everything around it.
When a fast signal like a clock line changes layers and switches to a different reference ground plane, put a ground via right next to the signal via, which gives the return current a short path to follow.
If both layers use the same reference ground plane, the return current never has to switch, so that extra via isn’t needed.
If the signal moves from a ground plane reference to a power plane reference, a via can’t connect those two planes, so use a stitching capacitor instead.
A stitching capacitor is just a small cap between the two planes, placed right next to the signal via, so the return current can hop across.
Rule #2 – NEVER Split Analog and Digital Grounds Unless Nothing Crosses the Split
Analog and digital grounds still get split on a lot of boards, because ADC datasheets and app notes often show separate AGND and DGND pins.
That leads people to cut the ground plane into two islands and connect them at a single point.
The problem is that any signal crossing the split has its return path blocked.
The return current has to go all the way around to that single connection point, which creates a huge loop that radiates and puts a voltage difference between the two halves of your ground.
That voltage difference can corrupt your ADC readings, which is why a split ground is usually noisier than the single plane it replaced.
Use one solid plane, and keep analog and digital apart with both placement and routing, so digital traces and their return currents stay out of the analog section.
If a datasheet shows separate AGND and DGND pins, you’ll usually connect both to the same solid plane right at the chip, but check that chip’s grounding instructions.
Rule #1 – NEVER Break the Ground Plane Under a Signal
Ground plane breaks are the problem hiding behind several of the other rules in this video, which is why I saved this one for last.
Breaks sneak in all the time, like a slot cut so a trace can squeeze through, a cutout around a mounting hole, or a row of vias whose clearance holes merge into one long gap.
None of these look like a problem in your layout tool, but return current wants to flow directly under its signal.
Any break in the plane under that signal forces the return current to detour around the gap.
That detour adds inductance, creates a loop that radiates, and can couple noise into other signals that share the same detour.
Cutting your ground into separate analog and digital sections creates this same kind of break for any signal that crosses between them.
And when a signal changes layers and switches to a different reference ground plane, which is the plane its return current flows on, that return current has to jump from one plane to the other.
If there’s no ground via nearby to make that jump, the return current takes a long detour, even though both planes look perfectly solid in your layout.
This is also why two-layer boards make grounding so hard, since every trace you route on the bottom layer cuts a slot through your ground plane.
On a standard 1.6mm two-layer board, the ground plane also sits much farther below your signal traces than it does on a four-layer board, so the return loops are bigger even when the plane is solid.
Unless you can keep almost all of your routing on the top layer, a four-layer board with a dedicated ground plane is usually the better choice.
When a board fails radiated emissions testing, the cause is often a single slot in the plane under one clock line or switching signal.
So pour your ground plane solid under your signal routes and keep it that way, except for keepout areas a datasheet tells you to clear, like the area under an antenna.
Before you send your board out, hide every layer except ground and look for gaps, slots, and rows of vias that have merged together.
Then check that every fast signal runs over unbroken copper from start to finish.
Grounding problems are hard to catch in your own layout, because a slot or a long return path doesn’t look wrong until the board is sitting in a test lab.
If you’d like a second set of eyes on your board before that happens, you can get help from me and other experienced engineers inside my Hardware Academy.