Solana does not have one fixed rent cost for every account. The minimum balance required for rent exemption depends on the amount of data an account stores and the network's current rent parameters.
Historically, a basic 165-byte SPL Token Account required 2,039,280 lamports, or 0.00203928 SOL, under Solana's previous rent parameters. This is why approximately 0.002 SOL per token account became a commonly quoted figure.
However, Solana began reducing its rent parameters in 2026. The rent-exempt minimum for the same account size can now change as the phased reduction progresses, so 0.00203928 SOL should no longer be treated as the current fixed cost of a standard token account.
- Solana rent is not a universal flat fee. The rent-exempt minimum depends on account data size and the network's current
lamports_per_byteparameter. - The current calculation can be expressed as
(128 + data size) × lamports_per_byte. - Before Solana's 2026 rent reduction began,
lamports_per_bytewas 6,960. - A basic 165-byte SPL Token Account therefore historically required 2,039,280 lamports, or 0.00203928 SOL.
- SIMD-0437 is reducing
lamports_per_bytefrom 6,960 toward 696 through five separate activation steps. - As rent parameters decrease, the same account size requires fewer lamports to remain rent-exempt.
- The lamports held for account storage remain refundable when an eligible account is closed.
- Applications should query current network data rather than hard-code a historical rent amount.
How is Solana rent calculated?
Solana accounts store state on-chain. Accounts that store data generally need to maintain a minimum balance of lamports to remain rent-exempt.
The minimum depends on two primary inputs:
- the effective size of the account; and
- the network's current
lamports_per_byteparameter.
The calculation can be expressed as:
min_balance = (128 + data_size) × lamports_per_byte
Where:
128
→ fixed account storage overhead
data_size
→ amount of account data in bytes
lamports_per_byte
→ current network rent parameter
The result is the minimum number of lamports required for that account size under the applicable network parameters.
Applications normally do not need to hard-code this calculation. Solana RPC provides getMinimumBalanceForRentExemption, which can return the current minimum balance required for a specified account data size.
What was the old Solana rent rate?
Before Solana's 2026 rent reduction began, the effective lamports_per_byte value was:
6,960 lamports per byte
For a basic 165-byte SPL Token Account, the calculation was:
(128 + 165) × 6,960
= 293 × 6,960
= 2,039,280 lamports
Which equals:
0.00203928 SOL
This is the source of the familiar 0.002 SOL or 0.00204 SOL per token account figure.
It was accurate for a basic 165-byte token account under the previous rent parameters, but it should now be treated as a historical reference, not a permanent current price.
Is a standard token account still 0.00203928 SOL?
Not as a fixed current requirement.
Solana began reducing its rent parameters in September 2026 under SIMD-0437.
The proposal reduces lamports_per_byte through five steps:
| Stage | lamports_per_byte | Reduction from original |
|---|---|---|
| Original | 6,960 | — |
| Step 1 | 6,333 | 9% |
| Step 2 | 5,080 | 27% |
| Step 3 | 2,575 | 63% |
| Step 4 | 1,322 | 81% |
| Step 5 | 696 | 90% |
Step 1 became active on Solana Mainnet on September 3, 2026.
The later stages use separate feature gates, so the network should not be treated as if the final 90% reduction became active all at once.
For the rollout details, read Solana Rent Reduction Explained.
How does reduced rent change the cost of a token account?
A basic SPL Token Account remains 165 bytes of account data. What changes is the network parameter multiplied by that account size.
For the same 165-byte account:
Effective size
= 128 + 165
= 293 bytes
Under the previous parameter:
293 × 6,960
= 2,039,280 lamports
= 0.00203928 SOL
Under Step 1:
293 × 6,333
= 1,855,569 lamports
= 0.001855569 SOL
If the final target of 696 becomes active:
293 × 696
= 203,928 lamports
= 0.000203928 SOL
These examples show why account size alone is no longer enough to quote a permanent SOL amount. The calculation also depends on which rent parameter is active on the network.
Why is Solana reducing rent?
The previous rent parameter had remained unchanged for years.
Because the requirement was denominated in lamports rather than tied directly to the real-world cost of validator storage, the economic cost of creating and maintaining account state could change substantially as the market value of SOL changed.
SIMD-0437 lowers the storage deposit required for account state.
The reduction is intentionally divided into multiple feature-gated stages so the network can observe the effect of cheaper account storage on state growth before progressing further.
The proposal also includes safeguards because significantly cheaper account creation could increase demand for on-chain state.
The final target reduces lamports_per_byte from 6,960 to 696, which would represent a 90% reduction from the original rent-exempt minimum for the same account size.
Does every token account require the same rent?
No.
Account size remains one of the main inputs to the rent calculation.
A basic token account under the original SPL Token Program uses 165 bytes of account data, but not every token account has the same layout.
Token-2022 supports extensions that can require additional account space.
A larger account produces a larger effective size:
128 + larger data_size
and therefore a larger rent-exempt minimum under the same lamports_per_byte parameter.
The general relationship remains:
larger account
→ more on-chain data
→ higher rent-exempt minimum
This is why there should not be one universal "token account rent" value applied to every SPL Token and Token-2022 account.
Is the rent amount permanently spent?
No.
Despite the name, the rent-exempt minimum is not a recurring payment that is gradually consumed while a typical account remains open.
The lamports remain held by the account.
A simplified lifecycle looks like this:
| Event | What happens |
|---|---|
| Account is created | Lamports fund its required rent-exempt balance |
| Account remains open | The lamports remain held by the account |
| Rent parameters change | The current minimum requirement may change |
| Account becomes unused | Its lamports can remain in the account |
| Eligible account is closed | Its remaining lamports are transferred to the specified destination |
This is why describing the balance as a refundable storage deposit is often more intuitive than thinking of it as a recurring rental payment.
For more background, see What Is Solana Rent?.
What happens to existing accounts when rent decreases?
An existing account is not automatically debited when the network lowers the rent-exempt minimum.
Suppose an account was funded under an earlier, higher rent requirement.
After the network reduces lamports_per_byte, the same account may need fewer lamports to satisfy its current rent-exempt minimum while still holding its previous balance.
Conceptually:
Account's existing lamports
>
Current rent-exempt minimum
The difference can represent excess lamports.
For supported Token Program and Token-2022 accounts, excess lamports can be withdrawn without closing the account or changing its token balance.
This is different from closing an unused token account and reclaiming all of its remaining lamports.
Read Solana Rent Reduction Explained for more detail.
Why can an old account hold more SOL than a newly created account requires?
Because lowering the rent requirement does not automatically rewrite the balance of every existing account.
For example, an older basic token account may have been funded when the minimum was:
2,039,280 lamports
A newly created account of the same size may require less under a later rent parameter.
The older account can still retain its original balance unless an authorized operation moves some or all of those lamports.
This means two accounts with the same data size can temporarily hold different amounts of SOL even though they are subject to the same current rent-exemption requirement.
The account's actual lamport balance and its current required minimum should therefore be treated as separate values.
Why shouldn't you multiply the number of accounts by 0.002 SOL?
Because 0.002 SOL is no longer a reliable current per-account estimate.
Even before reduced rent, account balances could differ because of account size, Token-2022 extensions, or additional lamports.
The phased rent reduction introduces another variable: accounts may have been created or funded under different rent parameters.
For example:
Wallet A
├── older basic token account
├── older Token-2022 account
├── newer basic token account
└── account with additional lamports
There is no reason to assume all four contain the same amount.
What determines whether account SOL can be reclaimed?
Holding lamports does not automatically mean an account should or can be closed.
For ordinary token-account cleanup, relevant factors include:
- token balance;
- account state;
- token program;
- account owner;
- configured close authority;
- Token-2022 extensions;
- whether the account is a native Wrapped SOL account; and
- whether you still need the account.
Closing an eligible token account transfers its remaining lamports to the specified destination and removes the account.
Reduced rent also creates another possibility: a supported account may contain excess lamports that can be withdrawn while leaving the account open.
These are different account-management operations and should not be treated as interchangeable.
Solana rent vs transaction fees
Solana rent and transaction fees are different concepts.
| Cost | Purpose | Potentially refundable? |
|---|---|---|
| Rent-exempt balance | Maintains the minimum balance required for account storage | Yes, remaining lamports can be recovered when an eligible account is closed |
| Network transaction fee | Pays for transaction processing | No |
| Priority fee | Optional additional fee for transaction priority | No |
| Third-party service fee | Pays for an application or service | Depends on the service; normally no |
Reduced rent changes the first category. It does not mean Solana network transaction fees or third-party service fees are reduced by the same percentage.
This distinction matters when calculating the net SOL change after reclaiming account balances.
How can developers check the current Solana rent?
Applications should query the network rather than depend on a hard-coded historical constant.
Solana provides the RPC method:
getMinimumBalanceForRentExemption
Given an account data size, it returns the minimum lamport balance required for rent exemption according to the network's current parameters.
Conceptually:
Account data size
↓
getMinimumBalanceForRentExemption
↓
Current required minimum
This becomes particularly important during a phased rent reduction because the correct result can change when a new feature gate activates.
For production applications, current network data should be the source of truth.
How can wallet users check the actual reclaimable amount?
Wallet users usually care less about the theoretical minimum and more about the SOL actually held by accounts they may no longer need.
Your Free SOL scans relevant public on-chain data for supported empty token accounts and shows their detected reclaimable balances before you approve a transaction.
A typical process is:
- Connect your Solana wallet.
- Scan for supported eligible empty token accounts.
- Review each account and its detected SOL balance.
- Select the accounts you actually want to close.
- Review the destination, transaction instructions, and applicable fees.
- Approve the transaction through your wallet if everything is correct.
Your Free SOL is non-custodial. Connecting your wallet does not give the application your seed phrase or private key, and transactions still require your authorization.
For the complete process, see How to Reclaim Solana Rent with YourFreeSOL.
Does Solana rent change when SOL's market price changes?
The protocol's rent-exempt requirement is denominated in lamports, not U.S. dollars.
Therefore, two different things can change independently:
Network rent parameter
→ changes the required number of lamports
SOL market price
→ changes the fiat value of those lamports
For example, even if the required lamport amount did not change, its dollar value would rise or fall with the market price of SOL.
Conversely, Solana's reduced-rent upgrade changes the required lamport amount independently of SOL's market price.
This is why rent should generally be discussed in lamports or SOL rather than as a fixed dollar cost.
Can you get the entire account balance back?
When an eligible token account is closed, its remaining lamports are transferred to the destination specified by the close instruction.
That amount does not have to equal the account's current rent-exempt minimum.
An account can contain:
exactly the current minimum
or:
more than the current minimum
depending on its history and current balance.
This distinction has become more important as rent decreases because an older account can hold more than it currently needs for rent exemption.
Transaction fees and any applicable service fees are separate from the account's lamport balance.
For account closure, read How to Reclaim Solana Rent with YourFreeSOL.
The simple answer
Solana rent does not have one fixed price.
The rent-exempt minimum for an account depends on:
(128 + account data size) × current lamports_per_byte
Before Solana's 2026 rent reduction began, lamports_per_byte was 6,960. A basic 165-byte SPL Token Account therefore required:
2,039,280 lamports
= 0.00203928 SOL
That historical value is why approximately 0.002 SOL per token account became so widely quoted.
Solana is now reducing lamports_per_byte in phases toward a target of 696, so the minimum required for the same account size can decrease as additional stages become active. (GitHub)
For this reason, 0.00203928 SOL should no longer be treated as the current fixed cost of a standard token account.
Developers should query the current network minimum, while wallet users interested in reclaiming SOL should inspect each account's actual on-chain lamport balance and eligibility.