How to Convert DipTrace Files to Altium, Eagle & KiCad

Switching between PCB design tools is a reality for most engineers. Whether you’re collaborating with teams using different software, inheriting projects from other designers, or migrating to a new platform, knowing how to convert DipTrace files to other formats saves countless hours of redrawing. This guide covers practical methods for DipTrace to Altium, DipTrace to Eagle, and DipTrace to KiCad conversion.

Understanding DipTrace Export Capabilities

Before attempting any conversion, understand what DipTrace can export natively. DipTrace version 5 supports extensive import/export options across schematics, PCB layouts, and component libraries.

File Type	Export Formats Available
Schematic	DipTrace ASCII, DipTrace XML, Eagle Schematic, P-CAD ASCII, SPICE Netlist
PCB Layout	DipTrace ASCII/XML, Eagle Board, P-CAD ASCII, PADS PCB ASCII 2005
Component Libraries	DipTrace ASCII/XML, Eagle XML, P-CAD/Altium ASCII
Pattern Libraries	DipTrace ASCII/XML, Eagle XML, KiCad Footprints, P-CAD/Altium ASCII
Manufacturing	Gerber, Gerber X2, ODB++, IPC-2581C, N/C Drill

The key to successful conversion is identifying which intermediate format works best for your target software.

Converting DipTrace to Altium Designer

DipTrace to Altium conversion uses P-CAD ASCII as the bridge format. Altium can import P-CAD files through its Import Wizard, making this the most reliable path.

Step-by-Step PCB Layout Conversion

In DipTrace PCB Layout:

1. Open your completed PCB design (.dip file)
2. Go to File → Export → P-CAD ASCII
3. Save the file with .pcb extension
4. Repeat for any associated schematic files

In Altium Designer:

1. Launch Altium and select File → Import Wizard
2. Choose “P-CAD Designs and Libraries” as the source
3. Select the P-CAD ASCII files you exported
4. Follow the wizard to specify output locations
5. Review and complete the import

Schematic Conversion Considerations

Schematic DipTrace to Altium conversion has some limitations. Users report that wire connections sometimes don’t transfer correctly—components appear but some nets show as unconnected.

Workarounds:

• Export netlist from DipTrace separately
• Manually verify net connectivity after import
• Use the PCB layout as reference to fix schematic connections

Library Conversion

Converting component libraries requires extra steps because DipTrace and Altium handle footprint-to-symbol associations differently.

The Issue: In DipTrace, patterns are embedded within component libraries. Altium keeps schematic symbols and PCB footprints in separate files.

Solution:

1. Export schematic library to P-CAD V16 format (.lia)
2. Export pattern library to P-CAD V16 format (.lia)
3. Import both files separately into Altium
4. Manually attach footprints to schematic symbols in Altium

Known Issues and Fixes

Problem	Cause	Solution
File format error	Binary vs ASCII format	Ensure DipTrace exports ASCII, not binary
Missing connections	Net label translation issues	Manually reconnect using exported netlist
Overlay text displaced	Formatting differences	Adjust text positions in Altium after import
Scaled incorrectly	Unit mismatch	Verify units match (mil, mm) before export

Converting DipTrace to Eagle

DipTrace to Eagle conversion is more limited because DipTrace doesn’t export directly to Eagle format. However, several methods exist.

Method 1: Eagle Board Export (Direct)

DipTrace can export PCB layouts directly to Eagle board format:

1. Open your PCB in DipTrace PCB Layout
2. File → Export → Eagle Board
3. Save the .brd file
4. Open in Eagle

This method works for PCB layouts but doesn’t include schematic data.

Method 2: Schematic via Eagle XML

For schematics, DipTrace exports to Eagle Schematic format:

1. Open schematic in DipTrace Schematic Capture
2. File → Export → Eagle Schematic
3. Import the resulting file into Eagle

Method 3: Using Netlists

When direct conversion fails, use netlist export as a bridge:

1. Export PCB netlist from DipTrace (File → Export → Netlist)
2. Import the netlist into Eagle
3. Place components manually and use the netlist for connectivity

Limitations of DipTrace to Eagle Conversion

DipTrace to Eagle conversion faces challenges because Eagle’s format is proprietary and not fully documented. The DipTrace forum shows years of user requests for better Eagle export support.

