> 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/asset-packs/how-to-publish-an-asset-pack.md).

# How to publish an asset pack

Publishing puts an exported asset pack on the Sandbox Studio website. Create the zip first. Follow [How to create and export an asset pack](https://studio-docs.sandbox.game/asset-packs/how-to-create-and-export-an-asset-pack.md) if you do not have one yet.

## Step 1: Start the listing

On the Sandbox Studio website, sign in and open **Creator** → **My Projects**.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-482a6105b35510c3ed589507335cd9e3f5ca82d1%2Fasset-pack-my-projects.png?alt=media" alt="My Projects with a New Asset card"><figcaption><p><em>My Projects is where a new pack listing starts.</em></p></figcaption></figure>

Select **New Asset** for a new pack. To change one that is already listed, select **Edit** on its card.

The listing has four pages: **Basic Info**, **Images**, **Tags**, and **Publishing**. Set the project type to **Creator Asset**.

## Step 2: Upload the zip

On **Basic Info**, drag the zip into **Asset pack file**, or browse to it. The maximum size is 500 MB. The zip must contain a `config.json` with `id`, `name`, `version`, and `description`.

**Upload destination** names where the pack is sent. On this form that line reads `create.sandbox.game`.

**Asset details** fill in from the zip. Every field there is required.

| Field                 | What it is                                                                                                                       |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Asset Name**        | The pack name from the zip.                                                                                                      |
| **Slug**              | Taken from the zip. This is the id.                                                                                              |
| **Short Description** | The line under the name on marketplace cards. Edit it here if the sentence in `config.json` is not the one you want on the card. |
| **Full Description**  | The longer text on the pack's page.                                                                                              |

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-854451aed89f4dfa5ecac9d8dc8e9df8f13b4a64%2Fasset-pack-basic-info.png?alt=media" alt="Basic Info with the zip uploaded and asset details filled in"><figcaption><p><em>Creator Asset is selected. The zip is uploaded, and the name, slug, and descriptions come from that zip.</em></p></figcaption></figure>

{% hint style="info" %}
**Creator Asset** is the pack type. **Cosmetic** is marked **Coming soon** on this screen.
{% endhint %}

## Step 3: Add the images

Open **Images**.

**Main image** is required. It is the thumbnail on the card.

**Detail images** are optional, up to 8. They appear in the carousel on the pack's page.

Use a square JPG or PNG, at least 600×600, up to 4 MB. You can add or replace images later and save again.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-2209fcf09e91a0e2b61a57553686fba1f1ad73fa%2Fasset-pack-images.png?alt=media" alt="Images page with a main image and empty detail slots"><figcaption><p><em>The main image is required. Each detail slot is optional, up to eight.</em></p></figcaption></figure>

## Step 4: Add tags

Open **Tags** and add the search labels you want, such as `sci-fi`, `casual`, `solo`, or `pvp`.

## Step 5: Set the pack Live

Open **Publishing**.

| Choice          | What it means                  |
| --------------- | ------------------------------ |
| **Development** | Draft. The pack is not public. |
| **Live**        | Public. The pack is released.  |

Choose **Live**, then select **Save changes**. That save publishes the pack.

**Preview on Marketplace** opens the public page before you save.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-0aa05370e1c4549719211efca0304cae79447bb7%2Fasset-pack-publishing.png?alt=media" alt="Publishing page with Live selected"><figcaption><p><em>Development is a draft. Live is public. Save changes stores the choice.</em></p></figcaption></figure>

To change a pack that is already live, choose **Development**, make the edits, choose **Live** again, and save.

Back in Sandbox Studio, open the hamburger menu and choose **Asset Packs** → **Browse Asset Packs**. The pack should be in the list, with the image from the website on the card.

## What you've done

The pack is set to **Live** and shows up under **Browse Asset Packs**. To publish a game, follow [How to Publish](https://studio-docs.sandbox.game/publishing/how-to-publish.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 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/asset-packs/how-to-publish-an-asset-pack.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.
