A footprint is where the logical part meets physical reality. Get the copper wrong by half a millimetre and the finest circuit works loose. Most footprint errors are boring, measurable and entirely preventable.
At a glance: 7 minute guide · part 2 of 10 in the PCB design complete guide track · includes a worked example and a quick-reference table.
Pad geometry from the datasheet
Land patterns come from the package drawing: pad width × length and pitch. For SMD parts, follow the IPC-computed pattern in the manufacturer's datasheet. For THT, hole = lead diameter + 0.2 mm, annular ring ≥ 0.15 mm.
| Feature | Rule of thumb | Why |
|---|---|---|
| THT hole | Lead + 0.2 mm | Insertion + solder flow |
| Annular ring | ≥ 0.15 mm | Drill breakout margin |
| SMD pad | Datasheet pattern | Self-centring in reflow |
| Courtyard | Body + clearance | Assembly collisions |
| Pin-1 mark | Silk dot + bevel | Orientation both ways |
Courtyards and courtyard exceptions
What this means at the bench. Each footprint carries a courtyard the keep-out rectangle including part body and hand-soldering space. Courtyard overlaps flag at DRC. Deliberate exceptions (dense connectors) get documented, never silently accepted.
Verify against the physical part
Print footprints at 1:1 and seat real components before layout. Check polarity marks, pin-1 indicators and thermal pad openings. Ten minutes with paper and calipers prevents a fab cycle of discovery.
How to apply this in your build
Work through the sequence below each step assumes the previous one passed. For numbers that need calculating, the linked tools at the end of this guide do the arithmetic instantly.
- Pull the package drawing from the datasheet
- Build or verify pads to the recommended pattern
- Print 1:1 and seat real components
- Check pin-1 and polarity markings on silk
Worked example
An SOT-23 footprint copied from a mismatched library soldered two boards badly the pitch was 0.95 mm instead of 1.00 mm. A caliper check against the drawing caught it before the third. Run the numbers yourself with the PCB Trace Width and the result should agree to within rounding.
Practical note from the bench. Footprint checklists live inside our project folders: package drawing screenshot, measured pads, 1:1 print verified three lines per part.
Field mistakes we see again and again
- Mixing metric and imperial library parts in one design
- Silkscreen over pads legibility dies and soldering suffers
- Thermal pads with no via array heat and RF grounding both suffer
Key takeaways
- Pad geometry from the datasheet the foundation of this guide; revisit it if any measurement here surprises you.
- Courtyards and courtyard exceptions the foundation of this guide; revisit it if any measurement here surprises you.
- Verify against the physical part the foundation of this guide; revisit it if any measurement here surprises you.
Prerequisites and preparation
Before starting. Pull the package drawing from the datasheet and build or verify pads to the recommended pattern. Keep the PCB Trace Width open every number in the worked example is reproducible. Total time including the bench steps: about 6-7 minutes.
Who benefits most
Hobbyists meeting this topic for the first time, students who want the version with real numbers instead of abstract symbols. Returning engineers refreshing a corner of the craft. The mistake list alone justifies the visit every entry in it was learned the expensive way.
Quick reference card
| Aspect | Where to find it in this guide |
|---|---|
| Core theory | Pad geometry from the datasheet |
| Application steps | How to apply this in your build |
| Worked numbers | Worked example |
| Failure modes | Field mistakes we see again and again |
How this fits the PCB design complete guide track
This guide is one stop in the structured learning path. Start from the PCB design complete guide complete guide for the full map, or continue with layout best practices and assembly defects guide. For the arithmetic, open the PCB Trace Width.
Frequently asked questions
Can I reuse the library footprint for a "similar" part? Only after checking the drawing package names lie across vendors.
What is a courtyard exemption? A documented DRC exception where parts intentionally sit closer; record why in the design notes.
Is there a calculator for this? Yes the PCB Trace Width tool runs the formulas from this guide instantly, client-side, with no signup.
Where to go next
- The complete pcb design guide: PCB Design complete guide
- Read next: rf pcb layout: rules for wifi, lora and beyond
- Also in this track: [what is vlsi design?
- Continue with: kicad schematic capture: clean beginnings
- Calculate as you go: PCB trace width calculator · resistor value decoder · SMD code decoder
- Bookmark this page against the day a measurement surprises you. Most readers return to the table and the mistake list first, and that is the correct order.
Bench verification habits
When a result here disagrees with your expectation, write down both numbers before changing anything. The gap between predicted and measured is where the real engineering lives. It is usually a tolerance, a parasitic or an assumption that was never checked.
Keep a lab notebook entry for every build in this track. The measured values, the deviations from the guide and the reason for each. Six months from now, those notes are worth more than any tutorial. They describe your bench and your components rather than a general case.
Formulas and checks from this guide
Verification checklist for this track: run DRC early and often, verify footprints against the datasheet drawing. Walk the return path of every fast signal before ordering. A five-minute Gerber preview has saved more fab cycles than any other habit.
Bookmark this page against your next build in the track. The checklist above is the same one used across 15 guides in this series.
From our lab notebook
Run DRC continuously, then once more after every final edit. The last small change breaks the most boards.
Two for hobby density, four the moment ground integrity or impedance matters. The cost gap has collapsed.
Final note from the author
A note on layout order, which decides most boards in this track: connectors, then ICs with decoupling, then critical routes, then fill. Reversing that order is how revisions multiply.
Working through Pad geometry from the datasheetand Courtyards and courtyard exceptions with that habit in mind takes minutes, and it is the difference between reading about this topic and owning it.
Extended Application Notes
This section expands the practical application of pcb footprints: pads, courtyards and the checks that matter beyond the worked example, into the situations builders actually meet. Component substitution: when the exact specified part is unavailable, the substitution logic follows the governing parameter of this design, not the nominal value, and the verification step after any substitution is to re-measure the one quantity this guide identified as critical. Batch variation: components vary, and the design margins recommended in the sections above absorb that variation; if a second build behaves differently, the difference itself is diagnostic and points to the tolerance that dominated. Environmental limits: temperature, supply variation and ageing each push a real circuit away from its bench behaviour, and the recommended practice is to test the extremes deliberately rather than discover them in the field. These notes exist because the bench taught them, repeatedly, and each one was once a real troubleshooting session that ended in understanding.
Failure Analysis in Depth
The mistakes section above lists the traps; this section explains why each trap exists and how to recognize it early. Mixing metric and imperial library parts in one design Silkscreen over pads legibility dies and soldering suffers Thermal pads with no via array heat and RF grounding both suffer. Each of these failures has a signature that appears in measurement before it appears in smoke: a reading that drifts, a waveform that differs from the prediction, a temperature that climbs faster than the calculation. The discipline this guide teaches is to measure at the first sign, not at the last, and the sections above give the specific instrument and setting for each check. Failure analysis is not pessimism; it is the fastest curriculum in electronics, because a fault understood once is a fault prevented forever.
Pre-Build Checklist
Before powering any build of this design, run the list: every component value verified against the specification above, the critical measurement points identified and accessible, the instrument modes and ranges chosen in advance, the expected values written down beside the bench, and the power source current-limited for first application. The checklist takes two minutes and replaces the most expensive class of beginner error, which is not ignorance but confidence outrunning verification. Builders who adopt the checklist across the guides in this track report first-apply success rates that feel like cheating, but it is not cheating, it is engineering.
What Comes Next
Having worked through this guide, the natural next steps are the adjacent guides in the track index above, each of which assumes exactly the vocabulary this page built. The calculators linked in the tools section verify every number in seconds, and the complete guide at the head of this track maps the entire curriculum. Read once, build once, measure always: that is the method this site teaches and the method every section above followed before publication.
Theory in Practice, Extended
The theory section of pcb footprints: pads, courtyards and the checks that matter deserves one more pass with the bench in mind, because knowing a relationship and applying it under constraint are different skills. In application, the relationship is never isolated: it interacts with tolerances, with temperature, with the behaviour of adjacent stages, and with the measurement itself. The extended practice is to take the governing formula from the sections above and stress it, deliberately. Push the input to the edge of its specified range and watch the output follow the prediction, then push past it and watch the prediction break, because the edge of the specification is exactly where the formula stops being the whole story. That boundary, found on the bench rather than in the datasheet, is the real knowledge this guide offers beyond the mathematics.
Component Sourcing and Substitution Notes
Real builds meet real supply chains, and this section addresses the practical reality. The specified components in this guide were chosen for the reasons stated in the design sections, but equivalent parts from reputable manufacturers almost always serve, provided the governing parameters match, not merely the nominal ones. The substitution checklist: match the parameter this guide identified as critical, verify the package and pinout against the physical part before layout, check the datasheet revision for silent changes, and re-run the verification measurement after installation. Avoid unbranded surplus and marketplace components for anything this guide treats as safety-relevant; the failure mode of a counterfeit is not degradation, it is unpredictability, and unpredictability defeats every other design decision in the chain.
Instrumentation for This Design
Every measurement recommended in this guide maps to a specific instrument configuration, and this section consolidates them. Voltage checks: DC range selected before probing, leads verified against a known source, meter burden considered when the node is high impedance. Current checks: circuit broken at the defined point, meter inserted with the correct range and fuse status confirmed first. Waveform checks: probe compensated against the reference before any amplitude claim, ground lead kept short, bandwidth sufficient for the edge rather than the repetition rate. The instrumentation discipline matters more than the instrument class, and a modest instrument used correctly outperforms an expensive one used casually, a claim this site demonstrates throughout its measurement guides.
Documentation Template for This Build
Close the loop the way professional builds do: record the design values from this guide, the as-built values including every substitution, the measured results beside the predicted ones, and the deviation notes that explain every gap. The template is short, a single page, and it converts a successful build into a reference that survives component changes, firmware updates and the passage of months. Every guide on this site was built and documented exactly this way before publication, and the discipline is offered here as part of the curriculum rather than an afterthought. A build that is documented is twice built, once in copper and once in confidence.
Last updated 23 August 2026