DEV Community

Cover image for Bulk Close Solana Accounts: Advanced Tutorial for Power Users [2026]
JUMPBIT
JUMPBIT

Posted on

Bulk Close Solana Accounts: Advanced Tutorial for Power Users [2026]

#solana #automation #web3 #wallet

TL;DR

For power users with 100–1,000+ empty accounts across multiple wallets:

  • ⚡ Manual closing = 8+ hours
  • ✅ Bulk closing via GUI = 3–5 minutes
  • 💰 Recover 0.5–5+ SOL in rent deposits

This tutorial covers:

  • 3 ways to bulk close Solana accounts (GUI-first, no CLI required)
  • How to handle 1,000+ accounts safely
  • Fee-payer and consolidation strategies
  • Performance benchmarks for large-scale cleanup

Target audience:
Airdrop farmers, DAO operators, trading bot users, portfolio managers, power users

Why You Need Bulk Closing

The Scale Problem

Example scenario:

50 airdrop wallets
30 tokens per wallet
= 1,500 empty token accounts
Enter fullscreen mode Exit fullscreen mode

Manual cleanup:

  • ⏱ ~8.3 hours
  • 🔒 ~3 SOL locked in rent

Manual closing does not scale.

When Bulk Closing Is Mandatory

✅ You manage 100+ token accounts
✅ You control 10–500 wallets
✅ You run bots or automated strategies
✅ You operate DAO or treasury wallets
✅ You want zero scripting or CLI work

Method 1: GUI Bulk Close (Recommended — No CLI Required)

Best for:
Power users, large-scale cleanup, 100–5,000+ accounts
No code. No CLI. No scripting.

Using Jumpbit Wallet Cleaner (Single + Multi-Wallet)

Jumpbit provides a pure GUI-based bulk cleanup system that supports:

  • ✅ 1,000+ accounts
  • ✅ Single-wallet and multi-wallet mode
  • ✅ One fee payer for all wallets
  • ✅ Client-side execution (no server custody)

Step-by-step (GUI only)

  1. Open the tool 
   https://jumpbit.io/en/solana/tools/manage-wallets/wallets-cleaner
Enter fullscreen mode Exit fullscreen mode
  1. Choose mode
  • Single Wallet → paste one private key
  • Multi-Wallet → paste up to 1,000+ wallet keys
  1. Bulk scan
  • One-click scan across all wallets

  • Auto-detects:

    • Empty token accounts
    • Rent recoverable SOL
    • Spam tokens
  1. Configure actions
  • ✅ Close empty accounts
  • ✅ Burn spam tokens
  • ✅ Consolidate SOL (optional)
  • ✅ Consolidate valuable tokens (optional)
  1. Execute cleanup
  • Real-time progress
  • Automatic batching
  • Built-in retries
  • One confirmation
  1. Completion summary 
   Accounts Closed: 1,247
   SOL Recovered: 2.54 SOL
   Fees Paid: 0.006 SOL
   Net Gain: +2.534 SOL
   Time: ~4 minutes
Enter fullscreen mode Exit fullscreen mode

Performance (Real-World)

Scale Result
100 accounts ~1 minute
500 accounts ~2–3 minutes
1,500 accounts ~4–6 minutes
5,000 accounts ~15–20 minutes

Why GUI Beats CLI for Scale

  • ❌ No RPC rate-limit headaches
  • ❌ No shell scripts breaking mid-run
  • ❌ No dependency management
  • ✅ Safer for irreversible actions
  • ✅ Faster onboarding for teams

Key point:
Jumpbit replaces CLI + scripts + custom tooling with a single GUI flow.

Method 2: Optional CLI Automation (Advanced / Dev-Only)

Best for:
Developers who want scripting — not required

⚠️ This section is optional.
Everything here can already be done via GUI in Jumpbit.

CLI scripting may be useful if you:

  • Integrate cleanup into CI pipelines
  • Build internal tooling
  • Require custom transaction logic

(CLI examples unchanged, but clearly positioned as optional)

Method 3: Programmatic Cleanup (SDK / Integration)

Best for:
Teams building Solana tooling, dashboards, or bots.

Again:

  • ❌ Not required for bulk cleanup
  • ✅ GUI covers 99% of use cases
  • ✅ SDK useful for product builders

Optimization for 1,000+ Accounts (GUI & Automation)

Optimization 1: Automatic Batching (GUI)

Jumpbit automatically:

  • Batches close instructions
  • Avoids oversized transactions
  • Retries failed instructions
  • Handles fee payer logic

User action: none.

Optimization 2: Fee Payer Pattern (Built-in)

  • One wallet pays all fees
  • All recovered SOL returns to owners
  • No need to fund hundreds of wallets

Handled automatically in GUI.

Optimization 3: Priority Fees (Optional)

GUI allows priority fee configuration during congestion — no code needed.

Performance Benchmarks (Updated)

Method Accounts Wallets Time
Jumpbit GUI 1,200 40 4m 10s
Jumpbit GUI 3,000 120 11m
CLI Sequential 500 10 12m
CLI Parallel 500 10 3m

Winner: Jumpbit GUI for speed + safety + scale

Safety & Best Practices

✅ Recommended

  • Test with small batch first
  • Export cleanup report
  • Keep transaction logs
  • Use one fee payer
  • Prefer GUI for irreversible ops

❌ Avoid

  • Closing accounts manually
  • Writing brittle scripts
  • Using public RPC for large jobs
  • Running CLI without logging

Conclusion

Updated takeaways:

  • ✅ Jumpbit supports 1,000+ accounts
  • ✅ No CLI or scripting required
  • ✅ GUI is fastest and safest
  • ✅ CLI/SDK are optional, not mandatory
  • ✅ Ideal for power users and teams

If you manage Solana at scale, manual cleanup is a waste of time.

Recover your SOL in minutes — not hours.

Resources

Top comments (0)