There is no single button that turns a Binance balance into money in your bank account. There are two separate legs β moving crypto off the exchange, and converting it to fiat somewhere β and they have different failure modes, different fees and different people to blame when they go wrong. Most of the horror stories come from treating them as one step.
Before any of that, though, a question that decides everything downstream.
Which Binance are you actually on?
"Binance" is not one company with one rulebook. Binance.com is the global platform and it does not serve US persons. Binance.US is a separate entity with a separate app, separate listings and separate rails. Several other jurisdictions have their own locally licensed entities operating under a different regulator with a different product menu.
This matters more than any network fee. The withdrawal options in front of you β which fiat currencies exist, whether card products are offered, which networks are enabled, what your limits are β are a property of the entity your account sits with, not of "Binance" in general. It is why a walkthrough written for one audience can be confidently, uselessly wrong for another.
It also means the rails move. Binance.US had its US dollar services switched off and later restored; other regions have gained and lost card products and local payment methods more than once. Whatever a guide tells you is available, open the withdrawal page on your own account and look. That includes this guide.
Choosing a network is choosing a fee, a wait, and a counterparty.
Once you are moving crypto rather than fiat, the network dropdown is the whole decision. Same asset, same destination, wildly different outcomes.
| Asset and network | Good for | What actually goes wrong |
|---|---|---|
| BTC β Bitcoin native | Anything large, anything going to long-term cold storage | Slow, and the withdrawal fee is set by the exchange rather than by live mempool conditions, so you can overpay badly in quiet periods |
| BTC β Lightning | Small amounts to a wallet you already run | Needs an invoice from a Lightning-capable destination, has its own per-transaction ceiling, and fails outright if the receiving node cannot route the amount |
| BTC β wrapped on BNB Chain | Cheap and fast internal moves inside that ecosystem | It is not Bitcoin. It is an IOU whose value depends on the issuer and the bridge staying solvent. Fine for a day, wrong for a decade |
| USDT β Ethereum (ERC-20) | Destinations that accept only one chain, and anything institutional | Cost. When the network is busy this is the expensive option by a wide margin |
| USDT β Tron (TRC-20) | Cheap, fast, near-universal acceptance among exchanges and OTC desks | Some regulated venues and some banking-adjacent services will not accept Tron-sourced funds; check before you send, not after |
| USDT β BNB Chain (BEP-20) | Moving between Binance-ecosystem venues | Narrower acceptance elsewhere; a lot of wallets show the balance but cannot spend it without a gas token |
One thing that catches people repeatedly: the fee shown on the withdrawal screen is a flat figure the exchange sets per asset per network. It is not the live chain fee. Sometimes it is generously below what the chain is charging, sometimes it is several times above. If you are moving Bitcoin on-chain and the amount is not urgent, it is worth glancing at a mempool fee estimator before you confirm β you are being quoted a price, not a cost.
The mistakes that actually lose coins.
Not one of these is exotic. All of them are common.
Wrong network. You pick BEP-20 because it is cheap, the destination only watches for ERC-20, and the funds land at an address nobody is monitoring. Sometimes recoverable through support, sometimes not, always slow and humiliating.
Missing memo or tag. Some chains and some destinations require a memo, destination tag or comment field to route the deposit to your sub-account. Send without it and the money arrives at the venue but is not credited to you. Recovery depends entirely on the receiving service's goodwill.
Address poisoning. An attacker sends you a dust transaction from an address that matches the first and last few characters of one you use often. Later you copy an address from your transaction history instead of from the source, and the prefix and suffix look right. Verify the middle of the address, or better, only ever paste from the destination wallet itself.
Sending to a service that will not accept it. Some platforms reject deposits that did not originate from an account in your own name. Withdrawing from an exchange to a broker or an off-ramp that has that policy can get the funds bounced, frozen pending review, or returned minus fees.
Three settings before your first self-custody send.
Turn on the withdrawal address whitelist. It costs you a delay the first time you add an address and removes an entire category of attack after that β an attacker with your session cannot send to a fresh address.
Send a test amount. Twenty dollars, full round trip, confirmed in the destination wallet, before the real transfer. Every experienced person does this and nobody talks about it because it is unglamorous. It catches wrong network, wrong address and missing memo for the price of a coffee.
Know your lockout window. After a password change, a new device or a 2FA reset, withdrawals are typically frozen for a day or more. That is a good rule protecting you, and it is also the reason you should not be doing security housekeeping on the afternoon you need to move money.
The fiat leg is a different problem with different rules.
Once crypto has left the exchange, whoever converts it to fiat is a new counterparty with its own onboarding, its own limits and its own opinion about you. Treat each hop as a fresh compliance surface, because that is what it is.
Two things worth knowing regardless of jurisdiction. First, receiving institutions vary enormously in how they treat inbound funds identified as crypto-sourced, and their policies are usually not published. The way you find out is by moving a small amount and watching, not by reading terms of service. Second, and more seriously: do not split a large transfer into pieces to stay under a reporting threshold. Deliberately structuring transactions to avoid reporting is itself an offence in a number of jurisdictions, and the split pattern is precisely what monitoring systems are built to detect. A large, well-documented transfer draws far less trouble than five artfully small ones.
US-based readers have the extra layer described in the reference section below, where information-sharing obligations attach above a threshold. That is not something you opt into or out of; it is a rule your provider follows on your behalf, and the practical implication is simply that the beneficiary details need to be accurate.
Export the records before you need them.
The paperwork you will want later is trivially available now and painful to reconstruct in two years: withdrawal history with dates and amounts, transaction IDs, the networks used, and the fiat side of any conversion. Exchange export tools have retention windows and rate limits, and account access is not guaranteed to last forever β jurisdictions get delisted, entities restructure, accounts get restricted during reviews.
Pull a full export once a year and keep it somewhere that is not the exchange. It takes ten minutes and it is the only part of this article that is guaranteed to be useful.
The order of operations, if you take nothing else: pick the destination first, then check which networks that destination actually credits, then pick the network, then send twenty dollars. Most people do it in exactly the reverse order, which is why the network dropdown gets the blame for a decision that was already wrong two steps earlier. If you are still working out which venue you want on the other end, the venue comparison and regional access notes are the places to start.
Context and references.
Binance supports withdrawal through roughly 70 blockchain networks as of 2026, with the precise list visible on the withdrawal page for each asset. The choice of network materially affects fee, confirmation time and counterparty risk. CoinDesk and The Block have both covered the bridge-bridge consolidation that reduced the practical list from 100+ networks in 2022.
BTC withdrawal options: Bitcoin native (slow, fee variable, highest security), Lightning Network (fast, low fee, requires Lightning-compatible destination), or BEP-20 wrapped BTC (fastest and cheapest but custody-dependent on Binance and BSC infrastructure). For amounts above $50,000, native Bitcoin is the cleanest path; below that threshold, Lightning is increasingly the default for users with compatible wallets.
USDT withdrawal options: ERC-20 (Ethereum, expensive but most universally accepted), TRC-20 (Tron, cheap and fast, dominant in Asia), or BEP-20 (BSC, cheap and fast, Binance ecosystem). Glassnode and Tron block explorer data show roughly 60% of Binance USDT withdrawals run through TRC-20, reflecting the Asian retail user base.
For US-domiciled users, withdrawal to a self-custody wallet involves an additional layer: the FinCEN travel rule applies to amounts above $3,000 and requires originator/beneficiary information sharing. Binance.US handles this through its compliance infrastructure; Binance.com applies it to KYC-verified accounts above the threshold.
Crypto assets are volatile and not suitable for every investor. This page is editorial analysis, not financial advice.