[{"data":1,"prerenderedAt":67},["ShallowReactive",2],{"blog-odb-plus-plus-vs-gerber-ipc-2581-en":3},{"title":4,"description":5,"date":6,"lastUpdated":6,"category":7,"image":8,"imageAlt":9,"readingTime":10,"wordCount":11,"timeRequired":12,"htmlContent":13,"faq":14,"tags":30,"slug":36,"sourceLocale":37,"availableLocales":38,"jsonld":43},"ODB++ vs Gerber X2 vs IPC-2581: Which Files Should You Send?","Choose PCB manufacturing data by the receiver's supported versions, required fields and verified import results, then name the authoritative production files.","2026-11-12","design","/assets/blogs/odb-plus-plus-vs-gerber-ipc-2581/pcb-data-release-check-original.png","PCB data handoff: choose an agreed production master, check the receiver's import, and compare the result with the released design",10,1891,"PT10M","\u003Cp>Choose the PCB manufacturing format that your supplier can import and verify with the fields your order needs. Gerber X2 packages are widely used; ODB++ and IPC-2581 can carry structured fabrication and assembly information. None guarantees that an exporter included every field or that the receiver interpreted it correctly. Agree on one authoritative production master, its revision and the supporting requirements before release.\u003C/p>\n\u003Cp>The decision here is how to choose and validate a transfer between your EDA tool and a supplier. For a more detailed Gerber release checklist, including drill settings and CAM change control, see the \u003Ca href=\"/en/blog/gerber-data-preparation-pcb-manufacturing-quality/\">Gerber data preparation guide\u003C/a>.\u003C/p>\n\u003Cp>\u003Cimg src=\"/assets/blogs/odb-plus-plus-vs-gerber-ipc-2581/pcb-data-release-check-original.png\" alt=\"PCB data handoff: choose an agreed production master, check the receiver's import, and compare the result with the released design\">\u003C/p>\n\u003Ch2>1. What Can Each Format Represent?\u003C/h2>\n\u003Cp>Format support has three separate steps: the specification can represent a field, the EDA exporter must actually write it, and the receiving software must interpret it for the intended operation. Confirm all three for the versions and configuration used on the order.\u003C/p>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Information\u003C/th>\n\u003Cth>Gerber X2 package\u003C/th>\n\u003Cth>ODB++ design data\u003C/th>\n\u003Cth>IPC-2581 data\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Copper, mask, legend and paste\u003C/td>\n\u003Ctd>Layer images, normally separate files\u003C/td>\n\u003Ctd>Can include layer data in a structured design archive\u003C/td>\n\u003Ctd>Can include layer data in a structured design file\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Layer and feature function\u003C/td>\n\u003Ctd>File and aperture attributes when exported and read\u003C/td>\n\u003Ctd>Can include layer and feature information\u003C/td>\n\u003Ctd>Can include layer and feature information\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Drills and layer spans\u003C/td>\n\u003Ctd>Gerber drill data or separate NC drill files; confirm span identification and interpretation\u003C/td>\n\u003Ctd>Can include drill data and spans\u003C/td>\n\u003Ctd>Can include drill data and spans\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Connectivity\u003C/td>\n\u003Ctd>Net, pin and component attributes may be exported; agree on a separate test netlist when required\u003C/td>\n\u003Ctd>Can include connectivity; verify actual export and import\u003C/td>\n\u003Ctd>Can include connectivity; verify actual export and import\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Stackup\u003C/td>\n\u003Ctd>A separate Gerber Job file can describe a design stackup\u003C/td>\n\u003Ctd>Can include structured layer and stackup information\u003C/td>\n\u003Ctd>Can include structured layer and stackup information\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Component and assembly data\u003C/td>\n\u003Ctd>Gerber X3 can add component information; confirm placement and BOM requirements separately\u003C/td>\n\u003Ctd>Can include component and assembly data\u003C/td>\n\u003Ctd>Can include component and assembly data\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Fabrication and test requirements\u003C/td>\n\u003Ctd>Some general specifications may be represented; agree on authoritative requirements\u003C/td>\n\u003Ctd>Confirm what the export includes and what needs separate notes\u003C/td>\n\u003Ctd>Confirm what the export includes and what needs separate notes\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>The \u003Ca href=\"https://www.ucamco.com/files/downloads/file_en/554/gerber-layer-format-specification-revision-2026-05_en.pdf\">Ucamco Gerber specification\u003C/a> defines attributes including file function, aperture function, net name and component pin. Attributes are useful only when present and interpreted. They do not by themselves prove that the recipient has an independent, usable electrical-test netlist. Ask whether the test process requires an IPC-D-356 file or another agreed source.\u003C/p>\n\u003Cp>The \u003Ca href=\"https://www.ucamco.com/files/downloads/file_en/435/gerber-job-format-specification-revision-2020-08_en.pdf\">Gerber Job specification\u003C/a> describes a separate job file with general specifications and a design material stackup. It is not automatically present in every X2 package, and a design stackup is not automatically the fabricator&#39;s approved production construction. The \u003Ca href=\"https://www.ucamco.com/en/gerber/gerber-x3\">Gerber X3 overview\u003C/a> describes component information; do not assume it replaces the agreed procurement BOM or variant instructions.\u003C/p>\n\u003Cp>\u003Ca href=\"https://odbplusplus.com/design/why-odb-d/\">ODB++Design\u003C/a> uses a structured data model, commonly transferred as an archive containing a hierarchy of files. \u003Ca href=\"https://www.ipc2581.com/\">IPC-2581\u003C/a> describes its format as bidirectional. Neither statement establishes the content of a particular export, the receiver&#39;s version support or its handling of a returned DFM query. Agree on the actual exchange workflow with both tool and supplier teams.\u003C/p>\n\u003Ch2>2. Choose a Package the Receiver Can Use\u003C/h2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Situation\u003C/th>\n\u003Cth>Starting point\u003C/th>\n\u003Cth>Confirm before release\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>First fabrication order\u003C/td>\n\u003Ctd>Gerber X2 images, drill data, drawing and the test netlist requested by the supplier\u003C/td>\n\u003Ctd>Layer identification, drill units and spans, and attribute handling\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Several suppliers\u003C/td>\n\u003Ctd>A common agreed package each supplier can import\u003C/td>\n\u003Ctd>Versions, missing fields and whether the same master is used by each supplier\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>HDI with several drill spans\u003C/td>\n\u003Ctd>ODB++ or IPC-2581 if the supplier accepts and validates the export; otherwise an agreed Gerber and drill package\u003C/td>\n\u003Ctd>Each span, plated status, hole size, layer pair and construction\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Fabrication plus assembly\u003C/td>\n\u003Ctd>An agreed manufacturing package plus BOM, placement and assembly instructions as needed\u003C/td>\n\u003Ctd>Component references, positions, rotation, board side, variants and procurement BOM\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Long-term archive\u003C/td>\n\u003Ctd>Preserve the released native design, agreed production master and relevant drawings and requirements\u003C/td>\n\u003Ctd>Access to tools, revision, dependencies and the ability to reconstruct the released data\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>An ODB++ archive or IPC-2581 file may reduce the number of separate items to manage, but it can still contain incorrect or missing data and conflict with a separate drawing or BOM. Additional reference formats can help comparison; identify their purpose and do not let an unreviewed reference silently override the master.\u003C/p>\n\u003Ch2>3. Example: One 8-Layer HDI Release\u003C/h2>\n\u003Cp>Consider a hypothetical 1+6+1 board with eight copper layers, laser microvias from L1 to L2 and L8 to L7, buried vias from L2 to L7, and through vias. The release also calls for a 0.5 mm pitch BGA, controlled impedance and assembly. This is a document-planning example, not a tested supplier import.\u003C/p>\n\u003Cp>One possible Gerber-based package has 15 image files: eight copper, two mask, two legend, two paste and one profile. Four drill files separately identify the through, buried and two laser-via spans. That makes \u003Cstrong>19 image and drill files\u003C/strong>. If this example also includes one separate test netlist, one job file, one fabrication drawing, one placement file and one BOM, the total is \u003Cstrong>24 files\u003C/strong>. Another export may organize or omit these items differently; count the actual deliverables rather than treating 24 as a requirement.\u003C/p>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Transfer\u003C/th>\n\u003Cth>Example handoff\u003C/th>\n\u003Cth>Review at the receiver\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Gerber package\u003C/td>\n\u003Ctd>15 images, four drill files and the five supporting files above\u003C/td>\n\u003Ctd>Layer function, drill units and spans, test netlist, drawing, placement and BOM revisions\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>ODB++\u003C/td>\n\u003Ctd>One archive plus the drawing and any separately required BOM or other documents\u003C/td>\n\u003Ctd>Contents actually exported, layer mapping, hole spans, connectivity and assembly data\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>IPC-2581\u003C/td>\n\u003Ctd>One design data file plus the drawing and other documents as agreed\u003C/td>\n\u003Ctd>Supported revision, imported fields, hole spans, connectivity and assembly data\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>For example, both parties might see the same total number of holes while a buried-via span is mapped to the wrong layer pair. Compare holes by type and span, not just the total. Also compare finished-size requirements, plated status, outline and critical net-to-pin connectivity against the released design. A one-file or one-archive handoff does not make those checks unnecessary.\u003C/p>\n\u003Ch2>4. What Must Be Agreed Outside the File Format?\u003C/h2>\n\u003Cp>Specify the applicable requirements in the drawing, purchase order or other document that both parties recognize as authoritative. Where a file can carry a field, agree whether that field or another document controls in a conflict.\u003C/p>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Requirement\u003C/th>\n\u003Cth>Release decision\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Construction\u003C/td>\n\u003Ctd>Confirm layer order, finished thickness, material grades, copper and approved substitutions\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Holes and vias\u003C/td>\n\u003Ctd>State finished sizes, plated status, layer spans, tolerances and fill or cap requirements\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Controlled impedance\u003C/td>\n\u003Ctd>State target, tolerance, test structure and required report where applicable\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Quality and finish\u003C/td>\n\u003Ctd>Specify applicable standard and revision, acceptance class, finish and special process requirements\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Electrical test\u003C/td>\n\u003Ctd>Agree on the reference netlist, test scope and acceptance evidence\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Assembly\u003C/td>\n\u003Ctd>Agree on BOM revision, manufacturer part numbers, approved alternates, placement, polarity and variant rules\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Conflicting files\u003C/td>\n\u003Ctd>Name the production master and the process for resolving discrepancies\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>Do not assume a field in a data file settles a conflicting contractual requirement. When the drawing and data disagree, stop and raise an engineering query rather than choosing silently.\u003C/p>\n\u003Ch2>5. Validate the Export and Import\u003C/h2>\n\u003Col>\n\u003Cli>\u003Cstrong>Agree on the transfer.\u003C/strong> Ask the supplier which format, exporter version or IPC revision, and import workflow they support. Identify a contact for conversion warnings and engineering questions.\u003C/li>\n\u003Cli>\u003Cstrong>Inspect the export.\u003C/strong> Open the released package in a suitable independent viewer where available. Confirm all expected files or structured sections exist, the revision is correct, and the board outline and layers are recognizable.\u003C/li>\n\u003Cli>\u003Cstrong>Check drill data.\u003C/strong> Compare hole counts by type and span, units, coordinates, finished sizes and plating requirements against the design and drawing. A matching total alone is insufficient.\u003C/li>\n\u003Cli>\u003Cstrong>Check electrical and assembly data.\u003C/strong> Compare net-to-pin connections and intended test data. For assembly, compare reference designators, part numbers, position, rotation, side and variant against the approved BOM and placement source.\u003C/li>\n\u003Cli>\u003Cstrong>Review the receiver&#39;s result.\u003C/strong> Request an import report or other agreed data review. Unsupported fields may be rejected, ignored or mapped incompletely; resolve warnings and discrepancies before authorizing production.\u003C/li>\n\u003Cli>\u003Cstrong>Record the decision.\u003C/strong> Keep the exported package, revision, comparison results and closed queries with the release record. A clean viewer display alone is not proof of complete connectivity or manufacturing acceptance.\u003C/li>\n\u003C/ol>\n\u003Cp>If two representations are sent, state the governing source. For example: \u003Cem>“ODB++ archive Rev C is the production master; Gerber set Rev C is reference only. Stop and raise an engineering query if they disagree.”\u003C/em> Here Rev C is an illustrative \u003Cstrong>design revision\u003C/strong>, not a claim about the ODB++ format version.\u003C/p>\n\u003Ch2>6. Prepare the RFQ\u003C/h2>\n\u003Cp>Send the production files, drawing and stackup with quantities, material and finish requirements, critical features, test scope and requested records. For assembly, include the procurement BOM, placement data, variant and sourcing instructions; see the \u003Ca href=\"/en/blog/pick-and-place-file-checklist/\">pick-and-place checklist\u003C/a> and \u003Ca href=\"/en/blog/what-is-a-bom/\">BOM guide\u003C/a>.\u003C/p>\n\u003Cp>HILPCB&#39;s \u003Ca href=\"/en/products/hdi-pcb/\">HDI PCB\u003C/a> page requests Gerber X2 or ODB++ data, drill files and a target stackup for an HDI quote. Its \u003Ca href=\"/en/products/smt-assembly/\">SMT assembly service\u003C/a> requests Gerber or ODB++, BOM, placement and assembly information. Send the agreed package with a \u003Ca href=\"/en/quote/\">quote request\u003C/a>, and confirm the supported versions, required checks and deliverables for your specific order. The published service descriptions do not establish IPC-2581 import support for every order.\u003C/p>\n\u003Cdiv data-component=\"BlogQuickQuoteInline\">\u003C/div>\n\n\u003C!-- faq:start -->\n\u003Ch2>FAQ\u003C/h2>\n\u003Ch3>Is ODB++ better than Gerber?\u003C/h3>\n\u003Cp>It depends on the information needed and both parties&#39; tools. ODB++ can group structured design data in an archive, while Gerber packages are widely used. Validate the actual export and import before selecting the production master.\u003C/p>\n\u003Ch3>What is the difference between Gerber X2 and older Gerber image files?\u003C/h3>\n\u003Cp>X2 adds attributes that can identify file and feature functions and may carry net-related information. The exporter must write the attributes and the recipient must read them. A Gerber Job file is separate and is not automatically included.\u003C/p>\n\u003Ch3>Does IPC-2581 guarantee two-way DFM communication?\u003C/h3>\n\u003Cp>No. IPC-2581 is designed for bidirectional exchange, but the supported revision, fields and return workflow depend on the tools and the supplier&#39;s implementation. Agree and test the particular exchange.\u003C/p>\n\u003Ch3>Do I still need a fabrication drawing with ODB++ or IPC-2581?\u003C/h3>\n\u003Cp>Often yes. Confirm where the authoritative construction, tolerances, finish, acceptance and test requirements are stated and how conflicts will be resolved. A structured data file does not guarantee that all agreed requirements are present.\u003C/p>\n\u003Ch3>Can I send both Gerber and ODB++?\u003C/h3>\n\u003Cp>Yes, if the supplier agrees. Identify one as the production master, label the other as reference where appropriate, and compare the exported data and revisions. Resolve any discrepancies before release.\u003C/p>\n\u003C!-- faq:end -->\n\u003Csection class=\"related-links\" aria-label=\"Related\">\u003Ch3>Related links\u003C/h3>\u003Cul>\u003Cli>\u003Ca href=\"/en/blog/gerber-data-preparation-pcb-manufacturing-quality/\">Gerber Data Preparation for Reliable PCB Fabrication\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/pick-and-place-file-checklist/\">Pick-and-Place Files: CPL Fields, Rotation and BOM Matching Checks\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/blog/what-is-a-bom/\">What Is a BOM in Electronics Manufacturing? PCBA BOM Format, Sample Table, and Sourcing Rules\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/products/hdi-pcb/\">HDI PCB\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/products/smt-assembly/\">SMT assembly service\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/quote/\">quote request\u003C/a>\u003C/li>\u003C/ul>\u003C/section>",[15,18,21,24,27],{"question":16,"answer":17,"answerText":17},"Is ODB++ better than Gerber?","It depends on the information needed and both parties' tools. ODB++ can group structured design data in an archive, while Gerber packages are widely used. Validate the actual export and import before selecting the production master.",{"question":19,"answer":20,"answerText":20},"What is the difference between Gerber X2 and older Gerber image files?","X2 adds attributes that can identify file and feature functions and may carry net-related information. The exporter must write the attributes and the recipient must read them. A Gerber Job file is separate and is not automatically included.",{"question":22,"answer":23,"answerText":23},"Does IPC-2581 guarantee two-way DFM communication?","No. IPC-2581 is designed for bidirectional exchange, but the supported revision, fields and return workflow depend on the tools and the supplier's implementation. Agree and test the particular exchange.",{"question":25,"answer":26,"answerText":26},"Do I still need a fabrication drawing with ODB++ or IPC-2581?","Often yes. Confirm where the authoritative construction, tolerances, finish, acceptance and test requirements are stated and how conflicts will be resolved. A structured data file does not guarantee that all agreed requirements are present.",{"question":28,"answer":29,"answerText":29},"Can I send both Gerber and ODB++?","Yes, if the supplier agrees. Identify one as the production master, label the other as reference where appropriate, and compare the exported data and revisions. Resolve any discrepancies before release.",[31,32,33,34,35],"ODB++","Gerber X2","IPC-2581","PCB manufacturing data","CAM data","odb-plus-plus-vs-gerber-ipc-2581","en",[37,39,40,41,42],"de","cn","fr","ru",{"blog":44,"breadcrumb":53},{"@context":45,"@type":46,"headline":4,"description":5,"image":8,"url":47,"datePublished":6,"dateModified":6,"timeRequired":12,"keywords":48,"articleSection":7,"author":49,"publisher":52},"https://schema.org","BlogPosting","https://hilpcb.com/en/blog/odb-plus-plus-vs-gerber-ipc-2581/","ODB++, Gerber X2, IPC-2581, PCB manufacturing data, CAM data",{"@type":50,"name":51},"Organization","HILPCB",{"@type":50,"name":51},{"@context":45,"@type":54,"itemListElement":55},"BreadcrumbList",[56,61,65],{"@type":57,"position":58,"name":59,"item":60},"ListItem",1,"Home","https://hilpcb.com/",{"@type":57,"position":62,"name":63,"item":64},2,"Blog","https://hilpcb.com/en/blog/",{"@type":57,"position":66,"name":36,"item":47},3,1795278537522]