MultiCharts vs TradingView for Futures Backtesting

Contents

1. MultiCharts vs TradingView: which one for futures system trading?
2. What is the difference between PowerLanguage and Pine Script?
3. Can you backtest on the TradingView free plan? What sets backtest depth and data?
4. Which suits automated orders, MultiCharts or TradingView, and which broker do you need?
5. How are MultiCharts and TradingView priced?
6. Which traders fit MultiCharts, and which fit TradingView?
7. Frequently asked questions
8. References

MultiCharts vs TradingView: which one for futures system trading?

The answer to MultiCharts vs TradingView depends on what you need to do. If you want long-history backtests on your own futures data and fully automated orders straight through a broker API, choose MultiCharts. If you mainly chart, test ideas quickly and share scripts, and do not need automated orders for now, choose TradingView. The two do different jobs, so ranking one against the other tells you little.

MultiCharts is a charting and trading platform installed on your own Windows PC. You write strategies in PowerLanguage, connect your historical data yourself (a data vendor, futures broker quotes or imported files), run backtests locally, and send orders to your futures account directly through a broker-provided API or a broker edition of MultiCharts. TradingView is a charting and community platform that you use in a browser. TradingView supplies the historical data according to your plan tier, strategies are written in Pine Script and run on its servers, and automated orders go through strategy alerts plus a webhook, or through the broker connections TradingView publishes.

Think of MultiCharts as your own kitchen: you buy the ingredients, control the heat and serve the dish straight to the table, but you supply the cookware and the ingredients yourself. TradingView is like a cloud restaurant: the menu opens up by membership tier and you never wash a pot, but getting the meal delivered to your door takes a third-party courier.

Item	MultiCharts	TradingView
Where the code runs	Your own computer	TradingView servers, shown in the browser
Source of historical data	Data vendor, futures broker quotes or files you connect yourself	Supplied by TradingView; length depends on plan tier
Strategy language	PowerLanguage	Pine Script (currently v6)
Order path	Broker API or broker edition of MultiCharts, straight to the futures account	Alert trigger → webhook → bridge service or connected broker
Testing several symbols together	Built-in portfolio backtest tool	Mainly the single-symbol Strategy Tester

What is the difference between PowerLanguage and Pine Script?

The two differ in syntax, where the code runs and the order model, so one rule has to be rewritten separately in each language and the fill timing checked on each side. PowerLanguage is the MultiCharts strategy language. It shares an origin with TradeStation's EasyLanguage and most of the syntax carries over; the differences are laid out in EasyLanguage vs PowerLanguage: what changes when you move a strategy. The code compiles locally and runs bar by bar. Pine Script is TradingView's scripting language, currently v6, and it runs on TradingView's servers. The same script can be an indicator, or it can be declared a strategy and sent to the Strategy Tester.

Next-bar execution means the strategy reads its signal at a bar's close and fills at the next bar's open price, not at the price of the bar that has just closed. In PowerLanguage, each order command itself states whether it fills at this bar or the next bar. Pine strategies by default fill orders sent at the close at the next bar's open, but a setting lets you change that to fill at the current bar's close. Both sides can produce the same fill model, provided you open the settings on both and check them.

Aspect	PowerLanguage	Pine Script v6
Where it runs	Compiled and run locally	TradingView servers
How fill timing is set	Each order command states this bar or next bar	Strategy-level setting; default is the next open
Data available	Every data series loaded on the chart, across multiple data sources	Data TradingView provides by plan
How you share	Exported file or source code	Public or invite-only script library
Same rule, other platform	Rewrite in PowerLanguage	Rewrite in Pine Script v6

A rewrite is not finished once a few keywords are translated. The default moving average type on each side, how ATR is smoothed and how a session's open and close are defined: any one difference gives the same rule a different trade list on each side. For the steps to move a strategy to TradingView, and the fields to check at each step, see How to export an AlphaPrime strategy to TradingView, step by step.

Can you backtest on the TradingView free plan? What sets backtest depth and data?

Yes. On TradingView's free plan you can open the Strategy Tester and run Pine strategies, but the number of bars each chart can load, the smallest timeframe available and the level of real-time quotes are all tied to the plan tier. How far back and how fine a MultiCharts backtest can go depends on the data you connect yourself. A backtest reapplies trading rules to past prices to see how they would have entered and exited; if the data is short, the backtest sees only a small slice of the market.

The Strategy Tester is TradingView's built-in backtest panel, showing net profit, the trade list and the equity curve. Its settings, and what the free plan lets you see, are covered in TradingView Strategy Tester: free backtests and what to check first. Watch the data tier: on TradingView, real-time quotes for some exchanges (including CME) need a separately purchased data package, otherwise you see delayed quotes. That affects the live signals you see, but not a backtest on closed bars.

