ODB++ or Gerber for review
Gerber is an excellent manufacturing format and a poor review format. The question is which format answers what you're actually asking.
Gerber has served manufacturing for half a century and does that job well. The problems begin when Gerber is reused for design review — something it was never built for. The question isn’t which format is “best”, but which answers what you’re asking.
What Gerber contains
Gerber is essentially a set of 2D images, one per layer (copper, solder mask, text), plus a drill file. It gives the shop exact geometry: copper placement, widths and holes. That precision makes it the right format for a CAM engineer about to build the board.
What Gerber doesn’t contain
No netlist — connected pads are just shapes, and nothing marks them as a signal. No component identity — no reference designators, part numbers or pin functions. No structure — no stackup meaning, hierarchy or link between pads and devices. Modern Gerber X2/X3 can carry some netlist and component attributes, but that’s optional, often stripped at export, and still image-first.
What ODB++ adds
ODB++ is a database rather than a drawing. It carries the same geometry and drill data as Gerber, plus connectivity that’s built in — signals can be followed through connectors, series components and planes. The component intelligence comes with it: reference designators, packages and pin mapping. And the structure is there: stackup, hierarchy and relationships between pads, nets and components.
Why the reviewer cares
Review questions are about connectivity and function: where a signal lands, what loads a supply, which inputs are unconnected, whether a pull-up sits on the right net. They depend on nets and components — which Gerber doesn’t hold. From Gerber, a reviewer can mostly check that the copper looks sound. From ODB++, they can ask the design itself.
Three concrete cases. Follow a net: a reset line past its series resistor — ODB++ lets you follow it; in Gerber you trace touching shapes visually across layers. Identify a component: is the part the 1.8 V regulator? ODB++ names it; Gerber shows a footprint and lets you guess from the text. Check a supply: confirming a supply pin reaches a real supply needs pin function and net data together, which Gerber lacks.
When Gerber is enough — and when ODB++ is needed
Gerber is the right tool when the question is manufacturing rather than design intent: releasing a proven board to the shop, CAM panelisation, a quick visual check that the copper is right. ODB++ is needed when the question shifts from “can it be built?” to “is it the design we meant?” — functional correctness, connectivity and parts run within their limits. ODB++ is also neutral: a coherent model anyone can open, whatever CAD drew the board. It carries review across a mixed toolchain and with EMS partners (review without a CAD licence).
How Probe uses ODB++
Probe reviews ODB++ files already exported for manufacturing — or a schematic and a BOM before the layout exists. It reads connectivity and components, not just shapes, so reviewers can follow nets, see component function and search the board. The findings carry their evidence and come along to later revisions. No CAD seat required.
Gerber is the right format for manufacturing and should stay there. The mistake is using it for review. Bring your own ODB++ file and we’ll run a review live.