Framer · Rate Limits

Framer Rate Limits

Framer's developer surface is in-editor (Plugin API, Code Components, Code Overrides, Fetch), so there is no public REST API with documented per-second rate ceilings. The user-facing constraints are plan-level quotas (CMS collections, pages, bandwidth) and add-on per-editor limits.

4 Limits Throttle: 429
ProductivityDesignNo-CodeWeb DesignSaaSRate LimitingQuotasThrottling

Limits

CMS Collections (Plan-Level) site
collection
tier-dependent
Free 10, Basic 1, Pro 10, Scale 20, Enterprise custom.
Pages (Plan-Level) site
page
tier-dependent
Free 1000, Basic 30, Pro 150, Scale 300, Enterprise custom.
Bandwidth (Plan-Level) site
gigabyte ยท monthly
tier-dependent
Basic 10 GB, Pro 100 GB, Scale 200 GB, Enterprise custom.
Plugin Sandbox editor
api_call
not published
Plugin API runs sandboxed inside the Framer editor; not a remote rate ceiling.

Policies

Backoff in Fetch
Endpoints exposed via Framer Fetch should implement their own rate-limiting and return Retry-After when needed.
Cache Plugin Calls
Plugins should cache results client-side rather than re-querying CMS data on every render.

Sources