Most articles about Bitcoin faucet withdrawal limits repeat the same vague warning: "faucets cap how much you can take out." That's true and also useless, because it doesn't tell you which limit you're actually running into or why. On a Lightning-based faucet, withdrawal limits are not one number. They're a stack of separate rules: a per-payment cap tied to how Lightning routing actually works, a daily payout ceiling, a playthrough gate on bonus funds, and a short-window rate limit that exists to stop automated abuse. We run this pipeline every day on Lightning Faucet, so here's what each one means and what to do when you hit it.
If you came here because a withdrawal stalled or got blocked, skip to the section on failed withdrawals or the security hold. If you're trying to understand the system before you start earning, read straight through.
Quick reference: the actual numbers
The limits, as configured on the live payment system
These aren't rounded estimates, they're the values the withdrawal pipeline enforces on every request:
- Per-transaction cap: 100,000 sats maximum in a single Lightning payment.
- Daily payout cap: 500,000 sats total per account per day, across as many withdrawals as it takes to reach it.
- Rate-limit trigger: more than 6 withdrawal attempts inside a rolling 30-minute window auto-freezes the account.
- Auto-refund window: a failed payment refunds the debited balance in roughly a minute or two.
Keep those four numbers in mind and most "why is my withdrawal stuck" situations resolve themselves before you'd ever need to contact support.
The four limits hiding under one name
People say "withdrawal limit" as if it's a single ceiling. In practice it's several independent checks stacked on top of each other, and each one fails differently.
Per-transaction cap
This limits how many sats can move in a single Lightning payment. On Lightning Faucet, a single withdrawal payment tops out at 100,000 sats. This isn't an arbitrary business rule, it's a routing reality: larger Lightning payments need to find a path across channels with enough liquidity in the right direction, and bigger amounts fail to route more often. Capping the single-payment size keeps success rates high instead of leaving you stuck retrying a payment that can't find a route.
Daily payout cap
Separate from the per-payment cap, Lightning Faucet enforces a daily ceiling of 500,000 sats in total payouts per account. You can hit this even if each individual withdrawal is well under the 100,000-sat per-transaction limit, simply by withdrawing several times in one day (five max-size withdrawals would use up the whole daily allowance on their own). If you're blocked here, it isn't a sign anything is wrong: it's a safety limit, and the remainder becomes available to withdraw the next day.
Playthrough gate on bonus funds
If any part of your balance came from a bonus (a first-deposit match, a promo credit, a free spin award), that portion carries a playthrough requirement before it converts to withdrawable balance. This isn't rate-limiting, it's eligibility: the sats simply aren't withdrawable yet, regardless of the other caps.
Rate-limit freeze
This one isn't about amount at all, it's about attempt frequency. Enough rapid withdrawal attempts in a short window trips an automatic security hold, covered in detail below.
Four different mechanisms, four different fixes. Knowing which one you hit saves you from emailing support about something that resolves itself in a minute, or waiting on something that genuinely needs a human to clear.
How you actually withdraw on Lightning Faucet
LNURL-withdraw, not a pasted invoice
A lot of confusion around "withdrawal limits" actually starts with people trying to withdraw the wrong way. Lightning Faucet doesn't ask you to generate an invoice in your own wallet and paste it into a form. Instead, the withdraw page shows an LNURL-withdraw QR code and a matching tappable link. You open your Lightning wallet, scan the QR (or tap the link if you're already on mobile), pick the amount within your available balance, and confirm. Your wallet automatically fetches the invoice behind the scenes and pulls the sats. Any LNURL-withdraw-capable wallet works: Wallet of Satoshi, Phoenix, Blink, Zeus, Coinos, and most others that support the standard.
The reason this matters for limits specifically: the amount picker on the LNURL-withdraw screen is where the per-transaction cap gets enforced in real time. If you try to pull more than the single-payment ceiling, the wallet won't let the slider go past it, because the LNURL response itself declares the max withdrawable amount for that request.
Why this flow, and not manual invoices
Manual invoice paste-in is where most faucet withdrawal problems come from industry-wide: mismatched amounts, expired invoices, wrong wallet, typos in a long payment string. LNURL-withdraw removes essentially all of that because the wallet and the site negotiate the amount and invoice directly. If you've used a faucet before that made you generate and submit an invoice, that's not how Lightning Faucet's withdrawals work, and treating it that way will just produce errors.
What happens when a withdrawal fails
The auto-refund window
Lightning payments occasionally fail to route, especially near the top of the per-transaction cap where liquidity has to line up across multiple channels. When that happens on Lightning Faucet, the balance that was debited for the attempt is automatically refunded, typically within about a minute or two. You do not need to file a ticket, and you do not need to re-send anything manually.
Why your balance "looks unchanged"
If you check your balance immediately after a failed attempt and it looks like the sats vanished, that's the refund still settling, not a lost payment. Give it the minute or two and check again before assuming something is wrong.
Why retrying immediately makes it worse
Firing off another withdrawal attempt before the refund lands is the single most common way people accidentally trigger the security hold described next. Each attempt counts toward the rate limit whether it succeeded, failed, or is still refunding. Wait for the refund, confirm your balance is back, then try again once.
The security hold: more than six attempts in thirty minutes
Why it exists
Rapid repeated withdrawal attempts are a classic pattern for automated abuse and account takeover attempts, so Lightning Faucet's payment system auto-freezes withdrawals after more than roughly six attempts inside a thirty-minute window. This is intentionally aggressive because the cost of a false positive (a legitimate user waiting for support) is much lower than the cost of letting an abuse pattern run unchecked.
It does not clear on its own
This is the detail that trips people up: the freeze isn't a timer that expires. It stays in place until support reviews the account and manually removes it. If your withdrawals suddenly stop working after several tries in quick succession, that's almost certainly what happened, and the fix is contacting support rather than waiting it out or trying yet again (which won't help and just adds to the same counter).
How to avoid tripping it
Make one withdrawal attempt, let it either complete or auto-refund, confirm your balance, and only then make another if needed. Treat the LNURL-withdraw QR as a single-shot action per balance check, not something to mash repeatedly.
Bonus sats and why depleting a bonus doesn't unlock withdrawal
What the playthrough requirement actually locks
Bonus-funded balance (from a signup gift, a promo, or free spins) carries a playthrough requirement before any winnings from it become withdrawable. The requirement is fixed at the amount originally granted, and it stays open until you've actually wagered that much in total, whether that comes from winnings or from your own deposited funds.
Why hitting zero doesn't help
A common misunderstanding is that if you wager through the entire bonus and it hits zero, the requirement is satisfied. It isn't. Running the bonus balance down to zero doesn't reduce or clear it. This matters for withdrawal limits specifically because a balance can be sitting right there on your account screen and still not be eligible to move through the LNURL-withdraw flow until playthrough is met.
Why limits and provable fairness are part of the same system
The server seed, client seed, and nonce
Withdrawal limits only mean something if the balance behind them is trustworthy, which is why Lightning Faucet's games are provably fair by design rather than by claim. Every round in the casino games uses a server seed, a client seed, and a nonce that combine to produce the outcome. The server seed is hashed and shown to you before you play, so it can't be changed after the fact.
Verifying a result yourself
Once a server seed is rotated and revealed, you can independently verify any past result by recomputing the hash yourself and confirming it matches what was shown before you played. That verification loop is what makes the balance you're withdrawing meaningful in the first place: the caps control how fast sats move, the provably fair system controls whether the numbers behind them are honest.
Putting it into practice
Getting your first withdrawable balance
If you're setting up an account for the first time, the fastest path to a withdrawal you'll actually use is to claim your signup gift, start earning through the faucet's earn surfaces, and build a withdrawable balance by playing a provably fair game like dice or joining a multiplayer poker table.
Making the withdrawal count
Withdraw once via the LNURL-withdraw scan rather than in a burst of small attempts, and let any failed attempt auto-refund before trying again. If you'd rather grow a balance through forecasting instead of games, Lightning Faucet's prediction markets work the same way on the withdrawal side: same LNURL flow, same per-transaction cap, same auto-refund if a payment doesn't route.
Understanding the four limits ahead of time, and using the withdraw flow the way it's built to be used, is what turns "why is my withdrawal stuck" into a non-issue.