Airtable Views Guide 2026: Grid, Gallery, Kanban, Gantt, Calendar & Form Views Explained

If you have opened an Airtable base and felt like you were only scratching the surface, Airtable views are where the real power lives. Every table you create has access to eight or more distinct view types — and switching between them does not just change the look of your data, it fundamentally changes how you interact with it. After years of deploying Airtable across project management, marketing operations, product development, and client services teams, the pattern is consistent: most organizations use only one or two views. That is leaving serious capability on the table.

This guide covers every Airtable view type available in 2026, how to create and configure each one, and — critically — which view is the right tool for which job. We will also cover new 2026 developments including Field Agents across views and Interface Designer’s expanded embed capabilities.

What Are Airtable Views and Why They Matter

Airtable views are saved configurations of how your table data is displayed. Every view is tied to a single table but can have its own independent filters, sorts, grouped rows, hidden fields, conditional formatting, and row height settings. When you change a view, you are not moving or altering data — you are changing the lens through which that data is seen.

This distinction matters enormously in practice. Your marketing team can have a Calendar view showing only published content filtered by the “Content” table, while your project manager looks at the same table through a Gantt view focused on deadlines. Your external client sees a shared link to a read-only Gallery view. Your operations lead receives form submissions through a Form view. All of this runs from one table, one source of truth.

In 2026, Airtable supports the following view types:

• Grid — spreadsheet-style rows and columns (the default)
• Gallery — card-based visual layout
• Kanban — status-based column board
• Gantt — bar-chart timeline (Team plan+)
• Timeline — multi-track scheduling (Team plan+)
• Calendar — date-based month/week view
• List — simplified mobile-optimized list
• Form — public data capture form

To add a new view, click the + Add a view button at the bottom of the Views panel on the left sidebar of any base. You will see all available view types presented as cards — click any type to create and name it immediately.

Grid View: Your Default Power Tool

Grid view is where most Airtable work happens, and for good reason. It resembles a spreadsheet but behaves far more like a relational database — cells can hold attachments, linked records, long-form text, checkboxes, ratings, barcodes, and dozens of other field types that a standard spreadsheet cannot. For data entry, bulk editing, and database administration, Grid view has no equal inside Airtable.

Business impact is immediate: operations teams use Grid view to maintain master records, QA teams use it to review and update records in bulk, and data managers use it to validate imports. The ability to group rows by any field — status, owner, department, date — turns a flat list into a structured report without leaving Grid view.

How to Create and Configure a Grid View

1. In the left sidebar of your base, click + Add a view at the bottom of the Views panel.
2. Select Grid from the view type cards. Name your view (e.g., “Team Operations View”) and press Enter.
3. Click Hide fields in the toolbar to collapse any fields irrelevant to this view’s audience. Hidden fields remain in the table — they are just not shown in this view.
4. Click Filter to add conditions (e.g., “Status is not Done” or “Assignee is [current user]”). Filters are view-specific and do not affect other views.
5. Click Sort to order rows by one or more fields — useful for surfacing the highest-priority records first.
6. Click Group to bucket rows by a Single Select, Linked Record, or other categorical field. Grouped Grid views act like pivot tables for quick summaries.
7. Right-click any column header and select Customize field type or adjust field width to optimize the layout for this view’s purpose.
8. To lock the view so only you can change its configuration, right-click the view name in the sidebar and select Lock view.

Pro tip: Use multiple Grid views for the same table to serve different audiences. A “CEO Dashboard Grid” can be heavily filtered and sorted by priority, while an “All Records Grid” shows everything unfiltered for admin use. Each view is a snapshot configured for a specific job.

Gallery View: Visual Browsing for Content Teams

Gallery view displays each record as a card with a featured image at the top — pulled from any Attachment field you designate. Below the image, up to 10 additional fields display as labeled text. For content libraries, product catalogs, candidate profiles, portfolio pieces, and event listings, Gallery view transforms a dense data table into a visually scannable interface that non-technical stakeholders can browse without confusion.

Marketing and creative teams use Gallery view daily: brand asset libraries display thumbnail previews; editorial calendars show article cover images alongside publication status; e-commerce teams browse product records by photo. The visual hierarchy makes Gallery the fastest view for identifying the right record by appearance.

How to Create and Configure a Gallery View

