RAYPCB · ENGINEERING GUIDE
LGA vs PGA vs BGA: Terminal Interfaces, Sockets and Assembly Evidence
LGA, PGA and BGA describe grid-array terminal forms: lands, pins and balls. They help identify the mechanical interface, but they do not by themselves define whether a component is socketed, soldered or interchangeable with another package. The exact component and any socket drawing govern the board design.
This page compares the interfaces and the evidence needed to choose between them. It is not a CPU replacement guide or a claim that one grid-array form is universally faster or more reliable. The selector creates a short interface brief for a supplier discussion.
Identify the surface that makes contact
An LGA presents an array of lands. Depending on the product, those lands can mate with a specified socket or be attached using a supported board-assembly process. Assuming that every LGA is a desktop processor socket can lead to the wrong footprint and retention design.
A PGA presents pins, which may engage a socket or another specified interface. A BGA presents solder balls intended for a corresponding board or substrate attachment. The terminal form is only the beginning: pitch, population, material, coplanarity, contact load and package dimensions still need the actual drawing.
Treat a socket as its own component
If the design uses a socket, obtain its board mounting, contact, loading, retention and service requirements. The PCB connects to the socket, while the package connects to the socket's contacts. These two interfaces can have different geometry and acceptance evidence.
Include the loading mechanism, heatsink force, board support and service access in the mechanical review. A socket may enable replacement, but that does not eliminate assembly constraints or guarantee unlimited insertion cycles. Use the specified operating and service conditions rather than inferring them from the package acronym.
| Review item | What to establish |
|---|---|
| Terminal | Land, pin or ball geometry comes from the exact drawing. |
| Attachment | Direct soldering and socket interfaces are separately specified. |
| Routing | Escape is based on the actual populated map and nets. |
| Evidence | Inspection, electrical and mechanical checks match the interface. |
Grid-array interface brief
Grid-array interface brief
Use the current inputs and keep the assumptions
Choose the question you want to resolve before entering numbers. The fields start blank. Load example deliberately if you want to understand the calculation, and keep that example separate from your project record. The example label remains visible after editing; reset the tool before preparing a record from your own data.
Use the displayed units and identify the source of each input. A dimension should refer to the same layer, reference plane and design revision as the other dimensions in the model. An entered limit is your review requirement, not an IPC value supplied by this website. Where a value is unknown, obtain it or preserve the question as open instead of guessing a familiar number.
Read the assumptions with the result. A negative margin is retained so a conflict remains visible. A positive margin only answers the stated mathematical question. It does not establish process capability, compliance, electrical performance or production yield. Checklist statuses are self-reported and do not imply that the underlying evidence has been inspected.
Changing a field invalidates the result and disables its download until you calculate again. The text download contains the current inputs, result and limitations. No CAD file is read, no project data is uploaded and nothing is automatically inserted into Contact. Attach the record manually if useful. You can request a review directly without using the worksheet.
| Input | What to establish before using it |
|---|---|
| Review reference | Connect this worksheet to a nonconfidential design/revision reference. |
| Terminal form | Form alone does not specify socketing, pin map or assembly route. |
| Planned interface | Verify that the selected package actually supports this interface. |
| Joint / contact evidence | A proposed plan, not a record of inspection performed. |
Compare board routing from the actual terminal map
The same nominal grid pitch can produce different escape problems when terminal population, power/ground distribution and allowed routing differ. Vacant positions can create useful channels, while a dense array may require a different via and stackup approach. Count the paths that must leave each region rather than treating every grid position as an independent signal.
The BGA pitch worksheet explains local channel geometry, and the BGA package-types guide separates construction labels from board-interface data. Neither total terminal count nor package family determines a complete stackup without a layout and manufacturing review.
Match inspection to the chosen attachment
For soldered hidden terminations, visible package alignment is only partial evidence of joint formation. For a socketed interface, contact engagement and mechanical loading require their own checks. Functional testing can reveal certain failures, but its coverage depends on what is actually exercised and measured.
Define an inspection strategy before selecting the production route. Record accessible features, hidden interfaces, relevant electrical checks and any mechanical or environmental validation. Avoid treating an attractive X-ray or optical image as evidence of every required connection and service condition.
Consider thermal and mechanical behavior at system level
The package, board, cooling structure and mounting system form a mechanical and thermal system. Terminal form alone does not determine thermal resistance, signal integrity or durability. A change in package can also change die configuration, substrate construction and power delivery requirements.
When comparing alternatives, hold the functional requirement and operating condition constant. Use component-specific thermal and electrical data, then review the resulting board and enclosure interfaces. Claims such as BGA is always faster or PGA is always stronger omit the conditions needed to make them meaningful.
Build a useful comparison record
For each candidate, list the exact part and package, terminal drawing, board or socket attachment, supply availability, rework/service approach and verification needs. Keep unknowns explicit. If a socket is planned but not selected, its footprint and loading requirements remain open even if the processor package is fixed.
The worksheet reports the selected terminal form, planned attachment and evidence strategy. It does not recommend an unsupported socket or approve a process. Use it to identify the next document or engineering decision needed, then preserve that decision in the PCBA release package.
Discuss the assembly scope with the right data
Send the package and socket information, board layout, quantity, service expectation and inspection/test requirements to RAYPCB. For a soldered BGA build, continue to the established BGA manufacturing process. A well-defined interface lets the supplier evaluate the actual work; a package acronym alone is insufficient for a reliable fabrication or assembly proposal.
Compare complete alternatives rather than labels
Write down the function the component or assembly route must deliver. Then identify the exact alternatives being compared. Similar package names, pin counts or body areas do not establish electrical interchangeability. A useful comparison starts with specific part numbers and their documented interfaces, not a general ranking of one acronym above another.
Compare the complete occupied region on the board. Include terminals, escape routing, supporting parts and the process space that the selected assembly method needs. If the comparison is about serviceability, identify how the part or assembly will actually be removed and replaced. A socket can change both the mechanical envelope and the electrical interface.
Keep production consequences visible. Printing, soldering, inspection and test may differ between alternatives. Some interfaces expose joints to visual inspection, while others require different evidence. None of those observations alone establishes total quality; they help define the appropriate verification plan for the product.
Purchasing should compare approved, available configurations with a clear substitution process. A lower component price can be offset by a different board construction or additional assembly operations. Conversely, a more expensive component can sometimes simplify the implementation. Use actual scoped quotations or clearly labeled internal allowances, rather than a universal claim about which package is cheapest.
Review the product environment and expected changes over its life. Mechanical loads, temperature conditions, repair policy and recurring supply needs can influence the choice. A successful prototype does not automatically settle those questions for production, especially when the component or assembly route changes.
End the comparison with a decision and the evidence still required. If the selection is provisional, say what would change it. This creates a useful next step for an engineering enquiry: the alternatives, constraints and unresolved question can be reviewed together, instead of asking a supplier to endorse a broad package category without seeing the actual design.
Standards, source context and limits
The references below support the stated package, design or process context. Apply a component manufacturer's guidance to its named device or family and confirm the exact drawing revision. A supplier application note is not a universal manufacturing rule, and a public standards scope is not the complete controlled standard.
Agree the governing documents, revision basis, acceptance requirements and exceptions with the responsible engineering and quality teams. The official IPC revision table is useful for checking document status; it does not by itself resolve a project's contractual requirements. This page does not reproduce paid normative tables or claim certification.
Archive photographs illustrate relevant boards, components or assembly activity. They are not proof of the current equipment inventory or a completed qualification for your project. The explanatory drawings and worked examples are original teaching aids. Confirm actual process availability and the proposed inspection scope during the project review.