Why "insufficient funds for fee" appears on a funded wallet | Core Flow Point Guides
This error frustrates newcomers because the wallet screen shows enough SOL for the transfer. The runtime checks whether the fee payer account retains enough lamports after all instructions execute — including rent for new accounts and inner instruction debits.
Cause 1: Transfer amount plus fee exceeds balance
If you attempt to send "max" SOL without leaving a buffer for the base fee, the transaction fails before submission. Leave at least 0.00001 SOL beyond the amount field, more if creating accounts.
Cause 2: New token account rent
Creating an associated token account requires rent-exempt lamports locked in the new account. The fee payer must cover both the transaction fee and that rent deposit in the same transaction.
Cause 3: Wrong fee payer
Multi-signer transactions can designate a fee payer other than the sender you expect. Check the transaction preview in your wallet before approving.
Reading the log
Failed simulation logs often state which account lacked lamports. Match that pubkey to your accounts in the explorer's account list. Our consultation sessions frequently start here — clients paste a failed signature and we trace the shortfall together.
Prevention checklist
- Keep a small SOL buffer untouched for fees
- Preview total debits including rent when minting or receiving new token types
- Retry with reduced amount rather than repeatedly submitting identical failing transactions
For hands-on practice, bring a failed transaction ID to a one-to-one consultation — redact sensitive labels if you prefer.
Questions about this topic? Send an enquiry or browse our fee reference tables.