1. Click + Add a view in the sidebar and select Gallery.
2. Name the view (e.g., “Product Visual Library”) and confirm.
3. In the Gallery configuration panel on the right, click Card preview and select the Attachment field that contains your images. If no attachment field exists, create one first via the field editor.
4. Under Fields shown on card, toggle on the fields you want visible beneath the image — name, status, assignee, and date are common choices. Keep it to 4-6 fields maximum for readability.
5. Adjust card size using the Card size slider — larger cards make images more prominent; smaller cards fit more records on screen.
6. Apply filters (e.g., “Status is Active”) to show only relevant records in this gallery.
7. Click any card to open the full record detail panel for editing.

Gallery view is an excellent candidate for sharing via public link — clients reviewing a creative brief or executives browsing a product line do not need edit access, just a clean visual reference. More on shared view links in the View Management section below.

Kanban View: Workflow and Status Management

Kanban view organizes records into vertical columns based on the values in a Single Select or User field. Each column represents a stage, status, or owner, and you can drag cards between columns to update records without opening the record detail view. This direct manipulation of data — moving a card from “In Review” to “Approved” by dragging it — makes Kanban view the most intuitive choice for active workflow management.

Software development teams use Kanban for sprint tracking; marketing teams use it for campaign status; HR teams use it for hiring pipeline stages. Anywhere a process has defined sequential stages, Kanban view makes that pipeline visible and actionable in seconds. It also surfaces bottlenecks instantly — a column with 20 cards while others have 3 is a problem you can see without running a report.

For a deeper comparison of how Airtable’s Kanban stacks up against dedicated project management tools, see our Airtable vs Monday.com 2026 comparison.

How to Create and Configure a Kanban View

1. Click + Add a view and select Kanban.
2. Name the view and confirm. Airtable will prompt you to select a Stack by field — choose a Single Select field (e.g., “Status”) or a User field (e.g., “Assignee”).
3. Each unique value in that field becomes a column. Drag and drop cards between columns to update the field value directly.
4. Click Fields in the toolbar to select which fields appear on card faces. Name is always visible; add 2-4 supporting fields like due date, priority, and assignee.
5. Click Card preview to enable an image thumbnail on each card if you have an Attachment field.
6. Apply filters to scope the Kanban — for example, show only records assigned to the current user, or only records created in the last 30 days.
7. Reorder columns by dragging column headers left or right. Hide columns you do not want shown by clicking the column overflow menu and selecting Hide column.
8. Pair Kanban view with Airtable automations to trigger notifications when a card moves into a specific column — for example, sending a Slack message when a card enters “Ready for Review”.

Gantt View: Project Scheduling Made Native

Gantt view renders records as horizontal bars on a timeline, with bar length and position determined by Start Date and End Date fields. Dependencies between records — where one task cannot begin until another completes — are shown as connector lines on the chart. This makes Gantt view the right tool for project planning, resource allocation reviews, and milestone tracking where the sequencing of work is as important as the work itself.

Plan requirement: Gantt view requires a Team plan or higher. If you are on the Free or Plus plan, you will see Gantt in the “Add a view” panel but cannot activate it without upgrading. For teams that live in Gantt charts, this single feature is often the primary driver for upgrading. See our full Airtable 2026 review for a plan-by-plan feature breakdown.

How to Create and Configure a Gantt View

1. Ensure your table has at least two Date fields — one for Start Date and one for End Date. If not, add them via + Add field and choose the Date field type.
2. Click + Add a view and select Gantt (available on Team plan or higher).
3. In the Gantt configuration panel, map Start date and End date to the appropriate Date fields in your table.
4. To add dependencies, you need a Linked record field pointing to the same table (a self-linked table). Once created, map this field under Dependencies in the Gantt settings. Connector lines will appear between related bars.
5. Use the Group by option to organize bars into swimlanes by project, team, or assignee — making multi-project Gantt charts far more readable.
6. Adjust the time scale using the zoom controls in the toolbar — zoom in for day-level detail, zoom out for a quarterly overview.
7. Drag bar edges to extend or shorten duration, or drag the entire bar to shift dates. These changes write back to the Date fields in real time.
8. Apply color coding via Color in the toolbar — color bars by status, team, or priority to add a visual signal layer to the Gantt chart.

Gantt view excels in product roadmap reviews, construction project tracking, marketing campaign calendars, and any multi-phase initiative where deadline dependencies matter. The limitation compared to dedicated Gantt tools like Microsoft Project is that resource leveling is not automated — you have to manage overallocation manually. For most teams outside enterprise construction and engineering, Airtable’s Gantt is more than sufficient.

Timeline View: Multi-Track Resource Planning

