How to export Framer CMS content: CSV vs JSON

Four ways to export a Framer CMS collection

• Framer's CMS Export plugin. The first-party CMS Export plugin exports a collection as CSV from inside the editor. It is free and quick, and it runs only when someone opens the project and clicks export.
• The FrameVault Backup plugin. Our free FrameVault Backup plugin also runs in the editor. It downloads every collection as one JSON file, including gallery fields and localized values, or a single collection as CSV. Like any plugin, it runs only when someone clicks it.
• The Framer Server API. The Server API (beta) can read collections and items from a script, so you can write raw field data to any format you like. You maintain the script and its schedule. For a one-off copy without writing code, the free FrameVault CMS export tool uses the Server API to download every collection as JSON plus a CSV per collection.
• A backup service. Tools such as FrameVault read collections on a schedule and let you download any stored snapshot later as JSON or CSV.

CSV: good for people and spreadsheets

CSV is one table per collection: one row per item, one column per field. Anyone can open it in Google Sheets, Excel or Numbers, scan it, filter it and hand it to a client. That is its strength. Its weakness is that a CSV cell is plain text, so structured field types have to be flattened.

FrameVault's CSV export, as a concrete example, flattens fields like this:

Cells starting with =, +, - or @ get a leading apostrophe so spreadsheet apps do not run them as formulas. Remove it if you reimport the data elsewhere.

Other exporters flatten differently. Whatever tool you use, open one export and check rich text, images and references before you rely on it.

JSON: good for restores and migrations

JSON keeps structure. A FrameVault JSON download is the whole stored snapshot: every collection, its field definitions, and each item's field values with their types. Rich text keeps its markup and image fields keep their metadata. It is the format to keep if you may need to write content back into Framer or move it to another CMS with a script.

JSON is awkward to read by hand and not something to send a non-technical client on its own. Many teams keep JSON as the source of truth and generate CSV when a person needs to look at the data.

Neither format contains your media files

Framer CMS image and file fields point to hosted asset URLs. An export, in CSV or JSON, stores those URLs, not the files. If you need the originals independent of the Framer project, for example before cancelling a plan or handing a site to a client, download the assets separately and keep them next to the export.

Which one should you use?

• One-off review or content audit: CSV.
• Backup you may restore from: JSON, taken on a schedule, with dated copies kept.
• Migration to another CMS: JSON plus the media files, then test a small sample in the target system.
• Client handover: both. CSV so the client can read it, JSON so the next developer can use it. See the handover checklist.

Reimporting a CSV into Framer is possible with Framer's CSV import, but flattened fields will not come back the way they were. Review the column mapping and test a few items in a duplicate collection first.

The real risk: the export you did not take

A manual export only protects content up to the moment it was taken. If an item is deleted or overwritten on Thursday and the last export was three weeks ago, the newer edits are gone. Before bulk edits, imports or handing editor access to someone new, take a fresh export. For anything that changes often, schedule it. See Framer CMS backup options for the trade-offs.