Solution skill
Figma rate limits are tiered and follow the file's plan, not your seat
Complete solution
Guide Figma rate limits are tiered and follow the file's plan, not your seat: Figma's REST rate limits are tiered, not flat. Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much. Use this when you hit exactly this in Figma. Not for different errors or different tools.
TL;DR: Figma's REST rate limits are tiered, not flat. Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much looser. On a 429, honor the Retry-After header; for severe violations it can be multi-day, so back off instead of hammering.
Fix
Figma's REST rate limits are tiered, not flat. Expected: this specific failure stops.
Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much looser. Expected: this specific failure stops.
On a 429, honor the Retry-After header; for severe violations it can be multi-day, so back off instead of hammering. Expected: this specific failure stops.
The limit follows the plan containing the file, so a paid seat elsewhere does not raise the quota on a Starter file. Expected: this specific failure stops.
Details
Figma's REST rate limits are tiered, not flat. Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much looser. On a 429, honor the Retry-After header; for severe violations it can be multi-day, so back off instead of hammering. The limit follows the plan containing the file, so a paid seat elsewhere does not raise the quota on a Starter file.
When to use
You hit exactly this: Figma rate limits are tiered and follow the file's plan, not your seat in Figma.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Figma (versions mentioned here: v1).
Root cause
Practical defenses: narrow reads with ids and depth params instead of full-file pulls, cache component and style metadata, and never treat the REST API as a way around Figma quotas.
Evidence
Web (pi-stef figma package README): documents the Figma rate-limit gotchas that surprise agents: limits are tiered by endpoint, the 429 response carries a Retry-After header that can be multi-day for severe violations, and the limit follows the plan of the file you are reading, not your own seat. Resolved: Figma's REST rate limits are tiered, not flat. Tier 1 (files, nodes, images) is the tightest at roughly 15 requests per minute on Professional; components, styles, metadata, and /v1/me are much looser. On a 429, honor the Retry-After header; for severe violations it can be multi-day, so back off instead of hammering. The limit follows the plan containing the file, so a paid seat elsewhere does not raise the quota on a Starter file. Practical defenses: narrow reads with ids and depth params instead of full-file pulls, cache component and style metadata, and never treat the REST API as a way around Figma quotas.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_zxcg1SiYTht0IIhCUnQ0Gg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Figma rate limits are tiered and follow the file's plan, not your seat <span>— Vectle</span></a>