Importing Hyperliquid into TurboTax
TurboTax can handle crypto — but only through a fixed list of custodial exchange integrations and manual entry. Hyperliquid is on neither side of that line: it is not a supported integration, and it issues no 1099 a software importer could read. So the question is not "which button do I press," it is "which numbers do I type in, and where did they come from." That is a data problem, and it is solvable in an afternoon.
- No TurboTax–Hyperliquid integration exists. TurboTax imports from supported custodial exchanges; Hyperliquid is not one, and no broker form exists to import.
- What TurboTax ultimately needs is Form 8949 material: description, dates, proceeds, cost basis — per transaction or summarized, depending on volume and your preparer's mapping.
- Perps do not hand you clean proceeds/basis pairs: the reliable raw material is the exchange-reported
closedPnlandfeeper closing fill, totalled per tax year. - For high volume, the practical route is a summarized entry (dates "Various") backed by a detailed statement kept with your records — confirm the current-year rule and how TurboTax handles it.
- Cross-check before filing: the gain/loss total in TurboTax should reconcile to your exchange-reported yearly PnL, fees, and funding.
The direct answer
You will not "connect" Hyperliquid to TurboTax. You will reconstruct your year from the public API (or this site's scanner), decide the mapping with your preparer if you are unsure, and enter the result into TurboTax manually — as individual rows if your volume is small, or as summarized totals if it is not.
What TurboTax can and cannot ingest
- Can: import from a list of supported custodial exchanges and wallets; accept manual entry of Form 8949 / Schedule D data; accept summary entries with "Various" acquisition dates.
- Cannot: read an arbitrary broker or API CSV the way it reads a supported integration; fetch anything from a decentralized venue; generate the numbers for you.
- Consequence: the exchange-reported export is your source of truth — TurboTax is only the place the final numbers get typed.
TurboTax's crypto interview walks you through digital-asset questions and builds the 8949 and Schedule D for you. As of the 2025 tax year the form has dedicated digital-asset boxes (G–I short-term, J–L long-term); the Form 8949 guide covers how perp closes relate to them.
The summary workflow that works
- Reconstruct your year. Use the free scanner to get per-year totals — realized PnL, fees, funding paid and received — plus the per-fill detail behind them. If you are an extremely high-frequency trader, note the API coverage notes and request your archive if the totals look short.
- Decide the mapping (with your preparer). How each close lands in 8949 columns — and whether capital treatment applies in the first place — is the part no software should decide silently. Perps differ from spot here; see what closedPnl does and does not tell you.
- Enter it in TurboTax. Small volume: one row per close, dates and amounts from your export. Large volume: one summarized row per year and category, dates "Various", with the detailed fill-level statement retained in your records. Verify the current-year rule for summarized entries and how TurboTax implements it — software changes yearly.
- Cross-check the totals. The final gain/loss figure should reconcile to your exchange-reported yearly totals. A gap bigger than rounding usually means funding was dropped, fees were counted twice, or a wallet was imported once too often.
- Keep the evidence. The export (fills with
closedPnl,fee, timestamps and IDs) plus your reconciliation notes. With no broker form, these records are the only proof of what you filed.
Where funding fits — the question TurboTax can't ask
TurboTax's crypto interview has boxes for buys, sells, and income — it has no native concept of perpetual funding. Funding is a cash flow with a direction (paid or received), and most frameworks treat the two directions differently. That is a classification question for your accountant; what you can do is arrive with the split already totalled. Our funding guide lists the exact questions to ask.
Common mistakes
- Uploading alphabet soup. Trying to force a raw API CSV into TurboTax. Supported integrations only — everything else is manual entry.
- Reporting unrealized PnL. Mark-to-market swings on open positions are not per-event records; see realized vs. unrealized.
- Double counting fees. Fees appear inside your export; if your preparer nets them into PnL, do not also claim them separately.
- UTC vs. local year boundaries. The API groups by UTC year. A trade at the boundary may belong to a different local tax year than it appears — flag the edge cases to your preparer.
- Trusting one source. The Koinly-style failure modes (re-derived PnL, dropped funding) apply to any importer; the exchange-reported numbers are the reference. See the Koinly cross-check guide for the pattern.
Get the numbers TurboTax needs
Per-year realized PnL, fees, and funding — exchange-reported, free, read-only, in 30 seconds.
Scan my walletCommon questions
Does TurboTax support Hyperliquid?
No. TurboTax imports only from a fixed list of supported custodial exchanges, Hyperliquid is not one of them, and no 1099 exists for a software importer to read. You reconstruct your year from the public API (or a scanner built on it) and enter the numbers manually.
How do I enter Hyperliquid trades in TurboTax?
Reconstruct per-year totals first — realized PnL, fees, funding paid and received. Small volume: enter one row per close. Large volume: a summarized entry with "Various" dates, backed by a detailed statement retained in your records. Then cross-check the final gain/loss against the exchange-reported yearly totals before filing.
Where does funding go in TurboTax?
Nowhere natively — TurboTax's crypto interview has boxes for buys, sells and income but no concept of perpetual funding. Funding is a directed cash flow (paid vs. received is usually classified differently), so arrive with the split already totalled and let your accountant decide the treatment.