Item	TradingView free plan	TradingView paid plan	MultiCharts with your own data
Who supplies historical prices	TradingView	TradingView	Data vendor, futures broker or file you connect
How far back bars go	Depends on plan tier	Depends on plan tier; higher tiers go further back	Depends on your data
Smallest testable timeframe	Depends on plan tier	Depends on plan tier	Depends on your data (down to tick level)
Symbols tested at once	Mainly a single symbol	Mainly a single symbol	Portfolio backtest tool available
Cost of extending the history	Upgrade the plan	Upgrade the plan	Buy or import longer data

On any platform, four settings decide whether a backtest result is believable: commission, slippage, next-bar execution and session. For how to set the first two, see Trading costs in backtests: commission, slippage and the average trade. Use the session times published by the exchange. For Mini-TAIEX futures, for example, the day session is 08:45–13:45 and the night session runs from 15:00 to 05:00 the next day (source: TAIFEX Mini-TAIEX futures contract page). The exchange changes these times, so rely on the contract page; the futures market hours tool converts them to your time zone.

Below is one actual backtest from AlphaPrime (Valynox), showing what a complete summary looks like once all four settings are turned into numbers. This test used NQ daily bars, from 2019-01-02 to 2025-06-30, long and short, 1 contract, with $20 commission and $10 slippage deducted on each trade. It uses a stand-in rule whose only entry and exit condition is an ATR channel, with no stop loss, profit target or filter, and the rule itself is not the subject of this article. The candidate in the table is the one kept from 1,024 candidates in the same search run, ranked by the ratio of return to drawdown. Picking the best-looking one out of more than a thousand after the fact flatters the result by itself (the 2014 study by Bailey et al. explains why). The 34 trades are also only a clue, not a conclusion. These numbers are not money this rule earned, and not a result you should expect.

How to read this table: a maximum drawdown of $108,925 against a net profit of $184,055 means the rule carried an open loss of more than half its final net profit along the way. Time in market of 95.61% shows it was in a position almost the whole time, so most of the result comes from NQ's own move over this period. When you rerun the same rule on MultiCharts or TradingView, these are the relationships to look at first, not the net profit cell.

Which suits automated orders, MultiCharts or TradingView, and which broker do you need?

Futures strategies that need to watch the market and place orders around the clock mostly fall to MultiCharts, because there are only two links from strategy to futures account: the strategy sends the order, and the broker API or broker edition of MultiCharts delivers it to the account. TradingView's chain has four links: the strategy alert fires, a webhook sends a message, a third-party bridge or connected broker receives it, and it is turned into an order in the account. Each extra link is one more place where a fill can be delayed or missed.

A webhook is the mechanism by which TradingView sends a message to a URL you specify when an alert fires. The receiving end (a program you write or a bridge service) then translates the message into a broker order command. Whether webhook notifications are available, and how many alerts each plan allows, follows TradingView's published plan feature table. TradingView also has a list of brokers it connects to directly; check that list to see whether a futures account can use it.

Several Taiwan futures brokers offer a broker edition of MultiCharts or a bundled plan. Yuanta Futures, KGI Futures, Capital Futures, Concord Futures and President Futures have all offered one. The condition is usually a monthly trading-volume threshold in contracts or a monthly fee, and it changes, so rely on each broker's current announcement. When choosing, look at three things: whether the API supports the products you trade and the night session, how far back the historical data can be backfilled, and how reconnection after a dropout and unfilled orders are handled.

1. Check the fill model. If the backtest fills at the next open, live orders must use the same order type. For the steps to load an exported strategy into MultiCharts and compare the trade lists, see How to import a strategy into MultiCharts and match the backtest.
2. Run a full stretch on a paper account first. Cover at least one night session, one settlement day and one open after a holiday, and see whether orders and reports line up.
3. Record the gap between each fill price and signal price. This is the only measured source for how much slippage your backtest should use later.
4. Write down your dropout handling. Decide before going live what happens to open positions when the computer restarts, the network drops or the broker's system is down for maintenance.

How are MultiCharts and TradingView priced?

The two platforms put the money in different places, so what you need to add up is the total cost of backtest data, automated orders and the platform, not the platform fee alone. Amounts follow each side's official price page and the futures broker's announcements. MultiCharts is a purchased or rented license, or comes through a futures broker's bundled plan. Automated orders are built in, but historical data and real-time quotes come separately from a data vendor or futures broker. TradingView is a tiered subscription, billed monthly or yearly. The free plan has feature limits, data is included according to plan tier, real-time quotes for some exchanges are bought separately, and a bridge service for automated orders is another charge.

