> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/work-with-views/gallery-view.md).
# Gallery view
Display records as visual cards with images and key field values.
Use a Gallery view to display records as visual cards. Each card can show an image, a title, a background color, and selected field values.
In **Gallery view** you can:
* Use **Sort** to control the card order in ascending or descending order.
* Use **Configure cards** to adjust the information shown on the cards.
* To identify records more quickly, choose a field in **Title field**.
* To make cards more visual, choose a field in **Image field**.
* To distinguish categories at a glance, choose a field in **Color field**.
* Turn individual fields on or off to decide which values appear on the card.
* Use **Hide all** or **Show all** to update all field toggles at once.
* Use [**Filter**](#filter-records-in-a-view) to show only the records you need in the gallery.
To use record-based colors, first create a **Color** field in the table. Ninox then applies the stored color to each gallery card.
To show an image on the card, first create an **Image** field in the table.
You can open records directly from the Gallery board with a click on the card.
---
# 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.ninox.com/builder-hub/visualize-and-organize-your-data/work-with-views/gallery-view.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.
