Same coin + network
Compare exchanges on the same network. Cross-network minimums are route references.
How are these fees calculated?
Understand the sources, comparison rules and known limitations.
Three principles to start with
Unknown is not zero
Unpublished fees are not zero and are excluded from rankings.
Verify with the exchange
Confirm the network, fee and minimum withdrawal before proceeding.
How networks are matched
Venues do not agree on what to call a chain. Ethereum mainnet is ETH at Binance and ERC20 at Bitget, KuCoin and HTX; BNB Smart Chain is BSC or BEP20; Polygon appears as MATIC, Polygon, Polygon POS and POLYGON. Each name is normalised — case and punctuation removed — and looked up against one canonical list.
A name that cannot be placed is not guessed at. The reading is marked unplaced and still shown on that venue's own row, but it never sits beside another venue's — filing a fee under the wrong chain would have a reader act on it. Every unplaced name is listed on the collection status page as the operator's queue.
The alias table is hand-maintained and can therefore drift. For tokens there is a check that does not rely on anyone's diligence: every venue publishes the token's contract address, and two entries sharing one are on the same chain by definition. That cross-check is what finds aliases that disagree.
What the fee covers
Fees are denominated in the coin being withdrawn, so figures on one network compare directly with no price conversion. Some venues charge a proportion on top of the flat fee — KuCoin does on some routes, and HTX prices some coins by ratio outright — and the two are recorded separately rather than folded into one number.
A figure a venue does not publish on a public endpoint is shown as unknown and never as zero. A route with no published fee is not ranked: treating unknown as zero would put that venue at the top of the table for no reason.
Fees not priced in the coin
Some venues publish a fee that is not denominated in the coin being withdrawn. Spotting it does not take guesswork: a fee priced per token is computed from that token's price, so identical values are rare — across HTX's Ethereum routes no value repeats more than twice, and Binance's largest non-zero cluster is eleven. Against that, Bitget quotes exactly 1.6 for 198 different Ethereum tokens whose real values run from two billionths of a cent to over nine hundred dollars, and KuCoin quotes 0.01 for 176 of them. Those are not fees in the coin; they are a figure that was never converted into one.
A non-zero fee value shared by more than twelve unrelated coins on one venue and network is marked as not priced in the coin: the figure is still shown on that venue's own row, but it is never set beside another venue's. Zero is exempt, since a free withdrawal is a real offer and repeats legitimately. Without this the affected venue would look hundreds of times cheaper on every table, which is precisely the error this site exists to avoid.
Read frequency and freshness
Every reading stores the UTC time it was taken. A reading older than 24 hours is marked stale, is not ranked, and does not enter the sitemap. When a source fails its previous rows are left untouched: a partial pass is never committed, or a route the venue merely omitted that minute would be recorded as delisted.
Sources
Binance
Endpoint read
https://www.binance.com/bapi/capital/v1/public/capital/getNetworkCoinAll
Bitget
KuCoin
OKXAll of these but OKX are public endpoints, used with no account and no signature. OKX publishes its withdrawal schedule only to an authenticated caller, so it is read with a read-only API key that carries neither trade nor withdraw permission; with none configured OKX is absent from the site rather than approximated from a help page. MEXC and Bybit are behind authentication too and are not yet included.
Disclosure
An outbound link carries a referral code where one is configured, and this site may earn a commission from it; a venue without one links to its own site instead. Ordering follows only the method described above and is unaffected by whether a referral link exists.