Pine versions
Submit Pine Script version 5 or 6 with a valid version declaration. Missing, conflicting, or unsupported versions are rejected before conversion.
Conversion scope
What to expect from Pine Script conversion
PineAnywhere supports a broad Pine execution model, but compatibility is determined by the exact language features and platform behavior used by each script. Validation and compilation provide the final answer for a specific source file.
Accepted input
Source requirements
Files or pasted source
Accepted file extensions are .pine, .ps, and .pinescript. Source may also be pasted directly, up to a maximum of 400 KiB.
One protected workspace
Source, conversion jobs, diagnostics, and generated artifacts are associated with the authenticated account and governed by defined retention windows.
Behavior categories
Designed for the parts of Pine that execute on bars
The conversion pipeline models common language constructs and runtime behavior used by indicators and strategies.
This list describes capability areas, not a guarantee that every overload, library, visual object, broker action, or third-party dependency is supported.
- Series history, variables, functions, and collections
- Mathematical and technical-analysis calculations
- Indicator, strategy, and library declarations
- Inputs and generated MetaTrader parameters
- Plots, horizontal levels, markers, and selected drawing behavior
- Alerts and strategy-oriented state
Platform differences
Behavior that requires careful comparison
Data and sessions
Symbol naming, history, sessions, time zones, missing bars, and broker feeds can change calculated values even when logic is equivalent.
Orders and execution
Position models, fills, spreads, commissions, slippage, minimum volume, and tick processing differ between TradingView simulations and MetaTrader brokers.
Charts and visuals
The platforms expose different drawing systems. A calculation may convert successfully while a visual element needs adaptation or has no exact native equivalent.
How compatibility is reportedValidation Conversion Compilation
Useful failure stages instead of a silent result
Input problem
The source is missing required metadata, exceeds limits, or cannot enter the conversion workflow.
Unsupported source behavior
The parser or runtime conversion cannot represent a construct used by the script.
MetaEditor diagnostic
Generated MQL5 does not compile into the expected artifact. The job records a sanitized diagnostic for review.
Check a real script
Start freeCompatibility is best tested with your source.
Failed or cancelled jobs do not consume a successful-conversion allowance.