Identifying Traces on Multi-Layer Boards

Section Overview

This chapter has given you every piece needed to read a board's copper: you can follow a trace across a surface (§2.1), you know the via types that carry a connection between layers (§2.2), and you can read a board's stackup (§1.3). This final section brings them together on the hardest reading problem — following a trace across the hidden inner layers of a multi-layer board. The difficulty is simply that an inner-layer trace is invisible: a trace dives into a via, crosses the board on a buried layer, and surfaces somewhere else, and the copper in between cannot be seen from either face (§2.2). Two things let you follow it anyway. The first is the board's design package, when you can get it. Its Gerber files are one image per copper layer — the exact routing on every layer, inner ones included; its fabrication drawing gives the stackup, the drill sizes, and which layers each via spans; and its assembly drawing shows where each component sits and its reference designator. Together they lay every hidden trace and via open to you. The second, for when you have no files, is disciplined reasoning from what you can see: find a net's endpoints by their reference designator and the schematic, read which layers a via could reach (§2.2), use X-ray to glimpse the inner copper (10.5), and confirm every step with an unpowered continuity check (Volume 3). Neither route lets you simply look at an inner trace, but both let you establish where a connection goes. For a repairer that is the whole point: before you can fix a broken connection on a multi-layer board, you must work out where it runs, and this section is how you do that when the copper hides from you (Chapter 5). Learn to follow a trace through the layers, and a dense multi-layer board stops being a black box.

Why This Matters

Most boards you will repair are multi-layer, and their connections disappear inside them — so being able to identify where an inner trace goes is what makes those boards repairable at all. This matters because you cannot repair what you cannot locate: a broken connection on an inner layer must be traced to its endpoints before you can bridge or reroute it, and identifying that hidden path is the first step of the repair (Chapter 5). This matters because the files change everything: when you have a board's Gerber files and drawings, an otherwise-impossible inner trace is simply drawn for you, so knowing these files exist and what they show is a real diagnostic advantage. It matters because reasoning fills the gap: most of the time you will not have the files, and the ability to reconstruct a net from designators, the schematic, the vias, and a meter is what lets you proceed anyway (Volume 3). It matters because the stackup and vias constrain the path: knowing how many layers a board has and which layers a via spans narrows where a hidden trace can possibly go, turning guesswork into deduction (§1.3; §2.2). And it matters because it protects the board: knowing where inner copper runs keeps you from drilling, cutting, or heating into a trace you could not see (Chapter 5). Learn to identify inner-layer traces, and the multi-layer boards that make up most modern electronics become boards you can actually diagnose and repair.

Required Prerequisites

• Via Types — Through-Hole, Blind, Buried, Micro — Section 2.2 gave you the via types that carry a connection between layers, which is central to following a trace that dives out of sight.
• Layer Stackup Conventions — Section 1.3 covered how a board's layers are arranged, which you use to reason about which layer a hidden trace runs on. This is a knowledge and observation section — no hot work; power only if you choose to probe, with care.

Recommended Consumables

• A multi-layer board to study — a scrapped computer or phone board is ideal — to practice following traces that dive between layers
• A board's design files or schematic, if you can get them (Gerber files, a fabrication drawing, an assembly drawing) — to see how the files reveal inner routing
• A notebook — to map endpoints, vias, and the nets you reconstruct
• Isopropyl alcohol and a brush — to clean a board so surface traces, vias, and reference designators are clear

Recommended Practice Hardware

• A magnifier or loupe and a bright, angled light — to see fine traces, vias, and silkscreen designators
• A multimeter with a continuity beeper — to confirm, unpowered, where a hidden connection actually goes (Volume 3)
• Access to X-ray imaging, if available (often through a shop or service) — to glimpse inner-layer copper and via barrels (10.5)
• No iron, hot air, or hot work is needed — this section is reading and reasoning, not procedure

Real-World Applications

