> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/super-filter/features/10.-display-settings/x.-scale-visual.md).

# x. Scale Visual

The **Scale Visual** feature in Super Filter allows users to resize the visual elements—such as text, icons, and filter items—within the filter interface. This is especially helpful when working with custom-sized Power BI pages, where visuals may appear too small for comfortable interaction.

### Configuration Steps

{% stepper %}
{% step %}
Open the **Format Pane** of the Super Filter visual.
{% endstep %}

{% step %}
Expand the **Display Settings** section.
{% endstep %}

{% step %}
Locate the **Scale Visual** option.
{% endstep %}

{% step %}
Use the slider or input box to adjust the size as needed.
{% endstep %}

{% step %}
The visual will automatically update to reflect the new scale.
{% endstep %}
{% endstepper %}

### Why Use Scale Visual?

* Ensures **better visibility** of filter items on custom-sized or small report pages.
* Improves **readability and accessibility** for end users.
* Provides **flexibility** to align visual sizing with your dashboard design.
* Helpful for **high-resolution displays** where default sizing appears too small.

<figure><img src="https://2237530339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPIvQSuyE40UC9wv5uGgW%2Fuploads%2FACWxAfIwYmj03heeBk8X%2Fimage.png?alt=media&amp;token=07d77f88-6e5b-4148-ae88-dbb5511a3af1" alt=""><figcaption><p>Image 1: When Custom page size is used with scale visual set to 5.</p></figcaption></figure>


---

# 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://docs.inforiver.com/super-filter/features/10.-display-settings/x.-scale-visual.md?ask=<question>&goal=<user_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.