Plugins

Plugins published in cTrader Store run in a sandboxed environment with permission boundaries and confirmation flows on sensitive actions. That said, plugins can still send data to external services and can be designed to trade if granted permission — review the product description, supported permissions and data flow before installing. Test trade-capable plugins on a demo account first.

Yes — desktop plugins can add menu items, panels, custom windows, chart frames, ASP blocks and Trade Watch tabs in cTrader Windows and Mac. WebView plugins are placed in predefined UI slots (Active Symbol Panel, bottom sheet, embedded blocks) that the developer chooses during plugin setup.

Yes. Plugins can connect to external services for data, analysis, news, AI or webhooks. WebView plugins handle this through the host web app; desktop plugins can use C# networking APIs. Review the plugin's permissions and what data leaves cTrader — privacy and security matter especially when account data is involved.

Yes. Calculators — position size, margin, swap, profit/loss, pip value, risk-reward — are one of the most common plugin categories. They can be built as WebView plugins for cross-device use or as desktop plugins for tighter workspace integration.

Yes. WebView plugins can integrate AI assistants — chat-style helpers for market commentary, strategy ideas, calculation or workflow guidance — because they are built as web apps and can call external AI APIs. Note that AI output is not financial advice and should be treated as a decision input. WebView plugins must not include authentication or payment forms in the web app itself.

Sometimes — plugins that load heavy external web apps, perform large background calculations or maintain many open connections can affect platform responsiveness. WebView plugins running on Mobile have tighter resource budgets than desktop. If you notice slowdown, disable plugins one by one to identify the culprit, then check whether the developer has a lightweight mode.

Yes. Multiple plugins can run in parallel — for example, a calculator, a risk dashboard and an AI assistant. They operate independently and do not coordinate by default. The trade-off is performance: stacking many plugins can increase memory use and add UI clutter, especially with WebView plugins that load external web apps.

Yes — within limits. Plugins can access account data (balance, equity, positions, orders) through the WebView plugin SDK or cTrader Algo API when granted permission. They run in a sandboxed environment with extra confirmation flows on sensitive operations and local position/margin checks. WebView plugins must not include authentication or payment forms inside the web app.

Yes. Plugins can connect to external services to display news, market analytics, calendars, dashboards, AI assistants or third-party data feeds. WebView plugins in particular are built on web technology, which makes external service integration straightforward. Review the product description for data sources and what is sent outside cTrader.

Some plugins can place or modify trades when their code is designed to and the user grants permission. Many plugins, especially analytical and informational ones, do not trade. Check the plugin's permissions and product description before installing and test any trade-capable plugin on a demo account first.

Yes, multi-platform (WebView) plugins run on cTrader Web. Desktop plugins do not. The WebView plugin SDK is the development path for any plugin intended to reach Web users.

Yes. Both multi-platform plugins and desktop plugins run on cTrader Windows and Mac. Desktop plugins are Windows/Mac-exclusive; multi-platform plugins additionally run on Web and Mobile. Product pages should state both supported apps and where the plugin appears in the interface.

Yes, but only multi-platform (WebView) plugins. Desktop plugins are Windows/Mac only. When choosing a plugin for mobile workflows, filter for the multi-platform plugin badge in Store; desktop plugins will install to your cTrader ID but will not be usable from Mobile.

WebView plugins are built as web apps using JavaScript, HTML, CSS and (optionally) the WebView plugin SDK for interaction with cTrader. The web app is hosted externally; the cTrader plugin wraps it with placement settings, UI integration and permission boundaries. AI-assisted plugin creation is also supported.

To install a plugin, open its page in cTrader Store, click Install — the plugin links to your cTrader ID and syncs to compatible apps through cloud synchronisation. Multi-platform plugins become available on Web, Mobile, Windows and Mac; desktop plugins on Windows and Mac only.

Where the plugin appears depends on its placement settings. WebView plugins show up in the placements the developer enabled — Active Symbol Panel, bottom sheet, embedded blocks, mobile widgets. Desktop plugins appear in the menus, toolbars or chart areas they extend. If you cannot find a plugin after install, check the WebView plugins tab in cTrader Algo.