Identifying inner-layer traces is what lets a repairer work confidently on the multi-layer boards that fill modern devices. A technician repairing a broken inner connection locates its two endpoints by reference designator and schematic, confirms the break with continuity, and reroutes around it because the original inner trace cannot be reached (Chapter 5). Someone with a board's design files opens the Gerber files and fabrication drawing, reads which layer a net runs on and which vias it uses, and knows exactly where to work. A repairer without files reconstructs a net from what is visible — following surface copper to vias, checking continuity from pin to pin, and deducing the hidden path (Volume 3). A shop diagnosing an intermittent multi-layer fault uses X-ray to see a cracked inner via or trace the surface hides (10.5). And anyone who has drilled or scraped into a multi-layer board blindly learns that an unseen inner trace is easy to destroy, and that identifying it first is what protects it. The failures this skill prevents: repairing the wrong connection, cutting into a hidden trace, giving up on a reachable fault, and misjudging which layer a net runs on (Chapter 5).

Common Challenges

• Losing a trace at a via. A trace that dives into a via continues on a hidden layer — use the stackup, files, or X-ray to find where, or pick it up at its next visible point (§2.2; 10.5).
• Working without the design files. Most repairs have no Gerber files — reconstruct the net from designators, the schematic, and continuity instead (Volume 3).
• Assuming a net stays on one layer. A single connection may cross several layers through vias — follow it via by via, not as one surface line (§2.2).

Safety Notes

Risk Level: Low. Identifying traces on an unpowered board is a safe, reading task — the cautions are about probing a live board and about X-ray equipment, which is specialist gear.

Professional Tips Before Starting

• Get the files if you possibly can. A board's Gerber files and drawings turn an impossible inner trace into one that is simply drawn for you — ask, search, or check the maker's resources before assuming you must reason blind.
• Anchor on what you can see. Start from visible endpoints — a connector pin, a component pad, a test point — named by their reference designator, and work inward (§2.2).
• Let the meter settle every question. When you cannot see where a hidden trace goes, an unpowered continuity check between two candidates gives a definite yes or no (Volume 3).

Following a Trace Through the Layers

Recap and Frame

Before tackling hidden traces, it helps to see that this section is a synthesis — it uses every skill the chapter has built. You can follow a trace along a surface by eye and confirm it with a meter (§2.1); you know that a connection changes layers through a via, and that vias come as through-hole, blind, buried, and micro (§2.2); and you can read a board's stackup to know how many layers it has and in what order (§1.3). On a simple one- or two-sided board that is enough, because every trace is on a face you can see. The multi-layer board is where those skills must combine, because now a trace can run on a layer buried in the middle of the board, out of sight from either side. This section is about that case: how to identify and follow a connection when part of its path is hidden inside the board. It splits into two situations. When you have the board's design files, the hidden routing is documented and your job is to read it. When you do not — which is most of the time in repair — you must reconstruct the path by reasoning from the endpoints, the vias, the stackup, and a continuity meter. The section covers both, and then gives a method that ties them into a repeatable procedure. Keep the goal in mind throughout: not to admire the board, but to establish where a connection runs so you can test it and, if it is broken, repair it (Chapter 5). Start by seeing exactly what the difficulty is.

The Problem — Traces You Cannot See

The whole challenge of this section rests on one plain fact: the copper on a board's inner layers is buried, and you cannot see it. On a multi-layer board, only the top and bottom faces are visible; between them lie one or more inner copper layers, sandwiched inside the laminate (§1.3). A trace on such an inner layer is completely hidden — the solder mask and the outer layers hide it, and no light or angle reveals it. What you do see are the points where an inner trace meets the surface: a trace leaves a visible pad or via on the top, disappears, and a related trace emerges from another via somewhere else. In between, the connection is a black box: you know it goes in here and comes out there, but not the path it took or even, without more information, which layer it used. This is why following a trace by eye — the skill of Section 2.1 — runs out on a multi-layer board (§2.1): the eye can follow copper only on a surface, and the moment a trace dives through a via to an inner layer, the trail goes cold. The vias are the clue. Every time a connection changes layers it must pass through a via, so the vias on a board mark where inner traces begin and end (§2.2); a through-hole via you can probe from both sides, but a blind or buried via hides part of the path entirely. So the problem is precise: you can see a net's surface touchpoints but not its buried copper, and identifying the trace means bridging that gap — with files, with reasoning, or with both. Everything that follows is a way to see, or to deduce, what the board will not simply show you.

