Legacy NFTs
Create master editions, limited or open editions, standalone NFTs, and traditional Metaplex collections.
Token
Studio
Back to Home
Token Studio's Solana NFT Minter creates an NFT, defines its rules, places it in a collection, distributes it, updates it, and manages its complete lifecycle from one precise workspace.
Choose the standard that fits the asset, then work with its native capabilities. Token Studio keeps incompatible settings out of the way and shows advanced controls when they apply.
Create master editions, limited or open editions, standalone NFTs, and traditional Metaplex collections.
Create lightweight Core assets and collections with configurable royalties, attributes, delegates, and lifecycle plugins.
Create and update V1 or V2 compressed assets inside compatible Merkle trees at substantially lower on-chain cost.
An NFT is a set of on-chain authorities, relationships, and rules surrounding its media. Token Studio exposes those decisions before the wallet signs them.
Define collection metadata and authority using the collection system appropriate to the selected standard.
Verify or unverify compatible child assets when the connected wallet controls the required collection authority.
A Legacy standalone NFT can act as an unsized collection and later be upgraded to a sized collection. That conversion cannot be reversed.
Move assets between collections when their standard, current state, and authorities allow reassignment.
Core plugins let creators define behavior that would otherwise require separate accounts or custom workflows. Token Studio builds a compatible plugin plan for the asset being created or edited.
Configure attributes, royalties, verified creators, editions, autographs where supported.
Assign update, freeze, transfer, or burn delegates without confusing temporary permissions with permanent restrictions.
Immutable metadata and permanent transfer, freeze, or burn plugins can change what is possible for the lifetime of an asset. Token Studio identifies these controls before execution so they are not mistaken for ordinary editable settings.
Create a compatible Merkle tree, understand its capacity and estimated cost, then mint or update compressed assets without switching to a separate developer tool.
Validate depth, buffer, canopy, version, and expected cost before creating the on-chain structure.
Set creators, royalties, attributes, primary-sale state, collection relationships, and delegates where supported.
When a compressed NFT update cannot fit safely into one transaction, Token Studio can prepare multiple steps or use an address lookup table rather than hiding the constraint.
Want the underlying model first? Read what Solana Merkle trees are and how compressed NFTs use them.
Create editions from a compatible Legacy master edition for as many as 16 recipients in one organized Print workflow.
Move Legacy, Core, and compressed assets together, with exact transaction-capacity projections before signing.
Inspect delegates and asset restrictions in Token Explorer, then change permissions when the connected wallet has authority.
Select mixed NFT standards, review expected rent recovery and fees, and pack compatible burns into 4,096-byte V1 transactions in the Token Studio Burner.
The asset standard determines the Token Studio service fee. Solana network fees, account rent, and media-storage costs remain separate and are shown in the transaction flow where available. The service fees page is the authoritative current schedule.
| Operation | Token Studio fee |
|---|---|
| Legacy NFT mint | 0.004 SOL |
| Legacy NFT or collection edit | 0.002 SOL |
| Core asset or collection mint | 0.002 SOL |
| Core asset or collection edit | 0.002 SOL |
| Compressed NFT V1/V2 mint or edit | 0.0001 SOL |
| Token Time Vault collectors | 0 SOL |
For the complete rules and all other operations, use the authoritative Token Studio Fees page.
No. The connected wallet must hold the necessary update authority, the NFT must remain mutable, and the requested field must be supported by its standard and current state.
Yes. Token Studio has dedicated behavior for the original Metaplex Token Metadata model and the newer Metaplex Core standard rather than treating them as identical.
Yes. The compressed workflow can create compatible V1 or V2 Merkle trees after validating their depth, buffer, canopy, capacity, and estimated on-chain cost.
The current creation flow supports image and video-oriented media through configured Irys or IPFS upload paths. Dedicated audio, 3D, and Arweave creation flows are planned rather than advertised as current features.
No. Minting is the beginning. Token Studio also edits metadata, manages collections and delegates, prints editions, transfers assets, configures Core plugins, creates Merkle trees, and burns assets.
Choose the standard deliberately, see every supported rule, and keep control after the mint succeeds.