This release introduces worker-based chart processing for improved performance, migrates core widget methods to a Promise-based API, extends countdown support to daily, weekly, and monthly bars, and includes updates to drawing tool names and availability. Let's dive into the highlights.

Breaking changes​

Updated drawing tool names​

Drawing tool names have been updated throughout the UI for consistency. If you use either of the following options, update the name strings you pass in:

• custom_translate_function — the originalText argument now reflects the new names (for example, "Trendline" instead of "Trend Line").
• drawings_access — the name property in the tools array must use the new names (for example, "Trendline" instead of "Trend Line").

Updated return values for dataReady, setChartType, and saveChartToServer​

Calling these methods without a callback now returns a Promise instead of the previous value:

• dataReady() on IChartWidgetApi now returns Promise<boolean> instead of a synchronous boolean. Update any synchronous readiness checks accordingly.
• setChartType(type) now returns Promise<void> and rejects with an Error if the chart type change cannot load data.
• saveChartToServer() now returns Promise<void> and rejects with a SaveChartError (exported as TradingView.SaveChartError) on failure — handle the returned promise to avoid unhandled rejections.

Existing calls that pass callbacks retain their previous behavior.

Key updates​

Worker-based chart processing​

Indicator calculations and other internal chart workloads can now run off the main thread. Enable the new workers option in the widget constructor to let the library attempt to start a dedicated worker thread. If the worker cannot be started, the library automatically falls back to the main-thread implementation.

const widget = new TradingView.widget({
    container: 'tv_chart_container',
    workers: { enabled: true },
    library_path: 'charting_library/',
    datafeed: myDatafeed,

    /* Other widget constructor options */
});

Promise-based widget API​

The remaining callback-based methods on IChartingLibraryWidget and IChartWidgetApi now have Promise-based counterparts:

• chartReady
• save
• getSavedCharts
• saveChartToServer
• removeChartFromServer
• showNoticeDialog
• showConfirmDialog
• dataReady
• setChartType

The callback overloads remain for backward compatibility and emit a one-time deprecation warning on first use. widget.setSymbol() is also deprecated in favour of widget.activeChart().setSymbol().

Countdown for daily, weekly, and monthly bars​

The bar close countdown was previously limited to intraday resolutions. It now also works for daily, weekly, and monthly bars. Set the mainSeriesProperties.showCountdown chart override to true to display the countdown on the price scale. As before, implementing getServerTime in your datafeed ensures accurate countdown values.

Unpaired exit levels​

For Trading Platform integrations using supportMultipleExitLevels, the new supportUnpairedExitLevels flag allows each exit level to contain only one side — either a take-profit or a stop-loss — instead of requiring both. See Multiple exit levels for details.

Documentation​

Implement Datafeed tutorial​

The Implement Datafeed tutorial has been rewritten to use the Binance REST API, replacing the CryptoCompare integration. The tutorial now extends into a dedicated Extend to Trading Platform section that shows how to add quote-based features on top of a working datafeed: real-time quotes, the DOM widget, news, alerts, and save/load integration.

Margin meter​

The margin meter lets traders see how close their current exposure is to the available margin limit, giving them a real-time signal before placing or adjusting orders. A new Enable margin meter section in the Order Ticket article explains what the margin meter displays and walks through the full integration.

Conclusion​

This release also includes important bug fixes: timescale marks now render correctly on slow network connections, Risk/Reward drawings work properly with custom price formatters, and repeated no-data requests for monthly resolutions have been resolved. For the full list of updates, improvements, and fixes, see the Release notes.

This release introduces CSP nonce support for stricter security compliance, adds save/load context to enable globally shared drawings, and brings a new way to organize custom indicator inputs. Let's dive into the highlights.

Key updates​

Enhanced security with CSP nonce support​

Strict Content Security Policies (CSP) are essential for financial apps. To tighten security, you can now use a new nonce property in the Widget Constructor. This property applies a cryptographic nonce to all TradingView-owned scripts and runtime-generated tags inside the iframe.

