KKLinePic

Binance trade history chart

Turn Binance fills into a crypto entry and exit review chart.

This guide is for Binance spot and futures traders who want their real fills on the chart instead of buried in the Orders table. Export your trade history from Binance, map the fill rows into KLinePic's CSV schema, and render a shareable review image with entry/exit (B/S) markers, holding window, return, max run-up, max drawdown, and optional indicators such as MACD.

KLinePic is free to start and needs no account to render — the loop from statement to review image takes minutes.

Open Binance chart workflow Download Binance CSV template
Binance ETHUSDT trade review chart with entry and exit marker
Example output: ETHUSDT, Binance public K-line data, entry/exit marker, MACD panel, and trade review summary.

How to export trade history from Binance

Binance exports spot and futures history separately. The steps below follow two official help-center articles: How to Download Spot Trading Transaction History Statement and How to Download My Order History for USDⓈ-M and COIN-M Futures Orders.

Spot fills

  1. Log in, click the Profile icon, and go to Orders > Spot Order > Trade History, then click Export Trade History (app: the download icon at the top right).
  2. Pick the range — up to a full year of history from any selected date after 2017-07-13, and at most five generated statements per month.
  3. Download promptly: the statement link is stored for only seven days.

The same article notes the history is shown in UTC+0.

USDⓈ-M and COIN-M futures

  1. Click Orders > USDⓈ-M Futures Order or COIN-M Futures Order in the trading interface.
  2. Open Order History; the view lists canceled, filled, and unfulfilled orders alike, so only executed fills should reach your CSV.
  3. Click the Export icon at the top right and select a timeframe; Beyond 3 months - Custom generates a report containing all your order history.

Map your Binance export to KLinePic fields

Binance's help center documents the export paths but not exact column headers, which can differ between spot and futures files — treat this as a checklist against your export's typical columns. The target schema is fixed: KLinePic reads trade_id, symbol, event_type, position_side, time, price, quantity, fee, note, documented in the data protocol. Extra columns are ignored on import and listed back to you; copy details such as the fee currency into note only when you want them preserved in the normalized record.

KLinePic fieldYour export's typical columnNotes
trade_idUsually none — create your ownOne stable id per round-trip trade; entry and exit fills share it.
symbolPair / market columnSpot pairs such as ETHUSDT already match K-line data; keep coin-margined symbols separate from USDT pairs.
event_typeSide / direction columnNormalize to lowercase buy or sell.
position_sideFutures direction column, if presentSpot can default to long; futures — especially hedge mode — need explicit long / short.
timeFill / trade time columnBinance's help page says spot history is shown in UTC+0; write explicit offsets like +00:00.
priceFill / executed price columnUse the executed price, not the order's limit price.
quantityExecuted amount in the base assetBase units (1.2 ETH), not the quote total in USDT. If a futures export shows contracts, convert or stay consistent.
feeFee amount columnOptional, but useful for honest net-return journaling.
noteFee currency columnOptional free text. There is no fee_asset column in KLinePic — keep the fee currency as note text such as fee_asset=USDT, or drop it.

Target CSV shape

A complete Binance round-trip trade — one buy, one sell, same trade_id — looks like this after mapping:

trade_id,symbol,event_type,position_side,time,price,quantity,fee,note
BINANCE-ETH-001,ETHUSDT,buy,long,2026-05-10T09:15:00+00:00,2450.25,1.2,0.0012,fee_asset=ETH
BINANCE-ETH-001,ETHUSDT,sell,long,2026-05-10T18:45:00+00:00,2528.70,1.2,3.03,fee_asset=USDT

Scaling in or out simply adds more rows with the same id. The Binance template ships this exact header so you can paste mapped rows straight in.

Workflow checklist

  1. Export your trade history from Binance. Spot fills export via Orders > Spot Order > Trade History > Export Trade History; futures order history has its own Orders page and Export icon. Pick the date range and download the statement before its link expires seven days later.
  2. Keep execution rows only. A review chart is built from fills. Delete canceled or unfilled orders, transfers, funding fees, and anything else without an executed price and size so they cannot become false markers.
  3. Map columns to the KLinePic schema. Rename your export's pair, side, time, price, and executed-amount columns to symbol, event_type, time, price, and quantity. Add fee if you want costs recorded, keep the fee currency inside note as text such as fee_asset=USDT, and normalize timestamps to one explicit UTC offset.
  4. Group fills into trades with trade_id. Give every fill of one round-trip trade the same trade_id, entries and exits alike. Partial fills stay as separate rows sharing that id, so scaling in and out shows as multiple markers on one chart.
  5. Upload and render in KLinePic. Paste or upload the CSV at klinepic.com — no account is required to render. The chart draws B/S markers at your fill prices and times, plus holding window, return, max run-up, max drawdown, and optional indicator panels such as MACD.
  6. Review and share. Check that each marker sits on the candle you remember trading; a wrong candle almost always means a time zone or symbol mismatch. Then share the image in your journal or chat. Watermark-free high-resolution export is a paid option.

