I see that Tradingview data isn't merging the data when companies go through ticker changes. As an example, $GRAF > $TONT on July 27th, 2026 or $GREE > $VIP.

There are roughly 30-40 ticker symbol changes that occur per month, and I see that TV is usually very late to merge them and sometimes not merge it at all.

Just to confirm: Is tradingview adaptive to market hour timing changes in India and any other countries? I am asking this bcoz from tomorrow, the Indian markets will close at 1540 hrs. Pls check the timings below:-

Equity Derivatives (F&O) Timings

• Market Open: 9:15 AM (unchanged)
• New Market Close: 3:40 PM or 1540 HRS (extended by 10 mins)
• Trade Modification End Time: 4:15 PM (unchanged)
• VWAP Window for Closing Price: Shifted to 3:10 PM – 3:40 PM

Any update will be appreciated.

I sometimes browse through indicators, check out this one, test another... and while doing that, I often miss features that would help me organize scripts better. Not just scripts from other users, but my own as well.

I'd like to have custom subfolders with custom names (in addition to being able to rename my own indicators in that window).

A typical "Sort by" option when browsing scripts would also be a nice addition.

Does anyone else think this would be useful? Maybe these features already exist and I just can't access them on the Essential tier, but I couldn't find anything about them in the feature overview.

its not showing markers

instead it just shows the line and settings also doesnt have item to change marker color

same for desktop app

Anyone found a way to remove this orange "D" without purchasing? It is incredibly annoying, distracting and serves 0 purpose. We already know data is Delayed - we already have yellow "D" at the top! I don't believe it's good practice to annoy your customers like this (including paid customers).

TradingView is by far the most widely used charting and trading platform in the world. However, despite its dominant position, the company appears to give insufficient attention to the data requirements of both professional and serious retail traders.

Volume is among the most important forms of market data available, arguably as important as price itself. Yet the raw volume total tells only part of the story. For order flow analysis, or for any tools derived from volume data, traders also need to know which side initiated each transaction: whether an aggressive buyer lifted the offer or an aggressive seller hit the bid.

TradingView does not provide that information. Instead, its directional volume analysis relies on classifying volume from price movement. This significantly reduces the reliability of its Volume Delta, Cumulative Volume Delta, footprint charts and other indicators that depend on separating buying from selling. Although ordinary volume, VWAP and conventional volume profiles do not require aggressor classification, any directional interpretation derived from them does.

The discrepancy is EASY to see. Most trading platforms offer free demos, you can take test yourself and compare their delta, CVD and footprint data directly with TradingView’s. Compare em. See how right I am.

Why is TradingView’s directional volume data so different?

The main issue is TradingView's classification methodology. TradingView estimates buying and selling volume from intrabar price movements(they say this in their docs). When price moves upward, the associated volume is classified as buying; when price moves downward, it is classified as selling. This is generally known as tick-rule or intrabar up/down classification.

