- Since October 2022 each broker has its own MT5 web terminal, tied to its own platform and domain; the old shared terminal no longer serves arbitrary servers.
- There are three ways to put it on your website: a “Trade now” link, an iframe embed, or a full-screen branded terminal on your own subdomain.
- iframes are quick to set up but are cramped on phones, can be blocked by framing headers and can lose saved logins when browsers restrict third-party storage.
- Most “not working” reports trace back to a few causes: no web terminal enabled for the server, the generic demo terminal, framing headers, mixed content or DNS and certificate set-up.
- A terminal on your own subdomain, such as trade.yourbrand.com, keeps your brand, legal details and access rules in one place and works full-screen on every device.
- FXPTrader delivers that branded terminal through a Cloudflare Worker in your own Cloudflare account; it is not an MT5 licence, so you still need your own MT5 access.
How do you add the MT5 web terminal to your website?
You add the MetaTrader 5 web terminal to your website in one of three ways: link to your broker web terminal from a “Trade now” button, embed it in an iframe on one of your pages, or serve it full-screen on your own subdomain such as trade.yourbrand.com. In every case the terminal must be enabled for your trading server first, because since October 2022 MetaQuotes delivers an individual web terminal per broker rather than one shared page for everyone.
A link is the fastest route, an iframe keeps visitors on your page but brings technical limits, and an own-domain terminal gives the most consistent brand and mobile experience. The rest of this guide shows how to set up each option, the exact iframe parameters, a launch checklist and how to fix the errors brokers actually run into.
What changed with the MT5 web terminal in 2022?
For years MetaQuotes offered a shared web terminal that any broker could place on its site. Its 2017 MQL5 article on embedding describes an iframe with parameters such as servers, trade_server, lang, startup_mode, save_password, demo_all_servers and utm_campaign, and states: “We do not charge any fees for the use of the WebTerminal on your sites.” Many older tutorials and forum answers still describe this model.
On 12 October 2022 MetaQuotes announced a new web terminal that “operates as an individual web terminal, which only works with a specific broker’s platform”. It runs on the broker’s access server, is linked to the broker’s own domain and, in MetaQuotes’ words, gives “maximum security and full control for the broker”. According to the announcement, brokers that already hold a web terminal licence can deploy it at no extra fee, while others order it through MetaQuotes support.
In September 2023 MetaQuotes published video guides for brokers covering installation “from domain selection to web terminal integration into your website, all accomplished within 30 minutes”, including customising the home page, analytics and interface. The practical consequence for anyone searching “how to put the MT5 web terminal on my website” in 2026:
- The starting point is your own broker web terminal, enabled for your trading server, not the old shared page.
- Copying an old iframe snippet that points to the shared terminal usually ends in an error or in a terminal that only shows demo servers (see the troubleshooting section).
- Decisions about domain, branding and access now sit with the broker, which is why own-domain set-ups have become common.
What can clients do in the MetaTrader 5 web terminal?
Before you decide how prominently to place it, it helps to know what the web terminal offers compared with the desktop and mobile apps. According to the official MetaTrader 5 web trading page, the terminal is built in HTML5 and needs no installation. It runs in Chrome, Safari, Edge, Opera and Firefox on Windows, macOS and Linux, and is optimised for mobile browsers on iOS and Android.
| Area | MT5 web terminal (per MetaQuotes) | What it means for your website |
|---|---|---|
| Installation | None, runs in the browser | A single link or page is enough to get a client trading |
| Orders | All MT5 order types, one-click trading | Suitable as a primary platform, not just a viewer |
| Position accounting | Netting and hedging | Works with either account model on your server |
| Accounts | Demo and real | Usable in both demo sign-up and live onboarding flows |
| Analysis | 30 indicators, 24 analytical objects, 9 timeframes, 3 chart types, night theme | Enough for most discretionary traders |
| Languages | 8 interface languages listed on the product page; the MQL5 embedding article mentions 41 | Set the language to match the page the client came from |
| Automation | Expert Advisors and custom indicators do not run in the web versions (broker sources) | Point algorithmic traders to the desktop terminal |
For a fuller comparison of the three client platforms, see MT5 WebTrader vs desktop vs mobile.
Link, iframe or own domain: which option should you choose?
| Link | iframe embed | Branded own domain | |
|---|---|---|---|
| Setup effort | Minutes | Minutes to hours | Typically the same day |
| Address in the browser | The web terminal’s address | Your page, terminal framed inside | Your subdomain |
| Full-screen trading | Yes | Limited by the frame | Yes |
| Mobile experience | Good | Often cramped | Good |
| Saved logins | Normal browser behaviour | Can break when third-party storage is blocked | Normal browser behaviour |
| Company details and legal links | Limited | Around the frame only | Throughout |
| Access control by account range | No | No | Yes (with FXPTrader) |
| Servers to maintain | None | None | None (edge delivery) |
Use these questions to decide:
- Is the web terminal a main platform or a side option? If many clients trade only in the browser, a full-screen terminal on your own domain is worth the extra step.
- How much of your traffic is mobile? Frames inside a page leave little room on a phone; a link or own-domain terminal uses the whole screen.
- Do you need your legal entity, licence and privacy links visible in the terminal? Regulated brokers often do; see which company details to show in a web terminal.
- Do you run several brands or partner sites? Separate branded terminals per brand avoid mixing names and contact details.
- Do you need to restrict who can log in? Prop firms and IB programmes often want only certain account ranges on a given address.
A sensible path for many brokers is to start with a link on day one, then move to an own-domain terminal and keep the link pointing at the new address.
How to link to your MT5 web terminal from your website
Linking is the simplest and most reliable option, and it is the right first step even if you plan something more elaborate later.
- Get your broker web terminal address. If MT5 is provided to you by a platform provider, ask them for the web terminal URL enabled for your trading server. If you run your own MT5 platform, deploy the web terminal as described in MetaQuotes’ broker guides.
- Test it with a demo and a live account on desktop and on a phone, and note the exact trading server name clients must select.
- Add a clear button such as “Web Trader” or “Trade now” to your main navigation and client area. Open it in a new tab so clients keep your client area available for deposits and documents.
- Add campaign tracking to the link if your analytics set-up supports it, so you can see which pages drive logins.
- Repeat the link in onboarding emails, next to the login and server name, so new clients do not need to search for it.
The drawback is that the address and much of the presentation may not be yours. Clients move from your branded site to a page they may not recognise, which is a common point where new traders hesitate.
How to embed the MT5 web terminal in an iframe
An iframe places the terminal inside one of your own pages. A minimal embed looks like this, with the address replaced by your broker web terminal and the server name by yours:
<iframe src="https://YOUR-WEB-TERMINAL-ADDRESS/?servers=YourBroker-Live&trade_server=YourBroker-Live&lang=en" width="100%" height="700" allow="fullscreen" title="Web trading terminal"></iframe>
The parameter names below come from MetaQuotes’ 2017 MQL5 article on the shared terminal. Check with your platform provider which of them your own web terminal still honours.
| Parameter | Purpose | Practical tip |
|---|---|---|
servers | Trading servers offered in the login dialog | List only your own servers so clients cannot pick the wrong one |
trade_server | Server selected by default | Use your live server on client-area pages, your demo server on sign-up pages |
lang | Interface language | Match the language of the page that hosts the frame |
startup_mode | What the terminal opens with, for example opening a demo account | Useful on “try a demo” landing pages |
save_password | Whether the login can be remembered | Behaviour inside frames depends on browser storage rules |
demo_all_servers | Demo account opening across servers | Usually leave off so demos open on your server |
utm_campaign | Campaign tag for tracking | Use the same naming as your other campaigns |
Things to get right with an iframe:
- Height. A fixed height that looks fine on a laptop is often too short or too tall on a phone. Use a responsive height (for example based on viewport units) and test on real devices.
- Framing permissions. The terminal’s server must allow being framed by your domain. If it sends
X-Frame-Options: DENYor a Content-Security-Policyframe-ancestorsrule that excludes your site, the browser shows an empty box. - Your own page’s policy. If your site uses a Content-Security-Policy with
frame-srcorchild-src, add the terminal’s address to it. - HTTPS on both sides. An
http://frame inside anhttps://page is blocked as mixed content. - Storage and cookies. Several major browsers block or partition storage for third-party frames by default, so “remember me” may not survive between visits.
- Cookie consent. If your consent banner blocks third-party content until accepted, the frame may stay empty for visitors who have not yet chosen.
An iframe is a reasonable choice for a demo landing page or a “try it now” widget. For daily trading, most brokers prefer a full-screen terminal.
How to put the MT5 web terminal on your own domain
With an own-domain terminal, clients open trade.yourbrand.com and see a full-screen terminal with your company name, contact details and legal links. The address is one they recognise from your website and emails, and they can bookmark it like any other page.
FXPTrader delivers this through a Cloudflare Worker deployed in your own Cloudflare account. The Worker serves the terminal on your subdomain and connects it to your trading server; there are no servers to rent or patch. Cloudflare’s network, according to Cloudflare, spans 348 cities in more than 100 countries, and its Workers runtime supports WebSockets, which a live trading terminal relies on. The trade server itself stays with your MT5 platform, so execution happens where it always has.
Typical steps:
- Confirm your MT5 access. You need your own MT5 platform or access through a provider, with the web terminal available for your server. FXPTrader is not an MT5 licence or white label; see white label vs grey label vs own licence.
- Add your domain to Cloudflare if it is not there already, and choose the subdomain, such as
trade,webtraderorterminal. - Deploy the Worker into your Cloudflare account.
- Fill in the settings as Cloudflare environment variables (see the table below).
- Attach the custom domain. Cloudflare Custom Domains create the DNS record and certificate automatically; note that wildcard custom domains are not supported, so add each subdomain explicitly.
- Test demo and live logins, an account outside the allowed range, mobile Safari and Chrome, and the legal links.
- Link it from your navigation, client area and onboarding emails, and update any old iframe or link to the new address.
| Setting | What it controls | Example |
|---|---|---|
| Company name, address, email, telephone, website | Brand and contact details shown in the terminal | Your legal entity and support contacts |
| Trading server name | The server clients log in to | YourBroker-Live |
| Upstream | The web terminal back end the Worker connects to | Address provided with your MT5 access |
| Licence URL and privacy URL | Legal links shown to clients | Your regulatory and privacy pages |
| End-user text | Notices such as risk warnings | Your standard risk disclosure |
| Allowed login ranges | Which account numbers may log in on this address | Only live accounts of one brand |
Because everything is configuration, a typical deployment goes live the same day, and several brands can run side by side with one Worker and one configuration per brand; see multi-brand WebTrader. For the DNS side in detail, read WebTrader subdomain and DNS set-up, and for the product overview, White-Label WebTrader.
MT5 web terminal not working? Common errors and fixes
These are the problems brokers and their clients most often report when adding the web terminal to a site, with the usual cause and fix.
| Symptom | Likely cause | Fix |
|---|---|---|
| “WebTerminal is not supported by this MetaTrader 5 Server” | No web terminal is enabled for that trading server; each broker now hosts its own | Enable or order the web terminal for your server through MetaQuotes or your platform provider, then point the page at that terminal |
| Only MetaQuotes-Demo or other demo servers appear | The page uses the generic terminal, or the servers parameter is missing | Use your broker web terminal and list your own server names |
| Empty box or “refused to connect” inside the frame | X-Frame-Options or frame-ancestors forbids framing, or your own CSP blocks the source | Check the browser console; allow your domain to frame the terminal or switch to a link or own-domain terminal |
| Frame blocked as mixed content | Terminal loaded over http:// on an https:// page | Use HTTPS for the terminal address |
| Clients logged out on every visit | Browser blocks or partitions third-party storage inside the frame | Serve the terminal full-screen on your own domain |
| Terminal loads but shows no prices or keeps reconnecting | A proxy, firewall or misconfigured upstream interrupts the live connection, or the server name is wrong | Check the network tab for failed WebSocket connections and verify the server name and upstream |
Certificate warning on trade.yourbrand.com | DNS or certificate still being issued, or a conflicting DNS record exists | Remove old records for the subdomain and let Cloudflare issue the certificate for the custom domain |
| Valid account cannot log in on the branded address | The account number is outside the allowed login ranges | Widen the range or send the client to the correct brand’s address |
| Wrong interface language | No lang set, or browser default used | Set the language per page or per brand |
When you raise a ticket with your platform provider, include the full address you used, the trading server name, the browser and device, and a screenshot of the browser console. It shortens the back-and-forth considerably.
Where should the web terminal appear on your website?
A terminal only helps if clients can find it at the moment they want to trade. Good places to put the link or button:
- Main navigation: a “Web Trader” or “Trade now” item, visible on desktop and in the mobile menu.
- Client area: next to account details, deposits and the platform downloads, with the server name shown beside it.
- Account approval and welcome emails: login, server name and the terminal link in one block.
- Platform page: alongside the desktop and mobile downloads, explaining that the web version needs no installation.
- Demo landing pages: a direct route into a demo account, which is where an iframe can still make sense.
- Prop firm dashboards and IB partner pages: next to challenge credentials or partner sign-up links, ideally on an address restricted to the relevant account ranges; see how to restrict MT5 WebTrader login ranges.
Keep one canonical address. If the link changes, update every place above at once and redirect the old address where you can, so bookmarks and emails keep working.
Pre-launch checklist and common pitfalls
Run through this list before you announce the terminal to clients:
- The web terminal is enabled for your live and demo servers, and both server names are spelled exactly as clients will see them.
- A live account and a demo account can log in, place, modify and close an order.
- The terminal works on a phone in portrait mode, in both Safari and Chrome.
- Company name, address, contact details, licence link, privacy link and risk text are correct for the brand.
- The address uses HTTPS without warnings, and old links or iframes point to the new address.
- Account ranges that should not use this address are rejected, and support knows what clients see in that case.
- Analytics and cookie consent behave as your policy requires.
- Support staff have a short script for the errors in the troubleshooting table.
Pitfalls seen repeatedly:
- Copying a pre-2022 tutorial and pointing the embed at the shared terminal, which no longer serves arbitrary servers.
- Testing only on desktop, then discovering the frame is unusable on phones.
- Mixing brands: one terminal with one company’s legal details used for several brands or partners.
- Assuming the web terminal runs Expert Advisors; it does not, so tell algorithmic traders to use the desktop terminal.
- Treating a branded terminal as a licence. A branded front end needs MT5 access behind it; it does not replace your platform agreement.
Sources
- MQL5: how to embed the MetaTrader WebTerminal on your website (2017)
- MetaTrader 5: the new individual web terminal for brokers (October 2022)
- MetaTrader 5: video guides for brokers on the web terminal (September 2023)
- MQL5 forum: “WebTerminal is not supported by this MetaTrader 5 Server” (2024)
- MetaTrader 5 web trading platform features
- Cloudflare Workers: Custom Domains
- Cloudflare Workers: WebSockets
- Cloudflare global network
Frequently asked questions
Can I embed the MT5 web terminal on my website with an iframe?
Yes, provided the web terminal is enabled for your trading server and its address allows being framed by your domain. MetaQuotes’ 2017 article describes iframe parameters such as servers, trade_server and lang. Expect limits on mobile and with saved logins, because browsers restrict storage inside third-party frames.
Is embedding the MT5 web terminal free?
For the old shared terminal, MetaQuotes stated that it did not charge for using the WebTerminal on your sites. For the individual broker terminal launched in 2022, MetaQuotes said brokers with a web terminal licence can deploy it at no extra fee, while others order it through support. A branded terminal on your own domain is a separate service.
Why does it say “WebTerminal is not supported by this MetaTrader 5 Server”?
The trading server you are pointing to has no web terminal enabled for it. Since 2022 each broker hosts its own web terminal, and the shared terminal no longer connects to arbitrary servers. The broker or its platform provider needs to enable the web terminal for that server.
Why does my embedded terminal only show MetaQuotes-Demo?
The page is loading the generic terminal rather than your broker web terminal, or the servers parameter is missing. Point the embed or link at your own web terminal address and list only your own server names.
Why is my MT5 iframe blank?
Usually the terminal’s server forbids framing with X-Frame-Options or a Content-Security-Policy frame-ancestors rule, or your own site’s policy blocks the source. Mixed content, an http frame on an https page, has the same effect. The browser console names the exact cause.
Can I use a subdomain such as trade.mybroker.com?
Yes, and it is the most common own-domain set-up. With FXPTrader the subdomain is attached as a Cloudflare Custom Domain, which creates the DNS record and certificate automatically. Each subdomain is added individually, since wildcard custom domains are not supported.
Does a branded web terminal give me an MT5 licence?
No. A branded terminal is the client-facing front end; the trade server, accounts and execution remain on your MT5 platform. You still need your own MT5 access, either your own licence or access through a provider.
Can clients run Expert Advisors in the MT5 web terminal?
No. Broker sources consistently note that Expert Advisors and custom indicators do not run in the MT4 or MT5 web versions. Clients who trade with automated strategies should use the desktop terminal.
Which option is best for conversion?
A full-screen terminal on your own branded domain usually gives the smoothest and most trusted path, especially on phones, because the address, branding and legal details match your website. A link is a good interim step, while iframes suit demo landing pages better than daily trading.
Can I limit which accounts can log in to my web terminal?
Not with a plain link or iframe. FXPTrader lets you set allowed login ranges per deployment, so an address used for one brand, a prop firm programme or a partner only accepts the matching account numbers.
Can I track which campaign brought a client to the terminal?
MetaQuotes’ embed parameters include utm_campaign. On your own domain you can also use your normal analytics, subject to your cookie consent set-up and privacy policy.
How long does it take to put the web terminal on my own domain?
MetaQuotes says its broker guides take installation from domain selection to website integration in about 30 minutes. With FXPTrader, the Worker and settings are deployed in your Cloudflare account and a typical set-up goes live the same day, once your MT5 access and domain are ready.