MetaTrader workflow

MetaTrader Historical
Data Download

Audited forex data releases for Strategy Tester research workflows. Parquet delivery is live now; MT4 and MT5 conversion files are only released after matching QA artifacts are uploaded.

74
Verified symbols
300.4M
Rows in R2 bundle
518
Parquet files
QA
Source-observed coverage

Current source bundle spans May 30, 2000 through May 31, 2026 UTC. Coverage varies by pair and timeframe; we do not claim gap-free continuity.

What is live today

The commercial proof is the audited source package, not an unsupported platform export. For MetaTrader users, the offer is source data plus documented coverage so conversion decisions are visible before a Strategy Tester run depends on them.

Major-8 rows
79.0M
Major-8 files
56
Major-8 M1 rows
60.4M

Why traders switch to us

MT4's Built-in Data

  • History Center coverage varies by broker, symbol, and server.
  • "Not enough historical data" errors in Strategy Tester
  • Backtest results vary due to missing bars and import assumptions.
  • Free source downloads still require conversion, dedupe, range checks, and QA.

Our Solution

  • Audited release coverage with documented symbol ranges
  • Parquet files available now; MT4 and MT5 conversion artifacts are scoped separately
  • Coverage reports show which ranges are safe to convert and test
  • Order-assist path for invoices, delivery-fit questions, and MT4 conversion requests

Compare data sources

FeatureMT4 Built-inDukascopyHistoricalFX
Data Range~2 years2003+Audited release
Gap visibilityNoMostlyAudited coverage report
Account RequiredNoYesNo
FormatHSTBinary (conversion needed)Parquet now; MT4/MT5 artifacts pending QA
Download SpeedSlowVery slow (per pair)Instant

MetaTrader conversion workflow

The path we use before publishing MT4 or MT5-ready artifacts

1

Audit source coverage

Start from the Parquet release, coverage report, duplicate timestamp audit, null audit, and documented known gaps for each symbol.

2

Select tested ranges

Only source-backed ranges are converted. Multi-year gaps are not interpolated or smoothed into fake continuity.

3

Build platform artifacts

MT4 HST/FXT or MT5 custom-symbol exports must be generated from the audited source release and matched back to row counts.

4

Release only after QA

Conversion files are not listed for sale until the matching artifacts exist in storage and the public release notes reflect their coverage.

Current status: Parquet releases are live. MT4 and MT5-ready downloads are pending conversion QA.

Ready to backtest properly?

Start with audited Parquet source files, then scope MT4 or MT5 conversion only for ranges your strategy can defend. This keeps the paid path aligned with what is actually fulfilled today.

$0

EUR/USD sample

$49

Major-8 source kit

Quote

MT4 conversion or audit

Parquet delivery is live. MT4/MT5 conversion files are not sold until matching artifacts are generated, uploaded, and audited.

Need help before paying?

Request manual checkout help, an invoice, or delivery-fit confirmation. This captures the order context so we can reply without guessing.

If the intake endpoint is unavailable, use the invoice email path below. It preserves the same product context without waiting on automation.

Email invoice request

Frequently asked

Does this work with Expert Advisors (EAs)?
The current product is audited source data, not a direct EA plug-in file. Use it to build and validate MT4 or MT5 conversion files for the exact ranges you plan to test.
What timeframes are included?
The release includes M1-derived coverage across M1, M5, M15, H1, H4, D1, and W1 bundles where those release artifacts have passed QA.
Can I use this with MT5?
Yes, as source data for MT5 custom-symbol workflows. Direct MT5 import artifacts are not sold until the matching files are generated, audited, and uploaded.
Why not just use Dukascopy data?
Dukascopy is useful source material, but it still requires slow downloads, conversion, range checks, duplicate checks, and release packaging. We sell the audited source release first and only publish platform-specific files after QA.