Por William Harris · Última revisión
How to Install a .set Preset File in MT5
Qué necesitarás
- • MT5 with the matching EA already installed
- • .set file from the vendor or your own backtest
- • Text editor (optional, for inspecting the .set)
Instrucciones paso a paso
Paso 1: Understand what a .set file is
A .set file is a plain-text dump of every input parameter for one specific EA, including hidden internal parameters that the vendor exposed only for tuning. The format is one line per parameter: `ParamName=value`. It is human-readable and can be opened in any text editor.
Vendors ship .set files for one of two reasons: (1) they tested specific parameter combinations across years of backtests and want you to use those tested values rather than the compiled defaults, or (2) they ship different .set files for different broker types (ECN vs Standard) or different account sizes (Conservative for small accounts, Aggressive for $10k+).
The .set file is bound to a specific EA version. If you load a .set from EA v3.2 into EA v3.5 that added new inputs, MT5 will use the .set values for matching parameter names and use defaults for new parameters. Always source .set files from the same release as the .ex5.
Paso 2: Copy the .set file into MQL5/Presets/
Open MT5 → File → Open Data Folder. Navigate into MQL5\Presets\. If the folder does not exist (rare on fresh installs), create it with that exact name and capitalisation.
Drop the vendor's .set file into Presets. You can place multiple .set files here — MT5 lists them all when you click Load on the Inputs tab, sorted alphabetically. A common convention is to name them like `MyEA-Conservative.set`, `MyEA-Balanced.set`, `MyEA-Aggressive.set` so you can see at a glance which risk profile each one targets.
You don't need to restart MT5 after copying a .set; the load dialog scans the folder fresh on each open.
Paso 3: Load the .set from the EA's Inputs tab
Open or re-open the EA configuration popup by either double-clicking the EA name in Navigator and dragging it onto a chart, or right-clicking the chart with the EA already attached → Properties.
Switch to the Inputs tab. The bottom-right corner has Load and Save buttons. Click Load, navigate into the Presets folder (it should be the default location), and pick the .set file. The parameters in the table refresh to the .set's values.
If any input from the .set does not match a parameter that exists in the current EA version, MT5 silently drops it. You'll see a warning in the Experts tab on next attach. Conversely, parameters in the current EA that the .set does not mention stay at their compiled defaults — the .set is additive, not a full replacement.
Paso 4: Review the loaded values against your account
A vendor's .set is calibrated to assumptions: a specific account currency, a specific balance range, a specific broker spread, sometimes a specific leverage. Scan the inputs for anything that mentions: LotSize, FixedLot, Risk, RiskPercent, MaxLot, MaxDrawdown, StopLoss, TakeProfit, Slippage.
If the vendor's documentation says the preset was built for a $10,000 account and you have $1,000, divide lot-size related fields by 10. If they assumed Standard lots (1 lot = 100,000 units) but your broker uses Cent (1 lot = 1,000 units), divide by 100.
For stop-loss and take-profit values, check whether they are in pips or in absolute price units. The .set will show the same number, but the meaning changes — 200 means 200 pips on a USDJPY EA (= ~$200 risk per mini lot) or 200 price units = 2 cents (= $20 risk per mini lot). The vendor docs tell you which.
Paso 5: Save your tuned version as a new .set
If you adjust inputs from the loaded preset (different lot size for your balance, different time filter for your timezone, different broker symbol mapping), save those changes as a new .set file so you can restore them later without redoing the work.
From the Inputs tab, click Save. MT5 prompts for a filename and saves into the Presets folder by default. Use a descriptive name like `MyEA-Aggressive-LIVE-IC-$5k.set` that encodes the variant, account type, broker, and balance assumption.
Do not overwrite the vendor's original .set with your custom version. Keep the originals untouched as a reference; your edits go into a new file. This makes it easy to compare your tuning against the vendor baseline if the EA underperforms.
Paso 6: (Optional) Inspect or diff the .set in a text editor
Open the .set in VS Code, Notepad++, or any plain-text editor. The format is one `param=value` per line, with comments prefixed by `;`. You can:
- Compare two .set files via your editor's diff tool to see exactly what differs between Conservative and Aggressive presets — useful for understanding the vendor's tuning logic. - Hand-edit a .set to bulk-modify parameters across multiple presets (e.g. change LotSize from 0.1 to 0.05 in 5 .set files at once via search-replace). - Generate .set files programmatically for grid optimization — write a Python script that produces 50 .set files with different StopLoss values, then run MT5's Strategy Tester in Optimization mode pointed at the folder.
The one rule: do not introduce new parameter lines that the EA does not know about. They will be silently dropped and may cause MT5 to log warnings on every chart attach.
Errores comunes a evitar
- ✗ Placing .set files in MQL5/Files/ instead of MQL5/Presets/Solución: The Load dialog only scans Presets/. MT5 will silently not show files placed elsewhere.
- ✗ Loading a .set for v3.2 into a v3.5 EA without checking the versionSolución: Check the EA version line printed in the Experts log on attach. If versions differ, expect missing parameters and re-test.
- ✗ Forgetting that Cent accounts need lot sizes divided by 100Solución: A 0.10-lot preset on Cent opens 100× the exposure of Standard. Always verify against AccountInfoString(ACCOUNT_NAME) which usually includes 'Cent' for cent accounts.
- ✗ Editing the vendor .set file directly instead of saving a new versionSolución: Keep originals immutable. Save your tuning as YourEA-Tuned-Date.set so you can roll back if performance degrades.
Preguntas frecuentes
What is the difference between a .set file and a .tpl template?
Use .set files for vendor-shipped EA tuning that should be portable across accounts and broker setups. Use .tpl templates when you want to save the entire chart layout for one-click restoration after a terminal restart or account switch. Many traders use both: a .tpl that captures the chart, and the .set the .tpl references for the EA inputs.
Can I edit a .set file in a text editor and save it back?
Two formatting gotchas: (1) MT5 writes Windows .set files as UTF-16 LE with a BOM. If you open in a Unix-only editor and save as UTF-8, MT5 may refuse to load it. Use a Windows-friendly editor or explicitly convert encoding. (2) Numeric values like `LotSize=0.10` must use a period as the decimal separator regardless of your locale. Commas (e.g. `LotSize=0,10`) will cause MT5 to parse the value as zero.
Can I generate .set files automatically from a Strategy Tester optimization run?
After Strategy Tester optimization completes, the bottom panel shows a table sortable by every metric (Net Profit, Profit Factor, Drawdown, etc). Right-click the row of interest → 'Save as set' and pick a filename. The new .set is created in MQL5/Presets/ and immediately loadable. For systematic tuning workflows, this loop — backtest, pick winner, save .set, attach to live chart — is the standard MT5 development cycle.
If the EA vendor releases a new version, will my old .set still work?
The safe upgrade procedure is: (1) update the EA file in MQL5\Experts\, (2) load your .set into the new EA, (3) check the Experts log for any 'Unknown parameter' warnings, (4) cross-reference the vendor's changelog for renamed inputs, (5) save the merged result as a new .set named with the new version (e.g. MyEA-v3.5-Aggressive.set). Keep the v3.2 .set archived as reference.
Want to test your .set before going live?
Run the same .set through the Strategy Tester first. 30 minutes of backtesting catches configuration errors that would take weeks of live trading to surface.
Continue to: How to backtest an EA in MT5 →Guías relacionadas

William Harris
Fundador y Lead Developer de FxRobotEasy
Chicago, EE.UU. · Desde 2021
- 12+ Años de Trading en Vivo
- 10+ Años MQL5 / MQL4
- 3 Expert Advisors Verificados en Vivo
- Fundado en 2021
“He estado construyendo cosas con código desde la secundaria. He estado operando desde la universidad. La intersección de esos dos mundos — algoritmos, mercados, y la tecnología que los conecta — es donde he pasado los últimos quince años. FxRobotEasy es lo que pasa cuando te niegas a detenerte hasta que lo que imaginaste realmente funcione en una cuenta de broker en vivo.”