Magiceden

Magiceden limits are 10 Collection Drafts in Solana Creator Hub

Magiceden limits are a maximum of 10 saved collection drafts in Magic Eden's Creator Hub, including unfinished Solana listing applications. When all 10 slots hold drafts, a creator must submit a complete application or delete an obsolete draft before starting another. The cap counts draft records, not NFTs, mint addresses, wallet balances, or the size of a hash list. Efficient use therefore begins before the form: identify the collection standard, gather the correct on-chain address, prepare images and copy, and decide whether an auto-listed collection needs a claim rather than a new application. The sections below cover preparation, execution, verification, cleanup, and long-term slot maintenance.

Turning one draft slot into a submitted Solana collection

A single Solana listing draft moves from an empty Creator Hub slot to submission through preparation, four form stages, a final data check, and deliberate release of that slot.

Begin by logging into Creator Hub with the email used for collection management. Choose Create a Collection, select Solana, and reserve one slot only after the source material is ready. The application then passes through four numbered stages: Listing Details, Populating the Collection, Choose Your NFT Standard, and Submit. Stage 1 asks for the collection name and symbol. Stage 2 fills the marketplace record. Stage 3 selects NFT Legacy or Metaplex Core. Stage 4 sends the checked application out of draft state, with an optional note for the listings team.

The standard choice determines the identifier path. NFT Legacy accepts an MCC address, one or more FVCAs, or a hash list. Metaplex Core uses the MCC address. A compressed NFT application also needs its Merkle tree addresses, so a title and logo alone are not enough to finish the form.

Before Submit, compare every pasted address against the minting records and review the collection preview. A clean submission releases the working draft slot and creates a record that can be followed through Creator Hub, while an incomplete save continues to occupy capacity.

What happens when all 10 draft slots are occupied?

All 10 occupied Creator Hub slots prevent an 11th collection draft from opening until one unfinished application is submitted or deleted from the active draft pool.

The 11th idea has no separate queue or larger allowance. Magiceden limits count one unfinished collection form as one slot regardless of collection size, mint supply, or team size. Submitting one ready record or deleting one abandoned record returns exactly one place for the next application.

Draft disposition checklist

• Submit when all four stages are complete and identifiers match.
• Delete when the collection will not proceed and source files are saved.
• Keep when artwork or metadata is changing under an assigned deadline.
• Claim when the Solana collection already appears on Magic Eden.
• Start fresh only when an empty slot and final identifier are available.

A draft for an already auto-listed collection is the first candidate to review, because the Claim flow handles existing listings. Keeping nine active drafts and one empty slot gives a team room for a time-sensitive collection without treating the published cap as expandable.

Preparing identifiers before consuming another slot

Prepared identifiers shorten each Solana listing session because Creator Hub asks for different collection keys under NFT Legacy, Metaplex Core, and compressed NFT submission paths.

Matching each standard to its evidence

The identifier proves how the assets belong together. Collect it before draft creation, then label the value by standard and purpose to avoid mistaking an MCC address for a Candy Machine address.

NFT Legacy

NFT Legacy offers three routes: a Metaplex Certified Collection address, First Verified Creator Addresses, or a JSON hash list. MCC points to the collection NFT that Token Metadata uses for verified membership. An FVCA identifies the first creator entry whose verified flag is set, while a hash list enumerates mint addresses. Even a large hash list stays within a single draft; the draft counter still increases by one, not by the number of mints.

Metaplex Core and compressed NFTs

Metaplex Core has one listed identifier route in the Creator Hub flow: the MCC address. Core collections are first-class accounts, so the collection address replaces Legacy's FVCA and hash-list choices. Compressed NFTs add another layer. Each cNFT collection supplies its associated MCC and the relevant Merkle tree addresses created through Metaplex Bubblegum. One application groups those tree addresses under the collection instead of consuming one draft per tree.

Separating dashboard capacity from on-chain limits

Creator Hub's 10-draft ceiling governs unfinished marketplace forms, while Solana, SPL Token, Metaplex Token Metadata, and Metaplex Core enforce separate rules on actual assets and accounts. The published Creator Hub allowance is exactly 10 collection drafts at one time. Saving or deleting a draft is a dashboard action, so it does not create, transfer, burn, or update an NFT on Solana. These Magiceden limits describe workspace capacity, not network capacity. Minting through Candy Machine or creating a Core Asset invokes network programs separately, and those transactions do not expand the dashboard allowance.

