> 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-create-and-export-an-asset-pack.md).

# How to create and export an asset pack

An asset pack is a zip of models, materials, and textures. You build it in Sandbox Studio, then export the zip. Publishing that zip is covered in [How to publish an asset pack](https://studio-docs.sandbox.game/asset-packs/how-to-publish-an-asset-pack.md).

Open the project that contains the files you want to pack.

## Step 1: Open New Asset Pack

Open the hamburger menu at the top left, then choose **Asset Packs** → **New Asset Pack...**

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-aafd92ee225153534960cd620d89c8ceaa120204%2Fasset-pack-menu.png?alt=media" alt="Asset Packs menu with New Asset Pack selected"><figcaption><p><em>Asset Packs holds New Asset Pack, Export Asset Pack, and Browse Asset Packs.</em></p></figcaption></figure>

## Step 2: Enter the pack details

Fill in **New Asset Pack**. The editor creates the pack under `packs/` in the open project, next to that project's own `assets/` folder.

| Field                  | What to enter                                                                                                                                                        |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**               | A short name such as `my-asset-pack`. Use lowercase letters, digits, and hyphens.                                                                                    |
| **Id (registry key)**  | The same as the name. This id stays the same if you rename the folder later.                                                                                         |
| **Description**        | One sentence about the pack. This field is required. The website uses it as the short description on the marketplace card. You can change it later in `config.json`. |
| **Version**            | Leave `1.0.0`.                                                                                                                                                       |
| **Min Engine Version** | Leave `0.0.0`, unless the pack needs a newer engine.                                                                                                                 |
| **Author**             | Optional.                                                                                                                                                            |
| **License**            | Leave **MIT**, unless you need another template or **Custom**.                                                                                                       |

Leave both boxes checked: **Scaffold assets/ folder** and **Scaffold src/ folder**.

Select **Create**.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-b5ed36b17363006420f7e74b84b3369369882817%2Fasset-pack-new.png?alt=media" alt="New Asset Pack dialog with name, id, description, version, and license"><figcaption><p><em>Name and id match. Description is required. Both scaffold boxes are checked.</em></p></figcaption></figure>

The new folder is `packs/<your-pack-name>/`. It contains `config.json`, `LICENSE`, an empty `assets/` folder, and `src/`.

## Step 3: Add the files

Put files in `packs/<your-pack-name>/assets/`, with one folder per type. Models go in `models/`, materials in `materials/`, and textures in `textures/`. Add a folder only when you have that kind of file. A pack can be models only.

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-b96453dcf2e16a720557f065af5240ebf8e8c880%2Fasset-pack-folders.png?alt=media" alt="Pack assets folder containing materials, models, and textures"><figcaption><p><em>The pack's assets folder, with materials, models, and textures each in their own folder.</em></p></figcaption></figure>

```
packs/your-pack-name/assets/
  materials/
  models/
  textures/
```

Files left in the project's own `assets/` folder are not part of the pack.

## Step 4: Export the zip

Open the hamburger menu, then choose **Asset Packs** → **Export Asset Pack...**

| Field                    | What to do                                                                                                                                                                                                        |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pack**                 | Choose your pack. A project can hold more than one. The line under the menu is the description from `config.json`.                                                                                                |
| **Version Bump**         | For a first export, leave it unchanged. **Preview** is the version written into the zip. If that version is already published and you are shipping a change, choose **Patch (x.y.Z)** so `1.0.0` becomes `1.0.1`. |
| **Output Folder**        | Leave the default, or pick another folder. The zip is named `<your-pack-name>.zip`.                                                                                                                               |
| **Skip isolation check** | Leave this off.                                                                                                                                                                                                   |

<figure><img src="https://2877193296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgFjStdWWXj1Wc6xnrcJ%2Fuploads%2Fgit-blob-151fff7659ca0743f73d345034bf2aa7dcd2d861%2Fasset-pack-export.png?alt=media" alt="Export Asset Pack dialog with a patch bump and the output folder"><figcaption><p><em>Preview shows the version that will be written. In this export, Patch moves 1.0.1 to 1.0.2.</em></p></figcaption></figure>

Select **Export**. Sandbox Studio shows **Exporting asset pack…** while it runs.

The isolation check confirms the pack does not point at files outside itself. If the check fails, no zip is written. Move those files into `packs/<your-pack-name>/assets/` and export again.

Before you upload, open the zip. `config.json`, `LICENSE`, and `assets/` sit at the top level. They should not be wrapped in an extra folder named after the pack.

## What you've done

The pack folder is in the project and the zip is written to the output folder. Upload that zip in [How to publish an asset pack](https://studio-docs.sandbox.game/asset-packs/how-to-publish-an-asset-pack.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-create-and-export-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.