What Works	What Doesn’t Work Well
Basic board outlines	Complex copper pours
Component placement	Custom pad shapes
Simple routing	Multi-layer designs
Standard footprints	Custom components

Reverse Direction: Eagle to DipTrace

If you need to go from Eagle to DipTrace (useful for collaboration), DipTrace includes ULP scripts in the Utils folder:

1. Open Eagle and load your schematic or board
2. Click the ULP button
3. Navigate to C:\Program Files\DipTrace\Utils
4. Select Eagle_to_DipTrace_SCH.ulp or Eagle_to_DipTrace_BRD.ulp
5. Save the resulting ASCII file
6. Import into DipTrace via File → Import → DipTrace ASCII

Note: These scripts work best with Eagle versions 7.2 and earlier. Newer Eagle versions may produce compatibility issues.

Converting DipTrace to KiCad

DipTrace to KiCad conversion has improved significantly in recent DipTrace versions, which now support direct KiCad format export.

Direct PCB Export to KiCad

1. Open your PCB in DipTrace PCB Layout
2. File → Export → KiCad Board
3. Save the .kicad_pcb file
4. Open in KiCad PCB Editor

Schematic Export to KiCad

1. Open schematic in DipTrace Schematic Capture
2. File → Export → Schematic Netlist → KiCad format
3. Import the netlist into KiCad

Footprint Library Conversion

DipTrace exports directly to KiCad footprint format:

1. Open Pattern Editor
2. Select Library → Export → KiCad Footprints
3. Choose the .kicad_mod output folder
4. Import into KiCad Footprint Editor

Known DipTrace to KiCad Issues

Users report reference designator swapping during schematic import—components like JP1, JP2, JP3 may become JP3, JP1, JP2. This causes mismatch errors when linking schematic to PCB.

Solutions:

• Verify reference designators match between schematic and PCB after import
• Use “Update PCB from Schematic” in KiCad to re-establish connections
• Manually correct any mismatches before routing

Using Intermediate Formats for Complex Conversions

When direct conversion fails, intermediate formats provide alternative paths.

P-CAD ASCII as Universal Bridge

P-CAD ASCII format works with multiple tools:

From DipTrace	Intermediate	To Target
Export P-CAD ASCII	.pcb / .sch files	Altium Import Wizard
Export P-CAD ASCII	.pcb / .sch files	OrCAD (via PADS)
Export P-CAD ASCII	.lia library files	Altium library import

PADS ASCII 2005 Format

PADS format provides another bridge, especially useful for Mentor Graphics tools:

1. DipTrace exports PADS PCB ASCII 2005 format
2. PADS can open these files directly
3. From PADS, export to other formats as needed

One useful workaround: if you have PADS PCB version 9.3 or higher, you can open Altium schematics directly, export as PADS 2005 format, then import to DipTrace. This provides an indirect path when direct Altium-to-DipTrace conversion fails.

Netlist-Based Transfer

When visual layout preservation isn’t critical, netlist transfer ensures electrical connectivity:

Supported Netlist Formats:

• Accel
• Allegro
• KiCad
• Mentor
• OrCAD
• PADS
• P-CAD
• Protel 2.0
• Tango

Export the netlist, import into target software, place components, and route fresh. This guarantees electrical correctness even if layout needs recreation.

Advanced Conversion Scenarios

Converting Multi-Sheet Hierarchical Designs

Hierarchical schematics present additional challenges during conversion. DipTrace’s hierarchical block structure may not translate directly to other tools’ hierarchy implementations.

Recommended approach:

1. Flatten the hierarchy in DipTrace before export if possible
2. Export each sheet separately
3. Rebuild hierarchy structure in target software
4. Verify inter-sheet connections using exported netlist

Handling Differential Pairs and High-Speed Constraints

Design rules, differential pair definitions, and length-matching constraints typically don’t survive conversion between tools. These are software-specific features that must be recreated manually.

After conversion, you’ll need to:

• Redefine differential pairs in the target tool
• Re-enter length matching rules
• Reconfigure impedance calculations based on new stackup definitions
• Verify trace routing still meets original specifications

Converting Copper Pours and Planes

Copper pour conversion varies significantly between tools. Some conversions successfully transfer pour definitions while others lose them entirely, leaving ratlines where plane connections existed.

