Framer supports connecting a CMS Collection to an external Airtable base as one of its CMS data sources, alongside its own native Collections. It's a genuinely useful setup for teams that already manage content in Airtable and don't want to duplicate that data entry inside Framer — but it's worth understanding exactly what that connection is before you build a site around it.
How the Airtable connection works
You point a Framer CMS Collection at an Airtable base and table, map Airtable's columns to Framer's CMS fields (text, image, rich text, and so on), and Framer pulls that data in to populate your Collection pages — a blog where every post is really an Airtable row, for example. Content edits happen in Airtable; Framer reflects them, generally on a sync/refresh cycle rather than instantaneously, though the exact behavior depends on your plan and setup.
This is a live data connection, not a one-time import — the site keeps reading from Airtable for as long as the integration is active, which is exactly what makes it convenient for a team already living in Airtable, and exactly what makes it worth thinking through before you export.
What happens when you convert the site
A converted site (Hybrid or Pure Next.js) is a snapshot, not a live connection. Conversion crawls the published Framer site's rendered HTML — the Collection items as they appear on the live pages at the moment you convert — and turns that into static files or Next.js routes. It has no visibility into the Airtable base itself; it never sees your API key, your table structure, or Airtable at all. It only sees the pages Framer already rendered from that data.
The practical result: everything published at the time of conversion carries over correctly, formatted the same way it rendered on the live site. What doesn't carry over is the live connection — after conversion, adding a new row in Airtable does nothing to the converted site, because there's no longer a Framer CMS Collection reading from that base at all. The converted output is real content on real pages, but it's frozen at conversion time, not wired to Airtable going forward.
What this means in practice
- If you're done adding content and just want a fast, ownable version of what's already published — a portfolio you're not actively growing, a blog you're archiving — conversion is a clean fit. You get everything that's live today, as real files, with no ongoing Airtable dependency at all.
- If you're actively adding new Airtable rows on an ongoing basis — a growing blog, a live job board — converting once gives you a snapshot that immediately starts drifting out of date the moment you add a new row in Airtable, since nothing downstream is watching that base anymore. In that case, the realistic plan is to keep publishing new content through Framer and convert again periodically to pick up what's changed, rather than treating one conversion as a permanent replacement for the live Airtable connection.
Either is a reasonable choice — it just needs to be a deliberate one, made with the actual tradeoff in view rather than assumed.