Timeline view is Airtable’s answer to resource scheduling. Like Gantt, it renders records as bars on a horizontal time axis — but Timeline is optimized for displaying multiple records per row (multiple lanes), making it ideal for resource planning where a single person or team may have several overlapping tasks simultaneously. If Gantt is for project sequencing, Timeline is for capacity management.

Plan requirement: Timeline view, like Gantt, requires a Team plan or higher.

Use cases include agency resource allocation (who is working on what, when), editorial calendar management (articles in progress across writers), event planning (venue bookings, speaker slots, sponsor activations), and IT infrastructure change windows. The visual overlap detection Timeline provides is simply not possible in Grid or Kanban views.

How to Create and Configure a Timeline View

1. Confirm your table has Start Date and End Date fields. A User field for “Assignee” or “Resource” is also recommended.
2. Click + Add a view and select Timeline.
3. Map Start date and End date in the configuration panel on the right.
4. Select a Group by field (e.g., “Assignee” or “Team”) to create named row lanes. Each person or resource gets their own horizontal lane.
5. Enable Allow stacking in the settings if a single resource may have overlapping tasks — bars stack vertically within the lane rather than overlapping.
6. Apply filters to limit the view to relevant date ranges or specific team members.
7. Drag bars horizontally to reschedule, or drag edges to adjust duration — changes write back to the Date fields immediately.

Calendar View: Date-Driven Planning at a Glance

Calendar view places records on a monthly or weekly grid based on a Date field you choose. Any record with a date populates a cell in the calendar — no date means the record is not shown. This makes Calendar view the right tool for any process anchored to the calendar: publishing schedules, deadline tracking, event management, appointment booking, sprint planning, and client meeting logs.

The most powerful use of Calendar view in client deployments is the editorial calendar — content teams pin every article, social post, email, and podcast episode to its scheduled publish date, color-coded by content type. In a single screen, the entire content pipeline is visible. Editors drag cards between dates to reschedule without touching any form or field directly.

How to Create and Configure a Calendar View

1. Click + Add a view and select Calendar.
2. In the configuration panel, select the Date field that will drive placement on the calendar (e.g., “Publish Date,” “Due Date,” or “Event Date”).
3. Switch between Month and Week using the view controls in the top right — Month gives the big picture; Week gives you granular day-by-day detail.
4. Click Color in the toolbar to color-code records by a Single Select field (e.g., content type, project, team). This is where Calendar view becomes genuinely useful versus a generic calendar tool.
5. Apply filters to scope the Calendar — if you maintain multiple content tracks, create separate Calendar views filtered by content type or team.
6. Click any date cell to create a new record with that date pre-filled. Drag existing records to different dates to reschedule them.
7. Click any record card on the calendar to open the full record panel and view or edit all fields.

Calendar view does not support multi-day event spanning the way Google Calendar does — a record appears on its single date, not as a bar stretching across multiple days. For multi-day event display, use Timeline or Gantt view instead.

List View: Simplified, Mobile-Friendly Display

List view is Airtable’s most minimal view type — a clean, single-column list of record names with a small number of secondary fields visible beneath each item. It is intentionally simple. The design target is mobile access and quick scanning: field workers submitting updates via phone, executives reviewing action item lists, or anyone who needs to read and check off records without needing a complex interface.

List view also performs well as a read-only shared link for stakeholders who need to review a curated list without accessing the full base. It loads fast, displays cleanly on any screen size, and hides all the database complexity behind a presentation layer.

How to Create and Configure a List View

1. Click + Add a view and select List.
2. In the fields configuration panel, select the 2-4 fields to display beneath each record name. Keep it tight — the value of List view is its simplicity.
3. Apply filters to surface only the relevant records for this view’s audience.
4. Sort by due date or priority to surface the most urgent records at the top.
5. Tap or click any record to open the full detail panel for editing.

Form View: Capturing External Submissions

Form view is fundamentally different from every other Airtable view type because it does not display existing records — it creates new ones. A Form view generates a public-facing web form that anyone with the link can fill out and submit. Each submission creates a new record in your table automatically. No Airtable account is required to submit a form.

The business use cases are enormous: job application intake, event registration, client onboarding questionnaires, bug reports, content request submissions, vendor registration, internal IT helpdesk tickets, and project intake forms. Any process that starts with someone entering information belongs in a Form view. The data lands directly in Airtable without any copy-paste, manual entry, or third-party form tool.

How to Create and Configure a Form View

