Someone who finds your board on a project page usually wants one thing: to order a few. Whether they can do that in five minutes depends on which fabrication files you put in the release. Board houses have accepted roughly the same core set for decades, and two newer formats now sit next to it.
What are Gerber files?
Gerber files are a set of vector image files, one per board layer, that tell the fabricator where copper, solder mask, silkscreen and the board outline go.
The format is maintained by Ucamco, which publishes the specification for free. A typical two-layer board produces files for top and bottom copper, top and bottom solder mask, top and bottom silkscreen, top and bottom paste (for stencils) and the outline.
There are two generations still in use. Extended Gerber, often called RS-274X or X1, describes the shapes only. Gerber X2 adds attributes: each file can state which layer it is, and pads and tracks can carry their function. That means fewer mistakes when a fab has to guess whether board-B_Mask.gbr is the bottom solder mask. A later revision, X3, can also carry component information for assembly.
If your tool offers X2, use it. Fabricators that don't read the attributes simply ignore them.
Where does the drill data go?
Drill holes are normally exported as Excellon files that sit next to the Gerbers in the same ZIP.
Excellon is an older numerical-control format for drilling machines. Most EDA tools export plated and non-plated holes either in one file or two. Exporting them separately makes the fab's job slightly clearer, especially when your board has mounting holes that must stay unplated.
Gerber can also describe drill data, and some workflows use that. Excellon is still the most common choice in hobby and small-batch ordering.
What are ODB++ and IPC-2581?
ODB++ and IPC-2581 are single structured datasets that describe the whole board, including layers, stackup, drills, nets and components, instead of a loose set of image files.
| Format | Who maintains it | What it contains | Accepted by |
|---|---|---|---|
| Gerber + Excellon | Ucamco (Gerber); Excellon is a de facto standard | One file per layer, plus drill files | Nearly every PCB fab |
| ODB++ | Originated at Valor, now part of Siemens | Layers, drills, netlist, components, stackup | Many larger fabs and assembly houses |
| IPC-2581 | IPC, with an industry consortium | Layers, drills, netlist, BOM, stackup in one XML file | Growing number of fabs and assemblers |
Because these formats carry the netlist and stackup, a fabricator can check the board against the intended connections and build it with fewer questions. Assembly houses like having components and the board in one place.
Recent KiCad versions can export IPC-2581 and ODB++, as can most commercial tools. If yours can, adding one of them to the release costs a minute.
Which files should an open hardware release include?
Include a ZIP of Gerber X2 plus drill files, a PDF schematic, a BOM and a pick-and-place file, and optionally an IPC-2581 or ODB++ export.
gerbers.zip: all copper, mask, silkscreen, paste and outline layers, plus drill files.schematic.pdf: every sheet, so people can read the circuit without software.bom.csv: references, values, footprints and manufacturer part numbers.positions.csv: the pick-and-place file, if you want assembled boards to be possible.- Optional:
board.xml(IPC-2581) or an ODB++ archive. - A short
FABRICATION.mdwith board thickness, copper weight, finish, minimum drill and any special requests.
Name the ZIP with the revision, such as sensor-board-r1.2-gerbers.zip, and use the same revision string on the silkscreen. The release checklist for hardware repositories explains why that matching matters when someone reports a problem.
Do fabrication files count as the source?
No, fabrication files are outputs, and an open hardware release still needs the editable design files.
This is the point where releases most often fall short of the Open Source Hardware Definition. A ZIP of Gerbers lets someone clone your board exactly, but it is hard to modify. Moving a connector means redrawing copper by hand.
The definition asks for the design in the preferred format for making changes. For a PCB, that is the native project from KiCad or whichever tool you used, plus libraries. Our guide on what open-source hardware is walks through that requirement and the cases that look open but don't qualify.
How do you check the files before publishing?
Open the exported files in a separate Gerber viewer and compare them with the board, layer by layer.
A viewer catches problems your EDA tool will not show you: a missing outline layer, silkscreen over pads, a paste layer that was never exported, or drill files in the wrong units. KiCad ships with its own Gerber viewer, and many fabs show a preview after upload. Use both if you can.
Check that the drill holes line up with the pads. Misaligned drills usually mean the drill file used a different origin or unit than the Gerbers.
Once the files look right, attach them to a tagged release. If you haven't chosen a license for the design yet, the license chooser is a quick place to start.
FAQ
Are Gerber files enough to count as open source hardware?
No. Gerbers are manufacturing outputs. The Open Source Hardware Definition asks for design files in the preferred format for making modifications, which for a PCB means the native schematic and layout files from your EDA tool.
What is the difference between Gerber X1 and X2?
Both describe the image of each layer. X2 adds attributes inside the files, such as which layer a file represents and what a pad is for, so fewer details depend on file names and separate notes.
Do I need to publish ODB++ or IPC-2581?
No. They help some fabricators and assembly houses, and they cost nothing to add if your tool exports them, but Gerber plus drill files remain the widely accepted baseline.
Should I publish a PDF of the schematic too?
Yes. A PDF lets people read the circuit in a browser without installing any EDA software, and it is often the first file someone opens when debugging a board.