Figma AI Review: What It Does, Pricing, and Alternatives

Draft v0.1 — 2026-05-26 KST. content_status = qa_passed. Generated from templates/tool-page-template.md. Promoted to qa_passed after a 2026-05-26 page-body read of figma.com/ai/ and figma.com/pricing/; Section A of qa/adsense-seo-quality-gate.md satisfied. Meta description (≤ 155 chars): Figma AI is a set of AI features inside Figma for design teams — prototyping, image and content generation, and design-to-code — here is what it does and what it costs.

Quick verdict

• Best for: product and design teams that already work in Figma and want AI features inside the same canvas — generating layouts and prototypes from prompts, producing or editing images and copy in place, cleaning up layers, and feeding design context into coding agents — rather than adopting a separate AI design tool.
• Not ideal for: individuals or teams who do not use Figma as their primary design surface, or who need a standalone marketing-image or document generator. Figma AI is delivered as features inside Figma and FigJam, not as a separate product you can buy on its own.
• Pricing model: freemium. Figma AI features are metered with "AI credits," and an allocation is bundled into every plan listed on figma.com/pricing/ on 2026-05-26 — including the free Starter plan. Additional credits can be purchased as a pay-as-you-go or subscription add-on. Verify the current allocations on the official pricing page before relying on them.
• Free plan: yes. The Starter plan on figma.com/pricing/ on 2026-05-26 was free and listed "150 AI credits/day, up to 500 AI credits/mo." Paid plans list larger monthly allocations. Figma states that "Included AI credits are subject to change," so reconfirm on the official site.
• Last verified: 2026-05-26 (figma.com/ai/ and figma.com/pricing/ page-body reads)

Source-freshness note (2026-06-26)

If you are deciding whether Figma AI fits as an in-canvas design, prototyping, source-provenance, and design-to-code handoff workflow rather than a standalone generator, a 2026-06-26 KST recheck confirms Figma's own first-party surfaces for verifying that yourself are reachable — both the AI feature page and the pricing page returned HTTP 200, with the AI page title and the pricing page title/heading unchanged from prior rechecks.

• Evaluate it as a canvas-native workflow. Figma AI lives inside the file a team already designs in — in-canvas ideation, prototype generation, and asset production sit alongside existing work rather than in a separate app, with design-to-code handoff feeding a developer or coding agent at the end. Judge it by how your team actually moves from idea to prototype to code, not by a headline feature list.
• Review designs, prototypes, generated assets, and their provenance. Generated layouts, images, copy, and prototype code can be wrong, off-brand, or built on assets whose licensing and training-data provenance you should check before reuse. Treat generated work as a draft and verify the source and rights of any asset before it ships.
• Keep a human approval and handoff-review step before shipping. Designs, generated code, and prototypes still need a person to review and approve them before handoff or release; adopting AI features does not remove the design- and code-review loop.
• Verify current plans and limits at the source. Plans, AI-credit allocations, and feature gating change frequently — confirm the current details on Figma's official pricing page before relying on them, rather than inferring them from this page.

Source-backed freshness note: a 2026-06-26 KST reachability/title recheck of Figma's own pages — https://www.figma.com/ai/ (HTTP 200, title "Figma AI: Your Creativity, unblocked with Figma AI", unchanged from prior rechecks; the on-page H1 wording observed this pass differed from earlier rechecks, so it is treated as observed-this-pass only and current positioning is routed to the official site) and https://www.figma.com/pricing/ (HTTP 200, title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats", unchanged). No benchmark, ranking, price, plan, credit, quota, model-availability, speed, accuracy, or superiority claim is made here; volatile specifics are routed to the official site, and vendor positioning is reported as vendor evidence only.

Source-freshness note (2026-06-20)

If you are deciding whether Figma AI fits as an in-canvas design, prototyping, and design-to-code workflow rather than a standalone generator, a 2026-06-20 KST recheck confirms Figma's own first-party surfaces for verifying that yourself are reachable and stable — both the AI feature page and the pricing page returned HTTP 200 with unchanged titles and headings.

