Solana Rent by Account Type: Reserve Table for Common Accounts
Pricing and capability evidence checked September 24, 2026.
Every Solana account must hold a minimum amount of SOL for the data it stores. The amount follows one formula, but the inputs differ by account type and the per-byte rate is currently falling in stages. This page puts the common account types side by side so you can see what each one requires today, what it required before, and what it would require after the final proposed step.
How is Solana rent calculated?
Solana rent is a refundable minimum balance: (128 + data bytes) × lamports per byte. On September 24, 2026, mainnet returned values matching 5,080 lamports per byte, so a 165-byte token account needed 0.001488440 SOL and an empty wallet address needed 0.000650240 SOL.
The 128 is fixed overhead that every account pays for, including a plain wallet with no data. The data length depends on the program that owns the account. A classic token account always stores 165 bytes, while a Token-2022 account or an NFT metadata account can vary.
The rate is set by the network. SIMD-0437 lowers it from 6,960 to 696 lamports per byte through five independent steps, tracked on the Solana reduced-rent page. Our rent reduction explainer covers the rollout itself; this page is the lookup table.
Checked September 24, 2026 at 22:43 UTC: finalized mainnet getMinimumBalanceForRentExemption calls returned 650,240 lamports for 0 bytes and 1,488,440 lamports for 165 bytes, consistent with step 2 at 5,080 lamports per byte. Solana lists steps 3, 4, and 5 as expected in Agave 4.4 in November 2026. Re-check before relying on any column as current.
What is the rent for each Solana account type?
Data lengths below were confirmed against live mainnet accounts or the owning program's published layout. SOL amounts are the calculated rent-exempt minimum for that length.
| Account type | Data bytes | Legacy (6,960) | Live check (5,080) | Final step (696) |
|---|---|---|---|---|
| Wallet (System Program account, no data) | 0 | 0.000890880 SOL | 0.000650240 SOL | 0.000089088 SOL |
| Durable nonce account | 80 | 0.001447680 SOL | 0.001056640 SOL | 0.000144768 SOL |
| Metaplex pNFT token record | 80 | 0.001447680 SOL | 0.001056640 SOL | 0.000144768 SOL |
| Classic token mint | 82 | 0.001461600 SOL | 0.001066800 SOL | 0.000146160 SOL |
| Classic SPL token account | 165 | 0.002039280 SOL | 0.001488440 SOL | 0.000203928 SOL |
| Token-2022 account, immutable owner only | 170 | 0.002074080 SOL | 0.001513840 SOL | 0.000207408 SOL |
| Stake account | 200 | 0.002282880 SOL | 0.001666240 SOL | 0.000228288 SOL |
| Master edition, original allocation | 282 | 0.002853600 SOL | 0.002082800 SOL | 0.000285360 SOL |
| Token multisig | 355 | 0.003361680 SOL | 0.002453640 SOL | 0.000336168 SOL |
| Metaplex metadata, maximum allocation | 679 | 0.005616720 SOL | 0.004099560 SOL | 0.000561672 SOL |
The rows are sorted by size, not by how often you will see them. Every token you have ever received leaves a classic SPL or Token-2022 token account behind, so those two rows are the ones to multiply by your count of empty accounts.
Which account types vary in size?
Three kinds of account do not have one fixed length, which is why a single table row can never be a universal quote for them.
Token-2022 accounts. Extensions are appended after the classic layout. An associated token account created by Token-2022 normally carries the immutable-owner extension, which brings it to 170 bytes. Mints that enable extra account-level extensions make each holder's account larger: we observed 179-byte accounts that also carry pausable and transfer-hook state. The Token-2022 extensions guide explains how to inspect these.
Token-2022 mints. A mint with several extensions can be far larger than the 82-byte classic mint. The PYUSD mint, for example, used 866 bytes in our check, which works out to 0.005049520 SOL at the live rate. That deposit belongs to the mint, not to the people holding the token.
Metaplex NFT accounts. 679 bytes is the maximum metadata allocation, and 282 bytes the original master edition allocation. Many existing accounts have since been resized to fit what they actually store. In our sample, resized metadata accounts used 607 bytes and resized master editions used 20 bytes. Always read the live data length before estimating what an NFT burn returns.
| Variable example from our check | Data bytes | Live check (5,080) |
|---|---|---|
| Token-2022 account with extra extensions | 179 | 0.001559560 SOL |
| Resized Metaplex metadata | 607 | 0.003733800 SOL |
| Resized master edition | 20 | 0.000751840 SOL |
| PYUSD Token-2022 mint | 866 | 0.005049520 SOL |
Compressed NFTs do not appear in any of these tables. They have no individual token account, metadata account, or edition account, so there is no per-asset deposit at all. That is why burning a compressed NFT returns zero SOL.
How does each rent step change the most common accounts?
Each SIMD-0437 step multiplies the same 128 + data bytes by a lower rate. A classic token account falls from 0.002039280 SOL under the legacy setting to 0.000203928 SOL at the final proposed step, a 90% reduction, if every step activates.
| Step | Lamports per byte | Wallet (0 bytes) | SPL token account (165) | Token-2022 account (170) |
|---|---|---|---|---|
| Legacy | 6,960 | 0.000890880 SOL | 0.002039280 SOL | 0.002074080 SOL |
| Step 1 | 6,333 | 0.000810624 SOL | 0.001855569 SOL | 0.001887234 SOL |
| Step 2 | 5,080 | 0.000650240 SOL | 0.001488440 SOL | 0.001513840 SOL |
| Step 3 | 2,575 | 0.000329600 SOL | 0.000754475 SOL | 0.000767350 SOL |
| Step 4 | 1,322 | 0.000169216 SOL | 0.000387346 SOL | 0.000393956 SOL |
| Step 5 | 696 | 0.000089088 SOL | 0.000203928 SOL | 0.000207408 SOL |
A lower rate reduces what a new account must hold. It does not move SOL out of accounts that already exist. An older account created under the legacy setting still holds its original balance until someone closes it or withdraws the surplus.
What does the wallet row mean for your own address?
Your main wallet is a System Program account with no data. Its row is the smallest balance the address can hold while still existing: the account must stay at or above that minimum or go to exactly zero. Solana's account runtime documentation states that a fee payer cannot end up between zero and the rent-exempt minimum.
That is why a transfer that would leave your wallet above zero but below that minimum is rejected. It is also why sending SOL to a brand-new address fails if the amount is below the wallet row for the current step.
Which of these deposits can you actually recover?
Knowing the size of a deposit is only half the question. The other half is who has authority to release it.
| Account type | How the deposit is normally released |
|---|---|
| Classic SPL or Token-2022 token account | Close it once its token balance is zero; the owner receives the lamports |
| Token account you want to keep | Withdraw only the surplus above the live minimum with WithdrawExcessLamports |
| Classic token mint | Only surplus can be withdrawn, and only by its mint authority or the mint itself |
| Stake account | Its withdraw authority withdraws the full balance after deactivation, which closes it |
| Metaplex NFT accounts | Released through a supported burn path; recovery depends on the asset standard |
| Wallet | It is your spendable SOL; sending everything out reduces the address to zero |
Sol Incinerator automates the most common rows. Fun Mode closes empty token accounts and withdraws eligible excess rent from accounts you keep, while Pro Mode adds burning for tokens and NFTs you no longer want. The v2 cleanup fee is 2% of the live reclaimable lamports, and the transaction preview shows the exact amount before you sign.
Sol Incinerator
Scan your wallet to see which account deposits you can recover at today's rent rate.
Related Reading
Frequently Asked Questions
How much rent does a Solana token account cost?
A classic 165-byte token account needs 0.001488440 SOL at the 5,080 lamports-per-byte setting observed on mainnet on September 24, 2026. It needed 0.002039280 SOL under the legacy setting. The deposit is refundable when the empty account is closed, and later rent steps lower the requirement further.
How is Solana rent calculated for an account?
The rent-exempt minimum is 128 bytes of fixed overhead plus the account's data length, multiplied by the current lamports-per-byte setting. Divide the result by 1,000,000,000 to convert lamports to SOL. Because the setting is changing in steps, query the live value instead of copying one number.
Why do Token-2022 accounts cost more rent?
Token-2022 accounts append extension data after the classic 165-byte layout. A standard Token-2022 associated token account with only the immutable-owner extension uses 170 bytes, and accounts with more extensions use more. Each extra byte adds the same per-byte charge as the rest of the account.
Do NFT metadata accounts always use 679 bytes?
No. 679 bytes is the maximum Metaplex metadata allocation, but many existing metadata and master edition accounts have been resized to fit their actual contents. In our sample, resized metadata used 607 bytes and a resized master edition used 20 bytes, so check the live account length.