To withdraw from Hyperliquid, the first thing to decide is which surface the funds currently sit on: HyperCore (perp margin, native orderbook state) or HyperEVM (chainId 999, standard ERC-20 balance). Withdrawing from each uses a different rail, and the fastest path depends on where the funds need to land. This guide walks through both — including the Arbitrum-direct native withdrawal for HyperCore, the aggregator paths from HyperEVM back to Base, Ethereum, Solana, and the developer API path via Eco Routes.

The withdrawal flow mirrors the deposit flow in reverse, but with one structural asymmetry: the HyperCore-to-Arbitrum native withdrawal has a queue delay, while bridging out of HyperEVM via intent-based orchestration fills in the same single-digit minutes as a deposit. That asymmetry shapes the optimal path for most users.

Before initiating any withdrawal:

For users funding Hyperliquid for the first time, the USDC bridging guide covers the deposit flow; the withdrawal is essentially the same routes in reverse.

The native Hyperliquid bridge supports USDC withdrawal from HyperCore directly to Arbitrum. This is the official, single-step path.

This path has a queue delay inherent to the native bridge architecture. Users who need funds off Hyperliquid immediately should consider the HyperEVM path below if speed matters more than the direct Arbitrum destination.

For funds on HyperEVM (USDC or USDT0 ERC-20 balances), Eco Portal routes the outbound flow to any of the 15+ supported chains with intent-based atomic execution.

Underneath, Portal uses the same intent-based solver network that powers Eco Routes. Intent-based atomic execution means if the solver can't fill, the intent expires and funds stay on HyperEVM — no partial-fill limbo.

If you want USDC off Hyperliquid but your destination isn't Arbitrum, the native bridge can't help. The pattern:

Two steps, but both fast. This pattern is often faster end-to-end than the native HyperCore → Arbitrum path because the intent-based bridge on the second leg fills quickly, while the native bridge has its queue delay. For users whose destination is Base or Ethereum (not Arbitrum), this also avoids the extra hop of withdrawing to Arbitrum and then re-bridging elsewhere.

USDT0 on HyperEVM is a standard ERC-20 balance. Withdrawal paths mirror USDC but with different destination options — USDT0 is the omnichain USDT wrapper supported on Unichain, Plasma, Polygon, Arbitrum, and HyperEVM.

For more on the relationship between USDT variants, see what is USDT0 and the difference between Tether, OpenUSDT, and USDT0.

For desks, market makers, or automated treasury systems withdrawing from Hyperliquid on a schedule, Eco Routes exposes the same routing network as a CLI and API.

CLI:

API: POST to https://api.eco.com/v1/quotes with an intent specifying HyperEVM as source chain. Fill confirmation is available via the intent status endpoint. The full integration walkthrough is in publishing a cross-chain stablecoin intent with Eco Routes.

Centralized exchanges that support HyperEVM deposits directly (some do, some don't) give users a fourth withdrawal path — send HyperEVM USDC directly to the CEX deposit address. If the CEX only accepts USDC on Arbitrum, Base, or Ethereum, use Eco Portal or the native bridge to route there first.

Caveat: verify the CEX supports HyperEVM deposits before sending. Some exchanges support Hyperliquid-addressed withdrawals but not deposits, or they require a specific deposit memo. Sending to a CEX that doesn't support the source chain is the fastest way to lose funds.

Withdrawal fees follow the same structural logic as deposits — source gas, solver margin, destination gas. Since HyperEVM charges zero gas on the source side of a withdrawal, the fee is dominated by the solver margin and the destination chain's receive-side gas. For the full fee structure, see the Hyperliquid bridge fees comparison.

Noteworthy: because HyperEVM is cheap on the source side of withdrawals, outbound cost from Hyperliquid is often lower than inbound cost from an expensive-gas origin like Ethereum. The destination chain's gas becomes the main cost driver — withdrawing to Base or Arbitrum is cheap; withdrawing to Ethereum mainnet is the most expensive destination.

Hyperliquid's native bridge escrows deposited USDC on Arbitrum and credits HyperCore. A withdrawal unlocks the Arbitrum-side escrow. The integrity of that unlock depends on the bridge contract and its attestation process.

Intent-based withdrawals from HyperEVM work differently. The user's HyperEVM USDC is held in the intent vault on HyperEVM during the fill window, and a solver delivers USDC on the destination chain from their own inventory. When the solver proves delivery, the HyperEVM vault releases to the solver as reward. The user's funds are always held by a smart contract, never by a counterparty, during the fill.

For the general bridge security model, this "atomic-execution-via-vault" pattern is structurally safer than traditional lock-and-mint flows because there's no mint step that can fail separately from the lock step.

Traders closing out of HyperCore perp positions face a specific withdrawal pattern:

For repeated withdrawal-redeploy flows, programmatic Routes intents with multi-source routing keep capital moving efficiently across venues.

For active traders, the meaningful cost metric isn't the one-way deposit fee — it's the round-trip. Deposit + withdraw, measured against trading volume, becomes a drag factor on strategy returns.

For Hyperliquid, the round-trip structure:

The Base round-trip via Eco is often cheaper than the Arbitrum round-trip because Base gas is lower than Arbitrum gas at both ends, and the solver margin is symmetric. Counterintuitive but material for size: traders who think "native bridge is cheapest" may be overpaying on the combined round-trip versus the Base path.

Native bridge withdrawals (HyperCore to Arbitrum USDC) can take minutes to hours depending on queue conditions. Eco Portal withdrawals from HyperEVM typically fill in single-digit minutes with atomic execution. For the fastest withdrawal to a non-Arbitrum destination, use the HyperCore → HyperEVM → Portal pattern.

HyperEVM balances can withdraw to any of Eco's 15+ supported chains via Portal or Eco Routes. HyperCore's native bridge supports only Arbitrum USDC directly; other destinations require the HyperEVM crossover step first. See the best way to bridge to Hyperliquid for the full route matrix.

No. HyperEVM charges zero gas on source-side transactions, and HyperCore's native bridge doesn't charge a Hyperliquid-side gas fee (just a minimal protocol fee on Arbitrum-side execution). Withdrawal cost comes from solver margin and destination-chain gas.

Intent-based withdrawals expire cleanly if the solver can't fill — funds stay on HyperEVM and nothing is lost. Native bridge withdrawals that fail before completion are typically recoverable through the standard contract flow. Always check the transaction hash on both source and destination explorers.

Not in a single intent — each intent specifies one source token. For multi-asset withdrawals, sign separate intents for each asset. Programmatic Routes API supports batching multiple intents in sequence for treasury flows.

Withdrawing from Hyperliquid is a two-surface decision: HyperCore or HyperEVM. Arbitrum USDC is the native bridge's one supported destination. Everything else routes through HyperEVM plus an intent-based bridge to your chosen chain — Eco Portal for retail, Eco Routes for programmatic. For the full deposit side, see the USDC bridging guide; for cost optimization, the cheapest path breakdown covers origin-by-origin economics.