• Evaluate it as a canvas-native workflow. Figma AI lives inside the file a team already designs in — in-canvas ideation, prototype generation, and asset production sit alongside existing work rather than in a separate app, with design-to-code handoff feeding a developer or coding agent at the end. Judge it by how your team actually moves from idea to prototype to code, not by a headline feature list.
• Review generated assets and their provenance. Generated layouts, images, and copy can be wrong, off-brand, or built on assets whose licensing and training-data provenance you should check before reuse. Treat generated work as a draft and verify the source and rights of any asset before it ships.
• Keep a human approval step before shipping. Designs, generated code, and prototypes still need a person to review and approve them before handoff or release; adopting AI features does not remove the design- and code-review loop.
• Verify current plans and limits at the source. Plans, AI-credit allocations, and feature gating change frequently — confirm the current details on Figma's official pricing page before relying on them, rather than inferring them from this page.

Source-backed freshness note: a 2026-06-20 KST reachability/title recheck of Figma's own pages — https://www.figma.com/ai/ (HTTP 200, title "Figma AI: Your Creativity, unblocked with Figma AI", h1 "Figma AI is your creative collaborator") and https://www.figma.com/pricing/ (HTTP 200, title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats"). No benchmark, ranking, price, plan, credit, quota, model-availability, speed, or superiority claim is made here; volatile specifics are routed to the official site, and vendor positioning is reported as vendor evidence only.

Source-freshness note (2026-06-14)

If you are weighing Figma AI as an in-canvas design and design-to-code workflow rather than a standalone generator, note that Figma maintains its first-party AI feature and pricing surfaces on its official domain — both rechecked and reachable on 2026-06-14 KST.

• Workflow fit. Figma AI is positioned as a creative collaborator that lives inside the canvas a team already designs in — ideation, prototype generation, and asset production happen alongside existing files rather than in a separate app. Evaluate it against how your team actually moves from idea to prototype, and whether design-to-code handoff into your developer or coding agents is part of that path.
• Review source assets and provenance. Generated layouts, images, and copy can be wrong, off-brand, or built on assets whose licensing and training-data provenance you should check before reuse — treat generated work as a draft and review the source and rights of any asset before it ships.
• Keep a human approval step before shipping. Designs, generated code, and prototypes still need a person to review and approve them before they are handed off or shipped; adopting AI features does not remove the design- and code-review loop.
• Verify current plans and limits on the official pages. Plans, AI-credit allocations, and feature gating for this kind of product change frequently — confirm the current details on Figma's official pricing page before relying on them.

Source-backed freshness note drawn from Figma's own pages (figma.com/ai/ and figma.com/pricing/, both reachable on 2026-06-14 KST). No benchmark, ranking, price, plan, credit, quota, model-availability, speed, or superiority claim is made here; vendor positioning is reported as vendor evidence only.

What is Figma AI?

Figma AI is not a separate product but the collection of AI features built into Figma's design and collaboration tools. On its official feature page at https://www.figma.com/ai/ on 2026-05-26, Figma frames it as "your creative collaborator," with the supporting line: "From prompting prototypes to speeding up workflows, Figma AI helps teams bring their best ideas to life." The framing is squarely about a design team's existing workflow — the AI lives inside the canvas the team already uses rather than asking them to move work into a new app.

The feature page on 2026-05-26 describes several distinct capabilities. Figma Make is positioned around "Prompt to code anything you can imagine," letting users "build ideas into functional prototypes from a prompt." A Canvas Agent is described as "an agent that lives where you work—on the canvas" that can "apply your design system, automate bulk edits, and give you feedback." For imagery, Figma describes generating new images or refining existing ones "with Gemini 3.0 Pro and OpenAI's GPT" — meaning the image features are powered by third-party foundation models named on Figma's own page. Smaller, workflow-level features named on the same page include contextual layer auto-naming ("rename and organize all your layers"), content generation ("generate and replace text content directly in your design mocks"), one-step background removal, and text rewriting and translation to "adjust the length and tone of your copy or translate it directly in your design."