Desktop plugins run on cTrader Windows and Mac only and integrate deeper with the platform UI — extending menus, panels, workspace layout and chart frames — than multi-platform plugins. They are built in C# or Python in cTrader Algo. Pick desktop when the plugin needs Windows/Mac-only capabilities; pick WebView when cross-device matters more.

Multi-platform plugins (also called WebView plugins) are built as web apps and run inside cTrader Web, Mobile, Windows and Mac through the WebView plugin SDK. They are the right product type for cross-device tools — calculators, dashboards, AI assistants, news widgets, journals.

A cTrader plugin is an extension that adds tools, panels, dashboards or workflow features to the trading platform. Plugins sit alongside indicators and cBots in Store as a separate product category. They can be analytical (calculators, journals, dashboards), informational (news, data widgets) or workflow-oriented (trade management panels, AI assistants).

A desktop plugin is a plugin built for cTrader Windows and Mac only. Desktop plugins can integrate deeper with the platform UI than WebView plugins — extending menus, panels and workspace layout — but they do not run on Web or Mobile. Pick desktop when the plugin needs Windows/Mac-only capabilities; pick WebView when cross-device matters more.

A WebView plugin — also called a multi-platform plugin — is a plugin built as a web app that integrates into cTrader Web, Mobile, Windows and Mac through the WebView plugin SDK. The same plugin runs in every cTrader app, which makes it the right product type when the goal is a cross-device tool. Calculators, dashboards and AI assistants are common WebView plugin use cases.

The cTrader plugin SDK is the developer interface for building plugins. There are two paths: the WebView plugin SDK (JavaScript, for multi-platform web-based plugins) and the cTrader Algo plugin API (C# or Python, for desktop plugins). They expose different capabilities — the WebView SDK focuses on sandboxed account data and trading actions, while the Algo plugin API exposes deeper UI integration in Windows and Mac.

cBots automate or manage trading logic — they place, modify and close orders according to code. Plugins extend the platform with tools, UI and external data; some plugins can include trading controls, but most are informational or workflow-oriented. If the goal is automated execution, you want a cBot; if the goal is a calculator, dashboard or panel, you want a plugin.

Indicators analyse chart data and display values, levels or signals on the chart. Plugins extend the platform itself — panels, dashboards, calculators, external data, AI assistants, trade management UI. An indicator lives on a chart; a plugin lives in the platform. Many trading workflows combine both.

A good plugin product page answers four questions in the first screen: what the plugin does, where it appears in the interface, what permissions it needs and what the user sees after installation. Video matters more for plugins than for cBots because plugins are visual. Include screenshots from each supported app (Mobile, Web, Windows, Mac for multi-platform plugins) and disclose any external data the plugin sends or receives.

Check three things: what account data the plugin reads (balance, positions, orders, history), what actions the plugin can perform (read-only vs trade-capable) and what data the plugin sends to external services. WebView plugins surface this in the SDK methods they use; desktop plugins surface it in their AccessRights declaration. Trade-capable plugins should always be tested on a demo account before live use.

For manual trading, useful plugins include position-size and risk calculators, trade journals, multi-account dashboards, watchlists, news and economic-calendar widgets, alert managers and AI assistants for market commentary. WebView plugins make these tools available on Mobile and Web; desktop plugins add deeper workspace integration.

Prop traders benefit from rule-compliance plugins: daily loss limit monitors, max drawdown trackers, consistency dashboards, news filters, session filters, position-size calculators and trade journals. The goal is to avoid avoidable rule breaches — not to find more entries. Pair with a risk-controlled cBot that pauses trading when limits approach.

For risk management, look for position-size calculators, daily loss monitors, drawdown trackers, equity-stop tools, max-positions guards, news filters and kill-switch panels. Many of these are multi-platform plugins so they work on Mobile and Web alongside Windows and Mac. Combine a risk plugin with a risk-controlled cBot for both visibility and automated enforcement.

Common reasons: the active cTrader ID is not the one that installed the plugin, cloud synchronisation is disabled, the app does not support that plugin type (e.g. desktop plugin on Web) or the plugin is enabled but its placement settings do not include the area you are looking in. Open the WebView plugins or plugins tab in cTrader Algo to confirm installation, then check placement.