The Design Package — Gerber, Fabrication, and Assembly

The cleanest way to identify an inner trace is to have the documents that describe the board, collectively its design package. Three of these matter for tracing, and the first is the most powerful. The Gerber files are the manufacturing artwork for a board — a separate image for every layer it has, including each inner copper layer, plus the solder mask, the silkscreen, and the drill data (silkscreen); open the image for an inner layer and you are looking at the exact routing on it, every trace and pad, as if the layers above were peeled away. With Gerber files a hidden trace is no longer hidden: you can see which layer a net runs on and follow it directly. The second is the fabrication drawing, the mechanical drawing that specifies how the board is built: the stackup and layer order (§1.3), the drill sizes, the board's materials, and — crucially for tracing — which layers each kind of via spans, so you can tell a through-hole from a blind or buried via and know the range of layers a connection could use (§2.2). The third is the assembly drawing, which shows where every component sits on the board and labels each with its reference designator (reference designator), so you can find a given part — and therefore the pads and net you care about — quickly and unambiguously. Together these three give you the whole board: the assembly drawing tells you where a net's endpoints are, the fabrication drawing tells you the layers and via spans, and the Gerber files show the actual copper on each layer. You will not always have them — but when you can get a board's design package, identifying an inner trace becomes reading rather than detective work.

Reading the Stackup and the Vias

Even without full files, two things you can often determine — the stackup and the via types — sharply narrow where a hidden trace can go. Start with the stackup (§1.3). Knowing how many layers a board has, and their order, tells you how many places an inner trace could possibly be: a four-layer board has just two inner layers, often a ground and a power plane with limited signal routing, while a dense ten-layer board has many. Even an educated guess at the layer count — from the board's thickness, its complexity, and the vias you see — bounds the problem (§1.3). Then read the vias (§2.2). Because a connection changes layers only through a via, the vias along a net tell you where it dives and surfaces. A through-hole via passes through the whole board, so a trace using it could continue on any layer; a blind via only reaches from an outer layer to a nearby inner one, so it limits the trace to that span; and a buried via connects inner layers you cannot probe from outside at all (§2.2). Reading the via types along a suspected path therefore tells you not just that a trace changes layers, but roughly which layers are in play. Put the two together and you reason like this: this net leaves a pad on the top layer, drops through a via that — being a blind via to layer two — can only take it to layer two, so the trace continues on layer two until the next via. You still may not see the copper, but you have deduced its layer and its endpoints, which is often enough to test and repair the connection (Chapter 5). The stackup and the vias turn an invisible trace into a constrained puzzle rather than a blank.

Tracing Without the Files

Most repairs give you no design files at all, so the core skill is reconstructing a connection from what the board itself shows — and a meter. Begin at the endpoints you can identify. Components are labelled on the silkscreen with a reference designator — R47, U3, J1 — and a connector pin, a component pad, or a marked test point gives you a known, named point to start from (reference designator; test point). If you have even a schematic — far more common than full board files — it tells you which pins should be on the same net, so you know what ought to connect to what, and your task narrows to confirming it on the board (netlist, §2.1). Then follow and confirm. Trace the visible copper from a known pad until it enters a via and vanishes (§2.2), then look for where the net resurfaces — often at another via or pad nearby — and use an unpowered continuity check to confirm that the two points are truly connected through the board (Volume 3). The meter is decisive here: it does not care that the copper is hidden, only whether two points are joined, so probing from a known endpoint to each candidate endpoint reveals the net one confirmed link at a time. Where the eye and meter still cannot settle a buried path, X-ray can show the inner copper and via barrels directly (10.5). Working this way — endpoints from designators and the schematic, path deduced from vias and the stackup, every link confirmed by continuity — you can reconstruct a multi-layer net without ever seeing its inner copper. It is slower than reading a Gerber, but it is how most real multi-layer repairs are actually traced.

