> 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-and-launch/before-you-start.md).

# Before You Start

A little planning makes for a much smoother launch. Here's what to get ready before you open Studio 2.0 — you can prepare all of it without spending anything.

## Is Stargaze right for you?

Stargaze is a strong fit if you want to:

* Reach the **Cosmos** community
* Benefit from **low fees and fast transactions**
* Use **flexible minting** — whitelists, multiple phases, open editions
* Accept **ATOM or STARS** for your mint
* Earn **on-chain creator royalties** on secondary sales

## What you'll need

### 1. Your artwork

The images or media for your NFTs:

* **Formats:** images (PNG, JPG, GIF, WebP), video (MP4, WebM), or audio (MP3, WAV)
* **Size:** at least \~1000×1000px for images looks good everywhere on the marketplace
* **Keep files light:** Arweave storage is priced by size, so smaller files cost less to store and load faster. Run them through the [Image & Video Resizer](/create-and-launch/creator-tools.md) first. Large collections are supported too — the [Arweave Uploader](/create-and-launch/creator-tools.md) handles 1 GB and up.
* **Prepare everything up front** so your upload is one clean batch.

### 2. Your metadata

The information attached to each NFT:

* **Name** and **description**
* **Traits / attributes** (optional, but recommended for generative collections)

No spreadsheets required — the [NFT Generator](/create-and-launch/creator-tools.md) and [Meta Maker](/create-and-launch/creator-tools.md) can build metadata for you.

{% hint style="info" %}
**Bringing your own files?** If you're not using the built-in generators, name your files as plain sequential numbers — `1.png`, `2.png`, `3.png` (numbers only; something like `1-punk.png` won't work). Each image needs a matching metadata file with the same number (`1.png` ↔ `1.json`), and images and metadata go in separate folders. The generators handle all of this for you automatically.
{% endhint %}

### 3. Some ATOM

You'll need ATOM for permanent storage, the collection-creation fee, and gas. The app shows the exact amounts before you confirm — and you can rehearse the entire process on **testnet for free** first. See [Costs & Fees](/create-and-launch/costs-and-fees.md).

### 4. A plan

Before you launch, decide:

* **Collection size** — how many NFTs?
* **Price** — what will each mint cost, and in which token (ATOM or STARS)?
* **Phases** — a whitelist, a public mint, or both? See [Whitelists](/create-and-launch/whitelists.md).
* **Timing** — when does each phase open and close?
* **Marketing** — how will people hear about it?

## Planning your launch

**Timing.** Give yourself buffer time to rehearse on testnet, and start talking about your launch a week or two ahead.

**Community.** The launches that do well usually have an engaged audience before mint day — an active Discord or Telegram, a presence on X, and early supporters for your whitelist.

**Expectations.** Look at how similar collections have performed, price fairly for the current market, and focus on building genuine community rather than short-term hype.

## Ready?

Once your artwork, metadata, and plan are set, head to [Creating a Collection](/create-and-launch/creating-a-collection.md) to build and launch your first drop.


---

# 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-and-launch/before-you-start.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.