KiCad & Altium libraries
Use KiCad libraries as they are, import Altium libraries, open KiCad projects.
WireFrame reads KiCad symbol (.kicad_sym) and footprint (.kicad_mod) libraries directly and stores a project's own library in the same format, so KiCad can still open it. Altium Designer libraries import too, and whole KiCad projects open through File › Import.
What it does
KiCad, natively
No conversion step for .kicad_sym and .kicad_mod; your existing libraries just work.
Altium import
Bring symbols and footprints from .IntLib, .SchLib and .PcbLib.
KiCad projects
File › Import › KiCad Project opens .kicad_pro (KiCad 6+) and .pro (KiCad 5); the original project is not modified.
Project libraries
Parts used by a project live beside it in lib_<project>, ready to share.
Measured against the other tool, not judged by eye
An import that drops one net is worse than no import at all, because you will not notice until the board comes back. So the import is tested the only way that means anything: the project is imported, exported again, and the resulting netlist compared against the one kicad-cli produces from the original files. All 15 of KiCad's demo projects come through identical, net for net. The same method is being applied to Altium project import, and its number will be published when it exists — not before.
Libraries as they are, not converted copies
KiCad symbol and footprint libraries are read in place. There is no conversion step, no copy of your library living inside a WireFrame project, and therefore no second copy to go stale when your library is updated. Point WireFrame at the directory you already have.
What a footprint brings with it
Pads with their shapes, layers, drills and apertures; courtyard and keepout; silkscreen and fabrication layers; the 3D model path; pad-to-pin mapping; and the attributes that decide whether a part is through-hole, SMD or excluded from the BOM. A footprint's land pattern is also run through the land-pattern audit — the same sweep that checked all 15,447 footprints in KiCad's library without a false error on any footprint that has pads.
Leaving again is as supported as arriving
Export writes KiCad, Altium Designer and EasyEDA projects, and every net is checked against WireFrame's own netlist on the way out. A tool you cannot leave is a tool you should not adopt, and the export is tested with the same comparison as the import.
The details
| KiCad in | Projects (.kicad_pro), schematics (.kicad_sch), boards (.kicad_pcb), symbol (.kicad_sym) and footprint (.kicad_mod) libraries, 3D models |
|---|---|
| KiCad measured | 15 / 15 demo projects import with a netlist identical to kicad-cli's export; 15,447 library footprints swept by the land-pattern audit |
| Altium in | Integrated and discrete libraries (symbols, footprints, pin maps, land patterns) and projects |
| Out | KiCad, Altium Designer and EasyEDA Standard projects, every net checked against WireFrame's own netlist |
| Licensing | A footprint imported from KiCad's library does not place your board under KiCad's library licence — its exception exists for exactly this |
How to start
- File › Import › KiCad Project, then pick the .kicad_pro file.
- Run ERC and DRC, look at the zones and the 3D view.
- Compare Gerbers against KiCad's output if you have it.
Questions
Will my hierarchy survive the import?
Yes. Multi-sheet projects come across with their hierarchy, including sub-sheets instantiated more than once.
What about a part whose 3D model the project does not ship?
It becomes a block sized from the footprint's courtyard and height rather than a gap, so clearance checks stay honest and the missing model is obvious.
Can I keep working in KiCad at the same time?
Libraries, yes — they are read in place. For a project, work in one tool at a time and move it across deliberately; two tools editing one board is how a net goes missing.