> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/component-designer/pixel-perfect-app/hide-elements.md).

# Hide elements

Discover how to hide elements with Conditional Visibility

Hiding elements is useful for optimization, such as concealing large navigation menus on smaller screens. Conditional visibility improves user experience by showing only relevant content.

Hide elements in Component Designer using Conditional Visibility:

1. Click on the **element** you want to **set conditional visibility** to.
2. Go to the **Right Sidebar**.
3. Click on the `Conditional Visibility` button.
4. Scroll and choose the option that fits the best for your requirements.

{% @arcade/embed flowId="6ya9Zo2mBFCpaLEhofSA" url="<https://app.arcade.software/share/6ya9Zo2mBFCpaLEhofSA>" %}

Dynamically change elements in Component Designer using Conditional Fill:

1. Click on the **element** you want to **set the conditional fill** to.
2. Go to the **Right Sidebar**.
3. Go to the `Fill` section.
4. Click on the `More` button to see more options.
5. Scroll and choose the option that fits the best for your requirements.

{% @arcade/embed flowId="lXwalnXKIGa3TonER8z6" url="<https://app.arcade.software/share/lXwalnXKIGa3TonER8z6>" %}


---

# 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.jetadmin.io/classic-app-builder/component-designer/pixel-perfect-app/hide-elements.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.