> For the complete documentation index, see [llms.txt](https://easycatalog.nousmedis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://easycatalog.nousmedis.com/setting-up-your-data/field-options/available-field-options/the-format-pane/barcode.md).
# Barcode
EasyCatalog includes support for all major barcode types.
The **Barcode** field allows a quick and convenient way to create many types of barcodes into an image frame from a field.
Field Options > Format pane > Barcode dialog box
### List of supported Barcodes
* EAN5
* EAN8
* EAN13
* EAN14
* Code 39
* Code 128
* GS1-128
* UPCA
* I2Of5
* Data Matrix
* [QR Code](/setting-up-your-data/field-options/available-field-options/the-format-pane/qr-code.md)
The following QR code types are supported:
* Text
* URL
The following QR codes can also be inserted, but a custom field needs to be created first in order to collect the necessary data:
* Business/vCard
* SMS
* Email
### Barcode color
Choose a color from the list. EasyCatalog will display all color swatches defined in your document.
### Output human-readable text
Enable this option to display the barcode text beneath the graphic. Then, select a paragraph style from the `Paragraph Style` dropdown menu.
### Inserting barcodes
To insert a field as a barcode:
1. Edit the field’s Field Options using the *Field Options* menu from the data panel’s pop-out menu
2. On the “*Format*” pane, change the field’s type to be “*Barcode*“
3. Select the barcode type from the *Barcode Type* pop-up.
The field will now be treated in the same way as an image field, so to insert the barcode insert the field into an image box or assign a `Field Specifier` for this field to an image box.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://easycatalog.nousmedis.com/setting-up-your-data/field-options/available-field-options/the-format-pane/barcode.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
