> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jup.ag/llms.txt
> Use this file to discover all available pages before exploring further.

# Token Metadata Updates

> How to update your token's metadata across Jupiter products.

## What Are Metadata Updates

Token metadata updates allow anyone to submit changes to a token's information across Jupiter products, including Spot, Terminal, Mobile, and API services.

This is an open process. Anyone can submit an update request, not just project teams. This is particularly useful when:

* A project team has lost access to update onchain metadata
* New social channels need to be added
* A token has transitioned to <Tooltip tip="Community Takeover: when a token's ownership and development shifts from the original team to the community.">community ownership (CTO)</Tooltip>
* A community wants to keep token information accurate

<Note>
  This process is currently in beta. Review timelines and procedures may evolve.
</Note>

## What Can Be Updated

The following fields can be updated through this process:

* **Logo** (PFP)
* **Name**
* **Symbol** (ticker)
* **Description**
* **Socials:** website, X account, X community link, Telegram, Discord, Instagram, TikTok, Linktree
* **Circulating Supply**

## How to Submit

<Steps>
  <Step title="Go to the metadata form">
    Submit your request at [verified.jup.ag/metadata](https://verified.jup.ag/metadata).
  </Step>

  <Step title="Fill in the fields you want to update">
    Include all the changes you need in a single submission.
  </Step>

  <Step title="Pay the submission fee">
    A fee of 1,000 JUP is required per submission, collected at the time of submission. The tokens are burned by Jupiter through a <Tooltip tip="A wallet that requires multiple authorized signatures to execute a transaction, adding a layer of security.">multisig</Tooltip> wallet and are not retained by the team.
  </Step>

  <Step title="Submit your request">
    Once submitted, your request enters the review queue.
  </Step>
</Steps>

<Tip>
  To help speed up approval, include verifiable public sources that confirm the legitimacy of your request. Examples include announcements from your official X account, official project communications, or APIs hosted on your official domain.
</Tip>

## Review Process

Reviews are typically completed within 2-3 business days, though this may vary.

Once approved:

* Most changes reflect instantly across Jupiter products and APIs
* Some fields (such as descriptions) are cached on the UI and may take up to an hour to refresh

## Rejection and Resubmission

If your request is rejected, you can resubmit after addressing the issues.

A new submission technically requires a new 1,000 JUP fee, since the fee is collected at the time of submission. However, if the rejection was due to a misunderstanding or missing proof, contact support at [support.jup.ag](https://support.jup.ag) before resubmitting. The metadata team can assist without requiring a new payment in those cases.

<Warning>
  Avoid submitting duplicate or spam requests, as this may delay processing.
</Warning>

## Onchain Metadata Sync

For security reasons, Jupiter does not automatically sync metadata changes from onchain sources after a token has been verified. All changes must go through this manual review process to ensure legitimacy.

If you want Jupiter to pull the latest onchain metadata for your token, submit a request through the [same form](https://verified.jup.ag/metadata).

## Check Your Request Status

You can track the progress of your request on the [Submissions page](https://verified.jup.ag/metadata).