Converting an MT4 Indicator into an EA: What the Indicator Never Told You

An indicator draws an arrow, changes a colour or crosses a line. It tells you that something happened. It doesn’t tell you when to enter, how much to risk, where the trade is wrong or when to get out. Converting an MT4 indicator into an Expert Advisor means writing all of that, and making sure the EA sees the same signal you see on the chart.

The second part is where most conversions go wrong. An EA doesn’t look at the chart. It reads numbers from the indicator’s buffers, bar by bar, and some indicators keep rewriting those numbers after the fact. An EA built on such an indicator can trade signals that its own backtest never shows.

Below are the two ways to put an indicator inside an EA, what the EA can and can’t read from it, how to spot a repainting indicator, the trade rules a conversion has to add, and how to test the result. At the end is a list of what to prepare before you order one.

Two ways to put an indicator inside an EA

If you have the source code, rewriting is usually the better choice. If you only have the compiled file, iCustom() is the only route, and the next section decides whether it can work at all.

What the EA reads: buffers, not arrows

iCustom() calculates a custom indicator and returns one value from one of its buffers for one bar. The inputs have to be passed in the same order and with the same types as the indicator declares them, and the buffer index has to match the one the indicator fills (MQL4 Reference). Get either wrong and the EA reads a different line, or the same line calculated with different settings, without any error.

Arrow indicators usually store a price in a buffer on signal bars and an empty value on all the others. In MQL4 that empty value is EMPTY_VALUE, 2147483647, not zero. An EA that treats “not zero” as a signal will see a signal on every bar. Three more cases need care:

Repainting: when the history isn’t what you saw

Some indicators rewrite values on bars that have already closed. A swing-low arrow appears on the current bar, and when price makes a lower low later, the arrow moves there and disappears from the bar where you first saw it. Indicators built on future bars do the same by design: a ZigZag, a centred moving average, or a fractal, which needs two bars to its right before it’s confirmed.

For an EA this is serious. Live, it trades the arrow it saw. The backtest, run later on the rewritten history, only sees the arrow in its final position, which is usually a much better entry. The result is a strategy that looks excellent in the tester and can’t be reproduced live.

When exactly is there a signal?

An indicator’s value on the current bar, shift 0, changes with every tick until the bar closes. An arrow can appear at 10:03 and be gone by 10:14. That’s why most converted EAs read signals from the last closed bar, shift 1, and act once at the start of the next bar.

The choice has to be explicit in the specification. Reading the current bar gives earlier entries and signals that may not survive the bar. Reading the closed bar gives fewer, final signals, one bar later. The EA also needs a rule against acting twice on the same signal, for example after a restart, and a way to read higher-timeframe indicators without using a higher-timeframe bar that hasn’t closed yet.

The rules the indicator never had

Once the signal is read correctly, the EA needs everything a trader would otherwise decide by hand. These are the options we’re asked for most often, and any of them can be built in.

Testing the converted EA

Other platforms

The same indicator can drive an EA on MetaTrader 5, where iCustom() returns a handle and the values are read with CopyBuffer(), or a strategy on NinjaTrader, cTrader or TradeStation. We don’t use automatic converters for this. The indicator and the trading logic are rewritten by hand in the target platform’s own language, and checked against the original signal by signal.

What to prepare before you order

Building one with us

We convert MT4 indicators into Expert Advisors to the client’s own rules, from a single arrow indicator with a fixed stop to multi-indicator systems with filters and risk controls. You talk directly with the developer who writes your code. Before any code is written we check the indicator with you, including how it stores its signals and whether it repaints, and that first consultation is free.

You receive the EA with full source code, and bugs found after delivery are fixed at no extra cost. Since 2018 our team has completed over 3,000 development projects for traders in more than 120 countries.

Discuss your indicator conversion →

Need it on another platform? → MetaTrader 5 developers · NinjaTrader developers

FAQ

Can you convert an indicator without its source code?

Often, yes. If the compiled .ex4 file stores its signals in buffers, the EA can read them through iCustom(). If it draws its signals as chart objects, the logic has to be rewritten from a description of how the indicator works.

Why does my EA trade differently from the arrows on my chart?

The usual causes are reading the current bar instead of the closed one, a wrong buffer index or input order in iCustom(), testing for zero instead of EMPTY_VALUE, or an indicator that repaints its past signals.

How can I tell if an indicator repaints?

Screenshot its signals live, then compare with the same bars later, or watch it in the Strategy Tester’s visual mode. If arrows appear and disappear on bars that have already closed, it repaints.

Can the EA run on MetaTrader 5?

Yes. The indicator and the EA are rewritten in MQL5 by hand. MetaTrader 5 also brings a tester with real tick data, which helps for short-term signals.