# View Types (List, Grid, Calendar)

NotionApps' List screens show limited pages in a list based on the [Filtering, Sorting, or Grouping Items](/customize-app/customize-a-screen/filtering-sorting-items.md) conditions. Additionally, choose the right view type for each List screen—List (📋), Grid (🖼️), or Calendar (📅)—to match how your users browse and act on data.

**📋 List view**

      \- Classic table-like list with optional subtitle/caption/tag/image fields.

      \- Supports grouping, sorting, search, and inline “wrap text” toggle.

      \- Best for dense record scanning and quick actions.

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

**🖼️ Grid view**

&#x20;     \- Card/gallery layout with optional image and two-column support.

&#x20;     \- Supports grouping and sorting; good for media-heavy or visual browsing.\\

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

**📅 Calendar view**

&#x20;     \- Date-driven view with Month/Week/Day/Agenda modes (switchable if allowed).

&#x20;     \- Requires a date (start/end) field; title field is used for the event label.

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

#### &#x20; How to pick

&#x20; \- Use List for operational lists.

&#x20; \- Use Grid when visuals or summaries matter.

&#x20; \- Use Calendar when the primary dimension is time; great for schedules, launches, or reminders.

If you're looking for more view types like Kanban or Maps, please raise a request on [our community](https://community.notionapps.com/c/request-features/6).


---

# Agent Instructions: 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:

```
GET https://docs.notionapps.com/customize-app/customize-a-screen/view-types-list-grid-calendar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.