How to Install an EA on MT5 for a Prop Firm Account, Step by Step

The first step in learning how to install an EA on MT5 for a prop account has nothing to do with MT5. It is confirming that the firm permits automation on the specific account type you bought, in writing, with today's date. Policies differ between firms, between evaluation and funded stages, and between account models at the same firm, and they get revised.

Ask support directly and save the reply. If the answer is ambiguous, treat it as a no until it is not. This costs you ten minutes and removes the one scenario no configuration can fix: a technically flawless setup that violates policy from the first tick. The wider picture is in [are trading bots allowed at prop firms](/blog/are-trading-bots-allowed-prop-firms).

One more thing to settle before installing: which terminal your firm actually issued. A firm that gave you an MT5 login is straightforward. If you were issued cTrader, TradeLocker or DXtrade, the file in this guide will not load, and [running an EA on TradeLocker, DXtrade and cTrader](/blog/run-ea-on-tradelocker-dxtrade-ctrader) is the piece you need instead.

This part is genuinely quick, and it is the same on every MT5 build.

Automation has two switches and both must be on. The Algo Trading button in the toolbar controls the whole platform. The Allow Algo Trading checkbox inside the EA's own dialog, on the Common tab, controls that instance. Traders routinely enable one, see nothing happen and conclude the software is broken.

The proof is the face in the top right corner of the chart. A smiley face means the EA is loaded and permitted to trade. A sad face means it is loaded and blocked, which is almost always the toolbar switch or the per-EA checkbox. No face at all means it never attached, so go back to the drag step.

Some commercial EAs also need a URL added under Tools then Options then Expert Advisors, or DLL imports allowed in the same place. If the vendor instructions mention either, do it before you conclude the software is broken, because a missing permission there produces silence rather than an error.

Then read the Experts and Journal tabs in the Toolbox. Those two tabs are where MT5 tells you exactly what happened, including refused orders and the reason. A trader who reads the Journal solves most setup problems without asking anyone.

A set file is a saved list of input values. It exists because the same software has to behave differently for a $10,000 one-step account and a $200,000 two-step account at a different firm, and those differences are not cosmetic. Load it in the EA dialog, on the Inputs tab, with the Load button at the bottom.

This is the step where prop accounts are actually lost. Running a default or borrowed set file against a rulebook it was not built for produces software that trades correctly and breaches anyway, because its sizing and its stops were tuned for someone else's limits. If the concept is new, [set files explained](/blog/setfiles-explained) covers it properly.

The inputs worth checking by eye, whatever the set file says: the risk per trade, expressed as a percentage rather than a fixed lot; the maximum lot size, against your firm's cap; the daily loss ceiling, set well inside the firm's line rather than on it; and the news filter, if the EA has one. On sizing, [the half percent rule](/blog/position-sizing-half-percent-rule) explains why the small number survives more evaluations than the ambitious one, and a maximum lot set above your firm's cap is what makes orders get rejected with no explanation anywhere on the chart.

Prop firms hand out accounts on brokers that name instruments their own way. Gold might be XAUUSD on one server and XAUUSD.r, XAUUSD.pro or GOLD on another. An EA looking for a symbol that does not exist under that exact name does nothing at all, silently, and the trader concludes it is broken.

Check the exact spelling in Market Watch, and if the EA has a symbol suffix input, fill it in. While you are there, look at the spread and the contract size for that symbol on that server, because both change what a given lot actually risks.

Execution differences matter more than most traders expect at this stage. The same strategy on two servers can produce different fills, and the gap shows up as slippage on stops rather than as an error message. Expect some difference, and judge it against the same strategy on a demo of the same server rather than against a backtest.

An EA only exists while MT5 is running and connected. Close the lid, lose the WiFi, let Windows install an update overnight, and the software stops mid-session. The real damage is the position already open, with a stop that now depends on a platform that is no longer there.

A VPS solves this because it is a Windows machine in a data centre that never sleeps, and you disconnect from it without disconnecting MT5. Traders on Mac have a second reason to use one: MetaTrader on macOS runs through a compatibility layer where Open Data Folder commonly misbehaves, which makes the install itself harder than it needs to be. Our setup notes are in [VPS for a prop firm EA](/blog/vps-for-prop-firm-ea).

Run it on a demo account of the same size and the same firm for a few sessions before the evaluation starts. You are not testing whether the strategy is profitable, which a few days cannot tell you. You are testing that it attaches, sizes, places stops and respects its daily line exactly as configured, on that server, with that symbol name.

The install is finished when the software has traded, not when the smiley face appears. On the first live session, sit with it for the first two or three trades and check four things against what you configured, because this is the cheapest moment to catch a mismatch.

Check the lot size the EA actually sent, against the risk percentage you set. A set file tuned for a $100,000 account dropped onto a $25,000 one will size four times too large, and nothing in the platform warns you. Check that a stop loss is attached to every position the moment it opens, since some firms require it and an unprotected position is the fastest route to a breached account either way. Check the time the EA became active against the session you expected, because server time is commonly not your local time and a strategy built for London can end up trading Asia. And check that it stops where it should: paper-trade the daily line by adding up the losses it would take before halting, and confirm the number sits inside your firm's limit rather than on it.

Then leave it alone. The most common damage after a clean install is a trader tweaking inputs mid-evaluation because two trades went against them. Two trades are not information. If you genuinely need to change something, change it between sessions, write down what you changed and why, and give it enough trades to mean anything.

One licence commonly needs to cover several accounts, and MT5 handles this through multiple terminal installations, each in its own folder with its own login. The mechanics, including what breaks when people try to shortcut it, are in [running the same EA on multiple prop accounts](/blog/same-ea-multiple-prop-accounts).

Our disclosed position: PraxAI publishes this blog and sells trading software for MetaTrader 4 and 5, with set files built for each firm's rules and PraxAI GUARD enforcing daily loss and drawdown limits in code. How to judge any tool in this category, ours included, is covered in our guide to the [best AI trading bots for prop firms](/blog/best-ai-trading-bot-prop-firms-2026). We sell software, not funded accounts, and nothing here makes a pass certain. The installation sequence in this guide is the same whether the .ex5 came from us or from anyone else.

If you take one habit from this article, take the boring one: after every install, place one trade on demo and read the Journal line by line. The five minutes you spend confirming that the software did exactly what you configured is the cheapest insurance in this business.