How to Copy Trade on MT5 and cTrader: A Step-by-Step Setup Guide

A trader messaged us last month convinced his copier was broken. His MT5 master filled a 2-lot EURUSD buy, and nothing landed on his cTrader follower. No error, no rejection he could see, just silence. The copier was working fine. His follower broker listed the pair as EURUSD.r, the master fired EURUSD, and with no mapping rule the order was rejected before it reached the book. That single dot is the most common reason a "broken" MT5-to-cTrader setup is not broken at all. This guide walks the whole setup in order so you never hit that wall.

We will go in the exact sequence you should execute it: confirm what you need, pick master and follower roles, connect MT5, connect cTrader, set proportional lot sizing, map symbols, set firm buffers, run a minimum-lot test, then go live. Each step is concrete, with the numbers that matter.

What you need before you start

Before you copy a single trade, you need API access to every account and a clear picture of which platform speaks to which. Copy trading here means automated mirroring of orders from one source account (the "master") into one or more destination accounts (the "followers") in real time. The native tools each platform ships with only copy within their own walls, so the first thing to understand is what those tools actually are.

MT5 ships a built-in copy feature through the MQL5 Signals service. A provider publishes their account and subscribers auto-copy it by supplying the account's investor password, which connects the MQL5 Signal Server in read-only mode to scan open positions and trade history. The investor password cannot place or manage trades, and if the provider changes it, transmission stops automatically. A valid MQL5.community account must be set in the terminal's settings for any of this to work. That covers MT5-to-MT5 only.

cTrader is where people get confused, so define both products clearly. cTrader Copy is the in-app retail marketplace built into the platform: two-click subscribe, equity-to-equity sizing, providers who can charge performance, management, or volume fees shown upfront. Separately, the cTrader Open API is the developer layer, a protobuf or JSON API using OAuth 2.0, and it is the layer a server-side copier uses to reach a cTrader account programmatically. You join Copy through your broker. You connect through the API. They are not the same setup path, and a how-to that blurs them will send you down the wrong road.

So your pre-flight checklist is short but non-negotiable: login credentials for each account, API access enabled on each broker, your prop firm's current rules on multi-account copying read and confirmed, and a decision on which account is the master. The six-step flow in the diagram below is the whole job from connection to go-live.

Choosing master vs follower accounts

The master is the account you place original trades on, and every follower mirrors it, so pick the master you actually trade by hand. If you scalp your funded Apex-style futures account and want a CFD account to ride along, the account you click is the master and the rest are followers. Roles are not interchangeable mid-setup, so decide first.

There is one rule that overrides convenience: prop-firm policy. The 2026 industry pattern is that replicating your own trades across your own accounts is generally allowed, while copying any external signal or another person's account is treated as prohibited group trading regardless of how the software is configured. That generalization is a trap when stated flatly. It holds at firms like Apex, but FTMO explicitly restricts copying even between a user's own FTMO accounts because it wants independent decisions, and several firms moved to single-account-execution policies in 2026 that prohibit any multi-account mirroring at all.

Decision rule for master selection: choose the account with the cleanest execution and the broadest instrument list as master, because a follower can always trade a subset, but it cannot invent an instrument the master never sends.

Connecting MT5 accounts

Connecting an MT5 account to a server-side copier means giving the copier the credentials it needs to read fills on the master or place orders on the follower, depending on the role. For MT5-to-MT5 inside one terminal, the native Signals route works with an investor password, which is read-only by design and perfect for a master you only want observed.

