> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/badge-printing/custom-badge/badge-design-guidelines.md).

# Badge Design Guidelines

Once you know your badge type and dimensions, you can start designing. Follow the guidelines below:

We always recommend using our design templates as a starting point. The templates are already set up with the correct dimensions and layout and can be found and downloaded at the bottom of this page.

{% hint style="warning" %}
**Important Requirements**

* Save your design in **PNG** format.
* Use the **RGB colour space** to ensure accurate colour replication when printing.
* Do not include crop marks, trim lines, or any other layout markings in final submited design.
  {% endhint %}

#### **Layout and Design Guidelines**

**Folded badges (T180, T180S, 260T, 260TS)** The badge folds in the centre, so your design must cover both halves as a mirrored layout. See the example images at the bottom of this page for guidance.

**Sticker badges** Sticker badges do not fold. Your design covers the full sticker area as a single flat layout.

**Ink coverage** Full ink coverage across the entire badge can cause visible streaking during printing and slows down drying time, increasing the risk of ink spots. Where possible, avoid solid colour across the full badge area.

**Thin lines** Lines under 2 pixels may not be picked up during printing. Use thicker lines where needed.

**Edges** Keep all important elements away from the edges of your design. Anything placed too close to the edge risks being cut off during production.

**Font files** We will need the **.TTF (TrueType Font)** files when submitting the badge design. \
\&#xNAN;*(Also include bold/italic TTF files if used in the design.)*

### Prepare Two Versions of Your Design

You must submit two versions of your badge designs:

**Version 1 with Variables** This version shows where attendee information will be printed. Include clearly labelled placeholders e.g.

* *First name*
* *Last name*
* *Company name*
* *Company role*
* *QR code (if applicable)*
* *Tags (if applicable)*<br>

**Version 2  Background only (without variables)** This is the fixed background design where all variable elements are removed. e.g. no names, company name, company role or QR codes.

<figure><img src="/files/no7ofRTNVKsYgsOw5mBM" alt=""><figcaption><p>Badge versions with and without variables</p></figcaption></figure>

#### **Downloadable Design Templates**

{% tabs %}
{% tab title="T180" %}
{% file src="/files/iRWMJdOJ3dTNgJsGvY0i" %}

{% file src="/files/NlqVVwHEG7Nyq3Q0aE7h" %}
{% endtab %}

{% tab title="T180S" %}
{% file src="/files/LO3fNBQIMke6HLL5LMRy" %}

{% file src="/files/CUh99nanFeJ7UszAmWJr" %}
{% endtab %}

{% tab title="260T" %}
{% file src="/files/sSsNeftFDwZYRFFve05E" %}

{% file src="/files/8kvNj57CYVAk14aGdPNB" %}
{% endtab %}

{% tab title="260TS" %}
{% file src="/files/ojN0Y8Q9zBs72S2dUWus" %}

{% file src="/files/m7BRRioofNf4oic85fO4" %}
{% endtab %}
{% endtabs %}

#### **Ready to Submit?**

Once your design is complete and both versions are ready, head over to the submission page.

👉 [Submit your badge design](/badge-printing/custom-badge/submitting-your-badge-design.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge-base.letsgetdigital.com/badge-printing/custom-badge/badge-design-guidelines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.