> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/brand/brand-standards/using-brand-assets.md).

# Using Brand Assets

How to pick the right logo file, and what you may never change.

## Start with the end use

Before making anything, decide where it will end up. Picking the right file makes sure the color is reproduced accurately.

{% tabs %}
{% tab title="On a screen → 01 Digital (RGB)" %}
Use the **RGB** files in `01 Digital` for anything viewed on a device: websites, slides, social media, apps, email.

* **SVG** — best for websites and apps; infinitely scalable.
* **PNG** — supports transparent backgrounds; larger files.
* **JPEG** — smaller files, but no transparency.

Printing RGB files can give blurry images and inaccurate colors.
{% endtab %}

{% tab title="Printed → 02 Print (CMYK / Pantone)" %}
Use the **CMYK** files in `02 Print` for most physical items: business cards, fliers, brochures, banners, shirts. Use **Pantone/spot** files for offset printing when a vendor asks for them.

* **PDF** — universal vector format; ideal for printing and sharing.
* **EPS** — older vector format some print shops still request.
* **AF (Affinity)** — the source design file; some print shops request it.

CMYK files are not for screen use.
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Only use image files (PNG, JPEG) when a vector file (SVG, PDF, EPS) can't be used.
{% endhint %}

## Color variations

Every asset comes in several color versions. Any of them can be used to suit the document, but **the full-color version comes first**.

## File structure

Download any file from the [Asset Library](https://docs.raidrobotics.org/brand/asset-library/asset-library.md), or the [complete logo package](https://docs.raidrobotics.org/brand/asset-library/asset-library.md#download-everything) as one zip. The original package follows this structure:

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-f0bc5328f88943c32d522318aa4c270df6dfb669%2Flogo-package-structure.png?alt=media" alt="RAID logo package folder structure: mark, end use, color variation, then file formats"><figcaption><p>Logo package file structure</p></figcaption></figure>

Lockups only come in single colors: black and white, plus gray for the horizontal lockup on screen. Both icons also have Outline versions, and the primary logo and both icons have Yellow Background Only versions for use on AI Yellow. The Asset Library's zips are sorted the same way, into Screen-RGB and Print-CMYK folders by colorway.

## Modifications

### Approved modifications

Only modified logos or icons that are **approved by leadership and put to a team vote** may be used in team communication of any kind.

### Unapproved modifications

Only use the approved, published files. Never modify them in any way, including:

* Distorting all or part of the file
* Using a logo with little or no contrast against the background
* Changing any of the colors
* Removing portions of the file
* Rotating or rearranging any portion of the file

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-d8739dab52bc7d4d3fb0cc7ea9003639d4fa1d70%2Funapproved-modifications.png?alt=media" alt="Examples of unapproved modifications: stretched, recolored, cropped and rotated logos and icons, crossed out in red" width="420"><figcaption><p>Unapproved modifications</p></figcaption></figure>


---

# 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://docs.raidrobotics.org/brand/brand-standards/using-brand-assets.md?ask=<question>&goal=<user_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.