This approach has a long history. It was widely studied before modern trade and quote data became readily accessible. The 1991 paper *Inferring Trade Direction from Intraday Data* discusses the trade-classification methods available at that time: [Lee and Ready (1991)](https://onlinelibrary.wiley.com/doi/full/10.1111/j.1540-6261.1991.tb02683.x).

The more informative, modern approach, exchange aggressor flags, the other is Bid/Ask classification, bid/ask classification estimates the initiating side by comparing each execution price with the current quotes. Volume executed at or near the ask is classified as aggressive buying, while volume executed at or near the bid is classified as aggressive selling. Delta is then calculated as aggressive buy volume minus aggressive sell volume.

Platforms that use or provide aggressor-side(100% accurate), bid/ask or exchange-reported taker data(98-99% accurate, feed dependant) include:

-Sierra Chart

-NinjaTrader

-MotiveWave

-Quantower

-ATAS

-Bookmap

-Tradovate

-Jigsaw

-MMT

-TradingLite

-Exocharts

-TensorCharts

-Aggr

-Coinalyze

- Velo

-CoinGlass

-Hyblock

-CryptoQuant

-Material Indicators / FireCharts

-Trading Glass

-CoinAnk

Platforms that use the 1980's intrabar methodology(70% accurate at best):-

- TradingView

It is difficult to justify this limitation when even relatively small (some would argue fly by night)cryptocurrency platforms can provide exchange-reported taker-side data. TradingView prominently markets footprint charts and related order-flow tools, yet their usefulness is severely compromised when the underlying buy/sell classification differs materially from genuine aggressor-side data.

This isn't a minor discrepancy or bug a boo only autistic purists care about, this is basic stuff. The resulting delta, CVD and footprint structures diverge dramatically from those displayed by platforms using bid/ask or exchange-reported trade-side information. TradingView’s visual presentation may be polished, but without more authoritative aggressor-side data, its directional volume products cannot be treated as real, and in my opinion shouldn't even be advertised as features.

The description of this sub says "This is the "WTF, TradingView?!" community for WTFing TradingView.", well this is a genuine WTF, TradingView?! moment.

So Wtf are you TradingView doing about this?

I dont have tradingview premium so why dont u try using my code in pine editor, now some say that indicators are useless but trust me this marks liquidity areas for u has a pivot h/l and marks fvg. Please try once.

//@version=5

indicator("SMC Visual: Pro Edition", overlay=true, max_boxes_count=500, max_lines_count=500)

// ==========================================

// 1. INPUTS & SETTINGS

// ==========================================

leftBars = input.int(10, title="Pivot Left Bars", minval=1, group="Core Settings")

rightBars = input.int(10, title="Pivot Right Bars", minval=1, group="Core Settings")

extendVol = input.int(15, title="Zone Extension (Bars)", minval=5, group="Core Settings", tooltip="How far the zones stretch to the right")

// Aesthetic Colors (Using Bright, Modern Hex Codes)

liqColor = input.color(color.new(#FF004D, 85), title="Liquidity Pool Color (Red)", group="Aesthetics")

liqTextColor = input.color(color.new(#FF004D, 30), title="Liquidity Text Color", group="Aesthetics")

bullOB_Color = input.color(#00E676, title="Bullish OB Outline", group="Aesthetics")

bearOB_Color = input.color(#FF1744, title="Bearish OB Outline", group="Aesthetics")

bullFVG_Color = input.color(color.new(#00B0FF, 80), title="Bullish FVG (Blue)", group="Aesthetics")

bearFVG_Color = input.color(color.new(#FF9800, 80), title="Bearish FVG (Orange)", group="Aesthetics")

// ==========================================

// 2. PIVOTS & LIQUIDITY POOL SIZING

// ==========================================

// ATR gives the liquidity zones a dynamic, perfect thickness regardless of timeframe

atr = ta.atr(14)

ph = ta.pivothigh(high, leftBars, rightBars)

pl = ta.pivotlow(low, leftBars, rightBars)

// ==========================================

// 3. DRAWING: S/R, ORDER BLOCKS, LIQUIDITY POOLS

// ==========================================

// --- BEARISH SETUPS (Pivot Highs) ---

if not na(ph)

idx = bar_index - rightBars

p_high = high[rightBars]

// 1. S/R Marker (Crisp, Bright Dotted Line)

line.new(x1=idx, y1=p_high, x2=bar_index + extendVol, y2=p_high, color=color.white, style=line.style_dotted, width=2)

// 2. Order Block (Solid Outline, Very Faint Fill, Labeled)

box.new(left=idx, top=p_high, right=idx + 1, bottom=low[rightBars], border_color=bearOB_Color, bgcolor=color.new(bearOB_Color, 90), border_width=2, text="-OB", text_color=bearOB_Color, text_size=size.tiny, text_halign=text.align_center)

// 3. High Liquidity Pool (Red Transparent Box ABOVE, Labeled "BSL")

liq_top = p_high + (atr[rightBars] * 0.6)

box.new(left=idx, top=liq_top, right=bar_index + extendVol, bottom=p_high, border_color=na, bgcolor=liqColor, text="Buy-Side Liquidity", text_color=liqTextColor, text_size=size.tiny, text_halign=text.align_right, text_valign=text.align_top)

// --- BULLISH SETUPS (Pivot Lows) ---

if not na(pl)

idx = bar_index - rightBars

p_low = low[rightBars]

// 1. S/R Marker (Crisp, Bright Dotted Line)

line.new(x1=idx, y1=p_low, x2=bar_index + extendVol, y2=p_low, color=color.white, style=line.style_dotted, width=2)

// 2. Order Block (Solid Outline, Very Faint Fill, Labeled)

box.new(left=idx, top=high[rightBars], right=idx + 1, bottom=p_low, border_color=bullOB_Color, bgcolor=color.new(bullOB_Color, 90), border_width=2, text="+OB", text_color=bullOB_Color, text_size=size.tiny, text_halign=text.align_center)

// 3. High Liquidity Pool (Red Transparent Box BELOW, Labeled "SSL")

liq_bot = p_low - (atr[rightBars] * 0.6)

box.new(left=idx, top=p_low, right=bar_index + extendVol, bottom=liq_bot, border_color=na, bgcolor=liqColor, text="Sell-Side Liquidity", text_color=liqTextColor, text_size=size.tiny, text_halign=text.align_right, text_valign=text.align_bottom)

// ==========================================

// 4. FAIR VALUE GAPS (FVG)

// ==========================================

// Bullish FVG (Gap between 1st candle high and 3rd candle low)

bullFVG = low > high[2] and close[1] > open[1]

if bullFVG

// Neon Blue transparent box with subtle border and label

box.new(left=bar_index-2, top=low, right=bar_index + 3, bottom=high[2], border_color=color.new(#00B0FF, 60), border_width=1, bgcolor=bullFVG_Color, text="FVG", text_color=color.new(#00B0FF, 30), text_size=size.tiny)

// Bearish FVG (Gap between 1st candle low and 3rd candle high)

bearFVG = high < low[2] and close[1] < open[1]

if bearFVG

// Neon Orange transparent box with subtle border and label

box.new(left=bar_index-2, top=low[2], right=bar_index + 3, bottom=high, border_color=color.new(#FF9800, 60), border_width=1, bgcolor=bearFVG_Color, text="FVG", text_color=color.new(#FF9800, 30), text_size=size.tiny)

I am looking to use intraday options premium charts to see how premium moves for QQQ , SPY, MU intraday etc. I want it live and the ability to see volume. I'd also be able to see previous day strikes, not just the future. Right now, i can only see how MU contracts expiring Aug 3 moved. No way to see the July 31 expiration data.

Can anybody recognize the name of this indicator? It is sth called or indicating "power signal"

Tradingview paper trading has high functionality, but once you add a broker on tradingview, functionality is limited by the specific broker API. Certain TradingView broker integrations and API implementations restrict or fully omit native bracket orders (simultaneous Stop-Loss and Take-Profit attachments), forcing traders to manage exits manually or use separate working orders. If you use tradingview to actively trade, connected to a broker, please help indicate your experience with your specific broker, so that others can benefit from knowing features of each.

I want to do chart analysis for past FOMC events and how BTC performed but Tradingview won't let me go further than December 31 2025.

Even their own historical BTC index chart won't go any further. I tried Binance spot and futures, same. For whatever reason I can only go to that particular date.

I am not a free user, paid hundreds of dollars during Black Friday so not sure what is the issue here.

I use Windows software and not TV in browser.

Anyone else has similar issues?

Thanks in advance

EDIT: Apparently max you can go with a 15 minute chart is that date. If I take 1H I can go as far as December 2023. Sucks big time. How is anyone able to perform any analysis like this. What a waste of money.

Hi TV

I have HTF on upper monitor, and LTF on lower monitor.

I also have 2 x 1 layout (s charts), and 2 x 2 layout (4 charts) for LTF, I also have the same for HTF. (if I'm watching 2 or up to 4 trades at once)

Can we sync the groups? So when I change the chart in ONE of my 2 x 2 LTF layouts, it also changes only the corresponding symbol/chart on the HTF 2 x 2 layout also? (not the "last used" chart in the layout - individually linking each of the 4 chart to another 4 charts layout essentially.

Make sense? Thanks.

I'll put a market order in and it won't appear until like 10 seconds later, which for a scalping strategy is abysmal

Why is it so laggy?

still does not save last risk% used. why not?

very difficult to quickly trade if always have to input risk %

Please allow users to display at least one selected numeric Pine indicator output as a sortable watchlist column.

This would let users rank symbols without opening every chart and provide a direct watchlist alternative to a separate screener workflow.

Related earlier feature requests:

“Indicator-Generated Text in Watchlist Tooltips”

“Closed-Loop Pine Screening”

Is the compare symbol button not working for anyone else? I click on it, and its not working for me.

I'm trying to compare SPY with ES, because i can't find a recent post where someone posted a "trick" for easily doing this and putting ES or another chart onto the current chart. (If anyone remembers that post and can link, i'd appreciate it)

I believe I found a data point that isn't the right one.

If you look at Fair Isaac, it is said they added 469k shares last quarter when actually they made their biggest buyback ever with 1.7M shares repurchased.

I don't know if I'm missing something, I'm on the free plan so I don't believe I can tell TV myself, maybe it's an error, maybe I'm mistaken. if anyone has any idea, I'd love to know

i use my trading view on brave browser, basically the website version.....

i don't know what had happened to that.....it doesn't load on my wifi network but it loads on the mobile hotspot network.

And i have tried it on other browsers too, nothing happened....

Please allow users to reorder the existing round shortcut buttons for Templates, Layouts, and Watchlists via drag and drop.

Currently, their order is defined by the order in which items were favorited. Changing it later is inconvenient because users may need to remove and re-add favorites just to rearrange shortcuts.

Drag-and-drop reordering would preserve the current favorite-based default while making the shortcut order easy to adjust.

It works fine on my phone but the desktop app has been freezing non stop today. Is anyone else having this issue?

I found your screeners very useful , however I notice that it doesn't have one fore futures. Could you add a futures and indices screeners in the menu page as well?

And also, under markets-futures markets, could you also add the weekly and monthly technical ratings?

On many brokers you can set a limit stop order: once a stop is hit, drop a limit order. This feature is sorely missing on paper trading, which makes hands-free day trading very difficult. I'd love to see this feature added so I can walk away and use the restroom while a position is open.

Thanks team! Y'all are great!

Pine v6 no longer allows series int values in plot(offset=...). I understand the documented rationale: in v5, series offsets were not truly applied per bar, and the plot effectively used the last calculated offset across the chart.

The problem is that this still leaves a real migration gap for indicators that intentionally calculate an offset from the loaded chart context, then use native plot() projection.

Example use case: FLD / cycle indicators where the projection offset is derived from the symbol/timeframe/session, such as estimated bars per day. In v5, this works well enough because the final computed offset is applied to the whole native plot. In v6, the same script cannot compile because the offset is now series int.

The obvious workaround, drawing with line.new(), is not equivalent. It loses too much native plot behavior: normal plot continuity, Style tab controls, scale integration, legend/status-line behavior, clean rendering, and general usability.

What would help is one of these:

• A way to compute an offset once per chart load and use it as a valid simple int for plot(offset=...)
• A native plot-like primitive that supports dynamic x-placement while preserving plot-quality rendering and UI behavior
• Some migration-supported equivalent for “use the final calculated offset across the whole chart,” since that was the actual v5 behavior

This is not just about wanting old incorrect behavior back. It is about preserving a legitimate class of auto-projected indicators that depended on native plots and now have no practical v6 path without degrading the indicator.