> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/guidelines-compatibility/guidelines/workflows/adding-sprites.md).

# Adding Sprites

### Description​ <a href="#description" id="description"></a>

The GMetri file manager allows you the ability to add sprites to use in a GMetri experience. This tutorial will go over how to create a sprite with the correct format.

### Steps to create a sprite file​ <a href="#steps-to-create-a-sprite-file" id="steps-to-create-a-sprite-file"></a>

The GMetri file manager handles sprite as a `.zip` file. To create your own sprite file, follow the following steps.

1. All the sprite frames need to be named in sequence. You could number them as `01.jpg`, `02.jpg` and so on, or alternatively you could label them as `a.jpg`, `b.jpg` similarly.
2. Create an empty text file titled `sprite.txt`.
3. Compress the above mentioned files as a `.zip` file.
4. You have successfully created a sprite file. This file can be uploaded to the GMetri file manager and can now be used in any GMetri experience as you please.

{% hint style="warning" %}
Please ensure that an empty text file named `sprite.txt` is present in your zip file. This is so that the file manager can identify that the zip file is meant to be used as a sprite. If this step is missed, when trying to use the file as a sprite, the file manager will display the file as not supported.
{% endhint %}


---

# 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.gmetri.com/guidelines-compatibility/guidelines/workflows/adding-sprites.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.