1. Getting Started

MT4 Backtester Pro automates MetaTrader 4 batch testing so you can validate EAs across in-sample and out-of-sample periods, then inspect the results in a dedicated research workflow.

System requirements

Windows 10 or 11, MetaTrader 4 installed, and internet access for first-time licence activation.

Version

Current app version: v2.49 (as shown in the launcher and log output).

Installation

  • Download the installer or standalone build from your dashboard.
  • Run the installer if you want shortcuts and a standard Windows setup.
  • If you download the standalone package, extract it and launch the .exe directly.

First launch & licence activation

  1. Open the app and go to the Settings tab.
  2. Enter your licence key in the Licence Key field.
  3. Click Activate.
  4. If activation succeeds, the app stores the licence locally and validates it on startup.
Activation note: the licence uses online validation and machine fingerprinting. That keeps the licence tied to one PC unless your plan allows otherwise.

Connecting to MT4

  • MT4 Terminal path — point to the backtesting terminal terminal.exe.
  • MT4 Data Folder path — point to the folder used by MT4 for tester data.
  • Portable Mode — enable if you launch MT4 with /portable.

Tip: if the terminal path is wrong, the app cannot start tests. If the data folder is wrong, reports and tester settings may not line up correctly.

2. Quick Start Guide

Here’s the shortest path to your first run.

  1. Load an EA file (.ex4).
  2. Load a SET file containing optimisation parameters.
  3. Enter one or more symbols, comma-separated.
  4. Set your IS and OOS date ranges.
  5. Click Start.
  6. Wait while the app runs the automated phases.
  7. Open the Results tab and analyse the output.
Typical workflow: configure → run overnight → inspect IS/OOS results → drill into detail panels → save favourites or build portfolios.

3. The Run Tab

The Run tab is the control centre for every batch. In the codebase, it sits under the main notebook’s first tab alongside Results and Settings.

EA File
.ex4 selection
Choose the Expert Advisor you want to test.
SET File
.set selection
Load parameter ranges and optimisation flags.
Date ranges
IS / OOS
Separate in-sample from out-of-sample validation.
Phases
1, 2, 3
Optimise, validate, then full-run winners.

Core fields

  • EA File selection — pick the compiled Expert Advisor.
  • SET File selection — load the optimisation file; use the built-in editor if you want to adjust the parameter ranges first.
  • Symbols — enter comma-separated instruments, including symbols with dots such as .DE40Cash.
  • Test Name — unique per batch; helps keep runs organized.
  • Date ranges — IS From/To and OOS From/To fields define your validation split.
  • Phase selection — choose whether to skip OOS or full runs when needed.
  • Deposit, Currency, Leverage, Spread — tester settings that shape the run environment.

Buttons, log, and status

  • Start begins the automation pipeline.
  • Stop requests a graceful stop after the current operation.
  • The Progress Log shows detailed run events, warnings, and phase transitions.
  • The bottom Status bar tracks the current step and elapsed progress.

What happens in each phase

Phase 1: IS optimisation

Runs MT4 optimisation over the in-sample date range and captures every parameter combination.

Phase 2: OOS validation

Runs the same optimisation over the out-of-sample range and matches the results back to the IS winners.

Phase 3: Full backtests

Runs individual backtests on the filtered winners so you get complete trade data and deeper analysis.

Why it matters

This flow helps separate raw optimisation luck from results that can survive a second period and a full trade-level review.

Practical note: use the Run tab for batch orchestration, not manual tinkering. The SET editor and Results tab exist so you can work faster once the batch is queued.

4. The Results Tab

The Results tab is where completed batches become useful. It contains the batch list, combined IS/OOS tables, full runs, favourites, and portfolio views.

Batches view

  • Shows all completed test batches.
  • Click a batch to open its analysis.
  • Double-click a batch to filter down to its IS/OOS results.

IS/OOS Results

A side-by-side table of optimisation results. Compare in-sample and out-of-sample metrics without leaving the app.

Column Meaning How to read it
PFProfit FactorGross profit / gross loss. Above 1.0 is profitable; higher is stronger.
RFRecovery FactorNet profit / max drawdown. Higher is better and usually indicates cleaner equity growth.
DD%Max Drawdown %Largest peak-to-trough decline. Lower is safer.
TradesNumber of tradesEnough sample size matters; a tiny trade count can be misleading.
ProfitNet profitDisplayed in deposit currency.
Win Rate / Sharpe / Expected PayoffExtra quality metricsUse them together; no single number tells the whole story.

