Open Altium .PcbDoc boards and .SchDoc schematics

PCB files: PcbDoc, CmPcbDoc and CsPcbDoc

The board reader accepts binary OLE compound files using CFB version 3 and the supported ASCII PCB record format. It reads components, nets, pads and the first Board6 outline record. The extensions .PcbDoc, .CmPcbDoc and .CsPcbDoc are accepted when their contents match a supported layout.

Validation covers 28 openly licensed boards: 26 binary and two ASCII. Binary component, pad and net counts were checked independently against the raw streams; two ASCII/binary pairs agree on every pad to one micrometre. Other writers and versions remain unverified.

• Top, bottom and through pads are read. Inner and non-copper pads, and components on inner layers, are skipped and counted.
• Bodies are estimated from pad extents; component values are not read from the PCB file.
• Unequal round, octagonal and rounded-rectangle pads use rectangular approximations. Outline arcs use chords.
• Tracks, vias, fills, regions, text, models and design rules are omitted. Free pads and copper are not drawn.
• CFB version 4 and library files such as PcbLib and SchLib are unsupported.

Read the import notice before using the board view as a guide. TRACE does not edit the design, export an Altium project or run electrical or design-rule checks.

Schematics: SchDoc and project companions

The schematic reader handles the OLE FileHeader record stream and ASCII schematic exports. Connectivity is computed from the drawn geometry. Real-file validation covers 113 openly licensed SchDoc files; the checked LimeSDR nets agree with its Altium-written netlist (627 of 627).

Keep sibling .SchDoc files and the .PrjPcb project file together when they define project scope or hierarchy. Hierarchy, repeated sheets and scope 0 have synthetic tests only; real-file evidence covers flat designs. Repeated sheets are shown once.

Harnesses, design variants, off-sheet connectors and IEEE symbols are not modelled. Unknown scope values and skipped binary-flagged or Additional records are disclosed. The schematic view is useful for the supported circuits; complex projects need the original design tool for their complete semantics.

View the PCB beside the schematic

1. Download TRACE for Windows x64, Apple-silicon macOS or Linux x86-64. The Mac and Linux builds remain experimental.
2. Open the .PcbDoc with Ctrl+O (Cmd+O on a Mac), or drag it into the window.
3. Attach the matching .SchDoc through Documents, keeping companion sheets in the same directory.
4. Search for a part or net. Matching references let you cross-probe between the board and schematic; unresolved targets are reported instead of guessed.
5. Add datasheet or schematic PDFs and keep measurement notes on a part or pin. Search text PDFs directly, or run cancellable offline English OCR on a scanned PDF.

The getting started guide explains the common controls and document workflow. The demo shows that workflow with an openly licensed KiCad design in an earlier app version; it is not an Altium screenshot.

If the file is refused or something is missing

Compare the diagnostic and the import notice with the limits above. A library is not a board, a project file is a companion rather than a drawable PCB, and changing an extension does not convert the data.

For an unsupported PCB variant, ask the design owner for a GenCAD 1.4 export or use a compatible viewer. A plotted schematic PDF can be attached when its native schematic uses unsupported features; PDF links are based on exact text matches, not a reconstruction of the circuit.

For the maintained format scope, see the compatibility table and SUPPORT.md. Report reproducible import problems with the app version and diagnostic, using only files you may share.

Offline repair work without an account

TRACE is MIT-licensed open source. Files, OCR and notes are processed locally. The Altium readers are included on all three desktop platforms; support and payment verification are optional.

For other document families, read the KiCad guide, EAGLE guide or native Allegro guide.

Product names identify file formats and programs. They are trademarks of their owners; TRACE is not affiliated with them.