The token exists; the routes to it mostly do not
Tether lists TON among the blockchains it supports, as a jetton — TON’s own kind of token (Tether). That part is settled. The part this site can measure is whether anyone will move it for you, and the answer today is no: TON does not appear in the supported network lists of any provider we query, checked against their own endpoints rather than taken on faith. We do not show a route we cannot price, so there is no quote table on this page.
That leaves the exchange route, which is what the next section is about. Our methodology describes how provider coverage is established, and it is rechecked rather than assumed — if a provider adds TON, this page changes.
How people actually move USDT to TON
Through an exchange, in three steps, and the order matters.
First, check the withdrawal side before anything else. An exchange that accepts TON deposits does not necessarily offer TON for withdrawals, and finding that out after your money is sitting on its balance is the wrong moment. The live table on our USDT networks page shows which exchanges publish a USDT withdrawal on TON, what each charges and the minimum, with the date every figure was checked — the numbers are not repeated here because they change and this text would not.
Second, get the USDT onto that exchange on whatever network you already hold it — TRON, Ethereum, BNB Smart Chain — as an ordinary deposit. That leg is a normal transfer and can be compared like any other.
Third, withdraw, choosing TON as the network, to a TON address you control. Take the address from the receiving wallet itself rather than from a message or a screenshot, and if the destination is another service, take whatever it asks you to attach along with it.
What you are trading away by going this route is time and custody: the money sits with the exchange between the two legs, and it moves on the exchange’s schedule rather than the network’s. That is the honest cost of there being no bridge to compare.
Addresses look unlike anything else
A TON address exists in two forms. The raw form is the canonical on-chain one, but it carries no checksum, so a typo in it is just a different address. The user-friendly form wraps the same thing with flags and a checksum, which is what catches a mistyped character before the money moves (TON).
Those flags also encode whether a message bounces back if the destination cannot accept it. Addresses beginning with E are bounceable, meant for contracts with logic of their own; addresses beginning with U are non-bounceable, which is what wallets use so that funds are credited even when the receiving account has not been initialised yet. Two strings that look equally valid therefore behave differently, and the wallet you paste into will not always tell you which one you have.
A deposit is matched by more than where it landed
On TON a service credits a payment either by an address it issued to you alone or by data attached to the transfer itself (TON). Both are normal. What is not normal is sending to a shared address without whatever the service asked you to attach: the money arrives on the network and still does not arrive in your account, because nothing connects the two. Read the deposit screen before sending, not after.
Questions
Can I bridge USDT from TRON to TON?
Not through any provider we compare — none of them lists TON among its supported networks, so we have no quote to show you and will not invent one. What is left is an exchange that accepts a deposit on TRON and lets you withdraw on TON, which is two steps with the exchange's own fee and limits.
How do I bridge from TON to Ethereum?
The same answer in reverse: no provider we track covers TON, so the practical route is an exchange deposit on TON and a withdrawal on Ethereum. Check before you start that the exchange actually supports both ends — accepting a network for deposits does not mean it offers it for withdrawals.
Is there a bridge from Base to TON?
Not one we can quote. TON does not appear in the supported-network lists of the bridges and aggregators we query, which is checked against their own endpoints rather than assumed. Other bridges outside our comparison may exist; we only speak for what we measure.
Why does a TON deposit need more than an address?
Because a service can identify an incoming payment either by an address it issued to you alone or by data attached to the transfer itself. That is why an exchange may give you one shared address plus a comment or memo field, and why a transfer sent without it has to be matched by hand, if it can be matched at all.
Sources
- Tether — supported protocols · checked 2026-09-12
- TON documentation — address formats · checked 2026-09-12
- TON documentation — processing jetton payments · checked 2026-09-12