PCB design and layout is the process of translating an electrical schematic into a physical board — placing components, routing copper traces, defining layer stackups, and preparing manufacturing files. The quality of this translation determines whether a board works on the first build or spends weeks in debug cycles. Poor layout decisions — inadequate clearances, wrong trace impedances, uncontrolled return paths — cause failures that no amount of component selection can fix.
A structured layout sequence prevents most of these issues. The standard workflow is: define board outline and layer stackup → place high-speed and power components first → route critical nets (clock, differential pairs, power planes) → route secondary signal traces → run design rule checks (DRC) → generate Gerber and drill files. Jumping straight to routing without finishing placement is the single most common cause of rework.
For any board carrying signals above 100 MHz, controlled impedance traces are non-negotiable. A standard 4-layer stackup — signal / ground / power / signal — provides a solid reference plane beneath all routing layers, keeping trace impedance predictable. Target 50Ω for single-ended traces and 100Ω differential for most digital interfaces (USB, HDMI, PCIe). Trace width for a 50Ω microstrip on FR-4 with a 0.2 mm dielectric is approximately 0.38 mm — but always confirm with your fabricator's stack data, since dielectric thickness and Dk (dielectric constant) vary between suppliers.
Placement drives routing efficiency and signal integrity. Key rules that reduce layout iterations:

The right PCB board design software depends on team size, board complexity, and budget. All modern EDA tools share a common workflow — schematic capture → netlist → PCB layout → DRC → fabrication output — but they differ substantially in routing capability, library quality, collaboration features, and simulation integration.
| Software | Target User | Max Layers | Simulation | Cost |
|---|---|---|---|---|
| Altium Designer | Professional teams | 32+ | SI, PI, thermal | $$$$ |
| KiCad | Makers, startups | 32 | Basic SPICE | Free |
| Eagle (Fusion 360) | Hobbyists, small teams | 16 | Limited | Free–$$ |
| OrCAD / Cadence | Enterprise / aerospace | 40+ | Full SI/PI suite | $$$$ |
| EasyEDA / LCEDA | Prototype, cloud-first | 16 | None | Free–$ |
For professional hardware teams, Altium Designer remains the industry benchmark for high-density, high-speed board design — its interactive router, differential pair management, and native 3D MCAD integration justify the cost for complex projects. KiCad 7 has closed the gap significantly for 4–8 layer boards and is now the default for open-source hardware. Teams prioritizing cloud collaboration and direct fab integration increasingly use EasyEDA paired with JLCPCB for rapid prototyping cycles under 72 hours.
A schematic diagram for PCB is the logical representation of an electronic circuit — it defines every component, every electrical connection, and every reference designator, but contains no physical placement information. The schematic is the contract between the circuit designer and the layout engineer: every net on the schematic must be correctly realized in copper on the board, with no unintended connections and no missing ones.
A PCB board circuit diagram follows standard conventions that make it readable across teams and software platforms:
Electrical rules checks (ERC) in the schematic tool catch most wiring errors before the design reaches layout — unconnected pins, pins driven by multiple sources, power conflicts. Running ERC to zero errors before exporting the netlist is mandatory; layout cannot fix a schematic error.
A PCB via in pad places a through-hole or blind via directly within a component's SMD land pad, rather than routing a short trace from the pad to a nearby via. This technique is primarily used with fine-pitch BGAs (ball grid array packages), QFNs, and other components where the pitch between pads is too tight to route an escape trace alongside the pad.
Routing a short dog-leg trace from a BGA pad to a via introduces inductance and can create a stub that reflects high-frequency signals. Via in pad eliminates this trace entirely, reducing parasitic inductance by 30–50% compared to a 0.5 mm dog-leg escape trace. For DDR5, PCIe Gen 4/5, and 10GbE interfaces running above 8 GT/s, this difference is measurable in eye diagram margin.
Via in pad also enables tighter BGA escape routing — a 0.65 mm pitch BGA has only ~0.25 mm between pad edges, which cannot accommodate a standard via beside the pad without violating minimum annular ring and clearance rules. Via in pad is the only viable escape strategy for sub-0.5 mm pitch packages.
Via in pad requires specific fabrication treatment that adds cost. The via barrel must be filled with conductive or non-conductive epoxy and capped (plated over) before solder mask application. Without filling, solder wicks down the via barrel during reflow, starving the joint and causing intermittent contact or outgassing voids. Specify "via fill + cap plate" explicitly in your fab notes — it is not a default process. Expect a 15–25% fabrication cost premium for via-in-pad boards versus standard vias.
A PCB thermal hotspot map is a visual heat distribution analysis — generated either through simulation before fabrication or through infrared (IR) camera measurement on a live board — that shows which areas of the PCB exceed safe operating temperatures. Hotspots cause accelerated component aging, solder joint fatigue, and outright thermal shutdown in power management ICs, MOSFETs, and linear regulators.
Modern PCB design software with thermal simulation (Ansys Icepak, Cadence Celsius, Altium's integrated thermal solver) generates hotspot maps by applying power dissipation values to each component and solving the heat conduction equation across the board. Inputs required include component theta-JB (junction-to-board thermal resistance), copper pour coverage, via density, and ambient temperature plus airflow conditions. Boards with power densities above 5 W/cm² almost always require simulation before first build — reworking thermal issues post-fabrication is expensive and sometimes impossible without a board respin.
For built boards, a FLIR or similar mid-wave IR camera at 320×240 resolution or better can resolve hotspots down to individual QFN pads when operated at the correct working distance. Run the board at full rated load for at least 10 minutes before capturing thermal images — surface temperatures take several minutes to reach steady state, and early readings underestimate peak junction temperatures. Any surface temperature above 85°C under standard ambient conditions warrants investigation; many consumer-grade components are rated to 85°C case temperature, meaning internal junction temperature is already near or above the limit.
Once hotspots are identified, layout-level corrections are the most effective fix:
Knowing how to troubleshoot a PCB efficiently separates engineers who close debug loops in hours from those who spend days swapping components at random. The key is following a structured isolation method rather than guessing — most PCB faults are localized to a single functional block, and systematic measurement narrows the fault domain quickly.
Before applying power to a new or suspect board, inspect visually and with a multimeter. Check for solder bridges on fine-pitch ICs (a 10× loupe or digital microscope at 40× reveals bridges invisible to the naked eye), verify polarity-sensitive components (electrolytic caps, diodes, ICs with asymmetric pinouts), and measure resistance between power and ground rails. A resistance below 10Ω across the main supply rail before power-up indicates a short — applying voltage to a shorted board risks burning traces and destroying components.
Bring up power rails in sequence, starting with the main input and working through each regulator output. Verify voltage at the regulator output pin, then at the IC power pins — a voltage drop between these two points indicates trace resistance or a via with poor plating. Check ripple on each rail with an oscilloscope (AC coupling, 20 MHz bandwidth limit); ripple exceeding 50 mV peak-to-peak on a digital supply can cause logic errors that mimic firmware bugs.
Divide the board into functional blocks — power, MCU, communications, peripherals — and test each in isolation where possible. For an MCU that fails to boot, first confirm the crystal oscillator is running (measure at the XTAL pin with a scope; a flat signal means no oscillation), then check the reset pin is releasing properly, then verify the SWD/JTAG debug interface. A logic analyzer on the bus helps distinguish between firmware issues and hardware failures — if valid SPI clock and MOSI signals are present but MISO is silent, the fault is downstream of the MCU.