> For the complete documentation index, see [llms.txt](https://docs.stargaze.zone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stargaze.zone/create/stargaze-studio/create-an-nft-collection/upload-assets-and-metadata.md).

# Upload Assets and Metadata

## Upload Options

{% hint style="info" %}
**Storage Note:** Creators are required to maintain their own storage for NFT links. There are numerous popular options including Pinata and Arweave. Creators are encouraged to compare options and think long term about which storage provider fits best for their long term goals.
{% endhint %}

There are two ways to provide your collection files to Stargaze Studio.

You can either

* Upload assets & metadata through Stargaze Studio by providing an API key from a storage provider
* Upload your files manually to an IPFS hosting provider, then launch the collection in studio using the base URI link for those files or folders

Either way, you must follow some naming rules:

{% hint style="info" %}
Asset and metadata names must be in numerical order starting from 1 and must only be consisted of numbers. Symbols or letters are not allowed.

**This rule also applies to the metadata (JSON) files.**

<mark style="color:green;">**Valid**</mark>

* 1.png
* 2.png

<mark style="color:red;">**Invalid**</mark>

* 1-punk.png
* 2-punk.png
  {% endhint %}

{% hint style="info" %}
You must upload a corresponding JSON file containing the metadata for each asset and the names of the asset and metadata files must match.

<mark style="color:green;">**Valid**</mark>

**images**

* 1.png

**metadata**

* 1.json

<mark style="color:red;">**Invalid**</mark>

**images**

* 1.png
* 2.png

**metadata**

* 1.json
  {% endhint %}

### 1) Upload Assets and Metadata using Stargaze Studio (Recommended)

First of all, to upload assets and metadata, an API key to store your collection must be provided. Stargaze Studio currently supports [**Pinata**](< https://www.pinata.cloud>) using an API key.

#### Obtain an API Key

The API key for your collecton may be attained on Pinata.

After you obtain the API key and your secret key, simply paste it and proceed to the asset selection part.\ <br>

<figure><img src="/files/LLoBuH8nhywm3K4AW61p" alt=""><figcaption></figcaption></figure>

#### Asset Selection

Now is the time to upload your assets, you can either upload using **Choose Files** button or simply by dragging and dropping to the asset selection area.

{% hint style="info" %}
**Supported asset formats are**

Image: JPG, PNG, SVG, and GIF.

Audio: MP3 and WAV.

Video: MP4.
{% endhint %}

<figure><img src="/files/m5icKZHPddooQ3IpzF3L" alt=""><figcaption></figcaption></figure>

#### Metadata Selection

After you upload the assets, a metadata selection box will appear as seen in the image above. There you can upload the metadata for your collection in JSON format.

Here is the example metadata file designed for the first token in the collection used in this guide:

```json
{
  "attributes": [
    {
      "trait_type": "hat",
      "value": "bandana"
    },
    {
      "trait_type": "glasses",
      "value": "sunglasses"
    },
    {
      "trait_type": "personality",
      "value": "chill"
    },
    {
      "trait_type": "shirt_color",
      "value": "purple"
    },
    {
      "display_type": "number",
      "trait_type": "generation",
      "value": 1
    }
  ],
  "description": "Just some guy that likes to code_1.",
  "external_url": "https://example.com/?token_id=1",
  "name": "Shane Stargaze"
}
```

{% hint style="info" %}
Notice that \*\*\*\* the **image** key value is missing, which is needed while uploading assets manually. However, Stargaze Studio handles it by using your API key and fills it automatically.
{% endhint %}

#### Update Metadata

Stargaze Studio lets you update the metadata through the interface. Simply click on one of your assets after uploading the metadata files.

<figure><img src="/files/Kz1bVXh1IiScgpdozZON" alt=""><figcaption></figcaption></figure>

A pop-up will appear and you'll be able doublecheck and update the metadata if needed.

<figure><img src="/files/bV63bFDKQBpFNW7i5ptt" alt=""><figcaption></figcaption></figure>

If you have successfully uploaded assets and metadata, you can skip the rest of this page.

### 2) Use an Existing Base URI

There are many storage providers where you can upload assets to IPFS and obstain a base URI link to use in Stargase Studio. Some options are [Pinata](< https://www.pinata.cloud>) and [Arweave](https://www.arweave.org/).

<figure><img src="/files/3ky1m9h8SCmT0OWOdcxa" alt=""><figcaption></figcaption></figure>

If you have already uploaded your assets and metadata to IPFS or you want to handle it manually, first make sure that the folder structure is as follows:

```markdown
Project Folder:
  - images
    - 1.png
    - 2.png
    - 3.png
  - metadata
    - 1.json
    - 2.json
    - 3.json
```

{% hint style="warning" %}
Providing a different folder structure for your NFT collection can cause unexpected behavior.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stargaze.zone/create/stargaze-studio/create-an-nft-collection/upload-assets-and-metadata.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.