> For the complete documentation index, see [llms.txt](https://help.quantower.com/quantower/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.quantower.com/quantower/analytics-panels/chart/technical-indicators/trend/zigzag.md).
# ZigZag
Use the ZigZag indicator in Quantower to filter out minor moves and highlight significant swings, trends, and chart patterns
## Description
ZigZag is a trend-following indicator that allows to determing trend swings. A combination of ZigZag highs and lows can be used as a support or resistance level. Also, it helps to identify significant changes in price and filter out short-term fluctuations.
## Formula
ZigZag finds extremums in price movement. These extremums reflect the diviations of price that are more than setted value. By default, the value for a ZigZag is 5%, it will ensure that only price fluctuations of 5% or more will be shown in the chart.
## Most useful cases
* **Determining swings** - the most common case of ZigZag usage is eliminating small price fluctuations and paying attention to huge price swings.
* **Support/Resistant levels** - ZigZag is also very helpful in finding levels of support and resistance; to do it, traders generally analyse the price of ZigZag swing and combine the closest swings together in one price level.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.quantower.com/quantower/analytics-panels/chart/technical-indicators/trend/zigzag.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.