> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/nfts/20-public-mint-setup.md).

# 20. Launch a public NFT mint

Upload a collection set, define price and limits, and recover interrupted storage or launch steps.

**Open:** your collection page → **Launch a public mint**. Sign in as the creator and connect the collection's creator wallet. Public-mint creation must be enabled; an admin preview is not general availability.

## Prepare your files

* Select a set of 2–10,000 images, within the limits shown by the form.
* Use PNG, JPG, WebP or GIF, up to 5 MB each.
* Give every image a unique filename. Keep the original files for recovery.
* Optionally prepare a JSON traits file keyed by the exact image filenames.

```json
{
  "1.png": { "Background": "Lime", "Hat": "Crown" },
  "2.png": { "Background": "Black", "Hat": "None" }
}
```

The uploader also accepts arrays of `trait_type`/`value` objects. Filenames must match, including extensions. [Download the example traits file](https://1318082464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn4TawV5u26iTOJGwBeyB%2Fuploads%2F5ROhUKUUcvTbroxuty40%2Fnft-traits.json?alt=media) and replace its example filenames and values. Prepare only public artwork and metadata: uploaded permanent files cannot be withdrawn.

## Set up the mint

1. Under **1. Images**, select all images together.
2. Inspect the image count and order. Files are numbered by filename; optionally choose **Shuffle the order before uploading**.
3. Add the optional **Traits file** and review any parsing message.
4. Under **2. Mint settings**, enter the **NFT name** prefix, up to 20 characters. Items receive numbered names such as `Collection #1`.
5. Set **Price per NFT (SOL)**, **Minting opens**, optional **Minting closes** and optional **Limit per wallet**. Date/time inputs use the browser's local time; check your timezone before announcing an opening time.
6. Review the storage quote, setup network cost and what each buyer will pay.
7. Choose **3. Pay for storage and upload**. Approve the storage payment and keep the tab open until all files are stored.
8. Recheck the final settings, then choose **4. Create the public mint** and approve the separate on-chain setup transaction.
9. Confirm that the collection page displays the public **Mint** panel and correct rules.

Setting the creator price to zero does not remove SPAWN's public-mint fee or network costs. Buyers receive the next item in number order. Uploaded images are already public; this is not a hidden-art reveal system.

## Recover an interruption

| Situation                        | Recovery                                                                                                                   |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Storage upload stopped           | Return in the same browser, select the exact original images and choose **Continue the upload**.                           |
| Files/names locked               | Upload preparation has begun; use the original set.                                                                        |
| Setup transaction pending        | Choose **Finish launching** and inspect the existing signature.                                                            |
| Need to restart before launch    | **Start over** warns that paid storage is not refunded and uploaded files remain public. Read the warning before using it. |
| Wrong creator wallet             | Reconnect the original collection wallet.                                                                                  |
| Invalid traits file              | Use valid JSON, exact filenames and nonempty trait names/values.                                                           |
| Rules need changing after launch | SPAWN currently provides no edit control for the price, times or per-wallet limit after launch.                            |

Keep local browser data and original files until completion. Do not start a second paid setup simply because confirmation or indexing is slow.

**Next:** share the collection URL and [buyer instructions](/spawnmeme-docs/feature-guides/nfts/21-minting-and-collecting.md).

***

[Guide home](/spawnmeme-docs/feature-guides.md) · [Troubleshooting](/spawnmeme-docs/feature-guides/reference-and-support/38-troubleshooting.md) · [Get help](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.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://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/nfts/20-public-mint-setup.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.
