# Custom JSON

🚀 Custom Metadata Quick Start

### 1️⃣ Prepare Your Files

You need TWO sets of files:

* **Images**: `1.png`, `2.png`, `3.png`... (your NFT artwork)
* **JSON**: `1.json`, `2.json`, `3.json`... (your metadata)

**Important**: The numbers must match! First JSON goes with first image.

### 2️⃣ JSON Structure (Minimum Required)

```json
{
  "name": "Your NFT Name #1",
  "description": "Your NFT description",
  "image": ""
}
```

That's it! Toast will handle the image URL automatically.

### 3️⃣ Adding Traits (Optional)

Want traits? Add an `attributes` array:

```json
{
  "name": "Toast Warrior #1",
  "description": "A brave warrior",
  "image": "",
  "attributes": [
    {
      "trait_type": "Class",
      "value": "Warrior"
    },
    {
      "trait_type": "Level",
      "value": "50"
    }
  ]
}
```

### 4️⃣ Upload Process

1. Go to the Create page
2. Upload your **images** first
3. Toggle **"Use Custom Metadata"** to ON
4. Upload your **JSON files**
5. Launch! 🚀

### ✅ Checklist

* [x] Same number of images and JSON files
* [x] Files numbered correctly (1, 2, 3...)
* [x] Each JSON has `name` and `description`
* [x] Leave `image` field empty or with placeholder
* [x] Valid JSON format (check with [JSONLint](https://jsonlint.com/))

### 🆘 Common Fixes

#### Error: "Number of images and metadata files must match"

→ Count your files. You need exactly the same amount.

#### Error: Invalid JSON

→ Missing comma, quote, or bracket. Use [JSONLint](https://jsonlint.com/) to validate.

#### Traits not showing on marketplaces

→ Use `attributes` array with `trait_type` and `value` keys.

#### JSON uploader not accepting collection metadata.

→ Use the UI for all collection metadata, only upload JSONs for your actual assets.

### 💡 Pro Tip

Start with 3-5 NFTs as a test. Once it works, scale up to your full collection!

***

Reach out via our [telegram ](https://t.me/toastfunsol)for additional guidance.


---

# Agent Instructions: 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:

```
GET https://docs.toast.fun/custom-json.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.