> 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/token/burn-tokens.md). # Burn Solana Tokens From One or Many Wallets [Burn Tokens](https://j.tools/en/tools/burn-tokens) permanently destroys token balances on-chain and lowers the circulating supply. Scan a connected wallet or paste several private keys against a single mint, choose how much to burn per row, and run the whole list from one terminal. It works on classic [SPL tokens and Token-2022](/concepts/spl-vs-token2022.md), so LP tokens and newer mints are covered too. ## What it is Burn Tokens is a batch burn terminal. Most token interfaces destroy one balance at a time. This tool lines up many rows at once, across a single wallet or up to sixteen wallets, and burns them in sequence so you do not have to repeat the same transaction by hand. Burning is also not the same as capping or cleanup. [Revoke Mint](/tools/secure/revoke-mint.md) stops new tokens from ever being minted but leaves the current supply alone, and [Close Account](/tools/utilities/close-account.md) reclaims rent from a token account you have already emptied. Burning destroys tokens that exist today. They solve different problems, and you often use them together. ## How it works (under the hood) A burn is a single instruction in the SPL Token program (and its Token-2022 equivalent for newer mints). When the instruction runs, it subtracts the amount you chose from your token account and decreases the mint's total supply by the same amount. The tokens are not moved to another wallet or to a dead address. They stop existing on-chain, which is why a burn permanently lowers circulating supply. You can only burn tokens you hold. The burn instruction acts on your own token account and is authorized by that account's owner, which is the wallet that signs. There is no separate "burn authority" to hold; if the tokens are in your account and your wallet signs, the burn is valid. For each row, the tool builds the burn against the correct token program (classic SPL or Token-2022, detected per account) so the right instruction is used. ## When to use it * You run a deflationary token and want a supply cut recorded on-chain. * You are clearing dust or inactive balances across one wallet or many. * You are burning LP tokens after closing out a position with [Liquidity](/tools/liquidity/liquidity-add-remove.md). The terminal can filter to LP tokens only. * You hold Token-2022 tokens, not just classic SPL, and need a burn that handles both. ## Before you start * A connected wallet. Wallet Scan burns straight from it. Multi Wallet mode signs each row with its own pasted key, but the run still refuses to start until a wallet is connected. * Token balances to burn. Burning is permanent, so double-check the mint before you run. * Enough SOL in each signing wallet for the per-transaction network fee. Burning itself carries no platform fee; the [Fee schedule](/reference/fee-schedule.md) covers the rest of the tools. {% hint style="danger" %} Burning is final. It removes existing balances and lowers circulating and total supply. There is no recovery, no reversal, and no support ticket that brings the tokens back. {% endhint %} You pick one of two sourcing modes: * **Wallet Scan** reads the wallet connected in the top bar. Set an optional Target Mint to narrow the scan to a single token, or leave it open to load everything the wallet holds. * **Multi Wallet + Single CA** takes private keys pasted one per line, all targeting the same mint. A Target Mint is required here, and each pasted key's owner must actually hold that token. This mode is capped at 16 wallets, and duplicate or invalid key lines are flagged and block the scan until you fix them. {% hint style="warning" %} Multi Wallet mode asks you to paste raw private keys into the page. Keys are validated and signed locally in your browser, but pasting raw keys is still a sensitive action. Only do this with wallets you control and treat as disposable. Never paste keys you cannot afford to expose. {% endhint %} ## Step by step {% stepper %} {% step %} ### Pick a mode Choose Wallet Scan to burn from the connected wallet, or Multi Wallet + Single CA to burn from several wallets against one mint. In Multi Wallet mode, set the Target Mint with the token selector first. {% endstep %} {% step %} ### Choose a burn mode Select Full Burn to clear the whole balance per row, Partial Burn to set a percentage, or Specific Burn to set a fixed token amount. A specific amount is capped to each row's available balance. {% endstep %} {% step %} ### Scan wallet tokens Optionally set a Target Mint to filter, then run the scan. Both classic SPL and Token-2022 accounts are loaded. Each row shows the wallet, the token, its available balance with a USD estimate, and the planned burn. {% endstep %} {% step %} ### Select the rows Review the list and tick the rows you want. Use Only LP Tokens to filter, plus Select All and Clear Selection for bulk control. Only selected rows with a planned burn above zero will run. {% endstep %} {% step %} ### Execute the burn Click Execute Burn. Rows run one by one. If a selected row's planned burn is worth more than $5, a confirmation dialog asks you to type the word "burn" before it proceeds. Rows with no USD price never trigger that check, so a token the price feed does not cover goes through without the prompt. {% endstep %} {% step %} ### Confirm in your wallet Each burn is signed by its source, the connected wallet in Scan mode or the row's key in Multi Wallet mode, then confirmed on-chain. Watch the per-row status as it works. Use Retry Failed to re-run only the rows that did not go through. {% endstep %} {% endstepper %} [**Open Burn Tokens in the app →**](https://j.tools/en/tools/burn-tokens) {% hint style="info" %} **About wallet warnings.** Some tools bundle several instructions into one transaction, for example creating a token and its metadata together. Phantom can show a caution banner for these transactions. The banner is expected here and does not mean something is wrong. Read what you are signing, then approve. {% endhint %} ## The options, explained * **Mode:** Wallet Scan reads the connected wallet. Multi Wallet + Single CA burns from pasted keys against one mint, capped at 16 wallets. * **Burn mode:** Full burns the whole balance, Partial burns a percentage, Specific burns a fixed amount capped to each row's balance. * **Target Mint (CA):** Optional in Wallet Scan to filter the scan. Required in Multi Wallet mode. Picked with the token selector. * **Partial percent:** The percentage applied to each row's balance when burn mode is Partial. * **Specific amount:** The fixed token amount applied to every selected row when burn mode is Specific. * **Only LP Tokens:** Filters the list to rows detected as LP tokens. Detection starts from your on-chain LP positions and an on-chain LP mint check, with name-and-symbol matching as a fallback. * **Row checkbox:** Selects a row for the run. Only selected rows with a planned burn above zero are executed. {% hint style="info" %} You can deep-link a mint into this tool. The [My Pools](/tools/liquidity/my-pools.md) view's "Burn LP" button opens Burn Tokens with the LP mint already filled in, so the row is ready to scan and select. {% endhint %} ## Fees and costs {% 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 %} **Current platform fee: none.** Burning is free on J Tools. The summary above the Execute button counts the selected wallets, the rows, the planned burn and its USD value, and how many transactions the run will send. There is no fee line because there is no fee; the only cost is the Solana network fee on each transaction. | Cost | Amount | | -------------------- | ---------------------------------------------- | | J Tools platform fee | Free | | Solana network fee | about 0.000005 SOL per row, paid to validators | Each burn pays the standard Solana network fee, about 0.000005 SOL per transaction. Burns run one per row, so a 20-row run signs and pays 20 times. Burning empties the token account but never closes it, so the \~0.00204 SOL rent held in that account stays locked until you run [Close Account](/tools/utilities/close-account.md). ## Security and custody Multi Wallet mode is the only part of this tool that touches a raw private key. Rotate any wallet whose key you paste here, and keep long-term holdings in Wallet Scan mode, where you sign through your wallet adapter and no key is ever typed into the page. ## Common mistakes and troubleshooting * **Nothing loaded after a scan.** The wallet holds no balance for that mint, or your Target Mint filter excluded everything. Clear the filter and scan again. * **Invalid private key line.** A pasted key is malformed or duplicated. The flagged lines block the scan. Fix or remove them, then rescan. * **A row failed.** The transaction was rejected, expired, or that wallet ran out of SOL. Use Retry Failed to re-run only those rows. For the full list, see the [Error codes reference](/reference/error-codes.md). ## Related tools {% content-ref url="/pages/dDKMIJDsaV6TyBZPgRLH" %} [Revoke Mint Authority](/tools/secure/revoke-mint.md) {% endcontent-ref %} {% content-ref url="/pages/gbx1RbByQOVKZzt0PQkP" %} [Make a Token Immutable](/tools/secure/make-immutable.md) {% endcontent-ref %} {% content-ref url="/pages/tcfZtvMT2fZ8MMKcMlpF" %} [Close Token Accounts](/tools/utilities/close-account.md) {% endcontent-ref %} {% content-ref url="/pages/ABVX2mBQDoCv7DEdVmKp" %} [Multi Sender and Airdrop](/tools/wallets/multi-sender.md) {% endcontent-ref %} {% hint style="success" %} **J Tools is non-custodial.** We never store or transmit your private keys and never ask for your seed phrase. Every transaction is signed in your own browser, and nothing about a key ever reaches our servers. A few multi-wallet tools do let you paste private keys for throwaway hot wallets, which stay in your browser tab and are used only to sign locally. Never paste a key tied to long-term holdings, and if a page ever asks for your seed phrase, stop and close it. {% 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/token/burn-tokens.md?ask=&goal= ``` `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.