Note that the nonce value must match the nonce served in your server's Content-Security-Policy header for the current response. Nonces must be unique per page load and should be cryptographically random (at least 128 bits of entropy, base64-encoded).

const widget = new TradingView.widget({
    container: 'tv_chart_container',
    nonce: 'server-generated-nonce-value',
    library_path: 'charting_library/',
    datafeed: myDatafeed,

    /* Other widget constructor options */
});

If omitted, the library automatically infers it from window.__tvCspNonce or a host page's <script nonce>.

Globally shared drawings​

In Trading Platform, when the saveload_separate_drawings_storage featureset is enabled, users now have access to a New drawings sync globally button in the drawing toolbar. This allows users to synchronize their drawings across all layouts for a specific symbol.

To support this under the hood, we have extended the save/load adapter API when saving drawings separately. The saveLineToolsAndGroups method now receives an optional context argument containing metadata: sharingMode, symbol, and requestId. Now, context.sharingMode tells you exactly what type of synchronization is happening. This allows you to easily separate global drawings from layout-specific ones in your storage.

Organized custom indicator inputs​

As custom indicators grow in complexity, the Settings dialog can become cluttered, making it difficult for users to find the parameters they want to adjust. You can now use the group property in your custom indicator's inputs to organize related inputs under a common header.

In the example below, "Fast Length" and "Slow Length" appear under a MACD header while "Signal Smoothing" appears under a Signal header.

• Settings dialog
• Metainfo configuration

Conclusion​

This release also includes important bug fixes, such as resolving a delayed chart refresh when applying tradingProperties overrides and fixing a ReferenceError when adding orders with exit levels. For the full list of updates, improvements, and fixes, see the Release notes.

This major release introduces a new table view for precise data analysis, brings support for multiple exit levels, and applies UI updates across the chart. Let's dive into the highlights.

Key updates​

Data table view​

Users can now toggle their display to view chart and indicator data in table view. This mode is accessible via the legend's "More" menu or the chart context menu.

Multiple exit levels​

Risk management is the cornerstone of professional trading. Now, Trading Platform supports multiple exit levels (brackets).

When the supportMultipleExitLevels configuration flag is enabled, users can now protect their orders and positions with multiple take-profit and stop-loss levels at different prices and quantities. This gives your users granular control over their strategy execution directly from the chart. For more information, see Multiple exit levels.

No overlap mode​

When multiple orders or positions cluster at the same price level, labels often become unreadable. In version 30, we introduced no overlap mode, a context menu option that automatically offsets the trading lines and labels. In this version, the No overlap orders and positions setting is now persistent. Once enabled, the separation remains active until you manually toggle it off.

Adaptive trading layouts​

To help maintain a clean interface on smaller devices, we have introduced a new tradedGroupConfig object within the SingleBrokerMetaInfo interface. This configuration controls the traded group — the combination of elements drawn on the chart for a single position or order (including lines, dots, and UI controls).

Inside this configuration, the new supportAdaptiveLayout property controls responsiveness:

• When true (default), trading buttons (such as TP/SL modifications and P&L displays) on position and order lines will automatically hide on narrow viewports to optimize the layout.
• When false, these buttons will remain visible regardless of screen width.

Documentation​

New guides​

• Events and subscriptions guide clarifies how to handle the library's event system. The events are divided into three distinct scopes: widget, chart, and global, each with its own set of listeners and use cases.
• Trading overrides convention guide explains the hierarchical naming pattern used for trading properties. Following the {Side}.{State}.{Element}.{Property} format, you can determine the correct property name without guessing.

Streamlined structure​

We have significantly reorganized our documentation to make onboarding faster. The previously expansive Getting started section has been refined into a focused Introduction and Get started guides. Advanced topics previously located in Getting started have been moved to their specific functional categories (such as Configuration or Reference).

