Loading route...
Swap>
Swap APT to BTC
Route overview
SWAPAPT to BTC
The route begins with a major ecosystem token and ends in Bitcoin, which changes the end state from application- or chain-linked exposure into native BTC ownership. The source asset is a major ecosystem token, so the route reflects a transfer of value out of an established crypto network position. The destination asset is native Bitcoin, so the terminal settlement profile is oriented around direct BTC ownership rather than application-layer utility.
Non-custodialLive routeNetwork-aware routing
Route note: this asset is currently supported through a single send network, so the preset shown here reflects the only available source rail: Aptos.
Route profile
Use this route when a major ecosystem position needs to be reallocated into native BTC rather than retained inside another chain environment. This profile is generally associated with portfolio reallocation or ecosystem rotation from one major asset into another destination. This profile is generally associated with allocating value into native BTC settlement rather than maintaining exposure inside another token environment.
Send
APT on Aptos
Receive
BTC on Bitcoin
Live swap card
Swap APT to BTC with the route prefilled.
Current rate
Select a valid pair to fetch a live variable rate
You send
Network
Select network
Variable rate creates the shift first. The shift page shows the deposit range before funds are sent.
You receive
NetworkSelect network
Live unit rate
--
Current live rate before the shift is created.
Deposit rule
[warning] Select a pair to see the live min and max deposit range before you create the shift.
Status note
After you create the order, the app redirects to a dedicated shift screen with the QR code, countdown, waiting state, and live status polling.
Live route context
Builder first, then route-specific timing and limit context.
Send
APT on Aptos
The route starts with the exact deposit asset and network selected for this page.
Receive
BTC on Bitcoin
Settlement is sent to the destination asset and network defined by this route.
Timing
Provider-driven
Timing depends on deposit detection, route processing, and confirmation-sensitive settlement before BTC lands on Bitcoin.
Deposit limits
Live minimums
Minimums and maximums are route-specific, so the builder and final shift page remain the source of truth before funds are sent.
Step-by-step guide
Need a walkthrough before using the live route?
Read the dedicated guide for APT to BTC first, then come back here to execute the exact swap with the live builder.
Open guide
How this swap works
1
Choose APT as the asset you send and BTC as the asset you receive.
2
Confirm the route starts on Aptos and settles on Bitcoin before creating the shift.
3
Enter a BTC receiving wallet that matches the destination network exactly.
4
Create the shift, follow the deposit instructions, and track settlement until BTC lands on the destination side.
Route-specific notes
The destination wallet must be compatible with native BTC settlement rather than with a wrapped or ecosystem-specific BTC representation.
This route relies on a compatibility-oriented rail, which generally implies broader wallet support and more predictable address handling.
Routes that settle into Bitcoin are commonly used for ecosystem participation rather than for passive holding alone.
This route depends on wallet-format compatibility, which means the destination address must match the selected chain and asset precisely.
Related routes
Reverse route
Looking for the reverse path?
Move in the opposite direction while keeping the same pair context available from a dedicated route page.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
Explore tokens and networks
Explore APT routes
View routes where APT is the asset being sent or received.
Explore BTC routes
See more swap paths that settle into BTC.
Explore Aptos routes
Review routes that start from the Aptos network.
Explore Bitcoin routes
See destinations and routes that settle on Bitcoin.
Explore Altcoin to BTC routes
Move up one level and review the full altcoin to btc routes family instead of a single route only.
Compare Stablecoin to BTC routes
Review the adjacent stablecoin to btc routes family when the next decision could change the destination or landing intent.
Pair FAQ
Why do users swap APT to BTC?
This route is commonly used when a major ecosystem token position is being reallocated into native BTC settlement.
Why is this route described as compatibility-first?
Because the selected network is chosen primarily for wallet support and address-format predictability rather than for minimum transfer cost alone.
Why does the destination ecosystem matter here?
Because the receiving asset is generally intended for use within the destination chain's wallet, application, or transfer environment after settlement.
Why does wallet format matter on this route?
Because the destination asset can settle correctly only when the receiving wallet matches the exact chain and address format required by the selected route.
What does native settlement mean on this route?
It means the destination asset is expected to settle on its native network rather than as a wrapped representation on a different chain.
Route disclaimer
Rates, minimums, and maximums are provider-driven and can change before the shift is created.
Always verify the deposit instructions on the shift page before sending funds.
The selected receiving network must match the destination wallet and asset route.
For APT to BTC, the live builder and shift page remain the final source of truth.