> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/design/responsive-layouts.md).

# Responsive Layouts

Feathery forms have built-in responsiveness that is also customizable by you at a granular level.

Feathery forms will automatically adjust your layout as much as possible to fit a mobile viewport. You can also easily create a custom mobile design by toggling to the mobile viewport in the designer.

<figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2FdAmJxzkjBhQi5TmU3RFI%2FScreenshot%202024-04-30%20at%2010.05.46%E2%80%AFAM.png?alt=media&amp;token=ec1123dd-7d24-4932-b6bd-767dd0c4bfe5" alt="" width="187"><figcaption></figcaption></figure>

Note that in the mobile view, any styles you set on your form will be **mobile-only**.&#x20;

{% hint style="info" %}
In the mobile view, any styles you set will be **mobile-only**. To clear out mobile-only styling, click on the blue highlighted label of the mobile-only style and click **Reset to Desktop**.
{% endhint %}

Your mobile layout and desktop layout will stay linked unless you adjust the dimension of a container. You can easily re-link your layouts in the mobile step panel.

<figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2F8iuGOsfWITqoQVRTBqB5%2Fdocs_mobile-layout.png?alt=media&amp;token=14f8a276-e6ba-45c2-b502-d950b2994613" alt=""><figcaption></figcaption></figure>

**Rotate Axis**

You can quickly create mobile optimized layouts by rotating a container's axis. That action to `Rotate into rows` or `Rotate into Columns` can be found in the right click overflow menu and in the properties panel of the container.

<figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2FjzmjlkKXlJwKcAC49Tjt%2Fdocs_responsive-rotate.gif?alt=media&amp;token=e5996263-f378-4da5-9b8c-b38752ff3925" alt=""><figcaption></figcaption></figure>

**Element & Container Styles**

Set custom mobile styles for width, height, padding, font size, and more.&#x20;

{% hint style="info" %}
Toggle basic elements **visibility** to hide or swap out designs on mobile.
{% endhint %}

<figure><img src="https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2Fd9c3urxiykpZZh2wlOm6%2Fdocs_responsive-style.gif?alt=media&amp;token=22013924-d7b5-4f6f-b382-b89732ab4480" alt=""><figcaption></figcaption></figure>

### Demo

{% embed url="<https://www.loom.com/share/9b4b4d4f9d42461a827f2a38b4f0b991>" %}


---

# 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.feathery.io/platform/build-forms/design/responsive-layouts.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.