Target Tool	Copper Pour Status
Altium (via P-CAD)	Usually preserved, verify net assignments
Eagle	May convert as solid regions, verify connectivity
KiCad	Generally works, check thermal relief settings

Always verify ground and power plane integrity after conversion by running a design rule check and confirming no open connections exist.

Binary vs ASCII File Formats

A common conversion failure occurs when attempting to import binary files instead of ASCII versions. Both Altium’s .SchDoc and .PcbDoc files can exist in either format with identical extensions.

How to verify file format:

1. Open the file in a text editor (Notepad, VS Code)
2. ASCII files show readable text at the beginning
3. Binary files show garbled characters

If you receive “Wrong file format” errors during import, the source file is likely binary. Open it in the original software and save/export as ASCII format.

Best Practices for Successful Conversion

Before Exporting

1. Run DRC in DipTrace—fix all errors first
2. Verify component patterns have correct pin assignments
3. Save a backup copy of your original files
4. Note any custom components that may need manual recreation

During Conversion

1. Use ASCII format whenever available (not binary)
2. Check unit settings match between programs
3. Export libraries separately from designs
4. Document any manual fixes required

After Importing

1. Run DRC in the target software
2. Verify net connectivity against original
3. Check component footprints match specifications
4. Review silkscreen and mechanical layers
5. Compare 3D preview if available

Useful Resources

DipTrace Official Resources

Export Documentation: diptrace.com/support/tutorials/

DipTrace Forum: diptrace.com/forum/ (search “export” or specific target format)

Utils Folder Scripts: Located in C:\Program Files\DipTrace\Utils (contains Eagle ULP converters)

Third-Party Conversion Services

Elgris Technologies: elgris.com offers professional DipTrace to Altium conversion services for complex projects.

Component Library Resources

SnapEDA: snapeda.com — Download components in multiple formats, avoiding conversion entirely

Component Search Engine: componentsearchengine.com — Multi-format library parts

Ultra Librarian: ultralibrarian.com — Format-specific component libraries

Frequently Asked Questions

Can I convert DipTrace files directly to Altium format?

Not directly. DipTrace to Altium conversion requires using P-CAD ASCII as an intermediate format. Export from DipTrace to P-CAD ASCII, then use Altium’s Import Wizard to bring the files in. PCB layouts convert reasonably well, but schematic wiring may need manual verification and repair after import.

Why don’t my Eagle exports include schematics?

DipTrace to Eagle export for schematics uses Eagle Schematic format (File → Export → Eagle Schematic), which is separate from board export. You need to export the schematic and board as two separate files, then link them in Eagle. Some complex designs may require netlist-based reconstruction rather than direct conversion.

Does DipTrace support direct KiCad export?

Yes, DipTrace version 5 supports direct DipTrace to KiCad export for both PCB layouts (File → Export → KiCad Board) and netlists. Footprint libraries can also be exported directly to KiCad format through Pattern Editor. However, schematic symbol libraries require netlist-based transfer rather than direct format conversion.

What’s the best format for preserving design integrity during conversion?

P-CAD ASCII format generally preserves the most design information when converting between professional EDA tools. It captures component placement, routing, net names, and layer assignments. However, complex features like differential pair definitions, custom design rules, and embedded 3D models may not transfer completely and require manual recreation.

Why do reference designators change during conversion?

Reference designator mismatches occur because different EDA tools store component relationships differently. DipTrace uses internal IDs that map to RefDes names, while other tools may sort components differently during import. Always verify RefDes assignments after import by comparing against your original design, and use the target software’s annotation tools to correct any mismatches before proceeding with modifications.

Conclusion

Converting DipTrace files to other EDA platforms requires understanding both the source and target software formats. DipTrace to Altium works best through P-CAD ASCII, DipTrace to Eagle uses direct board export or ULP scripts for reverse direction, and DipTrace to KiCad benefits from DipTrace’s native KiCad export support.

No conversion is perfect. Budget time for verification and manual fixes, especially for complex designs with custom components. When precise layout preservation matters, consider maintaining parallel projects in both tools rather than relying entirely on conversion.

The effort invested in understanding these conversion workflows pays dividends when collaborating across teams or transitioning between platforms. Keep original files archived, document any manual modifications required, and verify electrical connectivity thoroughly before manufacturing converted designs.