How to Use TradingView Screeners: From Saved Filters to Watchlists and Alerts
A screener is not a machine for identifying what will rise next. Its durable value is reducing a defined universe into a manageable research queue with rules another person can inspect. This guide connects universe design, filter roles, missing values, threshold sensitivity, saved screens, watchlists, alerts and weekly review. Because fields, coverage and interface labels can differ by screener and change over time, every operational step includes a definition and as-of-date check rather than relying on a fixed feature list.
Who this guide is for: TradingView users who want to narrow stocks, crypto assets, forex or other symbols without overfitting filters or filling an unmanageable watchlist
Key points to understand first
- Fix the market, venue, asset type, currency and other universe rules before applying a filter, and preserve the denominator.
- Layer eligibility, liquidity, size, price behavior, fundamentals and technical observations by role rather than counting the same signal repeatedly.
- If a small threshold change replaces nearly every result, treat the boundary as unstable rather than as a precise discovery.
- Let the screener create a research queue, the watchlist manage states, and alerts request a fresh review.
- Save the screen name, run time, counts, missing-value treatment and exclusions so the process can be reproduced.
Universe → Screen → Review → Watch → Recheck
- 01Define the universeMarket, venue, asset type, currency and data time
- 02Check eligibilityTradability, price, liquidity and required data
- 03Apply purpose filtersA small predefined set tied to the research question
- 04Verify primary evidenceIssuer, exchange and provider records for each candidate
- 05Manage statesResearch, Ready and Invalid with a next-review date
Useful output: Not a buy list, but a short queue with reasons, evidence and invalidation rules
A screener reduces research scope; it does not make the decision
A TradingView screener applies selected filters to a selected universe and presents matching symbols and fields in a table. The output reflects a dataset, configuration and timestamp. It does not establish future return, execution quality, suitability or the economic identity of an instrument. The first objective is therefore not to find “the best asset.” It is to reduce the number of primary documents that require review through an explainable process. Similar ticker text can represent different venues or providers, so the exchange or source is part of the identifier.
A basic sequence is to choose the relevant screener, define coverage, display the necessary columns, add a small number of filters in a fixed order, save the screen, and verify every surviving symbol. Popular screens and presets can be useful orientation, but their labels and composition are not permanent definitions. Copy the active fields and thresholds into the research record instead of citing a preset name as the reason for inclusion.
Fix the denominator before adding conditions
A filter has different meaning across global equities, US primary listings, Japanese shares, a sector list or one exchange. At minimum, record screener type, country or region, venue, asset type, currency and whether secondary listings are included. For OTC forex and crypto assets, the exchange or data provider is also part of the context. Identical-looking values need not share session boundaries, volume definitions, delay status or conversion rules.
| Layer | Check | Error without it | Record example |
|---|---|---|---|
| Coverage | Asset class, country and venue | Mixes rules and trading hours | Japan / primary listing |
| Data | Provider, delay and update time | Compares delayed and live fields | Run time and status |
| Units | Currency, ratio, period and sign | Misreads magnitude or direction | JPY, %, 20 sessions |
| Eligibility | Price, liquidity, missing fields | Treats an uncomputable row as attractive | Exclude NA with reason |
Available markets, fields, saving and export differ across screeners. Verify the definitions displayed in the current product.
Saving the original count distinguishes a screen that reduced 1,200 rows to 24 from one that reduced 30 rows to 24. Exporting only the survivors cannot reproduce that strength. Keep date, timezone, screen name and a text or image record of active filters beside the exported result.
Layer filters by function and avoid double-counting
A practical order is: can this symbol belong in the study, does it have the required data and liquidity, and does it relate to the research hypothesis? A long-horizon equity screen might set venue and valid price, then minimum liquidity, scale and a small set of business measures. A short-horizon monitoring screen may focus on session, volume and range. Applying several close variants of momentum does not add independent confirmation; it can count the same recent price behavior repeatedly.
Stage retention = rows after stage ÷ rows before stage × 100Total retention = final candidates ÷ initial universe × 100Excluded rows = rows before stage − rows after stageRetention describes how restrictive the screen is. It is not a quality score or a forecast of candidate performance.- Eligibility: Handle venue, valid prices, minimum liquidity and missing required fields.
- Research purpose: Use two to four conditions directly tied to the question; do not keep adding filters after seeing results.
- Ranking: Separate inclusion from ordering and name the one field used to sort.
- Verification: Open issuer, exchange or provider records for every survivor and reconcile units and dates.
Test whether thresholds, missing values and refresh timing break the result
A cutoff such as P/E below 15 or volume above one million is a user-defined boundary, not a law of nature. A row at 14.9 is not necessarily economically different from one at 15.1. Compare a modestly looser and tighter version with the predefined baseline. If a tiny adjustment replaces almost every name, the screen is boundary-sensitive. Keep near-boundary observations in a separate research state instead of claiming that one side is categorically acceptable.
Missing is not zero. Treating an unavailable growth rate as 0%, or a negative-earnings company with an undefined P/E as extremely cheap, can reverse the meaning of a screen. State whether missing rows were excluded, separated or evaluated with another measure. Results can also change after a filing refresh, constituent update, currency conversion or corporate action, which is why a timestamp and data source belong in the evidence.
| Version | Liquidity floor | Measure A | Rows left | Purpose |
|---|---|---|---|---|
| Loose | 500k | ≤ 18 | 42 | Map neighbors and missing fields |
| Baseline | 1m | ≤ 15 | 24 | Predefined primary setting |
| Strict | 2m | ≤ 12 | 9 | Inspect concentration in a few names |
All values are fictional. The example does not recommend a measure, threshold or security.
Separate Research, Ready and Invalid watchlist states
Copying every survivor into one long watchlist loses why it entered and when it should leave. Use states. Research means primary evidence remains incomplete. Ready means observation and invalidation rules have been documented. Invalid means an assumption failed, but the case is retained for learning. Ready is not a recommendation or an instruction to place an order; it is a workflow status.
For each symbol, preserve the added date, saved-screen name, passing reason, unresolved question, next-review date and invalidation rule. If the TradingView watchlist does not provide enough free text for the record, keep the same identifier in a research worksheet from the Financial Templates Hub. A color or flag on a chart should not be the only explanation. Verify current availability of advanced views and export in the product and plan documentation.
- Add to Research
Save the symbol, venue, source screen and reason for inclusion.
- Reconcile evidence
Verify the value, unit and date with issuer, exchange or provider material.
- Define Ready
Write the observation to monitor and the separate condition that invalidates it.
- Retain Invalid
Move the record with its failure reason instead of deleting the evidence.
Use an alert to request another review
A screener is a cross-sectional search at a point in time, a watchlist manages candidate state, and an alert sends a notification when a configured condition changes. Keeping those jobs separate prevents constant rescanning and prevents a notification from becoming an automatic trade instruction. Available price, indicator and watchlist alert conditions depend on current product support. Preserve condition, interval, frequency, expiration and destination using the ledger in the TradingView alerts guide.
After a notification, verify the symbol and venue, then the data timestamp and bar state, and finally rerun the saved screen. Do not act from message text alone. When the underlying screen or chart input changes, confirm whether existing alerts must be recreated under current TradingView behavior. Never place credentials, passwords or unnecessary personal information in a webhook payload.
Audit saved screens and exclusions each week
During a weekly review, reopen the saved screen with the same universe and sort, then record initial rows, stage counts, additions, continuations, Invalid moves and changes in missing fields. Do not evaluate the screen only by whether survivors rose. Review whether it reduced research work as intended, agreed with primary records, depended excessively on a cutoff, or omitted a relevant group. If a threshold is changed after observing the market, save a new version rather than overwriting the original.
Use the Macro Research Workbench to organize published macro context separately. Connect price and liquidity columns to the Stocks price-formation guide, and compare candidate behavior with market breadth and concentration. A screener row cannot replace market structure or issuer research.
- Name a saved screen by purpose and version, not only by a date that soon loses meaning.
- Record missing counts and exclusions beside the survivor count.
- Save threshold changes as new versions so post-result tuning remains visible.
- Reread at least one removed case to learn where the screen failed.
- Recheck official help when fields, labels or coverage change.
Estimate survivors through three filter stages
Enter the initial universe and the percentage retained at each stage. The result describes filter strength, not candidate quality or future performance.
Each percentage is relative to the previous stage. Conditions may be dependent, and rounding, missing fields or ties can make the displayed count differ.
Frequently asked questions
Are TradingView screener results real-time?
Update behavior and delay depend on the market, field, data entitlement and connection. Check the displayed definition, timestamp and delay status, and preserve the run time.
Do more filters make a screen more accurate?
No. Similar measures can count the same information repeatedly, while adding conditions after seeing results can overfit the screen. Start with a few purpose-linked rules and test threshold sensitivity.
Can every custom Pine Script be used as a standard screener filter?
No universal assumption is safe. Standard screeners and Pine Screener differ in coverage, requirements and supported scripts or fields. Verify the current official specification for the tool being used.
Does adding a symbol to a watchlist make it a trade candidate?
No. Research, Ready and Invalid are workflow states in this guide. Ready only means evidence, observation and invalidation fields have been completed; it is not a recommendation.
Is an exported CSV enough to reproduce the screen?
Not by itself. Preserve the universe, screen name, filters, thresholds, sort, missing-value rule, timestamp and data provider beside the output.
Primary sources and verification links
- TradingView | TradingView screeners walkthroughOfficial workflow for saved screens, filters, columns, result tables and CSV export
- TradingView | How to use filters in screenerOfficial instructions for adding, configuring, resetting and removing filters
- TradingView | Mastering the TradingView watchlistsOfficial guide to watchlists, sections and management
- TradingView | Watchlist advanced view modeDefinitions and cautions for advanced views, grouping, summaries and export
Edited and published by: SG Group · Editorial approach: We prioritize official TradingView Help Center and Pine Script documentation, then use exchange, regulator and other primary materials for market and product context. Features, data, pricing and connection terms change, so verify the current interface and linked sources before use.
Important notice: This article provides general education about TradingView interfaces, charts, alerts, screeners, paper trading and Pine Script. It is not investment advice, a trading signal, a recommendation of any instrument, data source or broker, or a guarantee of future price or profit. Features, pricing, data, exchange coverage, notifications, order integrations and Pine Script behavior vary by plan, region, connection and date and may change. Before risking money, verify current TradingView documentation and the terms of the relevant data source and connected provider, then rehearse the workflow with fictional data or paper trading.

