Gerber vs ODB++
A practical comparison of Gerber RS-274X and ODB++ as PCB manufacturing data formats, and when to use each for CAM.
The format you hand a fabricator shapes how much can go wrong before the board is built. The two dominant options are Gerber and ODB++. They solve the same problem — describing a board for manufacture — very differently.
Gerber RS-274X
Gerber is an image format. Each layer is a separate file describing draws and flashes with embedded aperture definitions. It is universal, human-inspectable, and supported everywhere, but it is just imagery — it carries no inherent knowledge of nets, components, or stackup. Drill data and netlist travel as separate files, so consistency depends on the person assembling the package.
ODB++
ODB++ is an intelligent, hierarchical database. A single structure holds copper, mask, drill, netlist, stackup, and component data with the relationships between them intact. That richness means fewer ambiguities in CAM and fewer round-trips.
Side by side
| Aspect | Gerber RS-274X | ODB++ |
|---|---|---|
| Data model | Per-layer images | Single intelligent DB |
| Netlist | Separate (IPC-D-356) | Embedded |
| Stackup | External note | Embedded |
| Components | None | Included |
| Ubiquity | Universal | Very wide |
| Ambiguity risk | Higher | Lower |
Which to use
For simple boards or maximum compatibility, Gerber plus a separate drill and IPC-D-356 netlist is perfectly workable. For dense, high-layer-count, or controlled-impedance designs, ODB++ removes whole classes of error by keeping intent and geometry together.
Whichever you choose, include the stackup and fabrication notes so CAM has full build intent, not just images.
Related terms
Have a board that fits this chapter?
Send us the design and constraints — an engineer returns first-pass DFM findings, usually within hours.