Recommended Free Tools
Estimate XRP for an XRPL account in two parts: calculate the account’s reserve floor from the live base reserve and its OwnerCount, then add the fees for the transactions you actually plan to submit. The reserve is a balance requirement tied to the account and its ledger objects; transaction fees are XRP destroyed by the protocol. They are not interchangeable.
On Mainnet, XRP Ledger documentation checked on October 16, 2026 lists a 1 XRP base reserve and a 0.2 XRP incremental reserve for each counted owned object. Those settings can change through fee voting, and other networks may use different values. Query the target network immediately before funding or signing.
As an Amazon Associate I earn from qualifying purchases.
The calculation in one line
Use this formula for the reserve floor:
Reserve floor = current base reserve + (account OwnerCount × current incremental owner reserve)
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Then estimate a practical balance:
Practical balance = reserve floor + fees for planned transactions + any optional safety margin
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
The last two additions are planning choices, not a protocol-defined reserve. A fee can consume XRP that was helping the account meet its reserve, so an account should hold enough for both its required floor and its intended activity.
Why reserves and fees are different
Reserves lock a balance requirement
Every account needs a base reserve. Ledger objects owned by that account generally add an incremental reserve. The object count comes from the account’s ledger state, not from the number of transactions you have sent or the number of tokens you hold. XRP Ledger documentation lists checks, deposit preauthorizations, escrows, NFT offers and pages, offers, oracles, payment channels, signer lists, tickets and trust lines among objects that can count. See the official Reserves documentation.
Fees are permanently destroyed
A transaction’s signed Fee field specifies how much XRP is paid. The amount is not transferred to a validator or another account. As the Transaction Cost documentation states: “The transaction cost is not paid to any party: the XRP is irrevocably destroyed.” Once a transaction is signed, changing its fee invalidates the signature.
Free tools Windows power users keep installed
One-click scans. No signup required.
How the two interact
The reserve is not a separate escrow account. The Reserves page explains: “The XRP reserve is not dormant, however. You can use your reserves to pay transaction fees.” If fees reduce the balance below the reserve, the account remains on-ledger, but its capabilities are restricted (see the recovery section below).
Step 1: Read the account’s live OwnerCount
Call account_info against a server connected to the network you intend to use. Request a validated ledger state and read account_data.OwnerCount. A typical JSON-RPC request is:
{
"method": "account_info",
"params": [{
"account": "r...",
"ledger_index": "validated"
}]
}Use the returned account data rather than trying to count objects manually. The value is the protocol’s current count for reserve-bearing objects. Save the ledger index or server response time with your calculation so you can explain which state was used.
Objects that can change the count
- Trust lines, offers and payment channels can add owner objects.
- Escrows, checks, deposit preauthorizations, signer lists, tickets and oracle entries can add objects.
- NFTs are stored in NFT pages. A page can contain up to 32 NFTs, so reserve growth depends on page allocation, not simply one increment per NFT. Packing can vary as NFTs are created or burned.
- The first two trust lines have a special exception when a newly funded account has only the base reserve. Do not apply that exception to other object types or to accounts that do not meet its conditions.
Because objects can be created or deleted between your query and a transaction, query again when a funding decision is time-sensitive.
Step 2: Query the reserve settings for the intended network
Reserve values are network settings. Query server_info or server_state from a server on the same network as the account.
Rank #2
- Proven security at scale: Over 9 years and millions of cards issued with no known remote hacks, while military‑grade EAL6+ security keeps your private keys locked inside the chip. Your cryptocurrencies stay strongly protected from online attackers.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 14,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Smart backup: Use your second Tangem Wallet as your Backup keys with end‑to‑end encryption; no more papers, pictures. If one card is lost, the remaining can still restore full access, with an optional seed phrase available for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
Using server_info
The validated ledger section identifies validated_ledger.reserve_base_xrp and validated_ledger.reserve_inc_xrp. These values are already expressed in XRP. The request shape is:
{
"method": "server_info",
"params": [{}]
}Using server_state
Some deployments expose validated_ledger.reserve_base and validated_ledger.reserve_inc instead. Those fields are integer drops. Convert them with the protocol’s fixed unit relationship:
1 XRP = 1,000,000 drops
For example, 1,000,000 drops is 1 XRP and 200,000 drops is 0.2 XRP. Do not mix an XRP field with a drops field without converting units first.
Why you must query instead of hard-coding
Fee voting can change the reference fee and reserve settings. The documented recommended settings are 10 drops for the reference fee, 1,000,000 drops for the base reserve and 200,000 drops for the owner reserve, but the live ledger values govern your calculation. Mainnet and test or private networks can differ. The fee-voting rules are described at Fee Voting, and the ledger’s fee settings are defined in the FeeSettings reference.
Step 3: Calculate the reserve floor
Insert the queried values and OwnerCount into the formula. With the documented Mainnet figures checked October 16, 2026, an account whose OwnerCount is 3 has:
| Component | Calculation | Amount |
|---|---|---|
| Base reserve | 1 XRP | 1 XRP |
| Incremental reserve | 3 × 0.2 XRP | 0.6 XRP |
| Reserve floor | 1 + 0.6 | 1.6 XRP |
This 1.6 XRP is the balance floor for the queried state. It does not include transaction fees, and it can change if the account creates or deletes objects or if the network changes its reserve settings.
Step 4: Estimate the fees for each planned transaction
Do not multiply every transaction by the reference minimum. Call the fee method shortly before signing. The API reports current fee information, including the base reference, open-ledger, median and minimum values. The open-ledger value is the useful basis when you want a transaction to be considered for the current open ledger. Consult the fee method reference.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems{
"method": "fee",
"params": [{}]
}The 10-drop figure
Documentation lists 10 drops (0.00001 XRP) as the standard reference transaction minimum before load scaling. That is a reference, not a universal promise that every transaction will cost exactly 10 drops. Network load can scale the required fee, and some transaction types have special costs. Treat 10 drops as a baseline only when the live fee response and transaction type support it.
Rank #3
- UNPARALLELED SECURITY: Protect your assets with Trezor Safe 5's NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency.
- EFFORTLESS NAVIGATION: Experience seamless crypto management with the vibrant color touchscreen, designed for intuitive and user-friendly interactions.
- ENHANCED USER EXPERIENCE: Enjoy tactile confirmation with Trezor Touch Haptic Engine, making each interaction precise and engaging.
- SUPPORTS 1000s OF COINS & TOKENS: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet.
- EASY ASSET MANAGEMENT: Monitor and transact seamlessly with Trezor Suite, our user-friendly desktop and mobile app
Build a transaction budget
List every operation you expect to submit, select the fee basis for each, and add the amounts in drops before converting to XRP. A hypothetical plan of three ordinary transactions at the 10-drop reference minimum would be 30 drops, or 0.00003 XRP, before any load scaling. If the fee method returns a higher open-ledger value, use that value instead. Label examples as estimates; never present a baseline as a guaranteed inclusion fee.
Transaction types that need special treatment
The official transaction-cost rules include nonstandard cases. Use the transaction-specific calculation rather than assuming 10 drops for all operations.
| Transaction situation | How to budget it |
|---|---|
| Ordinary transaction at reference conditions | Start with the live reference or minimum fee, then check load scaling. |
| Key reset transactions | Some key-reset transactions have zero transaction cost under the protocol rules; confirm the exact type before budgeting. |
| Multi-signature transactions | Costs are higher than a single-signature transaction. Include the required signer-related cost and query the current fee conditions. |
EscrowFinish |
Cost depends on the size of the fulfillment. A larger fulfillment requires a larger fee. |
AccountDelete and AMMCreate |
These have higher protocol costs than the ordinary reference transaction. Use the current transaction-cost rules. |
Transaction fees are specified in the signed transaction’s Fee field. Check the fee immediately before signing; if load is unusually high, waiting can be cheaper than signing an inflated fee. After signing, changing Fee requires signing again.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Worked planning example
Account with three owned objects
Suppose a validated account_info response reports OwnerCount = 3, and server_info reports a 1 XRP base reserve and a 0.2 XRP owner increment. The reserve floor is 1.6 XRP.
Now suppose the planned activity is two ordinary payments and one offer cancellation. If the live fee response supports a 10-drop fee for each operation, the fee budget is 30 drops (0.00003 XRP). The practical balance estimate is therefore 1.60003 XRP before any optional margin. If the open-ledger fee is higher, replace 10 drops with that queried amount. If one operation is a multisigned transaction or another special case, calculate its protocol-specific cost instead of reusing the ordinary fee.
What this example does not prove
- It does not establish that future fees will remain 10 drops.
- It does not include a new object created by one of the transactions. If a payment or offer creates an object, the post-transaction
OwnerCountmay increase and so will the reserve floor. - It does not prescribe a personal buffer. Add one only as an explicitly chosen risk margin.
What happens if the balance falls below reserve?
An account is not deleted merely because fees reduce its balance below the reserve. It remains on-ledger, but it cannot send XRP to other accounts or create new reserve-increasing objects while below the required reserve. It can still submit transactions that do not perform those actions if it has enough XRP to pay the fee.
Recovery normally means adding XRP until the account again satisfies the current reserve and has enough for the intended fee. Re-query OwnerCount and network settings first; the required amount may have changed. Because the reserve is not a permanently inaccessible deposit, deleting eligible objects can release some XRP, and deleting an account can recover some XRP under the protocol’s account-deletion rules. Deletion itself has a transaction cost and eligibility requirements, so do not treat it as an instant withdrawal.
Networks, fee voting and timestamps
Always record three pieces of context with an estimate:
Rank #4
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
- Network: Mainnet, a test network or a private network.
- Ledger state: the validated ledger index or response time used for
OwnerCountand reserve values. - Fee basis: minimum, median, base or current open-ledger fee, plus any transaction-specific rule.
The 1 XRP and 0.2 XRP figures in this guide are documented Mainnet settings checked October 16, 2026, not a promise for every network or a permanent protocol constant. Validators can vote on fee and reserve settings. A calculation that omits its network and timestamp is not reproducible.
Sponsored reserves and fees
XRPL supports sponsored fees and reserves. Sponsorship can assign responsibility for reserve or fee requirements to a sponsor, but it does not transfer XRP into the sponsored account. If sponsorship applies, identify which party is responsible for each object and fee, then adjust the individual account’s funding estimate. Read the rules at Sponsored Fees and Reserves.
Comparing two XRP funding estimates
Two estimates are comparable only when they use the same assumptions. Check these dimensions:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Comparison point | Question to ask |
|---|---|
| Network and time | Were reserve values queried from the same network and at a similar ledger time? |
| Account state | Do both use the same OwnerCount and the same object situation, including NFT pages? |
| Transactions | Do they include the same transaction types, number of signatures and special conditions? |
| Fee basis | Is each estimate using minimum, base, median or open-ledger fees? |
| Sponsorship and margin | Does either estimate shift responsibility to a sponsor or add an optional safety margin? |
A lower number is not automatically better. It may simply omit fees, use an outdated reserve setting or assume sponsorship that does not apply to your account.
Common mistakes and fixes
Counting transactions instead of objects
Sending 100 payments does not create 100 owner objects. Conversely, one transaction can create an offer, trust line or other object that raises OwnerCount. Use account_info and inspect the resulting ledger state.
Assigning one reserve increment to every NFT
NFT reserve usage is page-based, with up to 32 NFTs per page. Check the account’s actual objects and page allocation rather than multiplying the NFT count by the owner increment.
Treating 10 drops as a guaranteed fee
Ten drops is the documented reference minimum before load scaling. Query fee, use the open-ledger value when inclusion matters, and account for special transaction costs.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Signing before checking the fee
A signed transaction cannot have its Fee field changed without invalidating the signature. Query fees first, then sign. If conditions change materially, rebuild and sign again.
Using Mainnet numbers on another network
Reserve settings are network-specific. Query the selected network’s server_info or server_state instead of copying a value from a guide.
Adding an unexplained “standard buffer”
No universal personal buffer is prescribed by the cited documentation. If you add one, state its purpose—for example, volatility in open-ledger fees or an expected new trust line—and keep it separate from the protocol reserve.
Quick Recap
A repeatable checklist
- Identify the network and endpoint you will use.
- Call
account_infowith a validated ledger and recordaccount_data.OwnerCount. - Call
server_infoorserver_stateand record the live base and incremental reserves. - Convert drops to XRP when necessary using 1,000,000 drops per XRP.
- Compute
base + OwnerCount × increment. - List every planned transaction, including signatures and special conditions.
- Call
feeand choose the fee basis appropriate to your inclusion goal. - Apply transaction-specific costs rather than multiplying every operation by 10 drops.
- Add the fee budget to the reserve floor.
- Add any personal safety margin as a separately labeled planning choice.
- Re-query immediately before signing if the account, ledger or network conditions have changed.
Official references
- XRP Ledger Reserves
- XRP Ledger Transaction Cost
- Fee Voting
- FeeSettings ledger entry
- XRPL
feemethod - Sponsored Fees and Reserves
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
