Airtable Embeds Do Not Show the Toolbar on Mobile and What You Can Do

You have embedded an Airtable base into a Zendesk knowledge base article.

On desktop, everything looks fine. Your users can see the toolbar, apply filters, group records, and interact with the base normally.

But on mobile, the experience breaks. The toolbar disappears completely, making filtering or grouping impossible.

Even when users tap the view larger option at the bottom, the problem remains. The base opens in a new tab but still shows the mobile view with no controls.

Airtable Embeds Do Not Show the Toolbar on Mobile

This makes the article hard to use for mobile visitors. So is this a bug, and can it be fixed?

Airtable Embeds Break on Mobile

The short answer is no. This is a long standing product gap in Airtable.

When you embed an Airtable view on your website, it works well on desktop. On mobile devices, Airtable hides the top toolbar inside embedded views.

As a result, filters, sorting, and grouping are not available. This behavior has existed since the early days of Airtable.

There is, however, a partial workaround. Airtable Interfaces behave differently from regular table views.

If you embed an Interface page instead of a table view, the toolbar can appear on mobile. But it only shows up when the phone is rotated horizontally.

So one solution is to embed an Interface and guide users to rotate their phones. It is not perfect, but it restores basic controls.

If that approach does not fit your use case, there are other options.

You can use third party portal tools like Softr or Zite. These platforms handle mobile layouts much better.

Another option is building a custom page. A developer can pull Airtable data and display it in a mobile friendly way.

You could also avoid embedding altogether. Instead, link directly to the shared Airtable view.

Each option has tradeoffs. The right choice depends on how critical mobile usability is for your audience.

For now, this is simply how Airtable embeds work on mobile. Until Airtable addresses it at the product level, workarounds are the only solution.