Ask a fab what files they want and the answer, in most of the world, is Gerber. But there is another name in the conversation — IPC-2581 — and the two represent genuinely different philosophies of how to describe a printed circuit board to the people who will manufacture it. Gerber X2 describes the board as a set of layer images, one file per layer, enriched with attributes that say what each layer and object is. IPC-2581 describes the board as a single XML document that aims to carry the whole manufacturing intent: layers, stackup, components and more in one structured file. This article explains the two models at a practical level, why fabs ask for what they ask for, and what it means for checking your files in Gerbv. For the Gerber side in depth, see RS-274X vs Gerber X2 and what is a Gerber file. The viewers on the Gerber side of this comparison are gathered in the best free Gerber viewers roundup.
The Gerber model: images plus attributes
A Gerber package is a folder, not a document. Each file is a complete, self-contained image of one layer — top copper, bottom copper, mask, legend, paste, outline — drawn with apertures, and the drill data rides alongside as a separate Excellon file. Gerber X2’s contribution to this model is the attribute system: inside each file, structured metadata records the layer’s function and can attach part and net information to the objects drawn. But the model stays plural and image-first. The board is the sum of its layers, and anything the layers do not say — the stackup order and materials, the finish, the assembly data — travels in other documents: a fabrication drawing, a readme, a BOM, a pick-and-place file.
The IPC-2581 model: one XML, whole intent
IPC-2581 starts from the opposite end. It is a single XML file built on an industry standard, designed so that the one document can describe the board comprehensively: the layer images, the stackup that orders and specifies them, the components and bill of materials, and the assembly and test intent alongside fabrication. Where Gerber says “here are the pictures, with labels”, IPC-2581 says “here is the board, described”. The appeal is structural: nothing essential has to live in a side document that can be forgotten, version-skewed or misread, because the format has a place for it inside the file itself.
Why most fabs still ask for Gerber
If one format carries more, why does the industry default remain Gerber? The honest answer is ecosystem, not merit in the abstract. Gerber has decades of installed tooling behind it: every CAD package exports it, every fab imports it, every viewer — including Gerbv — reads it, and every engineer’s checking habits are built around it. A fab’s request is really a statement about its own pipeline: send the format our import, quoting and CAM preparation are proven on. Some fabs accept IPC-2581 as well, and if yours does and your CAD tool exports it well, using it is a legitimate choice. But “supported somewhere” is not “accepted everywhere”, and the safe universal deliverable remains a checked Gerber set. Always follow your specific fab’s stated preference over any general argument — including this one.
What this means for checking your files
Your verification routine follows the model of the files you actually send. Send Gerber, and the check is the familiar one: open the set in Gerbv (from the download page), stack the layers, confirm the drills register, measure the outline, read the aperture and drill statistics — the flow on the Gerber viewer hub and in the pre-order checklist. Gerbv views Gerber RS-274X (including X2 files, whose images it renders) plus Excellon and CSV data; it does not read IPC-2581, because it is a Gerber viewer and the XML model is a different country. If you send both formats to a fab that accepts both, check both — the Gerber pass in a viewer, and the IPC-2581 export by whatever tooling your flow provides — because a correct Gerber set says nothing about a stale XML export sitting beside it.
The practical bottom line
Think of the choice as images-with-labels versus a single structured description, and of your fab’s intake desk as the referee. Gerber X2 is the lingua franca: universally exportable, universally importable, and checkable in free tools on any desktop. IPC-2581 is the more ambitious container, available where the toolchain at both ends supports it. For most readers, most weeks, the winning move is unglamorous: export clean Gerber X2, name the files clearly, include the stackup and finish in your order notes, and verify the exact set in a viewer before it leaves your machine.
Frequently asked questions
Is IPC-2581 better than Gerber X2?
They are different models rather than a ranking. IPC-2581 carries more of the board’s intent — stackup, components, BOM — in one XML file. Gerber X2 is layer images plus attributes, and wins on universality: every CAD tool exports it and every fab accepts it. Your fab’s preference decides.
Can Gerbv open IPC-2581 files?
No. Gerbv is a Gerber viewer: it reads Gerber RS-274X files (including Gerber X2, whose layer images it renders), Excellon drill files and CSV pick-and-place files. IPC-2581’s single-XML model needs tooling built for that format.
If my fab accepts both, which should I send?
Send the one your own workflow can verify best, and check exactly what you send. Many engineers send the Gerber set they have inspected layer by layer in a viewer, since that verification habit is proven; if you send IPC-2581, verify that export through its own tooling.