What to upload
Use a PADS ASCII board export containing decals, padstacks, placement and routing records. Retain the original units and version header.
Board CAD
Supported PADS Classic ASCII placements, simple decal copper padstacks, centered slots, explicit Value/MPN attributes, routing and pin connections. Verified source per-layer copper can be restored after native import loses layer differences; mask/paste, unsupported slots and unresolved geometry still limit output.
In development — results may be incomplete or inaccurate.
Use a PADS ASCII board export containing decals, padstacks, placement and routing records. Retain the original units and version header.
Review actual Value and manufacturer part attributes, net names, technical layers and drilled pads. Supported Classic ASCII records include simple decal copper and centered slots within checked orientation limits. Source per-layer copper can be restored when identity, connections and geometry agree with native import. Mask/paste rules, offset slots, custom shapes and unresolved mismatches can still block physical output; a recognized hole alone does not establish a usable board export.
These routes depend on supported source contents. Each upload receives its own result and notes. Shared editor engine for supported board and authored schematic profiles. Coverage and independent qualification are reported separately.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.
The source remains in scope. This shared-engine route is not available yet.