Package Manager
The Package Manager is a dedicated page for browsing, searching, and managing component packages. Access it from the Settings menu (gear icon) in any project.
Package types
Toggle between two package categories:
- SMD (TPSys) – surface-mount packages using the TPSys parametric system
- THT Generic – through-hole packages with visual pin/body definitions
Library sources
Filter packages by source library using the button row:
- All Libraries – show packages from all sources
- DigiKey KiCad – packages parsed from DigiKey's KiCad library
- KiCad – packages from KiCad's official library
- Gerbtrace – core Newmatik-maintained packages
- Newmatik (ERP) – the approved Package Outlines of the Newmatik ERP, read-only (teams connected to the ERP only)
- Team Library – custom packages created by your team
Scope
Toggle between Team and Space scope using the scope selector:
- Team – shows packages available to all team members
- Space – shows packages scoped to a specific space, selectable via a dropdown
Each package displays a scope badge (Built-in, Team, or Space) indicating where it is stored.
Copy to Space
When viewing built-in or team packages, use the Copy to Space action to copy a package into a specific space. Space packages are only available to members of that space, which is useful for customer-specific footprints or project-scoped variants.
Built-in packages load their footprint when you select one. They are read-only. To change one, copy it to your team or space and edit the copy. Package names are unique within a library: a copy is named <name> (copy), and New Package starts as New THT Package (THT) or New Package (SMD); if that name is already taken, Gerbtrace adds a number, for example New THT Package 2. If a save fails, for example because another package in the library already has that name, Gerbtrace shows the reason.
Searching
Use the search box to find packages by name or alias. The search matches against the canonical package name and all registered aliases.
Package type filter
Filter by TPSys package type classification (Chip 2-pole, Standard, QFP/QFN, BGA, Outline, Generic, etc.) using the dropdown.
Package details
Click a package in the list to see its details in the preview pane:
- Visual footprint rendering
- Package type and dimensions
- Lead geometry and pad sizes
- Alias list
Team packages
Team Library packages are stored in your team's Supabase database. Team admins and editors can create custom packages that are available to all team members. Team packages appear alongside built-in library packages in the SMD and THT package assignment dropdowns.
Import from EDA files
Import from EDA files builds an SMD package from the manufacturer's footprint instead of entering it by hand:
- Footprint (required): a KiCad
.kicad_modor an Eagle.lbr, also inside a ZIP as SamacSys and Ultra Librarian deliver them. An Eagle library with several packages lets you pick one. Only SMD pads are used; through-hole pads are listed and left out. - 3D model (optional): a STEP or IGES file adds the part's height.
- Link: paste a Würth (
we-online.com) download link instead of downloading the file. Sites that need a login or a licence click (SamacSys, Ultra Librarian, SnapEDA) are upload-only.
Gerbtrace converts the footprint to the TPSys 0° baseline (two-pad parts turned so pad 1 is on top; origin in the middle of the pads) and uses the parametric TPSys type when it draws the same pads, else lead groups. The body comes from the fabrication or documentation layer; without one the pad extent is used and the dialog says so.
Before you create anything, the dialog lists packages with the same or almost the same pads, ERP outlines first: same pads and body means Use existing (a part that differs only in height keeps the outline; the height belongs on the MPN). Near matches show what differs. A package created from the import keeps the file name, its SHA-256 and the link as its source, so importing the same file again points to it. In teams connected to the ERP, Propose to ERP opens next, with the near-match reason filled in.
The footprint is not yet checked against the pads of a project's Gerber data (lead-on-pad); check the drawing after assigning the package.
Propose to ERP
In teams connected to the Newmatik ERP, admins and editors can turn a saved SMD team package into a Draft Package Outline in the ERP with Propose to ERP. Gerbtrace sends the geometry as TPSys lead groups, the aliases and your name; you can add the ERP MPN record the outline is for, the datasheet link and notes.
- The name must follow the ERP rules: at most 25 characters, no leading, trailing or double spaces, and no placeholder words such as copy or new.
- The ERP refuses an outline whose geometry another outline already has, and names it: use that one instead. If an outline is almost the same, it asks for a near-match reason; enter it and propose again.
- A proposed package shows ERP · Draft until a production engineer approves it in the ERP, then ERP · Approved; Open in ERP opens the Draft.
See Package Library for more on how packages are structured and matched.