Pad Naming Convention: Building a Library That Stays Readable

A pad name is the label a layout tool uses to match a net, a symbol pin and a footprint pad. When the convention behind those names is inconsistent, the mistakes appear late and quietly: a component that connects to the wrong net, a footprint that is placed correctly but assigned the wrong pad, a design rule that applies to one library and not to another.

The purpose of a pad naming convention is not tidiness for its own sake, and a library that looks orderly can still be inconsistent where it matters. It is to make the mapping between a schematic pin and a physical pad unambiguous, so that a check can be automated and a substitution can be made without reading the whole library.

What a Pad Name Has to Express

At minimum, a name identifies the pad and its position in the component. A single pad may be numbered, lettered or named according to the package convention, and the same package may use different schemes: ball grids commonly use a letter and a digit pair, dual in line packages use sequential numbers, and connectors often use functional names. Whatever scheme is chosen, it has to match the manufacturer drawing, because that is the document both the engineer and the assembly house will consult.

Beyond identification, a working library convention also encodes the class of the pad. A surface mount pad, a through hole pad with a barrel, a mechanical hole with no electrical function and a fiducial are physically different objects even when they appear on the same footprint, and naming them consistently makes the distinction visible during a review.

<img src="https://www.gopcba.com/wp-content/uploads/2026/05/Industrial-Data-Acquisition-PCBA.png" alt="pad naming in a footprint library” />

Package, Structure and Layer

A commonly used structure is a name built from three parts: the package or family, the pad structure, and any qualifier that affects manufacture. The package part identifies the land pattern family, the structure part describes whether the pad is intended for reflow on the surface, for a through hole component, or for a mechanical feature, and the qualifier records properties such as a thermal pad, a plated slot or an oversized pad for a connector that has to carry current.

Layer and finish information belongs in the footprint rather than in the pad name, except where the same footprint must exist in two variants, for example a pad that is tented and one that is not. In that case the variant can be encoded as a suffix so that both are available in the library and neither is chosen by accident.

Naming the Special Cases

Thermal pads under power packages need their own convention, because they are frequently the pad that is forgotten in the netlist. Giving them a name that clearly marks them as either electrical or mechanical forces the designer to decide, and the decision is then visible to the review and to the manufacturing team.

Mounting holes, shield pads, test points and fiducials benefit from the same treatment. A test point that is named as an ordinary pad will be covered by solder mask if the footprint does not say otherwise, which reduces the coverage the test programme can achieve, and a fiducial named as a pad may appear in the paste layer, which it must not. Each of these cases is a small convention that prevents a specific and repeatable mistake.

Pin Numbering and Polarity

Pin one has to be identified in a way that survives the transition between the schematic, the footprint and the silkscreen. The convention should state how the numbering runs for each package family, whether a second row is numbered in the opposite direction, and how non electrical pads are numbered so that they do not consume a pin number that a real pin needs.

Polarity and orientation markers belong to the same discussion, because the assembly drawing and the silkscreen both depend on them. A diode, an electrolytic capacitor and a connector each need an unambiguous marker, and the marker should be named consistently so that the placement file and the drawing agree.

Making the Convention Enforceable

A convention that lives only in a document is a preference. A convention that lives in a design rule check is a constraint. The practical way to enforce it is to define a name pattern, verify that every pad in the library matches it, and let the tool report the exceptions. The same check can confirm that every footprint has a reference designator on the silkscreen, that the pad count matches the symbol, and that no pad is left unconnected where a connection was intended.

The remaining enforcement is procedural. New parts enter the library through the same review as a schematic change, with the datasheet and the manufacturer drawing as the reference, and the entry is dated and attributed so that a later question can be traced to a source. The manufacturer drawing is the authority, which places the part in the same chain as the procurement record. A library that grows without that discipline accumulates duplicates, near duplicates and parts whose land pattern matches no drawing.

Why Consistency Pays for Itself

The benefit appears at the points where a mistake is expensive. When a part is substituted during a shortage, the replacement has to fit the same land pattern, and a consistent library makes that comparison possible in minutes. When the assembly house queries a pad that appears to be shorted to its neighbour during production, a naming convention that distinguishes a thermal pad from a signal pad answers the question before production stops. When a board is re-spun, the same footprint provides the same evidence of its origin.

The cost of the convention is a small amount of work at the start of a project and a willingness to reject a part that does not follow it. That work belongs to the same layout discipline as the design rules themselves, and it is reviewed alongside them. The cost of not having one is a class of error that is invisible in review, reproducible only in production, and frequently blamed on the assembly process.

FAQ

Should pad names follow the manufacturer drawing or an internal standard? The numbering must match the drawing the assembly house will use. The internal standard governs the structural and qualifier parts of the name.

How should a thermal pad be named? In a way that states whether it is connected electrically, and it should be checked for a net assignment like any other pad.

Do fiducials need a naming convention? They need to be excluded from the paste layer and identified consistently so that the placement machine finds them.

Can the convention be checked automatically? Yes, with a pattern based rule and a library level audit, which is the only way it stays true over time.

Summary

A pad naming convention exists to make the path from schematic pin to physical pad unambiguous. Encode the package, the pad structure and the properties that affect manufacture, handle thermal and mechanical pads explicitly, keep the numbering consistent with the manufacturer drawing, and enforce the pattern with a check rather than a document. The result is a library that can be audited, substituted and trusted.