> 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/pumpfun-create.md).

# Pumpfun Create

[Pump.fun Create](https://j.tools/en/tools/pumpfun-create) is a single-wallet launchpad for Pump.fun coins. You enter the basics, upload a logo and an optional banner, and the app uploads your metadata to IPFS and builds the on-chain create for you. Signing happens in your browser wallet, so your keys never leave your machine. You can also buy your own first bag in the same transaction. Every launch lands on a `pump`-suffix mint address.

{% 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 to launch a coin on Pump.fun from a single wallet, without juggling the official UI.
* You want a guaranteed `pump`-suffix mint and the option to buy your own first bag in the same transaction.

If you want a launch where several wallets buy the first bags together, look at [Pump.fun Create + Bundle Buy](/tools/launch/pumpfun-create-and-bundle-buy.md) instead. That route leans on [bundles and Jito](/concepts/bundles-and-jito.md) to land every buy in one block. This page is the solo version. New to the terms here? The [glossary](/getting-started/glossary.md) covers mint, bonding curve, and ticker in plain language.

## Before you start

* A connected wallet ([how to connect](/getting-started/quick-start.md)) with enough SOL for the platform fee, any creator buy, the Solana priority fee, and a small network buffer of around 0.01 SOL on top.
* A token logo image, up to 15 MB. PNG, GIF, JPG, JPEG, or WEBP all work. A 1000x1000 square or larger looks best.

{% hint style="info" %}
On top of the J Tools platform fee, you also pay Pump.fun's own creation and curve costs, your optional creator buy amount, and the Solana priority fee. The in-app cost breakdown adds these up against your wallet balance before you sign.
{% endhint %}

## Step by step

{% stepper %}
{% step %}

### Connect your wallet

Connect a wallet in the top bar. The page reads it directly, so the create transaction is signed by the wallet you connect here.
{% endstep %}

{% step %}

### Fill the token basics

Enter the name and ticker, and a short description if you want one. Upload a logo (required) and an optional banner. The name takes up to 32 characters, the ticker up to 10 and must be letters and numbers only.
{% endstep %}

{% step %}

### Add socials and pick your options

Add website, X, Telegram, or Discord links if you have them. Then choose the launch options: buy-on-launch and the amount, and a speed preset. You can also reserve the exact mint address up front.
{% endstep %}

{% step %}

### Review the preview and cost

Check the live preview card and the cost breakdown. It lists the platform fee, your buy, the priority fee, and any address-reservation surcharge, then compares the total to your wallet balance.
{% endstep %}

{% step %}

### Launch

Click Pump launch. The app reserves a `pump`-suffix mint from the server pool, uploads your logo, banner, and metadata JSON to IPFS, reads the live Pump.fun config accounts, and builds the create instruction, plus your buy if you turned that on.
{% endstep %}

{% step %}

### Sign in your wallet

Approve in your wallet. A plain create needs one signature, and a create plus buy needs two. The app submits, waits for confirmation, and then shows a success card with the token address, the transaction, and share links.
{% endstep %}
{% endstepper %}

[**Open Pump.fun Create in the app →**](https://j.tools/en/tools/pumpfun-create)

{% 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                                                                                                                                 |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Name                             | Token display name. Required, 1 to 32 characters.                                                                                            |
| Symbol                           | The ticker. Required, 1 to 10 characters, letters and numbers only. It is uppercased before submit.                                          |
| Description                      | Optional blurb stored in the metadata. Up to 500 characters.                                                                                 |
| Image                            | The logo. Required, uploaded to IPFS, up to 15 MB. A 1000x1000 square or larger is recommended.                                              |
| Banner                           | Optional banner image, uploaded to IPFS, up to 15 MB. 1500x500 (3:1) looks best.                                                             |
| Website / X / Telegram / Discord | Optional social links. Use full `http` or `https` URLs. Saved into the metadata.                                                             |
| Buy on launch                    | Your wallet buys the first bag in the same transaction. SOL buys must meet the program minimum shown in the tool.                            |
| Buy amount                       | The size of that first buy, in SOL. Must be above zero when the buy is on.                                                                   |
| Speed                            | The compute-unit price that sets landing speed. Presets are Normal, Fast (default), and Turbo, plus a Custom budget.                         |
| Pregenerate token address        | Reserves and previews the exact `pump`-suffix mint before you sign, for a surcharge. Every launch already gets a `pump` suffix without this. |

{% hint style="info" %}
Every launch already lands on a `pump`-suffix mint pulled from a server pool. The Pregenerate option only lets you see and lock the exact address before signing, at a small extra cost.
{% endhint %}

## If something goes wrong

* **Initial buy too small.** SOL buys must meet the program minimum shown in the tool. Raise the amount, or turn the buy off.
* **Address pool empty.** The `pump`-suffix mint comes from a server pool. If it runs dry the launch stops with `VANITY_CA_POOL_EMPTY`. Try again shortly.
* **Not enough SOL.** Top up to cover the platform fee, your buy, the priority fee, and the network buffer, then retry.

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

## FAQ

<details>

<summary>What's the difference between this and Create + Bundle Buy?</summary>

This page launches from one wallet, with an optional buy from that same wallet. [Pump.fun Create + Bundle Buy](/tools/launch/pumpfun-create-and-bundle-buy.md) lets several wallets take the first bags together at launch.

</details>

<details>

<summary>Does this create a liquidity pool?</summary>

No. It launches your coin on the Pump.fun bonding curve only. There is no AMM or DEX pool here. Once your coin graduates off the curve, you can look at the [liquidity tools](/tools/liquidity.md), or read up on [DEXes and liquidity](/concepts/dexes-and-liquidity.md) to see what comes after the curve.

</details>

<details>

<summary>Why does Phantom show a caution banner?</summary>

A launch signs more than one thing at once, for example the create and your first buy. Phantom can flag multi-step transactions with a caution banner. It is expected here. The page already uses the official Pump.fun address lookup table and the live fee-recipient list to keep these warnings to a minimum. Read what you are signing, then approve.

</details>

<details>

<summary>Does J Tools hold my token or keys?</summary>

No. The token is created straight to your wallet, and every signature happens in your wallet, in your browser.

</details>

## Related tools

{% content-ref url="/pages/OUTARQ7CwmWSmwdYM3f6" %}
[Pump.fun Create and Bundle Buy](/tools/launch/pumpfun-create-and-bundle-buy.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/ABVX2mBQDoCv7DEdVmKp" %}
[Multi Sender](/tools/wallets/multi-sender.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/gbx1RbByQOVKZzt0PQkP" %}
[Make Immutable](/tools/secure/make-immutable.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/pumpfun-create.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.
