> For the complete documentation index, see [llms.txt](https://docs.j.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.j.tools/tools/launch/token-clone.md).

# Token Clone

[Token Clone](https://j.tools/en/tools/token-clone) reads any existing Solana SPL or Pump.fun token's public metadata from its mint address, drops it into the creation form, and lets you mint a brand-new token from it. You edit whatever you want first. The result is always a separate mint with its own contract address, never a copy of the original's liquidity or holders. If the terms here feel unfamiliar, the [Glossary](/getting-started/glossary.md) covers mint, metadata, and authority in one place.

{% hint style="warning" %}
**About fees.** Every action has two costs: the Solana **network fee** paid to validators, and the **J Tools platform fee**. The platform fee always shows in the app before you confirm, and nothing is charged until you sign. Fees can change over time, so trust the in-app summary rather than a number you saw once.
{% endhint %}

## When to use this

* You want a faster start from a proven token setup instead of retyping every field by hand.
* You are reissuing a token under a new authority because the original mint cannot be recovered.
* You want a sister mint with adjusted authority or supply settings.
* You want to reuse a Pump.fun token's public branding as a template for a new mint.

For the full path from idea to a tradable token, the [Launch a token](/guides/launch-a-token.md) guide walks through each step. If you are starting from a blank form, use [Token Creator](/tools/launch/token-creator.md) instead. To lock a token down after minting, see [Make Immutable](/tools/secure/make-immutable.md). The revoke toggles here map to the three mint, freeze, and update authorities explained in [Authorities](/concepts/authorities.md).

## Before you start

* A connected wallet ([how to connect](/getting-started/quick-start.md)).
* The mint address (CA) of an existing SPL or Pump.fun token you want to clone.
* Enough SOL for the platform fee plus network fees.
* An active RPC connection. Without one, Load fails with a "connection not available" error.

{% hint style="info" %}
Cloning copies **public metadata only**: name, symbol, description, image, socials, decimals, supply, and authority state. It does **not** copy liquidity, holders, or any bonding-curve state from the source token. Whether the source is a classic SPL or a Token-2022 mint, only its visible metadata comes across (see [SPL vs Token-2022](/concepts/spl-vs-token2022.md) for the difference).
{% endhint %}

## Step by step

{% stepper %}
{% step %}

### Open Token Clone and connect

Connect your wallet through the standard wallet source selector. The creation form is the same one Token Creator uses, opened in clone mode.
{% endstep %}

{% step %}

### Paste the source mint and Load

Drop the source token's mint address into the **Source Token Mint (CA)** field and click **Load**. It also auto-loads shortly after you stop typing. The address has to be a valid Solana pubkey (32 to 44 characters).
{% endstep %}

{% step %}

### Let the form fill in

Token Clone reads the on-chain Metaplex metadata and the token's JSON URI, then fills the form with the name, symbol, description, image, website, socials, decimals, supply, and authority state. This step is read-only and never touches private keys.
{% endstep %}

{% step %}

### Edit and set authorities

Change any prefilled field. Set the revoke toggles for mint, freeze, and update authority. If you want a custom or vanity contract address for the new token, enable that option here.
{% endstep %}

{% step %}

### Review and confirm

Check the fee summary, then sign the transaction in your wallet. A brand-new token mints on-chain with its own unique address, separate from the source.
{% endstep %}
{% endstepper %}

[**Open Token Clone in the app →**](https://j.tools/en/tools/token-clone)

{% hint style="info" %}
**About wallet warnings.** Some tools sign more than one thing in a single step, for example creating a token and its metadata together. Phantom can show a caution banner for these multi-step transactions. The banner is expected here and does not mean something is wrong. Read what you are signing, then approve.
{% endhint %}

## The options, explained

| Field                                   | What it does                                                                                                                                                        |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Source Token Mint (CA)                  | The mint address to copy public info from. Paste it and click Load, or wait for the auto-load after you stop typing. Reads on-chain metadata and the JSON URI only. |
| Name                                    | Prefilled from the source token's metadata. Fully editable before minting.                                                                                          |
| Symbol                                  | Prefilled from the source. Editable.                                                                                                                                |
| Description                             | Prefilled from the source JSON if present. Editable.                                                                                                                |
| Image                                   | Prefilled from the source token image. Editable.                                                                                                                    |
| Website / Twitter / Telegram / Discord  | Pulled from source metadata when available. Editable.                                                                                                               |
| Decimals                                | Prefilled from the source mint when it can be resolved. Editable.                                                                                                   |
| Total supply                            | Prefilled from the source. Editable.                                                                                                                                |
| Revoke mint / freeze / update authority | Prefilled to match the source token's resolved authority state when available. Set them yourself if the source authorities cannot be resolved.                      |
| Custom / vanity address                 | Optional. Pick a free custom mint pattern or a paid vanity address for the new token's contract during creation.                                                    |

{% hint style="warning" %}
If the source token's on-chain authorities cannot be resolved, the toggles are not auto-filled and a warning appears. Set the revoke options yourself before you mint.
{% endhint %}

## If something goes wrong

* **Connection not available.** Load needs an active RPC connection. Reconnect and try again.
* **Invalid address.** The mint has to be a valid Solana pubkey, 32 to 44 characters. Double-check what you pasted.
* **Authorities not filled.** The source authority state could not be resolved. The toggles stay blank on purpose; set them manually.
* **Not enough SOL.** Minting needs SOL for the platform fee plus network fees. Top up and retry.

For the full list, see the [Error codes reference](/reference/error-codes.md).

## FAQ

<details>

<summary>Does this give me the same contract address as the source?</summary>

No. The output is always a new, separate mint with its own contract address. It never reuses the source mint and never affects the original token's supply or authorities.

</details>

<details>

<summary>Does cloning bring over liquidity or holders?</summary>

No. Only public, visible metadata gets copied. Liquidity, holders, and bonding-curve state stay with the original token. Your new mint starts empty.

</details>

<details>

<summary>Can I clone a Pump.fun token?</summary>

Yes. Token Clone reads the public metadata of both SPL and Pump.fun tokens, so you can use a Pump.fun token's branding as a starting template for a fresh mint.

</details>

<details>

<summary>Does J Tools see my private key during Load?</summary>

No. Load is read-only. It only reads on-chain metadata and the token's JSON URI, and never requests or touches private keys. You sign the minting transaction yourself in your wallet.

</details>

## Related tools

{% content-ref url="/pages/9r2rW9r83CsCoJpYE8gL" %}
[Token Creator](/tools/launch/token-creator.md)
{% endcontent-ref %}

{% content-ref url="/pages/SZW5Dy4404uBRAQWvGqI" %}
[Vanity Token](/tools/launch/vanity-token.md)
{% endcontent-ref %}

{% content-ref url="/pages/gbx1RbByQOVKZzt0PQkP" %}
[Make Immutable](/tools/secure/make-immutable.md)
{% endcontent-ref %}

{% content-ref url="/pages/gclVFAjMJFchUipqQNOZ" %}
[Update Metadata](/tools/token/update-metadata.md)
{% endcontent-ref %}

{% content-ref url="/pages/QT0nYfDbGpJo4Cm5Tbs6" %}
[Create LP](/tools/liquidity/create-lp.md)
{% endcontent-ref %}

{% hint style="success" %}
**J Tools is non-custodial.** We never hold your private keys and never ask for them. Every transaction is built in your browser and signed by your own wallet. If any page ever asks you to paste a private key, stop, close it, and let us know.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.j.tools/tools/launch/token-clone.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