Cost item	MultiCharts	TradingView
The platform itself	Purchased or rented license, or futures broker bundled plan	Tiered subscription, monthly or yearly; the free plan has limits
Historical and real-time data	Data vendor or futures broker quotes, charged separately	Included by plan; real-time quotes for some exchanges bought separately
Automated orders	Built in, through a broker API	Webhook plus a third-party bridge, charged separately
Extending the history	Buy longer data	Upgrade the plan
Several computers or accounts	Per license terms	Per plan terms

The order for adding up total cost: first list the symbols you want to test and how many years you want to go back, and ask where the data comes from and what it costs per year. Then decide whether you want automated orders, and ask what the bridge or API costs. Only then look at the platform fee. People who add up only the platform fee often find in the second step that the data or bridge fee is higher than the platform itself.

Which traders fit MultiCharts, and which fit TradingView?

Traders who want long-history, multi-symbol backtests on their own futures data and fully automated orders fit MultiCharts. Traders who mainly chart, test ideas quickly and share scripts, and do not need automated orders for now, fit TradingView. Many people use both: they research on one side, then export the strategy source code to the side that will execute it. Find your situation in the table below.

Your situation	MultiCharts	TradingView	Use both
I need fully automated orders through a futures broker	✓ The order chain has only two links
I want to backtest years of my own minute data	✓ Depth is set by your own data
I test several markets together as one portfolio	✓ Built-in portfolio backtest tool
I mainly chart in the browser and test ideas quickly		✓ Open a chart and the Strategy Tester runs
I want to share or borrow scripts with others		✓ Script library and community
I research on one side and execute on the other			✓ The research side outputs source code; the execution side checks it and goes live

When you use both, the most time-consuming part is rewriting and checking. If the rule produced on the research side can be exported straight into the execution side's language, checking turns from "rewrite it again" into "compare field by field". AlphaPrime exports the source code of one strategy in six formats: MultiCharts (PowerLanguage), TradingView (Pine Script v6), TradeStation (EasyLanguage), NinjaTrader (NinjaScript), MetaTrader 4 (MQL4) and MetaTrader 5 (MQL5). The supported list is on the platform export page. After export, you still need to rerun the strategy on the execution side and compare the trade lists, because differences in data source, session and fill model can make the two sides differ. The fields to compare are laid out in From generated strategy to MultiCharts: a PowerLanguage comparison checklist.

You can take the next step today: open the platform you use now, find the earliest date of historical data for your target symbol, count how many complete trades your strategy has over that span, then open the fill settings and confirm that fills are at the next open and that the cost fields hold commission and slippage. These four items will tell you whether your current platform is enough for you or whether it is time to start building a second one.

Frequently asked questions

Which broker works with MultiCharts?

Several Taiwan futures brokers offer a broker edition of MultiCharts or a bundled plan. Yuanta Futures, KGI Futures, Capital Futures, Concord Futures and President Futures have all offered one. The conditions are mostly a monthly trading-volume threshold in contracts or a monthly fee, and they change at any time, so rely on each broker's current announcement. When choosing, first confirm that the API supports the products you trade and the night session, how far back the historical data can be backfilled, and how reconnection after a dropout and unfilled orders are handled.

Can a Pine strategy written on TradingView move straight into MultiCharts?

No, it cannot move straight over; it has to be rewritten in PowerLanguage. As you rewrite, check each indicator's calculation method, the session definition and the fill timing, then put the two trade lists side by side and compare dates and prices. Differences usually come from the data source, the way sessions are cut and the fill model, not from the rule itself.

Can you use MultiCharts and TradingView at the same time?

Yes, and many futures traders do exactly that: they chart and test ideas quickly on TradingView, then run the full backtest on their own data and place automated orders on MultiCharts. The key is to use the same commission, slippage, fill timing and session settings on both sides; otherwise the results on the two sides cannot be compared.

Will the same strategy's backtest results match on TradingView and MultiCharts?

Not automatically. The historical data sources differ, the session open and close definitions may differ, and the default indicator calculations and fill timing may differ too; any one of these changes the trade list. The approach is to align the four settings first, then compare the trade lists side by side and find the cause of whatever difference remains, instead of comparing only the net profit cell.

References

• Bailey, D. H., Borwein, J., López de Prado, M., & Zhu, Q. J. (2014). Pseudo-Mathematics and Financial Charlatanism: The Effects of Backtest Overfitting on Out-of-Sample Performance. Notices of the American Mathematical Society, 61(5), 458–471.
• Pardo, R. (2008). The Evaluation and Optimization of Trading Strategies (2nd ed.). John Wiley & Sons.
• CME Group. E-mini Nasdaq-100 Futures Contract Specs. https://www.cmegroup.com/markets/equities/nasdaq/e-mini-nasdaq-100.contractSpecs.html
• Taiwan Futures Exchange. Mini-TAIEX Futures. https://www.taifex.com.tw/enl/eng2/mTX