Full Runs

Individual backtest results with full trade data. Use this view when you want the exact trade list, equity curve, and per-result breakdown.

Favourites

Save promising results for side-by-side comparison later. This is handy when you want to keep a shortlist of robust parameter sets.

Portfolios

Combine multiple strategies into a portfolio view so you can check diversification, combined equity, and smoother overall risk.

5. Analysis Tools

Click a batch in the Results tab to open the analysis suite.

Parameter Importance

Ranked correlation bars show which parameters most influence PF, RF, DD%, and Profit. Green means higher values help the metric; red means they hurt it.

Scatter Analysis

Scatter plots show each parameter versus all four key metrics with trend lines. They’re useful for finding sweet spots and dead zones.

Robust Rankings

Neighbourhood-based scoring rewards results that still look good when nearby parameter values are considered. It’s an anti-curve-fitting tool.

Distribution

Histograms of PF and DD% show whether the EA has a genuine edge or just a few lucky peaks in a noisy search space.

If most of the parameter space is profitable, that usually means the strategy has a real edge. If only one tiny ridge works, be suspicious.

6. Detail Panel

Clicking a result opens the detail panel for that specific row or backtest.

Overview

Shows the headline metrics so you can sanity-check the result quickly.

Equity & Drawdown

The equity curve and drawdown chart let you assess whether the return profile looks smooth, lumpy, or fragile.

Trade Analysis

  • Year-by-year performance
  • Monthly P/L
  • By day and hour
  • By trade duration

Trade List

Every trade is listed with entry/exit prices, P/L, and duration. Use this to inspect execution quality and weird behaviour.

SET File

Shows the exact parameter values used for the result. That makes it easy to reproduce or adjust a promising configuration.

7. Settings Tab

The Settings tab holds the MT4 path configuration and the licence controls.

  • MT4 Terminal path (.exe) — the terminal the app launches for backtests.
  • MT4 Data Folder — the data directory used by MT4.
  • Portable Mode — check this when launching MT4 with /portable.
  • Licence Key — paste your key here, then Activate or Deactivate as needed.
Tip: if the app says the MT4 terminal cannot be found, check the path in Settings first. That’s the most common setup issue.

8. The SET File Editor

The built-in SET editor lets you inspect and modify optimisation parameters without leaving the app.

What you can do

  • Load a SET file.
  • Edit Start, Step, and End values.
  • Enable or disable optimisation per parameter.
  • Save the edited SET file back to disk.

How to use it

  1. Select a SET file in the Run tab.
  2. Click the Edit button beside it.
  3. Adjust the parameter rows.
  4. Save the file and run your batch with the updated ranges.
[Parameter name]    Start     Step     End     Optimize
StopLoss            20        5        80      Yes
TakeProfit          50        10       200     Yes
RSI_Period          10        1        30      No

9. Tips & Best Practices

  • Use exhaustive optimisation, not the genetic algorithm, if you want reliable results.
  • Make sure you have enough historical data for the date ranges you’re testing.
  • Use an IS/OOS split like 70/30 to validate robustness.
  • Look for parameter zones, not just a single peak.
  • High PF with 2 trades is not a strategy. It’s a coincidence with good PR.
  • Use the Distribution view to check whether profitable results are common or rare.
  • Don’t trust results with very few trades; under 30 is usually too thin to take seriously.
In practice, the strongest results are the ones that remain acceptable across multiple nearby settings and across the OOS period.

10. Troubleshooting / FAQ

Common issues and the fastest fixes.

MT4 terminal not found

Check the terminal path in Settings. Make sure you selected the correct terminal.exe.

No optimisation results

Ensure your SET file has parameters marked for optimisation. If every parameter is fixed, MT4 will have nothing to vary.

Data warning: insufficient history

Download more data in MT4 via Tools → History Center, then rerun the test.

Licence expired

Renew your subscription at mt4backtester.com.

Software hangs after MT4 closes

Make sure only the intended backtesting MT4 terminal is selected in Settings. If multiple terminals are open, the app may be watching the wrong one.

FAQ shorthand: most issues are path problems, data problems, or a SET file that doesn’t actually contain optimisation ranges.

11. Keyboard Shortcuts & Controls

  • Right-click on results tables for context menus.
  • Use the column picker to choose which metrics are visible.
  • Open the filter dialog to narrow results by PF, drawdown, trades, RF, and other criteria.
These controls are there to speed up review when you’re dealing with a large optimisation batch.

← Back to main site