> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/avatars/how-to-create-an-avatar-accessory.md).

# How to create an avatar accessory

An accessory is a 3D mesh on one socket. A hat uses the **Hat** socket. It follows that bone as one piece. It does not bend with the body.

Clothing textures are on [How to paint avatar clothing](https://studio-docs.sandbox.game/avatars/how-to-paint-avatar-clothing.md). The rigged character itself is on [How to create an avatar](https://studio-docs.sandbox.game/avatars/how-to-create-an-avatar.md).

## Open Create Accessory

Open the hamburger menu at the top left and choose **Avatar Studio...**. Choose **Create Accessory**. The name field is **Accessory Name**. Enter a name and select **Create**.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-1f7c1689c8a398be54085470ce9ad261e8f5bae4%2Favatar-studio-create-accessory.png?alt=media" alt="Avatar Studio window with Create Accessory selected and the name Hat_01"><figcaption><p><em>Create Accessory is selected. The name is Hat_01.</em></p></figcaption></figure>

The file is `.avatar-accessory.json`, under `assets/avatars/`. To reopen it, select it under **Open Recent**, or double-click it in the project.

### Step 1: Prepare the mesh

Build the mesh in Blender, Maya, or another 3D tool. Export one `.glb`, in metres, with all transforms applied. In Maya, freeze transformations. Put the origin where the accessory attaches. For a hat, that is the top of the head. Remove any Armature modifier. Use Sandbox Rigify to check the position against the socket before you import.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-0c4363b3dbf77b40630e96cb184caefaf55d2d62%2Favatar-studio-hat-blender.png?alt=media" alt="A cap in Blender with the Sandbox Rigify tools open"><figcaption><p><em>The hat in Blender, set up for the attachment point.</em></p></figcaption></figure>

### Step 2: Choose a preview avatar

On **Avatar**, choose a platform avatar or an avatar you made with **Create Avatar**. The preview is the only thing that uses this choice. On a player, the accessory hangs on the same socket of whichever avatar wears it.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-e33003b6f35447eb633cdb16e6dae946e7cc71d2%2Favatar-studio-accessory-avatar.png?alt=media" alt="Accessory Avatar step with a platform avatar selected"><figcaption><p><em>A platform avatar is selected for the preview.</em></p></figcaption></figure>

### Step 3: Import the mesh and pick the socket

Open **Import**. Drop the `.glb` and choose the socket. **Hat** is the default. The list shows the sockets that avatar has.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-0ccc530f50fd15875d12e2efe4d6c41af4bf56c2%2Favatar-studio-accessory-import-file.png?alt=media" alt="Import step with the file dialog open over the drop zone"><figcaption><p><em>The drop zone takes one .glb.</em></p></figcaption></figure>

The checks cover the mesh, whether it is rigid, its size, how far it sits from the socket, whether the avatar has that socket, and the triangle count. A missing mesh or a skinned mesh blocks the export. Anything else is reported, and each problem tells you how to fix it.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-8b3c76fecb132324f360371e05a3e74d42a6d20e%2Favatar-studio-accessory-import-checks.png?alt=media" alt="Import checks passed with the hat on the avatar"><figcaption><p><em>The hat is on the head. The checks have passed, and the socket is Hat.</em></p></figcaption></figure>

### Step 4: Place it on the socket

**Adjust** is optional. Move, rotate, and scale the accessory with the gizmo, or type the position, rotation, and scale. The avatar holds its rest pose while this step is open.

**Reset to the Imported Origin** puts it back where the `.glb` had it.

A new `.glb` dropped on **Import** keeps the placement you set here. Use **Reset** on **Import** when the new file is a different accessory.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-9d85b69204fbc7dd784be3091b6711f9fd23c2d9%2Favatar-studio-accessory-adjust.png?alt=media" alt="Adjust step with the hat selected and move, rotate, and scale fields"><figcaption><p><em>The hat is selected on the head. Move, Rotate, and Scale are on the right.</em></p></figcaption></figure>

### Step 5: Export the accessory

Open **Export**. Name the accessory, and select **Export Accessory...**. The placement you set in **Adjust** is written into the `.glb`.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-786427aedcfb44cec7817a4a14dfb22d23305370%2Favatar-studio-accessory-export.png?alt=media" alt="Export step with the accessory named and the hat placed on the avatar"><figcaption><p><em>Export is open. The hat sits where Adjust left it.</em></p></figcaption></figure>

You get a folder with an item pack recipe and the `.glb`.

## What you've done

The accessory is exported. Reopen it from **Open Recent**, or from `assets/avatars/` in the project.


---

# 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://studio-docs.sandbox.game/avatars/how-to-create-an-avatar-accessory.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.