Faster work with AI assistant​

As introduced in the previous major version, we provide a downloadable file containing our complete documentation and full TypeScript definitions. This file is updated with every release to reflect the latest API changes, new features, and deprecated methods. Feeding this file to your AI assistant ensures it generates answers compatible with the latest release. For more information, see Build AI library assistant.

Conclusion​

This release also includes important bug fixes, such as corrected P&L calculations for Risk/Reward drawings and improved quantity rounding logic. For the full list of updates, improvements, and fixes, see the Release notes.

This release introduces a more efficient way to handle extensive symbol lists, adds smarter data loading for the VWAP indicator, restores the dynamic Depth of Market, and includes other improvements and bug fixes. Let's dive into the highlights.

Key updates​

Paginated Symbol Search​

If your app supports an extensive number of available symbols, loading hundreds of tickers at once can create a sluggish user experience during search. Now, you can optimize this experience using paginated Symbol Search.

Usually, the Datafeed API relies on searchSymbols to return all results in a single payload. Now, you can implement the optional searchSymbolsPaginated method instead. This allows the library to request symbols in pages.

For example, you can return the first 50 matches instantly, and as the user scrolls down the list, the library will automatically trigger a request for the next batch. For implementation details, see Additional Datafeed API methods: searchSymbolsPaginated.

Smarter data loading for VWAP​

Few things disrupt a charting workflow like adding an indicator and seeing an error message due to insufficient history. Now, the VWAP indicator handles this automatically.

Instead of displaying a warning when there isn't enough data to calculate the target anchor for the latest bar, the indicator detects the gap and automatically requests the exact amount of historical data required. This ensures a seamless experience for your users without them needing to manually scroll back to load more bars.

Return of dynamic DOM​

The Depth of Market (DOM) widget now uses dynamic mode by default, restoring the pre-v28 behavior where the spread stays in focus automatically. You can still provide the static mode by enabling the static_dom featureset.

Conclusion​

This release also includes other fixes to make the library more stable and reliable, from accurate rounding in the Hull indicator to fixing context menu interactions on the floating toolbar. For the full list of updates, improvements, and fixes, see the Release notes.

This release brings clear indicator legends, more flexible drag-to-export feature, and various other improvements and bug fixes. Let's dive into the highlights.

Key updates​

Distinguish indicators at a glance​

When users apply the same indicator (like a Moving Average) to multiple symbols on a single chart, the legend can become ambiguous. Hiding inputs to clean up the view often removes the one piece of information they need most: which symbol each indicator line belongs to.

We've introduced the always_show_study_symbol_input_values_in_legend featureset. When enabled, symbol inputs in your indicator legends remain visible even when other inputs are hidden. This provides instant clarity, allowing users to confidently compare indicators across different instruments.

• Featureset enabled
• Featureset disabled

More flexible drag-to-export feature​

Previously, enabling the drag-to-export feature meant putting the entire chart into a rigid drag mode. This locked out normal interactions, forcing you to write complex logic with key listeners to toggle the mode on and off.

We've completely reimagined this feature to be more flexible and easier to implement. The new event-driven approach keeps your chart fully interactive at all times. For implementation details, see Enable drag-to-export feature.

Get the precise range of visible bars​

To give you more precision, we've added a new method that complements the existing getVisibleRange.

Use the new getVisibleBarsRange when you need the range of the actual data on screen. This method returns the precise time of the first visible bar to the last, including incomplete bars and correctly handling non-time-based styles like Renko. The range does not include any empty future space beyond the last visible bar.

Documentation​

Here are the key updates in the documentation:

• New Time and sessions section explains core principles of how to correctly handle bar times, symbol sessions, and resolutions in your datafeed to prevent common issues.
• The previous Tutorials section has been split into four focused categories: Tutorials, How-to guides, Framework integrations, and Interactive code examples. You can now find the type of content you need right away.
• New Troubleshooting article is a practical starting point for diagnosing and resolving issues you may encounter while implementing the library.