A Method for Following a Trace

Bringing it together, here is a repeatable method for identifying a connection on a multi-layer board, whether or not you have the files. First, define what you are looking for: the two (or more) endpoints of the net you care about — the pins a broken connection should join — found by reference designator and, if you have one, the schematic (reference designator). Second, get the files if you can: if the board's Gerber files, fabrication drawing, and assembly drawing are available, read the net's layer and path from them directly, and you are essentially done (§1.3). Third, if you have no files, gather what the board shows: the stackup or layer count, the vias along the likely path and their types, and the visible surface copper at each end (§2.2). Fourth, follow and deduce: trace visible copper to where it enters a via, use the via type and stackup to reason about which layer it continues on, and pick the net up again where it resurfaces. Fifth, confirm every link: with the board unpowered, use a continuity check to prove each point-to-point connection, and turn to X-ray for a buried path the meter alone cannot resolve (Volume 3; 10.5). Sixth, document what you found: sketch the net — its endpoints, the vias, and the layers — so that when you repair it you know exactly what to restore and what to avoid damaging (Chapter 5). The method scales: with full files it collapses to a quick read; without them it becomes patient detective work; but the sequence is the same. Follow it, and any multi-layer connection — however deeply it hides — becomes one you can identify, test, and repair.

Common Mistakes

• Trying to follow an inner trace by eye. Inner copper is invisible — use files, the stackup and vias, X-ray, or a continuity check instead of guessing from the surface (§2.2; 10.5).
• Ignoring the vias along a net. Vias mark where a connection changes layers — read their types to know which layers a trace could use (§2.2).
• Not seeking the design files. When available, Gerber files and drawings simply show the inner routing — look for them before reasoning blind.
• Confirming a hidden connection by eye alone. You cannot see inner copper — prove a multi-layer link with an unpowered continuity check (Volume 3).
• Cutting or drilling into a board without mapping it. An unseen inner trace is easy to destroy — identify the hidden copper first (Chapter 5).

Troubleshooting Guidance

Multi-layer tracing problems come down to where a hidden connection runs and whether it is intact. If a trace vanishes into a via: it has gone to an inner layer — use the stackup, the files, or X-ray to find which, or pick the net up at its next visible via or pad (§1.3; 10.5). If you cannot find a net's other end: use the reference designators and a schematic to identify which pins share the net (§2.1). If you have the design files: read the net's layer and path directly from the Gerber files and fabrication drawing. If you have no files: reconstruct the net from vias, the stackup, and unpowered continuity checks (Volume 3). If a connection reads open across the board: the break is on a hidden layer or in a via — locate it by X-ray or by testing each segment (10.5; §2.2). If you are unsure which layer a trace uses: read the via type where it dives — a blind via limits it to a nearby layer, a through-hole via does not (§2.2). If you must probe a live board: do it carefully and only when necessary — otherwise power down and check continuity cold (Volume 2). The throughline: identify the endpoints, use files or the stackup-and-vias to deduce the path, and confirm every hidden link with a meter.

Verification & Testing Methods

Use this as a check that you can identify a multi-layer trace, not a hot procedure:

• [ ] I can explain why an inner-layer trace cannot be followed by eye and where it hides (§1.3).
• [ ] I can say what a board's Gerber files, fabrication drawing, and assembly drawing each show and how each helps tracing.
• [ ] I can use the stackup and via types to reason about which layers a hidden trace crosses (§1.3; §2.2).
• [ ] I can reconstruct a net without files, using reference designators, a schematic, the vias, and continuity (Volume 3).
• [ ] I can follow a multi-layer connection end to end with a repeatable method and confirm it with an unpowered continuity check (Chapter 5).

