TradingView Advanced Charts

What it is

The chart engine other companies put in front of their own users. You get a widget constructor, a datafeed interface, roughly 110 drawing tools, over 100 indicators, custom indicators in JavaScript, up to eight price scales, synchronised multi-chart layouts, watchlists and 30-plus localisations — and you supply every number it draws.

It is the reason this category has a library half at all. Open a crypto product that is not an exchange and there is a good chance you are looking at this: Velo builds its derivatives terminal around a TradingView chart, and Bubblemaps embeds one next to its holder graph. Neither vendor wrote a candle renderer, and neither advertises whose they use. That is the normal state of this market.

The name is a trap. Most developers know it as the TradingView Charting Library, which is what it was called for years. The vendor renamed it to Advanced Charts and left the old name in the load-bearing places: the documentation is served from /charting-library-docs/, the private repository is tradingview/charting_library, and that is still the package name in the vendor's own package.json snippet. So the search term and the product name have diverged, and reviews written before the rename are about this.

It is not the platform and it is not the small one. The subscription product a trader buys is TradingView. The 35 KB Apache-2.0 renderer is TradingView Lightweight Charts. This card is the middle one: the full charting application, licensed rather than sold, for a team that wants TradingView's chart without TradingView's brand owning the user.

Pricing

The published price is zero, and the conditions are the product. The documentation states it in one sentence: Advanced Charts is available for free provided that the TradingView attribution remains visible and the implementation environment is public, which the same sentence defines as not for private use and not behind a paywall. The vendor's comparison table reduces that to a footnote reading "free with TradingView logo".

Unpack those two conditions before you plan around them, because each one rules out a real class of product:

• Attribution stays visible. TradingView's mark is on your chart, in your product, in front of your customers. If your brand guidelines forbid a third-party logo in the main workspace, the free licence is not for you.
• Public, not behind a paywall. An internal risk dashboard is private use. A charting screen that only subscribers reach is behind a paywall. Both are exactly the deployments a crypto company is most likely to be building, and the plain reading of the vendor's sentence excludes both from the free terms.

There is a "Contact us" button beside "Get the library" on the landing page, and no price behind it. The vendor publishes no figure, term or scope for a commercial arrangement anywhere we looked, so this card does not state one. If either condition above is a problem for you, that button is the whole of the published answer.

Redistribution is barred outright, and the wording is unusually direct. The quick-start documentation says the library is not redistributable and that it is prohibited to use any part of it in public repositories, and adds that obtaining it from third-party services is strictly prohibited and may lead to legal consequences. That has a practical edge for open-source crypto projects: you cannot commit the files, so a contributor cannot build your front end without getting their own access grant first.

Integrations

Access is granted, not downloaded. Submit the request form on the landing page; once approved, you get a GitHub invitation to a private repository. From there it is either a clone or a git dependency in package.json pinned by semver tag, and the npm route only works if your git client is authenticated to GitHub — which means your CI needs a deploy key before it can build.

The files are not bundled, and the docs say so. Everything under node_modules/charting_library/ has to be copied into a static-asset directory by a postinstall step, because your bundler will not process it. The vendor publishes the copy command. This surprises people arriving from a normal npm dependency, and it is the first thing to get wrong in a Docker build.

/charting_library/bundles is a declared black box. The documentation says TradingView may change its contents at any time without notice. Do not read it, do not patch it, and do not build anything that depends on a file inside it.

Data arrives through one interface. You implement the Datafeed API, or you point the bundled UDF-compatible adapter at an endpoint that speaks its protocol. The repository ships that adapter under /datafeeds/udf/ and the docs say you are free to edit it. Shipped alongside are TypeScript definitions for both the widget and the datafeed, ESM, CommonJS, UMD and IIFE builds, and mobile-app documentation.

Limitations

It ships no data, which is the whole design. The documentation's strapline is "your servers, your data, TradingView's charts". Every candle, every tick and every historical bar is your problem, and in crypto that usually means the work in the market data category has to be done before this library is worth installing. The demo feed in the quick start updates every ten seconds and exists to prove the chart renders.

670 KB. The vendor's own figure for the component, against 35 KB for Lightweight Charts. That is not a criticism — it is a full charting application with drawing tools, indicator engine and dialogs — but it is nineteen times the size of the alternative from the same vendor, and it is the number to put in front of anyone who says "just add a chart".

The trading UI is a different product. Order entry on the chart, the advanced order ticket, depth of market, bracket orders, account and position tracking, multi-chart layouts: in the vendor's comparison table those rows belong to Trading Platform, which is the 900 KB tier above this one. Bitpanda's Fusion, announced by the vendor in September 2026, runs Trading Platform — not this. If you are building an exchange front end and assumed the order ticket was included, check the table before you scope the work.

You cannot read the source. The repository is private, the bundles directory is explicitly undocumented, and a rendering bug is a support conversation rather than a patch. That is the trade for not writing a charting engine, and it is the opposite of the trade Lightweight Charts offers.

Custom indicators are JavaScript, not Pine Script. Scripts written for the TradingView platform do not move into a product built on this library. If your users expect to paste in a Pine indicator they found, the answer is no.

Public repositories are out. Stated under Pricing and repeated here because it is the clause most likely to be discovered late: an open-source crypto front end cannot vendor these files, and every contributor needs their own grant.

Alternatives

From the same vendor, TradingView Lightweight Charts is the honest comparison and usually the right first question: Apache-2.0, 35 KB, no indicators, no drawing tools, no licence conversation. If your product needs a price chart rather than a technical-analysis workstation, start there and come back here only when a user asks for Fibonacci retracements.

If neither the attribution nor the paywall condition works for your deployment, the choice moves to libraries that sell a licence outright rather than granting one — the commercial financial charting packages — and the card you should read next is whichever of those this catalogue has open in charting platforms and libraries.

And if you were looking for the product a trader subscribes to rather than the one a developer embeds, that is TradingView.