How to Use Airtable Gallery View for Visual Databases

A grid is the wrong way to present a product catalog. So is a list. The customer (or the salesperson, or the recruiter) needs to see the thing — the product photo, the headshot, the floor plan, the cover artwork. Airtable's Gallery view turns any table with an attachment field into a visual database where the image leads and the data supports.

This guide covers how to set up Gallery view, configure cover images, choose which fields appear on each card, filter and color for scannability, and share visual catalogs internally and externally — with the real templates we deploy for e-commerce, real estate, design, and HR teams.

What Gallery View Actually Is

Gallery view is a saved layout that renders each record as a card in a flexible grid, with a cover image on top and a configurable set of fields below. It is one of Airtable's view types — the same records also live in Grid, Kanban, Calendar, and Timeline views, all reading and writing to the same underlying data.

Gallery is the right view whenever the visual matters more than the structured data. A product without its photo is a SKU. A property without its hero image is a row. A designer's portfolio piece without its cover is just a project title. For all of these, Gallery is the daily-driver view.

For a broader survey of every Airtable view type, see our custom views guide.

Prerequisites: The Attachment Field

A Gallery view needs an attachment field to act as the cover image source. If your table does not have one, add it first.

1. Click + at the end of the field row.
2. Choose Attachment as the field type.
3. Name it (e.g. Cover Image, Photos, Hero Shot).
4. Save.

You can upload images directly to the field, drag-drop from your desktop, or paste image URLs and Airtable will fetch them. For high-volume catalogs, automate image uploads from Make or Zapier — see our Make automation guide for the pattern.

A single record can hold many images in one attachment field. Airtable always uses the first image as the cover; drag the preferred image to the front of the field's stack to swap which one appears on the card.

Step 1: Create the Gallery View

From any table with an attachment field:

1. Click + in the view sidebar.
2. Choose Gallery under the visual layouts.
3. Name the view (e.g. Product Catalog — Gallery).
4. Click Done.

Airtable creates a Gallery view using the first attachment field it finds as the cover image. Each record appears as a card with the cover on top, primary field as the title, and the next few fields as supporting text.

Step 2: Configure the Cover Image

Open the view's Customize cards panel. Find the Cover image section and choose:

• Source field. Which attachment field supplies the cover. Most tables have one; pick it explicitly so the view does not accidentally use a different attachment field added later.
• Crop vs fit. Crop fills the card with the image (often best for product photos). Fit shows the whole image with letterboxing (better for floor plans and screenshots where you cannot afford to crop edges).
• Size. Small, medium, or large. Small fits more cards per row; large gives each image room to breathe.

For a product catalog, crop large. For floor plans, fit medium. For headshots, crop small — you want to see as many people as possible on one screen.

Step 3: Choose Which Fields Appear on Cards

Below the cover, each card shows a few fields. Like Kanban cards, less is more. Click Customize cards and turn off everything except the four or five fields that matter for the person looking at the gallery.

Rule of thumb: if you have to squint, you have too many fields. Cards work when a viewer can absorb them in a second.

Step 4: Filter, Sort, and Group

Gallery is a layout, not a data filter. You still need filters and sorts to make a 500-record catalog navigable.

Common filter patterns:

• Active items only. Status is Available (real estate), In Stock (products), Active (team), or Published (designs).
• Current season or release. Release Date is in current quarter for product launches.
• Tag-driven subsets. Filter to Tags contains Featured for hero collections.

Sort by Display Order (a manual integer field) when humans curate the order, or by Updated Time when freshness matters. Gallery supports grouping the same way Grid does — group by Category or Collection and each group renders as a labeled section in the gallery, which makes large catalogs much more scannable.

Step 5: Color Cards

Click Color in the toolbar. Coloring in Gallery applies a thin colored bar at the top or side of each card.

Color rules apply per view, so different audiences see different urgency cues looking at the same records. The customer-facing gallery has no color rules; the internal merchandising gallery flags low stock in red.

Real-World Templates

Five Gallery view templates we deploy in client projects.

E-Commerce Product Catalog

Table: Products. Linked to Categories, Suppliers, Variants. Attachment field: Product Photos. Gallery cover crop large. Visible fields: Product Name, Category (lookup), Retail Price, In Stock rollup.

Two Gallery views over the same table: a Merchandising view filtered to all active SKUs grouped by Category for internal use, and a Storefront Feed view filtered to in-stock items only, sorted by Featured rank, shared via a public link to the marketing team's headless storefront builder.

Combine this with an inventory automation system and the gallery becomes the visual front-end of a real product database.

Real Estate Listings

Table: Properties. Linked to Agents, Buyers, Showings. Attachment field: Photos (one record holds 20+ images). Gallery cover fit large — floor plans cannot crop.