Then try the practice exercises below — observation and reasoning practice; scenarios differ from the quiz.

Practice Exercises

1. Follow a trace to a via (5 minutes, observation). On a multi-layer board, follow a surface trace until it dives into a via, and predict — from the via type and the stackup — where it might re-emerge (§2.2).
2. Map a net from designators (5 minutes, reasoning). Using a board's reference designators and a schematic if you have one, list the pins that should share one net and locate them on the board (§2.1).
3. Confirm a hidden link (4 minutes, applied). With the board unpowered, use a continuity check to prove whether two surface points are connected through the board (Volume 3).
4. Read the files, if you have them (4 minutes, reasoning). If you can obtain a board's Gerber files or fabrication drawing, identify which layer a chosen net runs on and the vias it uses.

These core ideas — why inner traces hide, the design package, reading the stackup and vias, tracing without files, and a method to follow a connection — are tested in the Chapter Quiz at the end of this chapter, where a score of 80% is required to continue.

Key Takeaways

• An inner-layer trace is invisible — buried between a board's layers — so you see only where a net touches the surface at pads and vias, not the copper in between (§1.3; §2.2).
• A board's design package identifies inner traces directly: its Gerber files show the routing on every layer, its fabrication drawing gives the stackup and via spans, and its assembly drawing shows component placement and reference designators.
• The stackup and via types narrow a hidden path: the layer count bounds where a trace can be, and a via's type — through-hole, blind, or buried — tells you which layers a connection could use (§1.3; §2.2).
• Without files, reconstruct a net from what the board shows: endpoints from reference designators and the schematic, the path deduced from vias and the stackup, and every link proven by an unpowered continuity check (Volume 3).
• A repeatable method — define the endpoints, get files or read the stackup and vias, follow and deduce, confirm each link, and document — lets you identify any multi-layer connection so you can test and repair it (Chapter 5).

Skills Learned

• You can now explain why inner-layer traces cannot be followed by eye and where they hide.
• You can now say what a board's Gerber files, fabrication drawing, and assembly drawing each provide.
• You can now use the stackup and via types to reason about a trace's path between layers.
• You can now reconstruct a net without files, using designators, the schematic, and continuity.
• You can now follow a multi-layer connection end to end with a repeatable method and confirm it.

Glossary Additions

• Gerber files — the standard set of manufacturing artwork files for a printed circuit board: a separate image for every layer the board has — each copper layer (inner ones included), the solder mask, the silkscreen — together with the drill data. Opening the image for an inner copper layer shows the exact routing on that layer, every trace and pad, as though the layers above had been peeled away. For a repairer, Gerber files turn an otherwise-invisible inner trace into something that can be read directly, revealing which layer a net runs on and the path it takes.
• fabrication drawing — the mechanical drawing that specifies how a printed circuit board is to be built: its layer stackup and order, its drill sizes, its materials, and which layers each type of via spans. For tracing, the fabrication drawing is what tells you a board's layer arrangement and whether a given via is a through-hole, blind, or buried via — and therefore the range of layers a hidden connection could use — even when you cannot open the copper artwork itself.
• assembly drawing — the drawing that shows where every component is placed on a printed circuit board and labels each with its reference designator (such as R47, U3, or J1), along with orientation and polarity information. For identifying traces, the assembly drawing is how you locate a net's endpoints quickly and unambiguously: it tells you where a given part and its pads sit on the board, so you know exactly which points a connection you are chasing should join.

Suggested Next Sections

Must read next:

• Controlled Impedance — with the trace, via, and pad behind you, Chapter 3 turns to how fast signals behave on a board: what controlled impedance is, why certain traces must be a precise width over a reference plane, and how impedance, ground planes, and signal integrity shape the traces you have learned to read and repair.

Recommended:

• Via Types — Through-Hole, Blind, Buried, Micro — the vias that carry a connection between layers, which mark where a hidden trace begins and ends.
• Layer Stackup Conventions — the arrangement of a board's layers you use to reason about where an inner trace runs.