Filename extension |
.gbr |
---|---|
Internet media type |
application/vnd.gerber |
Uniform Type Identifier (UTI) | com.ucamco.gerber.image |
Developed by | Ucamco |
Initial release | 27 August 1980 |
Latest release | Revision 2023.08 30 August 2023 |
Type of format | Image file format |
Standard | Gerber Format Specification |
Website | https://www.ucamco.com/en/gerber |
The Gerber format is an open, ASCII, vector format for printed circuit board (PCB) designs.[1] It is the de facto standard used by PCB industry software to describe the printed circuit board images: copper layers, solder mask, legend, drill data, etc.[2][3][4]
The standard file extension is .GBR
or .gbr
[1] though other extensions like .GB
, .geb
or .gerber
are also used. It is documented by The Gerber Layer Format Specification and some related (but less universally supported) extensions such as XNC drill files and GerberJob to convey information about the entire PCB, as opposed to single layers.
Gerber is used in PCB fabrication data.[5] PCBs are designed on a specialized electronic design automation (EDA) or a computer-aided design (CAD) system.[6] The CAD systems output PCB fabrication data to allow fabrication of the board. This data typically contains a Gerber file for each image layer (copper layers, solder mask, legend or silk...). Gerber is also the standard image input format for all bare board fabrication equipment needing image data, such as photoplotters, legend printers, direct imagers or automated optical inspection (AOI) machines and for viewing reference images in different departments. For assembly the fabrication data contains the solder paste layers and the central locations of components to create the stencil and place and bond the components.[7]
There are two major generations of Gerber format:
The official website contains the specification,[12] test files, notes and the Reference Gerber Viewer[13] to support users and especially developers of Gerber software.[1]
X2 FAQ
was invoked but never defined (see the help page).rev I1
was invoked but never defined (see the help page).