# Upload an ODB++ design

> What the ODB++ export needs to contain, and how to upload it in Probe — including pre-layout, dry run and comparison.

_Source: E-Sharp (esharp.se) · Probe guide_


Probe reads the neutral ODB++ export — the same file the design already produces for the board shop. You can also start before layout, with schematic, BOM and netlist.

## What the export should contain

ODB++ carries connectivity (netlist), component identity (reference designators, packages, pin mapping) and structure (stackup). Make sure the export includes:

1. **The netlist** — so signals can be followed through connectors, series components and planes.
2. **Component data** — reference designators and part numbers, so parts can be matched against datasheets and lifecycle.
3. **Stackup** — layer order and type, for reference-plane and return-path analysis.

Verified exporters: **Xpedition/PADS, Allegro, KiCad, Altium and OrCAD**. Other ODB++ exporters are supported on request.

## Before or after layout

A take becomes visible only once it's **complete**:

- **Before layout:** schematic + BOM + netlist — then connectivity and behaviour checks can run at schematic level already (see [review before layout](/en/probe/support/review-before-layout)).
- **After layout:** schematic + BOM + ODB++ — then the geometric checks are added (stackup, impedance, IR-drop, creepage).

An incomplete take (e.g. ODB++ without schematic/BOM) is hidden until what's missing arrives.

## Upload

1. Open Probe and choose **New design**.
2. Drag in the ODB++ archive (or schematic + BOM + netlist for a pre-layout design).
3. Probe reads in layers, components and nets. You see the number of layers, components and nets when the read is done.

## Preview and compare

- **Dry run** — read in and check an export without storing it, to see that it's parsed right before it becomes a take.
- **Comparison-only** — take in an export solely to compare against an existing take, without adding it to the design line (see [compare takes](/en/probe/support/compare-takes)).
- **Scripted upload** — for automated ingestion, a short-lived upload ticket is used against the API (see [API access and keys](/en/probe/support/api-access-and-keys)).

Design data stays in your own database and file volumes — nothing is sent to E-Sharp. Next step: [run your first review](/en/probe/support/run-your-first-review).
