Review and Fix Altium Libraries

Use Library Remediation in Trace Plugin to find unresolved symbol/footprint links, check library geometry and fields, and prepare a reviewed copy for the library owner.

Before starting

• Install and sign in to Trace Plugin. Open Components → Library Remediation → Open from its home screen.
• Obtain permission to read the library and, separately, to send its content to hosted AI.
• Keep the original library folder and a separate backup. Do not begin by changing your production library.
• For a database or web source, obtain an authorized read account and the connection details from its owner.

This workflow reviews Altium library formats even when no design project is connected. It is not an audit of KiCad's symbol and footprint library tables.

Audit a folder without changing it

1. Choose A folder → Choose folder. Select the folder containing the libraries and their supporting files.
2. Choose the Compliance ruleset. The default is IPC-7351B nominal. Use Copy and edit for your own policy, or Import an existing Trace ruleset.
3. Check required fields, layer assignments, silkscreen/courtyard clearances, pad tolerances and symbol pin grid before proceeding. Numeric lengths in this editor are in mils, not millimeters.
4. Choose Audit and wait for reading, linking and checking to finish.
5. Review scan warnings and unreadable files before interpreting the totals.

The local audit reads .SchLib, .PcbLib, embedded sources in .IntLib, and .DbLib/.SVNDbLib mappings. Supported Excel workbooks (.xlsx/.xlsm) and CSV tables can supply database rows when they are inside the selected folder. A recognized file is not necessarily a readable one; older Excel, Access and unsupported formats can remain unresolved.

A DbLib connection does not authorize a server connection or access to a file outside the folder. Trace reports those dependencies instead of following them automatically. Links, hidden directories, Altium History and preview folders are skipped; limits or unreadable content make the inventory incomplete.

Audits are retained for your signed-in account on this computer. Closing the Library Remediation window does not stop a local audit. Use Stop to stop it; an interrupted audit needs another Audit to finish, not an assumption that its partial results cover the whole library.

Copy a database or web source for review

1. Choose A database or web API.
2. Select SQL Server, PostgreSQL, MySQL / MariaDB or Web API, and enter the owner's approved settings.
3. Optionally use Paste instead → Fill in or From a DbLib…. Pasted text only fills the form; it is not executed. Check every resulting field.
4. Choose Test connection, then review the listed tables and any truncation notice. Select only the tables needed for the audit.
5. Keep Also copy the library files its rows name selected if needed, and choose their folder.
6. Choose Copy and audit. Review copy warnings and unresolved links.

Trace reads supported SQL sources and copies selected rows and library files into its own local working folder. It does not update the source database. DbLib field mappings are retained when supplied; inferred mappings still need review.

Web sources use the configured GET or POST request. Confirm with the owner that the address, method and body are a read operation: a successful response does not establish that an arbitrary service has no side effects. This is not universal support for every OLE DB provider, DbLib driver or web API.

Saved passwords and authentication headers are encrypted locally; saving a source can be refused when secure storage is unavailable. Do not paste credentials into chat, reports or support messages.

Interpret the findings

Use the verdict filters, Every check, Find a part and Show more to inspect the inventory. Disable Only parts with problems when you need to see all parts. Choose Pictures for the reconstructed symbol and footprint drawings.

• Unresolved: a symbol, footprint or part identity could not be resolved.
• Noncompliant: at least one error under the selected ruleset.
• Missing information: required information is absent.
• Needs review: warnings require a decision.
• Compliant: these checks found no errors or warnings; this is not certification against a manufacturer's exact package.

Checks cover supported pin/pad agreement, pad rows, origin, layers, silkscreen, courtyards and fields. Geometry alone cannot establish every package dimension or intended pinout. A failed check, missing drawing or unreadable library is not a clean result. Changing a rule's severity or disabling it changes the policy, not the part.

Add an optional hosted AI review

1. Finish the local audit first.
2. Under AI review, select a model. This picker is separate from chat and initially uses GPT Astra; compatible choices include GPT Sol, Trace Genie 2.0 Flash and Trace Genie 2.0.
3. Choose Parts with something to look at or Every part.
4. Choose Start AI review, review the scope/model/charging confirmation, then choose Start.
5. Follow part-number checks, part-review progress, Credit used so far and any unfinished results.

Part metadata and audit findings are uploaded to Trace's servers even when you select only parts needing attention; that scope limits which parts are reviewed and which drawings are included, not all uploaded metadata. Relevant symbol/footprint geometry and pictures are also sent. The review checks identity and available datasheet evidence and can flag findings that appear intended. Obtain permission before sending proprietary library content.

Usage is charged against your applicable Trace AI allowance or credits, like chat. There is no fixed price per part or advance estimate. A more expensive model or larger scope can consume more allowance; a paused review needs renewed allowance and explicit Continue.

Closing the window or companion does not cancel a server review. Reopen the original audit to check it, and use its Stop control when available. After an uncertain start, interruption or network failure, check that retained review before starting another. Fetching results is not completed review evidence.

AI suggestions can be wrong. Check the cited source, manufacturer part number, package variant and drawing before using a suggestion. A correction in the report does not itself modify your library.

Write selected fixes to a separate folder

1. In a completed audit's Fix section, review every checkbox and before/after value. Simple fixes start selected; nothing is written until you proceed.
2. Consider supported layer, silkscreen, courtyard and mask/paste fixes. Pad number/row/size/orientation, symbol pin/designator and origin changes need deliberate review.
3. Choose Fix … into a folder… and select a new, empty folder separate from the source.
4. Read the resulting Open the change log, refused changes and What to do in Altium.
5. Open and check the output libraries in Altium, save/reopen them, and re-audit the output before adopting it.

Trace copies eligible files and makes supported selected edits in the output, including supported embedded IntLib sources. It re-reads and checks changed libraries; a failed fix leaves that output file unfixed and reports why. Not every finding is automatically fixable.

Manufacturer, part-number and Datasheet field fixes require AI-review evidence. Supported CSV/Excel rows can be changed in the output copy; database proposals also appear in Trace database changes.csv for the owner. The live database is never updated by Fix. Some fields, including compiled IntLib part fields, remain advice only.

The source folder is not overwritten. Skipped links, hidden/History/preview directories and unreadable content are not a complete backup. An earlier Trace output may be replaceable; use a fresh folder if you need to retain an earlier result.

If copying or writing fails, the output can be incomplete. Keep the original, inspect the output and error, and do not adopt it or claim a full rollback. Re-audit changed source files before preparing another set of fixes.

Export and hand off

Use Open report to inspect the HTML report in a selected browser, or save HTML, PDF, Markdown or CSV. Large reports can limit embedded pictures; a PDF failure can be worked around by saving HTML and printing from the browser.

Reports and output libraries contain library information. Review them for confidentiality, incomplete checks and remaining advice before sharing. Hand the owner the output, change log, database proposals and unresolved findings—not a blanket “certified” claim.