In January 2025 I was trading two accounts: a $100,000 prop challenge and my personal $12,000 account. Same strategy, same entries — or so I thought. After three weeks, the prop account was up 4.2% and my personal account was up 1.1%. Same trades. The gap was my trade copier setup: the receiver ran on my home PC while the master traded on a London VPS, and every signal crossed thousands of miles of internet before my broker saw it. On gold, that delay cost me an average of 8 pips per trade. I was paying a distance tax on every single position. This mt5 trade copier local remote guide is everything I learned fixing it — when to copy locally, when remote makes sense, and the latency math that decides whether copying is even worth it.
I size every receiver account with the DarkWolf MT5 Signal Calculator before connecting it — copying without independent sizing is how small accounts die from trades meant for big ones.
How a Copier Actually Moves a Trade From A to B
A trade copier is two programs: a sender EA on the master terminal that watches for new positions, and a receiver EA on the slave terminal that opens matching positions. They talk through files or the internet, depending on the design. The master opens EURUSD buy 1.0 lot, the sender broadcasts it, the receiver reads it a fraction of a second later and opens its own buy, scaled to its account.
Local copying means both terminals run on the same machine — usually a VPS. Communication is nearly instant (under 50ms) because nothing leaves the computer. Remote copying means the terminals are on different machines, possibly different continents, talking over the internet. That adds hundreds of milliseconds each way, plus whatever the copier's own polling interval adds.
| Aspect | Local copier | Remote copier |
|---|---|---|
| Terminals location | Same machine/VPS | Different machines, anywhere |
| Typical delay | 10–50 ms | 150–600 ms |
| Failure mode | One machine dies, both stop | Internet drop orphans receiver |
| Best for | Scalping, news, tight stops | Swing trades, signal services |
| Cost | One VPS | Two always-on machines |
The rule I live by now: if your average stop is under 30 pips, copy locally. The delay tax on tight stops eats the edge. If you hold for days, remote is fine — 400ms doesn't matter on a 300-pip swing. My gold scalps moved to a local setup within a week of measuring that 8-pip gap. Before you enable anything, read the MT5 automated trading setup guide — both terminals need AutoTrading on, and that's the single most common "copier not working" cause.
$100,000 Account: 20 Copied Trades, Master vs Receiver
Here is the before-and-after from my own fix. First 10 trades on the remote setup (home PC receiver), next 10 after moving the receiver to the same London VPS as the master (local copy).
| Trade | Setup | Master fill | Receiver fill | Gap |
|---|---|---|---|---|
| 1–5 | Remote (home PC) | 1.0850 avg | 1.0857 avg | 7 pips |
| 6–10 | Remote (home PC) | 2942.10 avg (gold) | 2942.95 avg | $0.85 |
| 11–15 | Local (same VPS) | 1.0862 avg | 1.0863 avg | 1 pip |
| 16–20 | Local (same VPS) | 2951.40 avg (gold) | 2951.48 avg | $0.08 |
The gap collapsed from 7 pips to 1 pip on EURUSD and from $0.85 to $0.08 on gold. Over the next month, the receiver's performance converged to within 0.3% of the master's — the remaining difference was just the smaller account's rounding on lot sizes. One VPS move, edge restored.
The Latency Math That Decides Your Fill
Copy delay isn't one number — it's a stack. Each layer adds up, and the total decides how far price moves between the master's fill and yours.
| Variable | Meaning | My remote setup | My local setup |
|---|---|---|---|
| Sender interval | How often sender checks for trades | 250 ms | 100 ms |
| Network transit | Signal travel time | 380 ms | 5 ms |
| Receiver interval | How often receiver polls | 500 ms | 100 ms |
| Total delay | Sum of the stack | ~1.2 sec | ~0.25 sec |
At 1.2 seconds during a gold momentum burst moving $0.70/sec, the expected gap is $0.84 — matching my measured $0.85 almost exactly. The math predicts the pain before you feel it. If your expected gap exceeds 20% of your average stop distance, don't copy that strategy remotely. Either go local or don't copy it at all.
Running Two Accounts Off One Signal
My current setup: one London VPS, two MT5 terminals in portable mode with separate data folders, sender EA on the master chart, receiver EA on the slave. Risk multiplier 0.12 on the receiver — the master risks 1% of $100,000 ($1,000), the receiver risks roughly 1% of $12,000 ($120).
Three details that matter. First, symbol mapping: my master broker quotes XAUUSD and the slave quotes XAUUSD.pro. Every copier has a symbol-mapping table — fill it in or the receiver silently ignores gold trades while copying everything else. I lost a week of gold trades to this before I noticed. Second, the receiver needs its own magic number range so its trades don't confuse the sender — set the sender to ignore the receiver's magic, otherwise you can build an infinite copy loop. I watched a demo account open 40 duplicate positions in 90 seconds once. Third, partial closes: make sure your copier mirrors them. A master that scales out at +20 pips while the receiver holds full size to the final target is trading a different strategy with the same entries.
For copying third-party signal services, Myfxbook AutoTrade is the established third-party option — it handles the plumbing, but the latency math above still applies to your fills.
Sizing the Receiver Account in the Calculator
The receiver must be sized independently. Copying the master's 1.0 lot onto a $12,000 account when it was sized for $100,000 is an 8x risk multiplier you never agreed to. Here is my calculator routine for each new receiver.
| Input Field | What it means | Sample value |
|---|---|---|
| Account balance | Receiver account equity | $12,000 |
| Risk percent | Match the master's risk %, not its lots | 1% |
| Stop loss (pips) | Master's stop plus expected copy gap | 32 pips (30 + 2 gap) |
| Take profit (pips) | Master's target minus gap | 58 pips (60 − 2 gap) |
The output gives me the receiver's lot size directly, and I set the copier's risk multiplier to match. Note the stop adjustment: the receiver's effective stop is wider by the copy gap, so sizing off the raw master stop understates risk. Two pips sounds trivial until it's every trade for a year.
Copier Mistakes I Made So You Don't Have To
The infinite loop deserves its own warning: sender and receiver on the same account without magic-number filtering will copy each other's copies forever. My demo survived; my dignity didn't. Always filter by magic number.
Second mistake: leverage mismatch. Master on 1:500, receiver on 1:100 — same 1.0 lot, but the receiver's margin requirement was 5x higher. It didn't blow up, but it couldn't open the full basket during a grid sequence and missed the recovery leg. Match leverage across accounts or scale the multiplier down.
Third: the weekend-gap orphan. My remote receiver's PC rebooted for updates on a Sunday. Monday open, the master held weekend-gap-adjusted positions the receiver never saw. For two days the accounts held different portfolios while I assumed they matched. Now both terminals run on the VPS with updates paused during market hours, and I reconcile positions every morning — a 60-second check inside the server stability routine I run anyway. The Asian session notes cover the overnight monitoring habits that pair with this.
Trade Copier FAQs
Is a local or remote copier faster?
Local, by an order of magnitude — 10–50ms versus 150–600ms for remote. For scalping or news trading, always copy locally on the same VPS. Remote only makes sense for swing strategies where a half-second delay is irrelevant against multi-day holds.
Can I copy trades between two different brokers?
Yes, with symbol mapping. Brokers often suffix symbols (XAUUSD vs XAUUSD.pro), and the copier needs the mapping table filled in or it skips those symbols silently. Also verify both brokers allow the strategy — some prohibit latency arbitrage explicitly in their terms.
Do I need a VPS for trade copying?
For local copying, one VPS hosting both terminals is the standard setup and what I recommend. For remote copying you need each terminal online around the clock anyway, so that's two always-on machines. Either way, a home PC that sleeps is not a copying infrastructure.
What is reverse copying and when is it useful?
Reverse copying flips the direction — master buys, receiver sells. It is used for hedging across accounts or for fading a signal provider you believe is systematically wrong. Most copiers support it with a single toggle, but test on demo first: reversed averaging strategies get ugly fast.
Will the copier copy partial closes and breakeven moves?
Good ones do, bad ones don't — and this is the feature to verify before buying. If the master scales out at +20 pips and your receiver holds full size, you are trading a different risk profile with identical entries. Check the copier's docs for partial-close sync specifically.
Can different leverage between accounts break copying?
It can silently degrade it. Lower leverage on the receiver means higher margin per lot — during basket or grid sequences the receiver may fail to open later positions while the master continues. Either match leverage or reduce the receiver's risk multiplier to compensate. Investopedia's trading education library has a good primer on how leverage multiplies both gains and copying errors.
Do prop firms allow trade copiers?
Most allow copying between your own accounts but prohibit copying third-party signals or challenge-passing services — that is explicitly banned at many firms and detected via trade-pattern matching. Copying your own strategy across your own accounts is generally fine; read your firm's terms before connecting anything.