> For the complete documentation index, see [llms.txt](https://docs.floatgrids.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.floatgrids.com/ui-components/table.md).

# Table

{% hint style="info" %}
The Table UI component uses primitive prefabs in Unity for content and header cells, for content and headers rows and for the table as such.
{% endhint %}

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

## Features

**Responsiveness**\
The prefab "Table" is responsive, meaning it will adapt its size to any width you decide for your table.

<div align="center" data-full-width="false"><figure><img src="/files/KSgjZkLtjcZ0vdKhA8GH" alt="" width="375"><figcaption></figcaption></figure></div>

**Cell orientation**\
You have the flexibility to change the orientation of the cells to better align the content with the header.

**Number of columns**\
You can add as many columns as you wish; they will automatically adapt and fit to the container.

## Table structure in Unity

### Primitive prefabs

* Content Cell
* Content Row
* Header Cell
* Header Row

*Find them in FloatGrids/Design System/Customization/UI Components/Table*

### Final Prefab

This is the final prefab that includes all the primitives, use it as a container for your content

* Table

*Find it in FloatGrids/Design System/UI Components/Table*


---

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

```
GET https://docs.floatgrids.com/ui-components/table.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.