Does submitting a draft mint or modify NFTs?

No, submitting a Creator Hub draft sends marketplace listing information for review or processing; it does not execute a Solana mint, transfer, metadata update, or collection verification.

Creator Hub stores descriptive marketplace data, while Solana programs hold asset state. In Token Metadata, collection membership uses two values: a collection key and a verified Boolean. The key is a 32-byte Solana public key, and the verified value has two states, false or true. Moving it to true requires a Verify instruction signed by the collection authority; sending a marketplace form does not perform that instruction.

Metaplex Token Metadata supports up to five creators, and their percentage shares must total 100. Candy Machine configuration leaves four creator entries available because the machine occupies one Token Metadata creator position. Royalty values use basis points from 0 through 10,000: 100 basis points equal 1%, and 500 equal 5%. These fixed protocol fields remain independent of the 10 saved-form ceiling.

Cleaning an old draft without losing the source material

Deleting an obsolete Creator Hub draft releases one of the 10 form slots, while the minted Solana assets, collection authority, metadata accounts, and stored media remain unchanged.

Before using Delete, copy the collection description, social handles, image files, and every on-chain identifier to a project record. Preserve the MCC public key exactly, keep each FVCA under its own label, and retain the JSON hash list as a file rather than pasted text. For compressed NFTs, record every Bubblegum Merkle tree address beside the collection address. That package separates reusable source data from the temporary Creator Hub form, so recreating the application does not depend on browser state or a team member's memory. Include the intended standard and the person responsible for the next submission.

Deleting the dashboard record does not alter an SPL Token mint, close a Token Metadata account, change Metaplex Core authority, or remove stored media. It only removes the unfinished marketplace application and returns one slot to the 10-slot pool.

Name the backup with the collection, standard, and last review date, then assign one owner before removing the draft. Re-entry becomes a deliberate reconstruction from those records. Submission fits complete applications; deletion fits work with no active path to completion.

Using auto-listing and claims to preserve draft capacity

Solana auto-listing and Creator Hub's claim flow reduce unnecessary drafts by separating an existing marketplace collection from a fully minted collection that still lacks a listing.

Solana collections are auto-listed, and creators use Claim to control and edit an existing marketplace page. Solana collection management has run through Creator Hub since February 2023. If a fully minted collection does not appear on Magic Eden, the listing flow provides a manual application path. The distinction matters: an existing auto-listed collection calls for a claim, while an absent fully minted collection calls for a draft. Checking marketplace visibility before pressing Create a Collection prevents a duplicate form from taking one of the 10 slots.

Claiming works on the existing listing, whereas Create a Collection opens the application path covered by the draft cap. For a visible collection, the claim path is the direct operational alternative.

Verifying collection data after submission

Post-submission verification should confirm four things: the application status, the collection identifier, the indexed asset set, and the displayed collection relationship on Magic Eden itself.

Start in Creator Hub and confirm the record no longer appears among editable drafts. Then inspect the Magic Eden collection page and compare its identifier with the submitted MCC, FVCA, or hash list. Solscan provides a second view of Solana addresses and transactions. For Token Metadata assets, confirm the collection key and verified state. For Metaplex Core, confirm the asset sits under the intended Core collection.

Compressed NFTs require a different read path because Bubblegum stores compressed state in Merkle trees. Check the associated collection and each submitted tree address, then compare the indexed assets through a Digital Asset Standard API view. If Legacy items are missing, rebuild the JSON hash list with every mint address and submit a collection update rather than opening another collection draft.

Maintaining a ten-slot workspace over time

A durable Creator Hub routine keeps no more than nine active collection drafts, reserves the tenth slot for urgent work, and assigns every draft a next action.

Keep a small register with five fields: collection name, standard, identifier type, owner, and next action. Review it whenever a draft changes state. At nine active drafts, the tenth slot stays available; at 10, creation work stops until one record leaves. Close abandoned concepts promptly, submit complete applications, and use Claim for visible auto-listed collections. This routine makes the hard cap predictable. It also keeps project files outside the form, which is more resilient than using 10 unfinished applications as the team's only project tracker.

What to know about Magiceden limits