> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/elements/basic/progress.md).

# Progress

The `Progress` element displays the user's progress through a multi-step form. This can be displayed as either a bar or a stepper, depending on how you want to visualize the progress.

<figure><img src="/files/lOcXpOoTi59n6V7F8hqg" alt="" width="339"><figcaption></figcaption></figure>

### Bar

As a progress bar, the element will display a percentage indicating how much of the form has been completed. The percentage defaults to defaults to an automatic value based on the user's progress, but it can also be manually set in the **Properties** tab to a custom value.

<figure><img src="/files/it6DQaR91WPKmqtM8aD3" alt=""><figcaption></figcaption></figure>

### Stepper

As a stepper, the element will display a set of connected steps as well as the current active step. Previous steps are clickable, allowing the user to navigate backwards through the form.

Stepper elements across steps can be linked to each other, so you can maintain a single set of steps and labels across your entire form.

<figure><img src="/files/DWPPR8bqY1le6vYIbgqT" alt=""><figcaption></figcaption></figure>

## Styles

Aside from standard element styles, a set of progress-specific styles are available as well. You may configure the color of the progress element, if the text is shown or aligned, and the direction of the progress element - does it span horizontally or vertically.

<figure><img src="/files/joPERfc1L4H1GpzK47vY" alt="" width="515"><figcaption></figcaption></figure>

### For Developers <a href="#example" id="example"></a>

The Feathery SDK and API reference progress bar components with `type` equal to `progress_bar`


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.feathery.io/platform/build-forms/elements/basic/progress.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.