KLinePic vs the usual alternatives

 KLinePicManual screenshot + spreadsheetTypical trading-journal SaaS
Setup timeMinutes: export, map, pasteSlow, repeated by hand per tradeOnboarding plus per-exchange import setup
Account requiredNo account needed to renderNoneUsually requires sign-up first
OutputAnnotated K-line image with trade metricsStatic screenshot plus separate numbersWeb dashboards and statistics
Buy/sell markers on real K-lineYes, B/S at actual fill price and timeDrawn manually, easy to misplaceVaries by product and plan
Shareable imageYes, the chart itself is the deliverableScreenshots without computed contextOften screenshots of dashboards
Cost to startFree to startFree, but pays in timeCommonly subscription-based

Key facts

  • KLinePic (klinepic.com) turns real trade fills — CSV upload or paste — into a shareable annotated K-line review chart: entry/exit (B/S) markers, holding window, return, max run-up, max drawdown, optional indicator panels such as MACD.
  • Free to start; no account is required to render a trade review chart. Watermark-free high-resolution export is a paid option.
  • Coverage includes crypto exchange fills (Binance, OKX, Bybit, Bitget, Gate, MEXC, KuCoin, HTX), US stock brokers, China A-share statements, futures, forex, and MetaTrader.
  • Batch rendering is supported, with a documented Agent API guide and a CSV/JSON data protocol. The UI is bilingual (English and Chinese).
  • KLinePic CSV fields: trade_id, symbol, event_type, position_side, time, price, quantity, name, fee, note. Extra columns are ignored on import and listed back to you; put details such as fee currency inside note (for example fee_asset=USDT) only if you want to preserve them.
  • Binance export facts (per Binance's help center): spot exports live at Orders > Spot Order > Trade History > Export Trade History — up to one year per statement, five statements per month, links stored seven days, times shown in UTC+0; futures order history is a separate export.

Common mistakes and troubleshooting

UTC timestamps read as local time

Binance's spot history is shown in UTC+0. Chart those times as local and every marker shifts by hours. Encode the offset explicitly — +00:00 — in time.

Partial fills split into "trades"

One order can execute in several fills. Keep the rows but give them one trade_id; otherwise a single scale-in reads as five unrelated trades.

Quote value used as quantity

Exports often carry both the executed base amount and its quote total. quantity must be the base amount (1.2 ETH), not the USDT value of the fill.

USDⓈ-M and COIN-M mixed together

USDT-margined and coin-margined contracts are different products with different symbols and prices. Map each to its own symbol and never merge their rows into one trade.

Missing position_side in hedge mode

Hedge mode can hold long and short on the same contract at once. Without an explicit long/short, a closing buy is indistinguishable from an opening buy.

Order rows instead of fill rows

Order history records what you asked for — limit prices, canceled orders — not what executed. Drop every row without a real fill price and size.

FAQ

How do I turn Binance trade history into a chart?

Export your fills from Binance, map them into KLinePic's CSV fields (trade_id, symbol, event_type, position_side, time, price, quantity, fee, note), then upload or paste the CSV to render. No account is needed.

Does this work for Binance futures?

Yes. USDⓈ-M and COIN-M fills render the same way once each row has symbol, side, time, price, and size. Futures history is a separate export from spot, and derivatives rows should carry an explicit position_side.

How far back can Binance trade history exports go?

Per Binance's help center, a spot statement covers up to a full year from a selected date after 2017-07-13, with at most five statements per month. For longer periods, export in slices and merge the files.

What time zone are Binance timestamps in?

Binance's spot trade history help page notes the history is shown in UTC+0. Write that into time as an explicit offset such as 2026-05-10T09:15:00+00:00 so markers land on the correct candles.

Do I need a Binance API key to build the chart?

No. The statement download is enough; KLinePic renders from an uploaded or pasted file. For automation there is a documented Agent API and a CSV/JSON data protocol.

Can I render many Binance trades at once?

Yes. Batch rendering is supported — a month of Binance trades becomes a full set of review images in one pass, via the web UI or the documented Agent API.

Related guides