For a server-side copier, the steps are sequential. First, log in to the MT5 account in its terminal to confirm the credentials are live. Second, in the copier, add the account and choose its role, master or follower. Third, supply the server name (your broker's MT5 server string, not just "MT5"), login number, and the correct password: investor password for a read-only master, trading password for a follower that must place orders. Fourth, let the copier confirm the session is authenticated before you move on.

The single most common MT5 connection failure is using the wrong server string. Brokers run many MT5 servers ("BrokerName-Live7" vs "BrokerName-Live2"), and the login number only works against the exact server it was issued on. If authentication fails immediately, check the server string before you touch anything else. Our MT5 trade copier and MT4 trade copier pages cover the platform-specific connection details.

Connecting cTrader accounts

Connecting a cTrader account to a server-side copier goes through the cTrader Open API and OAuth 2.0, not through the in-app Copy marketplace. This is the part people skip and then wonder why their MT5 master will not reach cTrader.

The flow follows the API spec exactly. You authorize an app against your cTrader ID, which returns an authorization code. That code is short-lived: it expires in one minute, so exchange it for an access token immediately. The access token lasts roughly thirty days and is refreshable through a non-expiring refresh token, so a well-built copier renews it silently and you authorize once. The app then authorizes a specific account by sending an account-authorization request with the account ID and access token, and the "trading" scope grants the permitted trading operations.

In practice with a managed server-side copier like Thor, you click to authorize cTrader, approve the OAuth prompt, pick the account, and the token plumbing is handled. If you are building your own integration, re-verify the spec against the official cTrader docs first, because the auth-code window is unforgiving.

Setting proportional lot sizing correctly

Proportional lot sizing means each follower trades a volume scaled to its capital relative to the master, so a smaller account is not blown out by a master sized for ten times the equity. Get this wrong and the follower is either over-leveraged or trading dust. The diagram below shows one master feeding an MT5 follower at 1.0x and a cTrader follower at 2.5x through the copier.

The trap is that "proportional" means three different things depending on the tool. A server-side copier uses a fixed multiplier you set per follower. cTrader Copy uses a pure equity ratio, with copied volume equal to investor equity divided by strategy-provider equity times the provider's volume. MT5 Signals uses none of those cleanly: it sizes by deposit-percentage allocation, leverage ratio, and currency conversion, which means a leverage mismatch can silently inflate follower volume. Mixing these mental models is exactly how followers end up over-leveraged.

Here is the same master trade through all three models. The master places a 1.00-lot BUY EURUSD.

Look at the last row. The follower copies up, taking 1.60 lots from a 1.00-lot master, because the subscriber's higher leverage and deposit allocation worked out to a 1.6 ratio in MQL5's published example. That is the leverage-mismatch effect, and it is the single most overlooked sizing risk for anyone moving from MT5 Signals to a fixed-multiplier copier. Treat that 1.6 as an illustration; the real number depends on live equity, leverage, and FX rates at copy time.

A fixed multiplier is the only sizing model where you know the follower's volume before the trade fires. Equity-ratio and deposit-leverage models compute it for you, which is convenient right up until a leverage mismatch sizes you up.

Decision rule: set each follower's multiplier to its capital divided by the master's capital, then cap the follower's max position size as a hard ceiling so no sizing surprise can exceed it. For per-account and proportional sizing across mismatched account sizes, that ceiling is what saves you.

Symbol mapping across brokers

Symbol mapping is the rule that tells the copier the master's instrument name equals the follower broker's name for the same instrument, and without it cross-broker copying breaks silently. The same pair can be EURUSD on one broker and EURUSD.r, EURUSDecn, or EURUSD+ on another. Gold can be GOLD on one and XAUUSD on another. Some brokers even render it EUR/USD with a slash.

Copiers handle this with mapping rules and suffix settings. Simple dot-suffixes like .r can often be auto-mapped, because the copier strips the suffix and matches the root. Non-dot suffixes like ecn or + usually need a manual rule, and metals or indices aliases like GOLD versus XAUUSD almost always need manual mapping because the names share no common stem.

Return to the opening scenario through the lens of sizing. Follower B was set to 2.0x, so the master's 1.00-lot EURUSD becomes a 2.00-lot order on the follower. If that follower's broker lists the pair as EURUSD.r and there is no mapping, the 2.00-lot order is rejected outright, with no obvious error in most setups. The sizing was perfect. The mapping killed it.

• Auto-map dot-suffixes first (EURUSD to EURUSD.r) and verify each one fired.
• Manually map non-dot suffixes (EURUSDecn, EURUSD+).
• Manually map every metal and index alias (GOLD to XAUUSD, US30 to DJ30, and similar).
• Confirm slash variants are handled (EUR/USD to EURUSD).

If you trade the same instruments across MT4, MT5, and cTrader, our MT4 vs MT5 vs cTrader comparison covers where the symbol conventions diverge by platform.

Setting compliance buffers below firm limits

A compliance buffer is a self-imposed limit set below your prop firm's hard limit, so a copied trade never trips a firm rule by a fraction. Because a copier fires instantly across accounts, a master mistake replicates everywhere at once, and the buffer is your circuit breaker.

Set three buffers per follower. Max daily loss below the firm's daily-loss limit, so the copier stops opening new copies before the firm's threshold. Max position size below any firm contract cap. And, where the firm publishes one, a trailing-drawdown buffer that halts copying with headroom to spare. The exact gap is your call, but leaving five to ten percent of headroom between your buffer and the firm limit absorbs slippage and the timing skew between accounts.

This is also where the detection question lives. Firms cannot see the copier, but they can see its fingerprint, and 2026 detection leans on IP fingerprinting and millisecond fill-timestamp matching. A commonly reported threshold is that orders sharing an IP and filling within roughly ten milliseconds get flagged across firms. Treat that ten-millisecond figure as industry lore from prop-education sites, not an official firm-published rule, but the pattern is real: identical fills from one IP are a flag even on your own accounts. The mitigation people reach for is dedicated IPs and a little execution jitter, which again is third-party advice, not firm documentation.

Running a minimum-lot test before going live

Run one minimum-lot trade through the full chain before you go live, because it surfaces mapping and sizing bugs at the lowest possible cost. This is the step beginners skip and then pay for on a real position.

1. Place a single minimum-volume trade on the master during a liquid session.
2. Confirm it lands on every follower at the expected scaled volume, not just that it lands.
3. Check the symbol matched on each follower broker, especially any you mapped manually.
4. Close the master position and confirm every follower closed in step.
5. Open the copier's log and verify zero rejections.

If the follower volume is off, your multiplier or sizing model is wrong. If a follower shows nothing, it is almost always a symbol-mapping gap. If the close did not propagate, your position reconciliation needs attention before any real size goes near it. Only when all five pass do you scale up. Same discipline applies to futures and CFD legs; our CFD trade copier and futures trade copier pages cover the asset-class specifics.

Server-side vs a local EA copier

For MT5-to-cTrader or any cross-broker copying, a server-side copier is the only architecture that works, because a local MT5 Expert Advisor physically cannot reach a cTrader account. An EA runs inside the MT5 terminal and can only read and write MT5 accounts. cTrader speaks the Open API, which the EA has no path to, so people burn days trying to make a local EA "see" a cTrader account when it is architecturally impossible.

Here is the honest tradeoff, because server-side is not always the answer. If you copy MT5-to-MT5 only, on one machine you keep on anyway, a local EA is genuinely fine and cheaper. It avoids handing credentials to a third party and works inside a single terminal. The moment you add a second platform, a second broker, or you need the copy to run when your PC is off, the local EA stops being viable.

That is the niche a server-side copier fills. Thor copies one master into MT5 and cTrader followers server-side at about seventeen milliseconds with per-account proportional sizing, no local EA and no VPS to babysit, across futures and CFDs on eleven-plus platforms. Where it is not the answer is the simple single-terminal MT5-to-MT5 case, where the native Signals route or a local EA does the job without a subscription. If you are weighing whether you even need a VPS for any of this, our piece on whether you need a VPS for copy trading futures walks through it, and if you are new to the category, start with what copy trading is.

One last decision rule. If your answer to "does any follower live on a different platform or broker than the master" is yes, go server-side and stop evaluating local tools. If it is no, and your PC stays on, a local copier is a defensible, cheaper choice. The architecture follows the topology, not the marketing.

Frequently asked questions