What Scratch edits in Framer
- Rich-text (formatted-text) fields — HTML structure preserved
- Plain-text fields, including titles
- Slugs and the draft flag
- Date, number, boolean, link, color, and option fields
- Image, file, and reference fields
How it works
Scratch pulls a Framer CMS collection into local files, one file per item. Your AI rewrites the prose in your plain-text and rich-text fields. Rich text round-trips as HTML, so links and formatting survive the edit. Item IDs, localized slug variants, and the field structure itself stay locked, and layout-only elements like dividers are left out. Each collection carries its own field set, so the editable columns match what you actually built. Validators check length and required fields. You review every change in Scratch and approve what looks right. Framer gets the edits back through its Server API.
Scratch edits the items inside your collections, not the collections themselves. Connect with a Framer site API key and your project URL — one connection per site.