Export help · Binance

How to export your Binance transaction history for your crypto tax report

Binance’s transaction history export lists every balance change in your wallet, one row per coin per movement. A single trade is spread over several rows, and the file has no fiat values, so it needs a little more care than most exports. This page shows you how to generate the file, what the columns mean and how CryptoTaxOwl groups the rows back into trades in your browser.

  • CSV (one file per export period)
  • Transaction History → Export Transaction Records
  • Steps not yet confirmed on an official page
  • Updated 7 October 2026

How to export your Binance history

  1. 1

    Open your transaction history

    On the Binance website, hover over the wallet icon at the top right and choose Transaction History. In the app, look for the History icon next to your total balance on the wallet screen.

  2. 2

    Start an export

    Hover over the export icon and choose Export Transaction Records. In the app, look for a Download icon at the top right of the history page.

  3. 3

    Choose the period, account and coin

    Select a date range, set Account to all accounts and Coin to all coins, then select Generate. Binance says records covering more than a year may need several exports, so work through your history one period at a time.

  4. 4

    Repeat until your whole history is covered

    Generate one export per period back to the month you opened the account. Binance documents a limit on how many exports you can generate per month, so plan the periods before you start.

  5. 5

    Download each file within 7 days

    Binance notifies you when an export is ready. Return to the export window and select Download. According to Binance, download links are kept for only 7 days.

  6. 6

    Import all the files together

    If the download is a zip, extract it first. Then drop every file into the crypto tax calculator at once. Overlapping periods are flagged as duplicates rather than counted twice.

We couldn’t confirm these steps on a current official Binance help page, so they’re based on secondary sources. Check them against the current app; if a menu has moved, look for the full transaction history export. Wrong or out of date? Tell us at errors@cryptotaxowl.com.

What the columns mean

Column headers as documented in tax-tool help articles for the Binance transaction history export and checked against the parser’s test file. Binance can change the layout without notice, so compare these with the header row in your own file.

ColumnWhat it means
User_IDYour Binance user number. Identical on every row and not used in calculations.
UTC_TimeDate and time of the balance change, in UTC. Rows from the same trade share this value.
AccountWhich Binance account changed, for example Spot or Funding. Futures and margin accounts also appear here.
OperationWhat caused the change, for example Deposit, Withdraw, Transaction Buy, Transaction Spend, Transaction Fee or an earn or staking reward.
CoinThe asset whose balance changed, such as BTC, USDT or EUR.
ChangeThe signed amount: positive when your balance went up, negative when it went down.
RemarkExtra text Binance adds to some rows, often blank. Sometimes it describes a withdrawal or a conversion.

Quirks to know

  • One trade, several rows. A spot trade usually appears as a Transaction Buy row (what you received), a Transaction Spend row (what you paid) and a Transaction Fee row, all with the same UTC_Time. Sells may use Transaction Sold and Transaction Revenue. Older files may use other wording for the same thing.
  • Several fills in the same second. A large order can produce many rows with the same time. They are grouped into one trade with the combined amounts.
  • No fiat values. The file holds coin amounts only. If one side of a trade is fiat (for example EUR), that side gives the value. Otherwise the value comes from the other leg or from the bundled daily price dataset.
  • Moves between your own Binance accounts. Transfers between Spot, Funding and other Binance accounts appear as paired rows. They aren’t disposals.
  • Many reward types. Simple Earn interest, staking rewards, distributions and small-balance conversions each have their own Operation text.

How CryptoTaxOwl reads this file

The file is read in your browser and nothing is uploaded. CryptoTaxOwl never asks for API keys, recovery phrases or passwords.

  1. The format is detected from its header fingerprint: the exact set of column names above.
  2. Rows with the same UTC_Time and Account are grouped by documented rules into a single trade, with the fee attached.
  3. Each Operation value is mapped through a versioned table. A value the table doesn’t know becomes an “Unknown type” issue that you resolve; it is never silently treated as taxable or non-taxable.
  4. Values come from the file first (a fiat leg), then from the other leg of the trade, then from the bundled daily prices, as explained in how CryptoTaxOwl works.
  5. Withdrawals to your own wallets need matching with the deposit on the other side. See crypto transfers between your own wallets.

Known issues and gaps

  • Futures, margin and similar products. Rows from futures or margin accounts, or with operations that look like them, are flagged as unsupported activity and excluded by default. You can include them as plain movements, with a warning that the result may be wrong.
  • Deposits from other platforms. A Deposit of crypto bought elsewhere has no cost on Binance. Import the other platform’s file too, for example your Coinbase transaction history, or you’ll see a missing cost basis issue.
  • Gaps between export periods. If one period is missing, balances go negative later. A negative balance issue usually means a file is missing.
  • Regional platforms. Some countries use a separate Binance platform with its own export format. If your file has different columns, use the column mapper.
Before you import, check that the first date of each file follows on from the last date of the previous one.

If your file isn’t recognised

If the headers differ from the list above, for example because you downloaded an order history or trade history statement instead, the workspace opens the column mapper. Map UTC_Time to the date, the amount column as a signed amount and the coin column as the asset, then save the mapping. You can also convert the file to the CryptoTaxOwl template with the crypto CSV converter.

Binance export: frequently asked questions

How far back can I export in one go?

Binance’s help article says you may need several exports to cover more than one year, and that the number of exports per month is limited. Export period by period, starting with the oldest, and import all the files together.

Should I use the transaction history or the trade history?

Use the transaction history. It includes deposits, withdrawals, rewards and fees as well as trades. A spot trade history only covers trades, so you’d be missing transfers and income.

Why are there three rows for one trade?

Binance records each balance change separately: what you received, what you spent and the fee. CryptoTaxOwl groups rows sharing the same UTC time and account into one trade.

Why do some Binance rows show a missing price?

The export has no fiat values. When neither side of a trade is fiat and the asset isn’t in the bundled price dataset, you’re asked to enter a value. A missing price is never assumed to be zero.

Are futures profits included?

No. Futures and margin rows are flagged as unsupported and excluded by default, and the report lists them so you can deal with them separately.