Resolve Duplicate Footprint Names Before a Project Handoff

A project can appear portable while depending on the order of libraries installed on one workstation. If two libraries contain the same footprint name, another engineer may resolve the reference differently during an update or transfer. Record the actual model source and remove ambiguous resolution before handoff.

Altium’s file-based library documentation describes an ordered search that stops when a matching model is found. This makes library availability and precedence relevant to reproducibility, not merely convenient browsing preferences.

Inspect the resolved source

For each critical component, identify the selected footprint model and the file or managed revision that supplies it. Distinguish a generic model name from a controlled source identity. Search available libraries for duplicate names that could satisfy the same reference, including archived test libraries still installed locally.

Compare duplicates before removing or renaming anything. They may be identical copies, intentional revisions, or unrelated geometries. Preserve the approved version and document how the project should reference it; do not choose a model solely because its library appears first.

Check the handoff dependency set

Include associated dependencies needed by the model, but keep the footprint-resolution question distinct from 3D display. A visually correct body model does not prove that the electrical pads came from the intended footprint library.

Verify in a clean receiving environment

1. Open a copy using only the documented dependency set.
2. Check for unresolved or ambiguous model references.
3. Inspect the resolved source of representative components.
4. Perform a controlled update or transfer in the copy.
5. Compare pad geometry and pin mapping with the approved board.

Do not accept a successful project open as the only portability test. Existing placed geometry can conceal a missing source library until a later edit requests the model again. The controlled update exposes that dependency without changing the released design.

Resolve discrepancies by tightening references, consolidating approved libraries, or including the required project dependencies through the team’s supported workflow. Avoid deleting unrelated shared libraries from another engineer’s workstation to make one project behave correctly.

Close with a retained dependency manifest and the result of the receiving-environment check. The 3D-model portability guide covers the companion problem of external model paths after the footprint source has been established.