Two capabilities extend beyond the design canvas. FigJam AI brings generate/sort/summarize features into Figma's whiteboard tool, turning "complex ideas into simple diagrams." And the Figma MCP Server brings "Figma design context directly into agentic coding tools like VS Code, Cursor, Windsurf, and Claude" — a bridge between a design file and a developer's coding agent. As with any vendor description of what an AI feature does, treat these as Figma's stated capabilities, not measured guarantees of output quality.

• Vendor: Figma (Figma, Inc.)
• Official AI feature page: https://www.figma.com/ai/
• Category: AI Design

Main use cases

• Use case 1 — Prompt-to-prototype and design generation: Figma Make is described on 2026-05-26 as turning a prompt into a functional prototype, and the Canvas Agent can apply a design system and automate bulk edits. This targets the early, exploratory phase of design work where producing a starting point quickly matters more than pixel-perfect output. Expect to review and refine generated work like any AI output.
• Use case 2 — In-place image and content production: the feature page names image generation and editing (powered by Gemini 3.0 Pro and OpenAI's GPT per Figma), one-step background removal, text generation directly into mockups, and tone/length adjustment plus translation of copy. The common thread is producing or fixing assets without leaving the design file.
• Use case 3 — Whiteboard and ideation support (FigJam AI): generate, sort, and summarize features inside FigJam are aimed at workshops, brainstorming, and turning loose notes into structured diagrams — a different audience (facilitators, cross-functional teams) than the pixel-level design features.
• Use case 4 — Design-to-code handoff via MCP: the Figma MCP Server feeds design context into agentic coding tools (VS Code, Cursor, Windsurf, and Claude are named on the page on 2026-05-26). This is aimed at teams that want a developer's AI coding agent to see the actual design rather than work from a screenshot or a verbal description.

Pricing and plans

The values below were read directly from https://www.figma.com/pricing/ on 2026-05-26 KST. Figma's plans are seat-based, and each plan lists a bundled monthly allocation of "AI credits" that are consumed when AI features are used. Reconfirm with the official pricing page before quoting these numbers more than ~90 days from now, and note Figma's own statement that included AI credits are subject to change.

• Starter — free. Listed with "150 AI credits/day, up to 500 AI credits/mo." This is the entry point for trying Figma AI features at no cost, within the credit cap.
• Professional — listed at $16/mo for a full seat, with a $12/mo dev seat and a $3/mo collab seat, and "3,000 AI credits/mo." Confirm the exact billing cadence (monthly vs annual) on the official page, as seat prices commonly differ between monthly and annual billing.
• Organization — billed annually; listed at $55/mo full seat, $25/mo dev seat, $5/mo collab seat, with "3,500 AI credits/mo."
• Enterprise — billed annually; listed at $90/mo full seat, $35/mo dev seat, $5/mo collab seat, with "4,250 AI credits/mo."
• AI credits add-on — the pricing page describes purchasing additional AI credits "for your whole team to share," with the option to "enable pay-as-you-go for flexibility and/or subscribe to save." The add-on price was not stated in the section read on 2026-05-26 — verify on the official site.

Source: live page-body read of https://www.figma.com/pricing/ on 2026-05-26 KST. Figma states on that page that "AI credits are used to access Figma AI features. Number of credits used varies by request. Included AI credits are subject to change." Exact per-feature credit costs, the add-on price, region-specific pricing, the precise monthly-vs-annual price for the Professional plan, and any plan-specific feature gating beyond the credit allocations were not asserted from this fetch and should be verified on the official site.

When evaluating Figma AI for a team, also verify directly:

• How many AI credits the specific features you care about actually consume, since Figma states credit use "varies by request" and the page does not publish a per-feature cost table.
• The current data-handling and AI-training terms for files processed by Figma AI — this is policy-sensitive and should be read from Figma's official documentation and terms, not inferred from the marketing page.
• Which underlying models power each feature on the plan you intend to buy, given that Figma names Gemini 3.0 Pro and OpenAI's GPT for image features; model choice affects both output and the data-handling story.
• Whether any named feature (Figma Make, Canvas Agent, FigJam AI, MCP Server) is gated to specific paid tiers, since the pricing page primarily differentiates plans by credit allocation rather than feature list.

Pros

• AI features live inside the design tool teams already use, so there is no separate app to adopt or context-switch into — generation, image editing, copy adjustment, and layer cleanup all happen on the existing canvas.
• A genuine free tier exists: the Starter plan on 2026-05-26 bundled a daily and monthly AI-credit allowance, so individuals can try the features without a paid plan.
• The feature set spans the full workflow — ideation (FigJam AI), design and prototyping (Figma Make, Canvas Agent), asset production (image generation, background removal, content generation), and developer handoff (MCP Server) — rather than covering only one step.
• Image features are explicitly powered by named frontier models (Gemini 3.0 Pro and OpenAI's GPT per the 2026-05-26 page), and the MCP Server connects design context into mainstream coding agents (VS Code, Cursor, Windsurf, Claude).

Cons and caveats

• AI-generated designs, images, and copy can be wrong, off-brand, or subtly inappropriate — and AI-generated code or prototypes can contain mishandled edge cases or insecure defaults. Treat all Figma AI output as a draft requiring human review; adopting Figma AI does not remove the need for design and code review.
• Usage is metered by AI credits, and Figma states credit consumption "varies by request" without a published per-feature cost table on the pricing page. Heavy use can exhaust an allocation in ways that are hard to predict in advance, so budget accordingly and watch the add-on pricing.
• Included AI credits are, in Figma's own words, "subject to change," so the allocations quoted here may shift; treat them as a 2026-05-26 snapshot, not a contract.
• Generative image and text tools carry unresolved questions around training-data sourcing, output licensing, and commercial-use rights. This page asserts no legal conclusion; read Figma's official terms and the terms of the underlying model providers before relying on AI-generated assets for commercial work, and consult counsel for license-sensitive use.
• The AI-training status of user design files is policy-sensitive and changes over time; confirm the current setting and opt-out controls in Figma's official documentation rather than assuming a default.
• Outputs are not professional advice. Do not treat Figma AI's generated copy or summaries as a substitute for licensed legal, security, accounting, financial, or medical counsel.

Alternatives and related tools

• Canva AI — the closest direct alternative for AI-assisted visual design and marketing assets. It is tracked in this site's dataset (canva-ai) but does not yet have a finished page here, so there is no internal link to offer; see the AI Design category for where it will live, and verify Canva's current AI features and pricing on the official Canva site.
• Cursor — relevant on the developer-handoff side rather than as a design substitute. Figma's own AI page names Cursor as one of the "agentic coding tools" its MCP Server can feed design context into, so a team turning Figma designs into code may use the two together. Cursor is an AI-first code editor, not a design canvas. (See also the Cursor vs Claude comparison for choosing between coding agents on the receiving end of a Figma handoff.)
• Claude — also named on Figma's AI page as a coding agent the MCP Server connects to; better if your need is general-purpose reasoning, drafting, or working with the design context inside an assistant rather than producing the design itself.
• Native AI in adjacent tools — many design and document tools now ship their own AI features; if your work does not center on Figma, an AI feature inside the tool you already use may avoid adopting Figma specifically for its AI.

Where to compare Figma AI next

Figma AI is an in-canvas design, prototyping, and design-to-code workflow — not a general coding agent or a general-purpose assistant. So the useful "what next" question is rarely "which one wins" but "which tool picks up the job once the design leaves the canvas." These internal paths are organized by workflow fit, not as a ranking:

• AI Design category — start here to see where Figma AI sits among design-first tools, and to browse the category Figma AI belongs to rather than a single head-to-head.
• Cursor — the receiving end of a design-to-code handoff. Figma's own AI page names Cursor as an agentic coding tool its MCP Server can feed design context into, so a team turning Figma designs into code may use the two in sequence. Cursor is a code editor, not a design surface — it is a downstream complement, not a Figma substitute.
• Claude — also named on Figma's AI page as a coding agent the MCP Server connects to; reach for it when the next step is general reasoning, drafting, or working with the design context inside an assistant rather than producing the design itself.
• Cursor vs Claude — the relevant head-to-head once you are choosing which coding agent receives a Figma handoff, not for choosing a design tool.
• AI Coding category — browse the wider field of coding agents and assistants that live downstream of design, for teams whose Figma work ultimately becomes shipped code.

These are decision paths, not rankings — no benchmark, price, credit, speed, or model-availability claim is made here, and none of these tools replaces Figma AI's in-canvas role; they are the workflows that sit beside or after it.

Buyer control and the review boundary

If you are evaluating Figma AI as a buyer rather than an individual trying features, the deciding question is less "what can it generate?" than "which of your design system, files, and handoff outputs can Figma AI touch, and where does the review boundary sit before generated work becomes a shipped design, a shared component, or merged code?" These are the durable control questions to ask. <span id="figma-ai-review-boundary-2026-06-28"></span>

• Own the design system, don't let generation drift it. The Canvas Agent can apply your design system and run bulk edits across a file. Decide up front who owns the system of record for components, tokens, and styles, and treat agent-applied changes as proposals a maintainer reviews — so generation conforms to the system rather than quietly redefining it.
• Review source and provenance before reuse. Generated layouts, images, and copy can be off-brand or built on assets whose licensing and training-data provenance you have not checked. Keep a step where someone verifies the source and rights of any generated or imported asset before it enters a shared library or ships — see Cons and caveats for the open licensing questions.
• Put a review gate on the prototype and code handoff. Figma Make turns prompts into functional prototypes, and the MCP Server feeds design context into coding agents downstream. Generated prototype code and the code an agent writes from a Figma handoff are drafts: name who reviews, tests, and approves them before they merge or ship, not after.
• Keep human approval before shipping, and know where outputs stop being acceptable without it. Adopting AI features does not remove the design- and code-review loop. The closer generated design, copy, or code sits to a public release, a shared component, or production code, the tighter that approval gate should be — generated output is a starting point, never the final sign-off.
• Route tool-vs-tool questions to the right page. When the real question is which tool owns a job once design leaves the canvas, follow the workflow-fit decision paths above — the Cursor and Claude handoff complements, the Cursor vs Claude comparison, or the AI Design category — rather than treating Figma AI as a substitute for a coding agent.

Evergreen decision framing only. No price, plan, AI-credit, quota, model-availability, benchmark, ranking, speed, accuracy, superiority, or legal claim is made here; verify current plan inclusions, data-handling, and feature gating on Figma's official pricing page, and confirm how each Figma AI feature fits your team's review process against your own practice.

Who should not use Figma AI

• Teams that do not use Figma as their primary design surface — Figma AI is delivered inside Figma and FigJam and is not sold as a standalone generator you can adopt on its own.
• Anyone whose core need is large-volume marketing-image generation or document creation outside a design-collaboration context, where a purpose-built generator may be a more direct fit.
• Beginners who would accept generated designs, copy, or code uncritically — AI output here is a starting point, and uncritical use can cement off-brand or buggy results that reviewers will not always catch.

Author selection rubric

Choose Figma AI when at least two of these are true:

• Your team already designs in Figma and you want AI features on the same canvas rather than in a separate tool.
• Your workflow spans ideation, design, asset production, and developer handoff, and you value having AI touch several of those steps in one place.
• You want design context to flow into coding agents (via the MCP Server) instead of being re-described by hand.

Avoid Figma AI when any of these are true:

• Figma is not your primary design tool, so the in-canvas advantage does not apply to you.
• Your dominant need is standalone, high-volume image or document generation rather than design-collaboration features.
• Unpredictable per-request AI-credit consumption is a problem for your budgeting and you cannot tolerate metered usage.

Sources

• Official AI feature page: https://www.figma.com/ai/ — recorded as src-figma-ai-2026-05-21 in data/sources.json with access_status = ok; re-read on 2026-05-26 KST to confirm the positioning line and the named AI features (Figma Make, Canvas Agent, image generation/editing with Gemini 3.0 Pro and OpenAI's GPT, layer auto-naming, content generation, background removal, text rewriting/translation, FigJam AI, and the Figma MCP Server connecting to VS Code, Cursor, Windsurf, and Claude).
• Official pricing page: https://www.figma.com/pricing/ — recorded as src-figma-pricing-2026-05-26 in data/sources.json with access_status = ok after a 2026-05-26 page-body read; this is the source for every plan name, seat price, and AI-credit allocation quoted on this page, and for the "AI credits are used to access Figma AI features… Included AI credits are subject to change" statement.
• Official freshness recheck (2026-06-14): https://www.figma.com/ai/ (title "Figma AI: Your Creativity, unblocked with Figma AI", h1 "Figma AI is your creative collaborator") and https://www.figma.com/pricing/ (title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats") — both returned HTTP 200 on 2026-06-14 KST and are recorded as src-figma-ai-pricing-2026-06-14 in data/sources.json with access_status = ok. This is the source of the "Source-freshness note (2026-06-14)" section and supports only that Figma's official AI feature and pricing surfaces remain reachable with the stated titles/positioning; no price, plan, AI-credit, quota, model-availability, or ranking claim is drawn from it. Vendor evidence only.
• Official freshness recheck (2026-06-20): https://www.figma.com/ai/ (title "Figma AI: Your Creativity, unblocked with Figma AI", h1 "Figma AI is your creative collaborator") and https://www.figma.com/pricing/ (title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats") — both returned HTTP 200 on 2026-06-20 KST with titles/headings unchanged from the 2026-06-14 recheck, and are recorded as src-figma-ai-pricing-2026-06-20 in data/sources.json with access_status = ok. This is the source of the "Source-freshness note (2026-06-20)" section and supports only that Figma's official AI feature and pricing surfaces remain reachable with the stated titles/positioning; no price, plan, AI-credit, quota, model-availability, or ranking claim is drawn from it. Vendor evidence only.
• Official freshness recheck (2026-06-26): https://www.figma.com/ai/ (HTTP 200, title "Figma AI: Your Creativity, unblocked with Figma AI" — unchanged from prior rechecks; the on-page H1 wording observed this pass differed from the "Figma AI is your creative collaborator" H1 captured on earlier rechecks, so it is recorded as observed-this-pass only and current positioning is routed to the official site) and https://www.figma.com/pricing/ (HTTP 200, title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats" — unchanged) — both reachable on 2026-06-26 KST and recorded as src-figma-ai-pricing-2026-06-26 in data/sources.json with access_status = ok. This is the source of the "Source-freshness note (2026-06-26)" section and supports only that Figma's official AI feature and pricing surfaces remain reachable with the stated (unchanged) titles; no price, plan, AI-credit, quota, model-availability, or ranking claim is drawn from it, and the AI-page H1 wording change is not asserted as a claim. Vendor evidence only.
• Vendor: Figma (Figma, Inc.) — https://www.figma.com/

Sources marked needs_verification or blocked in data/sources.json must be re-fetched live before publish. Note the recheck date in the update log.

Internal links (at least 3)

• Category page: /ai-design/
• Related tool: /tools/cursor/
• Related tool: /tools/claude/
• Related comparison page: /compare/cursor-vs-claude/

Disclosure

• Affiliate links: none.
• Sponsored content: none. Figma has no relationship to this page.
• Generative AI assistance: this draft was assembled with the help of an AI assistant working from a 2026-05-26 live read of the official Figma AI feature page and pricing page; every feature, plan, price, and AI-credit claim is constrained to wording visible on those pages on that date.

Trademark notice

Figma, FigJam, and Figma Make are trademarks of Figma, Inc. Gemini is a trademark of Google; GPT and OpenAI are trademarks of OpenAI; Claude is a trademark of Anthropic; Cursor and Anysphere are trademarks of Anysphere; Windsurf, VS Code, and other product names are trademarks of their respective owners. Use here is referential only and does not imply endorsement, partnership, or affiliation.

Update log

• 2026-06-28 (buyer-control / review-boundary qualified-traffic increment — LOCAL content edit only, NOT a new revenue page/product and NOT a deploy): added one compact, evergreen "## Buyer control and the review boundary" section placed after "## Where to compare Figma AI next" and before "## Who should not use Figma AI", carrying durable marker figma-ai-review-boundary-2026-06-28 once as a single <span id="figma-ai-review-boundary-2026-06-28"></span> in the section lead. It frames Figma AI buying around Figma-specific control boundaries — owning the design system as the system of record so Canvas Agent edits stay proposals a maintainer reviews, reviewing source/licensing/training-data provenance before any generated or imported asset enters a shared library, putting a review gate on the Figma Make prototype and the MCP-Server code handoff before anything merges or ships, keeping human approval as the boundary that tightens the closer output sits to release/shared-component/production code, and routing tool-vs-tool questions to the existing /tools/cursor/, /tools/claude/, /compare/cursor-vs-claude/, and /ai-design/ routes already on this page. Existing page/source context only — no web fetch and no data/* edit; no new price/plan/AI-credit/quota/model-availability/ranking/benchmark/speed/accuracy/superiority/legal/security-certification claim; no Gumroad/UTM/affiliate/sponsored/coupon/checkout link or new CTA; data/sources.json, data/tools.json, and last_verified_at unchanged; content_type/content_status stay tool_page/qa_passed. Local-only increment; live verify/build/deploy is handled separately by Hermes.
• 2026-06-26 (source-freshness refresh — vendor evidence, NOT a new revenue page): added a compact "Source-freshness note (2026-06-26)" section above the "Source-freshness note (2026-06-20)" note, framing Figma AI as an in-canvas design, prototyping, source-provenance, and design-to-code handoff workflow — evaluate it as a canvas-native workflow, review designs/prototypes/generated assets and their licensing/training-data provenance, keep a human approval and handoff-review step before shipping, and verify current plans/limits on Figma's official pricing page. Evidence: a 2026-06-26 KST reachability/title recheck where both official surfaces returned HTTP 200 — https://www.figma.com/ai/ (title "Figma AI: Your Creativity, unblocked with Figma AI", unchanged from prior rechecks) and https://www.figma.com/pricing/ (title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats", unchanged). HONESTY NOTE: the AI page H1 text observed on this pass read "Figma AI workflows help teams confidently build the right thing—fast, on-brand, and together", which differs from the "Figma AI is your creative collaborator" H1 captured on the 2026-06-14/2026-06-20 rechecks; this is recorded as observed-this-pass wording only (possible vendor page update or extraction variance), no claim is drawn from it, and current positioning is routed to the official site. Added one source (src-figma-ai-pricing-2026-06-26, source_type = official_homepage, access_status = ok) to data/sources.json and the figma-ai sources_used, and listed it in the page Sources. Vendor evidence only, not an independent ranking. No exact price/plan/credit/quota/model-availability/ranking/benchmark/speed/accuracy/superiority claim was added; the existing 2026-05-26 pricing rows and data/tools.json last_verified_at are unchanged with current specifics routed to "verify on official site"; no Gumroad/UTM/affiliate/sponsored/coupon link added; content_type/content_status stay tool_page/qa_passed. Local-only increment; live verify/build/deploy is handled separately.
• 2026-06-20 (source-freshness refresh — vendor evidence, NOT a new revenue page): added a compact "Source-freshness note (2026-06-20)" section above the older "Source-freshness note (2026-06-14)" note, framing Figma AI as an in-canvas design, prototyping, and design-to-code workflow — evaluate it as a canvas-native workflow, review generated assets and their licensing/training-data provenance, keep a human approval step before shipping, and verify current plans/limits on Figma's official pricing page. Evidence: a 2026-06-20 KST reachability/title recheck where both official surfaces returned HTTP 200 with titles/headings unchanged from 2026-06-14 — https://www.figma.com/ai/ (title "Figma AI: Your Creativity, unblocked with Figma AI", h1 "Figma AI is your creative collaborator") and https://www.figma.com/pricing/ (title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats"). Added one source (src-figma-ai-pricing-2026-06-20, source_type = official_homepage, access_status = ok) to data/sources.json and the figma-ai sources_used, and listed it in the page Sources. Vendor evidence only, not an independent ranking. No exact price/plan/credit/quota/model-availability/ranking/benchmark/speed/superiority claim was added; the existing 2026-05-26 pricing rows and data/tools.json last_verified_at are unchanged with current specifics routed to "verify on official site"; no Gumroad/UTM/affiliate/sponsored/coupon link added; content_type/content_status stay tool_page/qa_passed.
• 2026-06-14 (source-freshness refresh — vendor evidence, NOT a new revenue page): added a compact "Source-freshness note (2026-06-14)" section after "## Quick verdict" (before "## What is Figma AI?") framing Figma AI as an in-canvas design and design-to-code workflow — durable workflow-fit questions around in-canvas ideation/prototype generation, handoff to developer/coding agents, source asset/provenance review, and a human approval step before shipping, plus a reminder to verify current plans/limits on Figma's official pricing page. Evidence: a 2026-06-14 KST reachability/title recheck where both official surfaces returned HTTP 200 — https://www.figma.com/ai/ (title "Figma AI: Your Creativity, unblocked with Figma AI", h1 "Figma AI is your creative collaborator") and https://www.figma.com/pricing/ (title "Plans & Pricing | Figma", h1 "Pick your plan, choose your seats"). Added one source (src-figma-ai-pricing-2026-06-14, source_type = official_homepage, access_status = ok) to data/sources.json and the figma-ai sources_used, and listed it in the page Sources. Vendor evidence only, not an independent ranking. No exact price/plan/credit/quota/model-availability/ranking/benchmark/speed/superiority claim was added; the existing 2026-05-26 pricing rows and data/tools.json last_verified_at are unchanged with current specifics routed to "verify on official site"; no Gumroad/UTM/affiliate/sponsored/coupon link added; content_type/content_status stay tool_page/qa_passed.
• 2026-06-05 (internal-link/traffic refresh — NOT a new revenue page): added a "Where to compare Figma AI next" workflow-fit section (placed after "## Alternatives and related tools", before "## Who should not use Figma AI") linking existing routes only — /ai-design/, /tools/cursor/, /tools/claude/, /compare/cursor-vs-claude/, and /ai-coding/ — framed as decision paths, not a ranking, and honest that Figma AI's in-canvas design/prototyping/design-to-code role is not substituted by general coding agents (Cursor) or general assistants (Claude). All five are existing qa_passed tool/comparison routes (cursor, claude, cursor-vs-claude) or established category routes (ai-design, ai-coding). No web fetch; no Canva or Figma comparison page invented. No price/quota/credit/benchmark/speed/accuracy/model-availability/legal/affiliate/sponsored/coupon/Gumroad/UTM or other volatile claim added or changed; data/sources.json, data/tools.json, and data/comparisons.json unchanged; last_verified_at and content_status (qa_passed) unchanged.
• 2026-05-26 (draft and qa pass): first local draft created from templates/tool-page-template.md. Live page-body reads of https://www.figma.com/ai/ and https://www.figma.com/pricing/ on 2026-05-26 KST (both HTTP 200) provided the "your creative collaborator" positioning and the named AI features, plus the plan/seat prices and per-plan AI-credit allocations (Starter free with 150 credits/day up to 500/mo; Professional $16/$12/$3 seat with 3,000 credits/mo; Organization $55/$25/$5 with 3,500 credits/mo; Enterprise $90/$35/$5 with 4,250 credits/mo) and the AI-credit add-on. New source entry added (src-figma-pricing-2026-05-26, access_status = ok); src-figma-ai-2026-05-21 retrieved_at/claim_supported refreshed after the homepage re-read. data/tools.json figma-ai pricing_model, pricing_summary, has_free_plan, confidence_score, last_verified_at, sources, and content_status refreshed. Section A1/A2 of qa/adsense-seo-quality-gate.md now satisfied; A3 (≥ 700 words), A4 (trust/safety/trademark), A5 (disclosure), and A6 (≥ 3 internal links) all pass. content_status advanced to qa_passed. Page is pricing-sensitive; re-verify by 2026-08-24 (90 days from the 2026-05-26 pricing-page fetch).