Short version: Master and slave terminals run on the same machine (PC or your own VPS) under the same Windows user. PropMirror on one chart each, choose the role, same channel name on both sides, Algo Trading on. Sizing by equity ratio or risk equivalence. Test on two demo accounts first, then go live. Own accounts only, hedging accounts only.
1. Prerequisites
| What | Why |
|---|---|
| Two or more MetaTrader 5 terminals on one machine, same Windows user | PropMirror exchanges the position state through a local file in the shared data folder (Common\Files). Terminals on different computers or different Windows users cannot see that file. |
| One master account and one or more slave accounts, all your own | Most prop firms allow mirroring between your own accounts; other people's accounts or signals are a breach. Check your firm's rules. |
| Hedging accounts | Netting accounts merge positions; the one-to-one pairing of master position and copy is impossible there. PropMirror refuses netting accounts. |
| An mql5.com account holding the purchase | One licence, both roles, ten activations; every terminal counts one (so up to five pairs). |
| Algo Trading on, on both terminals | The slave must be allowed to trade; the master only reads, but needs Algo Trading for its timer. |
| Optional: your own Windows VPS | The MQL5 VPS from within the terminal hosts a single terminal, not a pair. For 24/5 operation the pair needs its own Windows server. |
2. Installing a second terminal
Two accounts at the same broker: a terminal holds one account at a time, so you need a second installation. Two ways:
- Second installation into a different folder, change the target folder in the setup (for example
C:\MT5-Slave). Every installation has its own data folder underAppData\Roaming\MetaQuotes\Terminal\<ID>. - Portable copy: copy the terminal folder and start
terminal64.exe /portable(a shortcut with the parameter). The data folder then lives inside the program folder.
Accounts at two different brokers: each broker ships its own terminal anyway.
In both terminals: Tools → Options → Community tab → log in with the same mql5.com account. Otherwise activation of PropMirror fails in the second terminal.
3. Buy and install
- Market tab in the terminal → "PropMirror", or PropMirror on the MQL5 Market. 59 USD one-time, no subscription, one file for both roles.
- In the second terminal the product appears under Purchases → Install (same mql5 account). It then sits in both terminals under Navigator → Expert Advisors → Market → PropMirror.
- The free demo runs only in the strategy tester and shows a simulated copy cycle there (master opens, modifies, closes), so you have seen the pipeline before connecting real terminals.
4. Attaching the master
In the terminal of the source account: drop PropMirror on one chart of your choice.
| Input | Value |
|---|---|
| Role of this terminal | Master |
| Channel name | any name you choose, for example pmtest. Empty = the account number. Must be identical on every slave. |
| Sync interval (ms) | 50 (default). The master writes the complete position state twenty times per second and immediately on every trade event. |
| Broadcast only these magics | empty = all positions including manual ones; otherwise magic numbers, comma-separated. |
| Risk % per trade on the MASTER account | for example 2.0 if you want risk-equivalent sizing (section 6). 0 = not announced. |
| Privacy mode | masks account numbers on the panel and in the journal. |
The panel shows "PropMirror MASTER", the channel, the number of positions in the snapshot and the time of the last write. If the time keeps moving, the master is broadcasting.
5. Attaching a slave
In the terminal of every target account: drop PropMirror on one chart.
| Input | Value |
|---|---|
| Role of this terminal | Slave |
| Channel name | the same name as on the master. |
| Lot scaling mode | see section 6 |
| Copy SL/TP | only on if master and slave see the same prices (same broker). With different brokers leave it off: a stop copied as a price level can be triggered on the slave while the master keeps running. |
| Close copy when the master position is gone | on (default). |
| Copy only these master magics / Never copy these magics | filters, comma-separated, empty = all. |
| Magic number of copied positions | for example 777001. This is how PropMirror recognises its copies and leaves everything else on the slave alone. |
| SL/TP tolerance, Max slippage | 10 points / 200 points by default. |
| Freeze if master heartbeat is older (seconds) | 10. If the master stays silent longer, the slave freezes: no new copies, loud in the journal and by push. |
| Symbol mapping | only for differing symbol names: GER40>DE40;US100>NAS100 |
| Risk lock: name of a global variable | see section 7 |
The panel shows "PropMirror SLAVE", the channel, the state ("copying", "MASTER STALE", "RISK LOCK"), the number of copied positions and the measured latency between the master's write time and the slave's read time.
6. Sizing
- Multiplier: master lots times a fixed factor (1.0 = identical).
- Equity-proportional: slave equity divided by master equity. A 20k slave behind a 10k master doubles.
- Risk-equivalent (recommended between accounts of different size and rules): the master announces its risk per trade (for example 2%), the slave its own (for example 0.25%). Every copy carries the slave's risk, whatever the account sizes. The ratio is frozen at open; fluctuating equity never triggers rebalancing.
PropMirror never inflates below the broker minimum: if the calculation yields less than the minimum lot, the copy is skipped and the reason is written to the journal.
7. Coupling with PropGuardian
If PropGuardian runs on the slave account, enter the guardian's state variable in "Risk lock: name of a global variable": PropGuardian_<slave account number>_State. When the guardian locks the day (value 0) the slave stops reading the master at once: no new copies, no request hammering, existing positions untouched (the guardian closes those itself). On release, copying resumes. Every transition is one journal line and one push message.
8. Test on two demo accounts
See the whole sequence once before going live:
- Two demo accounts (the same broker is fine), attach master and slave as above, same channel name.
- Open a small position on the master. The copy appears on the slave within one cycle plus broker execution; the slave's journal names master ticket, lots and latency.
- Change SL/TP on the master (if Copy SL/TP is on), partially close, close. The slave follows.
- Close the master terminal briefly: after ten seconds the slave reports "MASTER STALE" and freezes. Start the master again: the slave carries on without opening anything twice.
- Close a copy on the slave by hand while the master still holds the position: PropMirror does not reopen it. That is intended (one-shot semantics); re-entry happens only through a new master trade.
9. Safety rules that are built in
Every master position is copied exactly once. One trade operation per cycle. Retry brake against rejected orders. Grace period after opening against double copies on slow brokers. Margin and trading-permission check before every order. Pairing through global variables, not comments, so restarts never lose an assignment.
10. What PropMirror cannot do
No copying over the internet (local only), no netting accounts, no third-party accounts, no pending orders (positions only), no proportional adding to existing positions (every master position is its own copy).
11. Help
Questions go into the Comments on the product page; every question gets an answer.