Import & export: KiCad, Altium, EasyEDA
Open KiCad and Altium projects; write KiCad, Altium Designer and EasyEDA projects — and get the same design back.
Bring the designs you have: KiCad projects (KiCad 5 to current) and Altium Designer projects (PrjPcb, SchDoc, PcbDoc, libraries, zip) open as ordinary WireFrame projects. Take them anywhere: File › Export writes a KiCad project, an Altium Designer project or an EasyEDA Standard project, and compares the nets the written files mean with WireFrame's own, pin by pin, before telling you it is done.
What it does
Altium in
Schematics, the stack, pads, vias, tracks, arcs, polygons, keep-outs, teardrops and embedded STEP models — an 8-layer, 791-part board opened from Altium.
KiCad in
Connectivity identical to kicad-cli's own netlist on 15 of 15 KiCad demo projects.
Three ways out
KiCad, Altium Designer and EasyEDA Standard, written in the background from the open project, unsaved edits included.
Nets proven, not assumed
Measured with kicad-cli on boards of up to 3,050 pins: no net split, none merged.
A round trip loses nothing
Export to KiCad or Altium and import again: the same design, compared field by field — parts, nets, pads, copper, pours, meanders, rules, text, 3D models and design variants. 72 of 72 round trips identical on 36 of KiCad's demo projects, through KiCad and through Altium.
Design variants
KiCad 10 and Altium variants in and out; the BOM and position files of each variant built as kicad-cli builds them.
Measured with the other tools' own rules
An export is checked the way the target tool will read it: WireFrame computes the connections the written schematic means by that tool's own rules and compares them pin by pin with its own. Anything that came apart is joined with labels; anything joined that WireFrame keeps apart is reported. The notification after every import and export says what came across and what could not.
Seventy-two round trips, compared field by field
On 36 of the demo projects that ship with KiCad — two- to ten-layer boards, hierarchical sheets, DDR4 length tuning, custom pads, net ties — every round trip comes back identical: 36 through KiCad, 36 through Altium. The comparison is by the copper and ink each design puts down, so a rectangle written as four lines, or a track split where a via lands, still counts as the same.
What to know when the other tool saves
Altium has no field for some KiCad data — a pad's own zone connection, teardrops, KiCad-only variant flags. WireFrame stores them under extra keys Altium ignores, so they survive a trip through the files; once Altium itself saves the project, it keeps only what it understands. Altium also keeps a pad's corner radius in whole percent, so a rounded pad can come back up to half a percent rounder.
The details
| Import | KiCad 5 .pro to current .kicad_pro · Altium .PrjPcb, .SchDoc, .PcbDoc, .zip · CAD outline (SVG, DXF) |
|---|---|
| Export | KiCad project · Altium Designer project · EasyEDA Standard |
| Altium accuracy | An RFSoC mezzanine board: 245 nets, 1,346 pads, nothing missing, split or merged |
| Documents | Schematic PDF · 1:1 PCB print · fabrication outputs · STEP for the case |
| Not imported | Eagle — open it in KiCad first, then import the KiCad project |
How to start
- File › Import › KiCad Project or Altium Project.
- Work in WireFrame: check, simulate, lay out.
- File › Export › KiCad / Altium Designer / EasyEDA project, and read the notification.
Questions
Can I open an Eagle project?
Not directly. KiCad imports Eagle; open the project there and import the KiCad project into WireFrame.
Does an export include my unsaved changes?
Yes. The export reads the open project, edits you have not saved included, and writes in the background.
Do design variants survive?
Yes — KiCad 10 variants and Altium's project variants come in with the project and go back out with it, the list and what each variant does to each part.