Conclusion​

This release also includes other fixes to make the library more stable and reliable, from fixing a VWAP indicator bug to ensuring UI elements resize correctly. For the full list of updates, improvements, and fixes, see the Release notes.

Key updates​

New floating tooltip for detailed bar analysis​

A new floating tooltip now appears after a long press on the chart, displaying detailed OHLC values and the price change for the selected bar. The tooltip follows your cursor or finger as you move across the chart, providing a seamless way to analyze data. To disable this feature, use the long_press_floating_tooltip featureset.

Inactivity gaps on daily, weekly, and monthly charts​

To provide a more accurate analysis of traded assets, we've extended inactivity gaps beyond intraday charts. You can now display gaps for periods with no trading activity on daily, weekly, and monthly timeframes. This gives users a better representation of time for instruments that don't trade every day.

This feature is enabled via the new inactivity_gaps featureset, which replaces the previous intraday-only version. Learn more about showing gaps on the chart.

New visibility controls in watermarks​

You now have granular control over the default chart watermark. We've added new API methods and corresponding UI checkboxes to independently toggle the visibility of the ticker, interval, and description. This allows you to set a cleaner default state programmatically, and gives end-users the power to customize the watermark to their exact preference through the chart settings.

Updated Broker sample​

The Broker API is the heart of our trading integration. To simplify your start, we’ve updated our broker sample 🔐 (access is restricted) so you can develop faster and with more clarity.

Choose between two distinct paths: a minimalist scaffold with only the essentials for our new step-by-step tutorial or a feature-rich mock that demonstrates advanced functionality like bracket orders. This new structure gives you the flexibility to either build from the ground up or learn from a complete example, streamlining your development process.

Instant trading info with enhanced tooltips​

To make it easier to read trading information on a busy chart, we've added price and profit/loss (P&L) details directly to the tooltips for positions, orders, and brackets. Simply hover over any on-chart trading line to see its exact price and current P&L at a glance, without searching for crowded labels on the price axis.

A more intuitive Trading Settings panel​

Meet the reworked Trading Settings panel, designed to be more intuitive and user-friendly. Clear descriptions now appear under checkboxes, removing any guesswork when customizing the view. A new toggle also lets you instantly hide Profit & loss information for both positions and brackets.

Watchlists now update across all your tabs​

To create a more seamless user experience, watchlists are now automatically synchronized across all open browser tabs. Changes made in one tab, like adding or removing a symbol, instantly appear everywhere else.

This feature is enabled by default and requires the use_localstorage_for_settings featureset. To disable the feature, use the watchlist_cross_tab_sync featureset.

Documentation​

Great features reach their full potential only when they're easy to understand and to use. That’s why our documentation focuses on explanations and practical examples, so you can go from idea to implementation faster.

Build your own AI expert​

Many of you already use AI assistants to explore our library and write code. Yet it's frustrating when a generic model hallucinates an answer or suggests a deprecated API based on outdated training data.

The power is now directly in your hands with a downloadable documentation file. This is a comprehensive base containing our complete, up-to-date documentation and full TypeScript definitions. By feeding this file to a modern LLM, you transform a general-purpose AI into a dedicated expert on our library. Ask complex questions, request full code examples, and get reliable, context-aware answers instantly. Learn how to set up your AI library assistant.

New guides​

We've also shipped a batch of new articles to tackle common questions and clarify powerful features:

• Customization with Watermarks. Learn how to dynamically control content, color, and visibility of chart watermarks.
• Best practices for Profit & Loss. Ensure the P&L values in your UI match your backend perfectly. This article explains why you should provide your own P&L data and shows you exactly how to do it, preventing discrepancies and building user trust.

Conclusion​

This release is about giving you better tools, clearer documentation, and more control over the user experience. This post covers the highlights — for the full list of updates, improvements, and fixes, see the Release notes.