Visible fields: Address, Bedrooms/Baths, List Price, Days on Market. Filter to Status = Active. Color by Days on Market (orange after 60 days, red after 90). Group by Neighborhood. A separate Sold view archives past listings for comp analysis.

Share a buyer-specific Gallery view via a client portal so each buyer sees only the listings their agent has curated.

Internal Team Directory

Table: Team Members. Linked to Departments, Offices, Manager. Attachment field: Headshot. Gallery cover crop small — fit as many faces per screen as possible.

Visible fields: Name, Role, Team, Office Location, Slack handle. Filter to Status = Active. Group by Team. The directory becomes a visual org chart that new hires actually use. Pair with a contact management system for full HR ops.

Design Asset Library

Table: Assets. Linked to Brand, Campaign, Owner. Attachment field: Final Files. Gallery cover crop medium. Visible fields: Asset Name, Format, Campaign, Last Updated.

Filter to Approved = checked for the public library; a separate Pending Approval Gallery view shows in-flight assets to reviewers. Color rules flag assets that have not been used in 6+ months (a candidate for archive) and assets newly added in the last 14 days (worth surfacing).

Creative Portfolio

Table: Projects. Linked to Clients, Service Lines, Team. Attachment field: Portfolio Image. Gallery cover crop large. Visible fields: Project Name, Client, Year, Service Line, Awards.

Two Gallery views: an internal All Work view including kill-fee projects and confidential work, and an external Public Portfolio view filtered to Public = checked. The public view becomes the portfolio page on the agency's site via an embed or client portal.

Sharing Gallery Views Externally

Right-click any Gallery view and choose Share view. Airtable creates a public read-only URL. Anyone with the link sees the cards in the configured layout — no editing, no other tables, no base structure.

Three sharing patterns we use:

• Password-protected catalog. The buyer-specific real estate gallery has a password the agent shares with their client. Anyone without the password gets a login wall.
• Domain-restricted directory. The internal team directory is shared with @company.com only (paid plans).
• Public embed. The portfolio gallery is embedded directly in the agency's marketing site using Airtable's embed code. Updates in the base appear on the site in real time.

For more on sharing patterns, see our collaboration guide.

Combining Gallery with Other Views

Like Kanban, Gallery is rarely the only view on a table. The standard pattern is two or three views per table tuned for different jobs.

Edits made in any view propagate to all others instantly. The merchandiser tags items as Featured in Gallery; the admin sees the change in Grid; the public storefront filter picks it up automatically.

Performance and Image Optimization

A Gallery view of 2,000 high-resolution product photos loads slowly on a typical connection. Three tactics keep it snappy.

• Compress images before upload. A 400KB JPG looks identical to a 4MB JPG on a card and loads ten times faster.
• Use WebP where possible. WebP files are typically 25-30% smaller than JPG at the same visual quality. Airtable renders them natively.
• Filter aggressively. No one looks at all 2,000 products at once. Filter to current season, current category, or in-stock-only so the view loads 50-200 records at most.

For automated image optimization workflows, see our AI product packshots guide.

Common Mistakes

Four issues we fix on most Gallery view audits.

Wrong cover field selected. A table with multiple attachment fields (Photos, Floor Plan, Documents) defaults to whichever was created first. Always pick the cover source explicitly in the customization panel.

Too many fields on the card. Eight visible fields per card turns the gallery into a wall of text under each image. Cap visible fields at four or five.

No filter on the view. A Gallery view of all 5,000 records ever entered is unusable. Filter to active, current, or in-stock items only; archive historical records in a separate view.

Using image links instead of attachment fields. A URL formula field showing image links does not render as a card cover. Use real attachment fields. If your source data is URL-only, run a Make automation that downloads each URL into an attachment field.

Troubleshooting

Quick fixes for the issues that come up most often.

• All cards show a gray placeholder. No attachment field is configured as the cover. Open Customize cards and select a source field.
• Some cards have images, others do not. Records without files in the attachment field show a placeholder. Either filter them out (Cover Image is not empty) or upload images.
• PDFs and Word docs not showing as covers. Airtable cannot render document formats as cover images. Convert to PNG/JPG or use a separate Image field for covers.
• Public share link shows old images. Browsers and CDN cache aggressively. Hard refresh or wait a few minutes — Airtable propagates within 5-10 minutes typically.
• Gallery view feels cluttered. Reduce visible fields, increase image size from small to medium, and consider grouping by a category field to add visual structure.

Where to Go Next

Gallery view is the simplest view type to set up and one of the highest-impact for any team that works with visual data. Once it is running, layer in automations that maintain image quality, build a client portal that exposes filtered galleries to external users, and pair with linked records so each visual record connects to the rest of your operating data.

For Airtable's official configuration reference, see the Gallery view documentation.