1. Click + Add a view and select Form.
2. The form editor opens in the main panel. Each field in your table appears as a form question. Drag fields up or down to reorder them as questions on the form.
3. For each question, click the field to edit its label text (the question as the submitter sees it), toggle whether it is Required, and add helper text beneath the question to guide responses.
4. Toggle Hidden on any field you do not want visible to submitters but want auto-populated (e.g., a “Source” field pre-set to “Web Form” using a default value).
5. Click Form settings in the right panel to customize the form title, description, logo or cover image, and the thank-you message shown after submission.
6. Enable Send respondent a copy if your form collects email addresses and you want to auto-email a submission confirmation.
7. Click Open form to preview the public-facing form, and click Share form to copy the shareable link or generate an embed code for your website.
8. Combine Form view with Airtable automations to trigger workflows on new submissions — notify a Slack channel, send a confirmation email via Gmail, or create a follow-up task in a linked table.

One limitation worth noting: Airtable native forms do not support conditional logic (showing or hiding questions based on previous answers) on the free plan. For conditional branching logic, you will need to integrate with a dedicated form tool or use Interface Designer’s form component, which offers more flexibility for logged-in users.

View Management: Permissions, Sharing, and Interface Designer

Understanding how to manage Airtable views — not just create them — is what separates a well-governed base from a chaotic one. There are three layers of view management every Airtable administrator should be familiar with: view permissions, shared view links, and Interface Designer.

View Permissions

By default, any collaborator with editor access or higher can modify any view’s filters, sorts, and hidden fields. This sounds reasonable until a team member accidentally removes a filter from a shared report view that executives use. To prevent this, use locked views. To lock a view, right-click its name in the sidebar and select Lock view. Once locked, only the view’s creator and base owners can change its configuration — other editors see the view but cannot alter it.

On Enterprise Scale plans, personal views are a separate concept — views that only their creator can see, marked with a lock icon. These are ideal for work-in-progress analyses you are not ready to share with the team.

Shared View Links

Every view can be shared publicly via a unique, read-only link. To share a view, click the Share view button that appears when you hover over any view name in the sidebar, or access it via the toolbar’s share controls. The public link allows anyone — including people without an Airtable account — to see the view’s current data. The view respects its filters, sorts, and hidden fields, so the recipient sees exactly the curated dataset you have configured, nothing more.

Shared links can be password-protected on paid plans. They update in real time — when you update records in Airtable, the shared view link reflects those changes immediately. This makes shared view links a lightweight alternative to building a full reporting dashboard for simple stakeholder updates.

Interface Designer in 2026

Interface Designer is Airtable’s tool for building custom, branded pages on top of your data — pages designed for end users who need a polished experience rather than a raw database view. Any standard view type (Grid, Gallery, Kanban, Calendar, etc.) can be embedded into an Interface page alongside buttons, record detail panels, filtered lists, and custom extensions built with the Airtable Interface Extensions SDK.

In 2026, Interface Designer has expanded to support per-user record filtering based on logged-in identity — meaning the same interface page shows different records to different users without any additional setup. This is the unlock for self-service portals, client-facing dashboards, and department-specific views all running from a single base.

Field Agents and AI Across Views in 2026

One of the most significant additions to Airtable in 2026 is Field Agents — AI workers that can read, analyze, and populate cell values across your base using large language models. Field Agents operate at the field level: you define a prompt and the AI populates that field for every record, or for records matching a filter condition.

Critically, Field Agents are view-agnostic — you configure them on a field, and they populate that field’s value regardless of which view you are currently working in. Whether you are looking at a Grid view, a Gallery view, or a Kanban, the AI-generated content appears in the cell. This makes Field Agents native to every workflow, not just the technical users comfortable in Grid view.

Practical applications across views in 2026:

• Gallery view: Field Agents write SEO-optimized product descriptions from structured product data fields.
• Kanban view: Field Agents auto-categorize inbound form submissions into the correct status column.
• Grid view: Field Agents extract sentiment scores from customer feedback text fields.
• Calendar view: Field Agents suggest optimal publish dates based on content type and historical performance data.

For a complete setup walkthrough, see our dedicated guide on how to set up Airtable Field Agents in 2026. Field Agents are configured via the field editor — click any AI-compatible field type, select Configure AI, write your prompt, and the agent runs on demand or automatically when new records are created.

For further reference, the official Airtable Views documentation provides the most current list of supported features per plan. The Airtable AI field support page covers Field Agent configuration options and model availability in detail.

Frequently Asked Questions