Solana is the cheapest and fastest chain to launch an NFT collection on — and it's not even close. Minting costs are a fraction of a cent per NFT, transactions confirm in under a second, and the tooling has matured to the point where you can go from artwork to live mint in a single afternoon.
But "cheap and fast" doesn't mean "simple." There are real decisions to make: standard NFTs vs. compressed NFTs, Candy Machine configurations, metadata standards, mint page options, and marketplace listings. Get these wrong and you're stuck with a collection that won't display properly, costs more than it should, or fails to attract buyers.
This guide walks through the entire process — from preparing your art files to a live, minted collection listed on Magic Eden and Tensor.
Before You Start: Key Decisions
Standard NFTs vs. Compressed NFTs (cNFTs)
This is the single most important decision you'll make. Solana supports two types of NFTs, and they're fundamentally different in cost and architecture.
Standard NFTs are stored as individual accounts on Solana. Each one costs roughly 0.01-0.02 SOL to mint (the rent-exempt minimum for the account). For a 10,000-piece collection, that's 100-200 SOL in minting costs.
Compressed NFTs (cNFTs) use state compression and Merkle trees to store NFT data off-chain while keeping a hash on-chain. The cost savings are dramatic:
| Collection Size | Standard NFTs Cost | Compressed NFTs Cost |
|---|
| 1,000 | ~15 SOL | ~0.1 SOL |
| 10,000 | ~150 SOL | ~0.5 SOL |
| 100,000 | ~1,500 SOL | ~2 SOL |
| 1,000,000 | ~15,000 SOL | ~10 SOL |
For most new collections in 2026, compressed NFTs are the default choice. Magic Eden, Tensor, Phantom, and all major wallets and marketplaces support them fully.
Choose standard NFTs only if:
- Your collection is very small (under 100 pieces)
- You need on-chain programmability that cNFTs don't support yet
- Your buyers specifically expect standard Metaplex NFTs
Choosing Your Metadata Standard
Metaplex is the standard for Solana NFTs. You'll use either:
- Metaplex Token Metadata: The original standard, used for standard NFTs
- Metaplex Bubblegum: The program for compressed NFTs, built on state compression
- Metaplex Core: The newest standard that simplifies the account model with a single-account NFT structure
For new collections, Metaplex Core is recommended unless you have a specific reason to use the older standards. It's simpler, cheaper, and has full marketplace support.
Step 1: Prepare Your Artwork
Image Specifications
Every NFT needs an image. For collections with traits (generative PFP projects), you'll need layered artwork that can be combined programmatically.
Recommended specs:
- Format: PNG (for pixel-perfect quality) or WebP (smaller files)
- Resolution: 2000x2000 or 3000x3000 pixels — high enough for display, reasonable for storage
- File size: Under 5MB per image (marketplaces may reject larger files)
- Aspect ratio: 1:1 is standard for PFP collections, but any ratio works for 1/1 art
Generating a Trait-Based Collection
If you're creating a generative collection (think variations of a base character with different hats, backgrounds, eyes, etc.), you need:
- Layer files: Each trait category (background, body, eyes, mouth, accessory) as separate PNG files with transparent backgrounds
- A generation script: Combines layers into unique combinations with controlled rarity
Popular tools for generation:
- HashLips Art Engine: Open-source Node.js tool for combining trait layers
- Bueno: Web-based generator with rarity controls and metadata export
- Custom scripts: Many creators use Python (Pillow library) or Node.js (Sharp) for full control
Rarity tips:
- Define trait rarities before generating — don't adjust after
- Keep total supply reasonable (5,000-10,000 is standard)
- Ensure no duplicate combinations exist in the final output
- Preview random samples to catch visual clashes between traits
For 1/1 Art Collections
If each piece is individually created (photography, illustrations, generative art), preparation is simpler:
- Create high-resolution files for each piece
- Name them consistently (001.png, 002.png, etc.)
- Prepare metadata individually for each piece
Step 2: Prepare Metadata
Every NFT needs a JSON metadata file that describes it. The Metaplex standard looks like this:
{
"name": "My Collection #1",
"symbol": "MYCOL",
"description": "A piece from My Collection on Solana.",
"image": "https://arweave.net/YOUR_IMAGE_HASH",
"attributes": [
{ "trait_type": "Background", "value": "Blue" },
{ "trait_type": "Eyes", "value": "Laser" },
{ "trait_type": "Hat", "value": "Crown" }
],
"properties": {
"category": "image",
"files": [
{
"uri": "https://arweave.net/YOUR_IMAGE_HASH",
"type": "image/png"
}
],
"creators": [
{
"address": "YOUR_WALLET_ADDRESS",
"share": 100
}
]
},
"seller_fee_basis_points": 500
}
Key fields:
- name: Display name on marketplaces
- symbol: Short ticker (3-5 characters)
- attributes: Traits that marketplaces use for filtering and rarity rankings
- seller_fee_basis_points: Royalty percentage (500 = 5%)
- creators: Wallet addresses and revenue share splits
Uploading Assets
Your images and metadata need permanent hosting. The two main options:
Arweave (via Metaplex's Sugar or Bundlr):
- Permanent, decentralized storage
- One-time payment — no recurring costs
- Industry standard for Solana NFTs
- Cost: roughly $0.01-0.05 per file depending on size
IPFS (via Pinata, NFT.Storage, or similar):
- Decentralized but requires pinning for persistence
- Cheaper upfront but may need ongoing pinning costs
- Widely supported but less permanent than Arweave
Recommendation: Use Arweave through Metaplex's built-in upload tools. It's the most reliable option and what marketplaces expect.
Step 3: Set Up Candy Machine
Candy Machine is Metaplex's program for managing NFT mints. It handles:
- Sequential or random minting from your collection
- Mint phases (allowlists, public mint, etc.)
- Payment (SOL, SPL tokens, or NFT gates)
- Mint limits per wallet
- Start and end dates
Installing Metaplex Sugar CLI
Sugar is the command-line tool for creating and managing Candy Machines:
# Install Sugar CLI
bash <(curl -sSf https://sugar.metaplex.com/install.sh)
# Verify installation
sugar --version
Configuring Your Candy Machine
Create a config.json file:
{
"number": 10000,
"symbol": "MYCOL",
"sellerFeeBasisPoints": 500,
"isMutable": true,
"isSequential": false,
"creators": [
{
"address": "YOUR_WALLET_ADDRESS",
"share": 100
}
],
"uploadMethod": "bundlr",
"awsConfig": null,
"nftStorageAuthToken": null,
"shdwStorageAccount": null,
"pinataConfig": null,
"hiddenSettings": null,
"guards": {
"default": {
"solPayment": {
"value": 0.5,
"destination": "YOUR_WALLET_ADDRESS"
},
"startDate": {
"date": "2026-03-20T18:00:00Z"
},
"mintLimit": {
"id": 1,
"limit": 3
}
},
"groups": [
{
"label": "WL",
"guards": {
"solPayment": {
"value": 0.3,
"destination": "YOUR_WALLET_ADDRESS"
},
"startDate": {
"date": "2026-03-20T16:00:00Z"
},
"allowList": {
"merkleRoot": "YOUR_MERKLE_ROOT"
}
}
}
]
}
}
This configuration creates:
- A 10,000-piece collection at 0.5 SOL mint price
- A whitelist phase 2 hours before public mint at 0.3 SOL
- A 3-per-wallet mint limit for the public phase
- 5% creator royalties
Deploy Sequence
# 1. Upload assets to Arweave
sugar upload
# 2. Deploy the Candy Machine
sugar deploy
# 3. Verify the deployment
sugar verify
# 4. (Optional) Set the collection as verified
sugar collection set
Sugar handles the entire upload, Candy Machine creation, and verification process. For a 10,000-piece collection, expect the upload step to take 30-60 minutes depending on file sizes and network conditions.
Step 4: Build Your Minting Page
You need a front-end where users can connect their wallet and mint. You have several options:
Option 1: Crossmint (No-Code)
Crossmint provides embeddable mint buttons and hosted minting pages. Users can pay with credit cards, Apple Pay, or crypto. Setup takes minutes.
Pros: No development needed, credit card payments expand your audience, handles wallet creation for non-crypto users
Cons: Platform fees, less customization, dependency on Crossmint infrastructure
Option 2: Custom Mint Site
Build a Next.js or React site using Metaplex's JavaScript SDK:
npm install @metaplex-foundation/umi @metaplex-foundation/mpl-candy-machine
The Metaplex Umi framework provides TypeScript-friendly functions for interacting with Candy Machine directly from your front-end. You'll need:
- Wallet adapter integration (@solana/wallet-adapter-react)
- Candy Machine state reading (items remaining, mint phase, price)
- Mint transaction building and signing
- Status feedback (loading, success, error states)
Pros: Full control over design and UX, no platform fees, your own domain
Cons: Requires development time, you handle hosting and reliability
Option 3: Marketplace-Hosted Launchpad
Both Magic Eden and other Solana marketplaces offer launchpad services where they host your mint, handle the front-end, and provide built-in audience exposure. Application processes are selective.
Step 5: Launch and List on Marketplaces
Pre-Launch Checklist
Before opening your mint:
Listing on Marketplaces
After minting, your collection needs to appear on marketplaces for secondary trading.
Magic Eden:
- Collections using Metaplex standards are usually auto-detected
- For verified collection status, apply through Magic Eden's creator portal
- Verification adds the checkmark and improves discovery
Tensor:
- Tensor auto-indexes all Solana NFT collections
- Collections appear automatically once minted
- Tensor's trading features (AMM pools, compressed NFT support) attract active traders
Royalty Considerations
Solana NFT royalties are not automatically enforced on all marketplaces. The current landscape:
- Magic Eden: Enforces royalties for collections using Metaplex's Programmable NFTs (pNFTs) standard
- Tensor: Offers optional royalty payment for buyers
- Most marketplaces: Trending toward creator royalty support, but enforcement varies
If royalty revenue is important to your project, use the Programmable NFT standard through Metaplex, which includes on-chain royalty enforcement via transfer hooks.
Marketing Your Collection
Creating the NFTs is the technical part. Selling them is the hard part. Here's what actually works in 2026:
Build Community First
Do not launch to zero followers. Spend at least 2-4 weeks building community before your mint date:
- Twitter/X: Share art previews, behind-the-scenes process, trait reveals
- Discord: Create a server with channels for announcements, chat, and allowlist signup
- Collaborations: Partner with other Solana NFT communities for cross-promotion
Allowlist Strategy
Allowlists create urgency and reward early supporters. Effective approaches:
- Require engagement (retweets, Discord activity) for allowlist spots
- Keep the allowlist smaller than total supply to ensure a public mint phase
- Give allowlist wallets a price discount as a genuine reward
Post-Mint Retention
The launch is just the start. Collections that maintain value long-term:
- Deliver on roadmap promises
- Provide ongoing utility (token airdrops, access passes, exclusive content)
- Maintain active community management
- List on aggregators and maintain marketplace presence
Cost Breakdown: What You'll Actually Spend
Here's a realistic budget for a 5,000-piece collection:
| Item | Standard NFTs | Compressed NFTs |
|---|
| Arweave storage (5K images + metadata) | ~5 SOL | ~5 SOL |
| Candy Machine deployment | ~0.02 SOL | ~0.5-2 SOL (Merkle tree) |
| Minting costs (creator-paid) | ~75 SOL | ~0.3 SOL |
| Minting costs (buyer-paid) | 0 SOL (buyers pay) | 0 SOL (buyers pay) |
| Domain + hosting | $10-50/year | $10-50/year |
| Total creator cost | ~80 SOL + hosting | ~7 SOL + hosting |
With compressed NFTs, you can launch a legitimate collection for under 10 SOL in total costs. This is why Solana has become the default chain for NFT creators who aren't already established on Ethereum.
Common Mistakes to Avoid
Rushing the artwork: Quality art is the single biggest factor in a collection's success. Don't use AI-generated art without significant human curation and modification.
Ignoring metadata standards: Incorrect metadata means your NFTs won't display properly on marketplaces. Test on devnet first, always.
Setting royalties too high: 5% is standard. Higher royalties discourage secondary trading, which hurts your collection's activity metrics.
Skipping the community phase: Launching to zero community is the fastest way to a failed mint. Build an audience before building the tech.
Overcomplicating the mint: Complex multi-phase mints with token gates, random reveals, and Dutch auctions add failure points. Keep it simple for your first collection.
Not planning post-mint: Buyers want to know what happens after the mint. Have a clear, achievable roadmap — don't promise what you can't deliver.
Next Steps
If you're ready to launch:
- Start with artwork preparation and metadata generation
- Test the full flow on Solana devnet using Metaplex Sugar
- Deploy your Candy Machine and build or configure your mint page
- Build community while the technical setup is in progress
- Launch, list on Magic Eden and Tensor, and engage your holders
For collections targeting non-crypto-native audiences, Crossmint removes wallet friction entirely — buyers can mint with a credit card and receive their NFT in a custodial wallet.
Solana's NFT infrastructure in 2026 is robust enough for everything from small art drops to million-piece gaming asset collections. The hard part isn't the technology anymore — it's creating something people actually want to own.
