NFT collection showing generic name instead of custom collection name

NFT
1

I’m working with candy machine v2 for minting NFTs and running into a weird issue. When I mint my tokens, they show up in my wallet but the collection name is displaying as “Collection NFT” instead of the actual name I specified in my metadata.

Everything else works fine - the minting process completes successfully and all the individual token metadata looks correct. But for some reason the collection name isn’t being picked up properly.

Here’s my metadata structure:

{
  "name": "MyToken #1",
  "symbol": "MTK",
  "description": "Sample token description",
  "seller_fee_basis_points": 500,
  "image": "token1.png",
  "external_url": "example.com",
  "edition": 1,
  "creator": "token_creator",
  "attributes": [
    {
      "trait_type": "background",
      "value": "blue"
    },
    {
      "trait_type": "eyes",
      "value": "green"
    }
  ],
  "properties": {
    "files": [
      {
        "uri": "token1.png",
        "type": "image/png"
      }
    ],
    "category": "image",
    "creators": [
      {
        "address": "wallet_address_here",
        "share": 100
      }
    ]
  },
  "collection": {
    "name": "My Custom Collection",
    "family": "My Custom Collection"
  }
}

I want the collection to show as “My Custom Collection” but it keeps defaulting to the generic name. What am I missing here?

2

Had this exact problem last month! Check if you set the collection authority properly when creating your collection NFT. Even if you made the collection NFT, the candy machine can’t verify the connection if the authority isn’t set right. Try running metaplex verify_collection to link them properly.

3

This happens when your collection NFT exists but isn’t properly verified with your candy machine tokens. The metadata collection field doesn’t control what wallets display - that’s all on-chain collection verification. I had this same issue. My collection NFT was created fine, but tokens weren’t getting marked as verified collection members during minting. You need your candy machine config to include the collection mint address AND make sure the collection authority matches your candy machine authority. After minting, check the token account data to see if verification worked. Look for a verified collection field pointing to your collection mint. If it’s missing or unverified, you’ll have to run verification manually for existing tokens. Wallets show the generic name because they can’t find the verified collection reference.

4

Yeah, I’ve seen this before. Usually it’s because the collection metadata isn’t properly linked or verified on-chain.

Are you using a separate collection NFT for your candy machine? Candy machine v2 needs you to create a collection NFT first - that’s the parent for all your minted tokens. Your individual token metadata looks fine, but wallets pull the collection name from that separate collection NFT, not from the “collection” field in your token metadata.

What’s your candy machine config look like? Did you specify a collection mint address when you created it? More importantly - did you actually create and mint the collection NFT with proper metadata before setting up your candy machine?

If you skipped creating a collection NFT, that’s probably why it’s showing the generic name. The wallet’s just using a default fallback when it can’t find proper collection metadata.

Which wallet are you checking? Phantom, Solflare, or something else? Different wallets sometimes handle collection names differently.