A Solana token’s identity involves more than its name and logo. The mint account holds core token state, such as decimals, current minted supply, and certain authorities. Descriptive details—including a name, symbol, image, or description—come from a metadata system, and the exact setup depends on the token program and metadata standard.
Understanding that difference helps you choose compatible metadata, prepare accurate token information, and avoid common launch problems. This guide explains how Solana token metadata works, where it is stored, what may be changed after launch, and what to check before creating a token.
Note: Wallets, explorers, and other applications may display metadata differently. Their supported standards, indexing, and caching can affect what users see.
What Is Solana Token Metadata?
Solana token metadata is descriptive information associated with a token, such as its name, symbol, or links to an image and description. It helps wallets, explorers, and applications identify and display an asset. The storage method depends on the token program and metadata standard.
Metadata does not replace the token’s mint address. The mint address is the token’s unique on-chain identifier. Names and symbols can be duplicated, so users should verify the mint address through a trusted project source.
What Information Does a Solana Token Contain?
Some token properties describe how the token works. Others help applications display it.
| Field | What it means | Where it is generally represented | Why it matters |
|---|---|---|---|
| Name | Human-readable token name | Metadata, depending on the standard | Helps users recognize the asset |
| Symbol | Short ticker-like label | Metadata, depending on the standard | Helps interfaces display the token; symbols are not unique |
| Decimals | Precision for token amounts | Mint account | Determines how base units are displayed |
| Supply | Number of units minted so far | Mint account records current minted supply | Distinguishes minted supply from circulating or maximum supply |
| Description | Additional information about the asset | Often off-chain JSON, or a custom field where supported | Gives users context |
| Logo or image | Visual representation of the token | Image file referenced by metadata | Helps wallets and explorers display the asset |
| Metadata URI | Address pointing to metadata, often JSON | Metadata record or Token-2022 extension | Connects on-chain information with additional data |
| Update authority | Permission to change supported metadata | Relevant metadata system | Determines who may update metadata, when supported |
A standard Solana mint account stores core state such as supply, decimals, Mint Authority, and Freeze Authority. It does not necessarily contain every descriptive field displayed by wallets. Solana’s mint-account documentation
Where Is Solana Token Metadata Stored?
There is no single metadata-storage format shared by every Solana token.
For a standard SPL token using Metaplex Token Metadata, the Metaplex program creates a separate metadata account associated with the mint. That account can hold fields such as a name and symbol, along with a URI pointing to off-chain JSON. Solana’s Metaplex metadata documentation
Token-2022 offers another option: its Token Metadata extension can store metadata fields directly on the mint. Its Metadata Pointer extension is separate; it identifies an account that stores metadata. Solana’s Token-2022 metadata documentation
A simplified example of a common Metaplex setup is:
Token mint
→ Metaplex metadata account
→ metadata URI
→ JSON document
→ image or other linked resources
This is an illustration, not a universal layout. With Token-2022’s Token Metadata extension, some fields can instead be stored directly on the mint.
What is a metadata account?
In the Metaplex setup, the metadata account is a separate on-chain account linked to a token mint. It is a Program Derived Address (PDA): an address calculated from known inputs, including the mint address and metadata program. This gives applications a predictable way to locate metadata for a mint. Solana’s Metaplex metadata documentation
Name, Symbol, Decimals, and Supply Are Different
A token’s name and symbol help identify it in interfaces. Decimals and supply describe core token state.
Decimals specify how many fractional places a token supports. For example, a mint with six decimals can represent amounts down to one-millionth of a token. Decimals are configured as part of mint creation; they are not simply a cosmetic metadata field. Solana’s mint-account documentation
Supply is the number of token units minted so far. It differs from:
- Circulating supply: an estimate of tokens available in the market, based on a provider’s methodology.
- Maximum supply: a cap a project may define or enforce through its design.
- Minted supply: the current supply recorded by the token mint.
A metadata update does not change a token’s decimals or minted supply.
How Do Logos, Descriptions, and Metadata URIs Work?
A metadata URI often points to a JSON document. That JSON can contain a description and an image URL. The image itself is a separate file; the metadata record points to it.
A wallet or explorer may retrieve the URI, read the JSON, and then attempt to load the image. A valid URI does not guarantee that every application will display the logo. The application may not support that metadata standard, may have cached older information, or may be unable to retrieve the JSON or image.
Before launch, check that:
- The JSON is valid and publicly accessible.
- The image URL loads without requiring a login.
- The image format works for your intended applications.
- The metadata URI points to the correct document.
- The document’s fields match your intended token name and symbol.
- The hosting method meets your availability requirements.
IPFS or Arweave may be used for hosting, but availability depends on how the content is stored and maintained. Do not assume a URI is permanent simply because it uses a particular storage network.
Metaplex Metadata vs. Token-2022 Metadata
| Approach | Where metadata is stored | Pointer or account relationship | What to check |
|---|---|---|---|
| Metaplex Token Metadata | In a separate metadata account associated with the mint; the account can contain a URI to off-chain JSON | A PDA links the metadata account to the mint | Client support, metadata mutability, and URI availability |
| Token-2022 Token Metadata extension | Metadata fields can be stored directly on the mint | The extension is part of the mint’s Token-2022 configuration | Token-2022 compatibility and extension configuration |
| Token-2022 Metadata Pointer | The pointer extension is on the mint; metadata may be stored at another account | Identifies the account that holds metadata | Whether clients recognize the pointer and referenced format |
These approaches are not interchangeable in every application. Choose based on your token’s requirements and the wallets, explorers, exchanges, and other software your users are likely to use. Solana documents the Metadata Pointer and Token Metadata extensions as distinct mechanisms. Solana’s Token-2022 metadata documentation
Can You Change Solana Token Metadata After Launch?
Sometimes. It depends on where the metadata is stored, the metadata standard, whether the asset is mutable, and who controls the relevant update authority.
With Metaplex Token Metadata, the update authority can modify metadata while the account remains mutable. Token-2022’s Token Metadata extension has its own update-authority mechanism. The Metadata Pointer also has a separate authority for changing the pointer. Solana’s Metaplex metadata documentation Solana’s Token-2022 metadata documentation
Changes may take time to appear in wallets and explorers because applications index or cache data differently. Updating metadata does not change the token’s mint address.
Do not assume you can change a token’s name, symbol, image, or description after launch. Verify the specific standard and permissions before relying on future updates.
How to Prepare Token Metadata Before Creating a Token
Prepare your token information before approving the creation transaction:
- Choose a clear name that is not easily confused with another project.
- Select a concise symbol, remembering that symbols are not globally unique.
- Decide on decimals and supply based on how the token will be used.
- Prepare a suitable logo file.
- Write an accurate, concise description.
- Choose a metadata standard that fits your compatibility requirements.
- Prepare valid JSON and accessible image resources if the standard uses off-chain metadata.
- Decide who should control the relevant update authority.
- Check which metadata settings your token creation tool supports.
- Review the final configuration and wallet transaction before signing.
- Verify the resulting token information in relevant explorers or applications.
Not every step applies identically to every metadata standard.
Common Solana Token Metadata Mistakes
Confusing decimals with supply
Decimals control precision; supply counts minted token units. Decide on both before creation.
Assuming the name and symbol are always stored in the mint
Their location depends on the metadata approach. Check the token program and standard.
Using a broken image URI
Test the image and metadata URLs from a browser that is not logged into your hosting account.
Providing malformed JSON
Validate the JSON and check that the fields match the format your intended applications support.
Expecting every explorer to update immediately
Indexers and wallets may cache metadata. Check more than one relevant interface and allow for indexing delays.
Treating a symbol as unique
Unrelated tokens can use the same symbol. Share the mint address alongside the project name.
Confusing metadata Update Authority with Mint Authority
Update Authority controls supported metadata changes. Mint Authority authorizes token issuance.
Assuming metadata is always editable
Update permissions depend on the metadata standard and the token’s current configuration.
Assuming immutable metadata proves legitimacy
Immutable metadata can still describe a misleading or untrustworthy project. Verify the mint and assess the project separately.
How Solsmint Helps With Token Creation
Solsmint provides a no-code workflow for creating Solana SPL tokens. Depending on the current creation interface, users can configure supported token information such as name, symbol, supply, decimals, logo or metadata, and authority settings.
Available settings can change, so review the live interface before starting. Visit Solsmint’s token creation workflow to see the current options.
This article explains Solana metadata generally. It does not imply that Solsmint can edit metadata after launch, change metadata authorities, or perform other post-launch operations unless those capabilities are available in the current product interface.
Frequently Asked Questions
What is Solana token metadata?
Solana token metadata is descriptive information associated with a token, such as its name, symbol, image, or description. Its storage method depends on the token program and metadata standard.
Where are an SPL token’s name and symbol stored?
It depends on the metadata setup. Metaplex Token Metadata uses a separate account associated with the mint. Token-2022’s Token Metadata extension can store metadata directly on the mint. Solana’s Metaplex metadata documentation Solana’s Token-2022 metadata documentation
How do I add a logo to a Solana token?
Usually, the metadata record points to a JSON document that includes an image URL. The exact setup depends on the token’s metadata standard and creation tool. Test the JSON URI and image URL, then check how relevant wallets and explorers display them.
Can I change a Solana token’s name after launch?
Sometimes. It depends on the metadata standard, whether the metadata is mutable, and whether you control the required update authority. Confirm the token’s implementation before assuming an update is possible.
What is a token metadata URI?
A metadata URI is an address that points to metadata, often a JSON document with fields such as a description and image URL. Some Token-2022 configurations can store metadata fields directly on the mint.
What is the difference between token decimals and supply?
Decimals define how token amounts are divided into fractional units. Supply is the number of units minted. They are different properties of a token.
Does changing metadata change the token’s mint address?
No. A metadata update does not change the mint address, which uniquely identifies the token. It may change what supporting applications display.
What is the difference between Metaplex and Token-2022 metadata?
Metaplex commonly uses a separate metadata account linked to the mint. Token-2022 can store metadata directly on the mint with its Token Metadata extension, while its Metadata Pointer extension identifies an account containing metadata. Compatibility depends on the client and implementation.
Conclusion
Solana token metadata helps wallets and applications describe an asset, but it is distinct from the mint account’s core state. Names, symbols, descriptions, and logos are descriptive information; decimals and minted supply are token properties; and the update authority determines who may change supported metadata.
Before launch, choose a metadata approach that fits your compatibility needs, prepare and test JSON and image resources where required, and understand who controls the update authority. To review Solsmint’s current no-code creation options, visit Solsmint’s token creation workflow.
Top comments (0)