Figma‘s 2026 release wave is dense, and the pricing page now reads like a credit ledger. If you’re a product designer deciding what to adopt this quarter, the useful question about the Figma 2026 release isn’t “what shipped” — it’s which of it lands in a file you’re already working in.
Here’s the short version: two changes touch your actual canvas today, one is a beta you can request, and the rest is infrastructure you can safely ignore until a project asks for it.
What actually lands in your file
The most consequential item is the Figma node, announced September 17. You copy a frame from Figma Design, paste it into Figma Weave, and it becomes a node in that workflow. You then pick which text and image layers act as inputs, while fonts, layout and styling stay locked.
That’s a real change to how a design system gets reused. Instead of rebuilding a campaign layout from scratch, you point a Weave workflow at the frame you already maintain and generate variations from it. Figma’s notes say changes made to the original design sync back into Weave, so the frame stays the source of truth.
The second is quieter but more immediately useful: opacity can now be set at scale through variables, applied on top of any colour without detaching it from your library. Figma’s notes describe aliasing opacity while the colour stays linked, setting opacity via a number variable, and scoping those variables for colour use. If you’ve ever hand-adjusted disabled states and overlays across forty components, that’s the one to test first.
Weave tools, and the catch in publishing them
Since September 16 you can build a Weave tool and publish it to the Figma Community, where anyone can run it directly in Figma Design. Figma’s release notes are explicit about the limit: publishing supports any output type, including video generation and 3D renderings, but only image and vector generation tools are usable inside Figma Design.
So a video tool you publish is discoverable but not runnable on the canvas. Worth knowing before you spend a week building one for your team.
The AI credit maths nobody puts on one line
Figma’s pricing page now lists AI credits per plan, and the numbers differ enough to matter when you’re budgeting. Checked September 2026, the page lists 150 AI credits per day up to 500 per month on the entry tier, then 3,000, 3,500 and 4,250 credits per month as you move up the paid plans.
Two details in that fine print are easy to miss. Extra AI credits can be bought for a whole team to share, with pay-as-you-go or a subscription. And on a paid plan, others can view and comment on your files without buying seats.
That second one changes how a small studio quotes a project. You can hand a client comment access without adding a licence line to the estimate.
| What you’re weighing | What Figma lists | Who it suits | The catch |
|---|---|---|---|
| Solo or small-team file work | Entry paid tier, 150 AI credits/day up to 500/mo | Freelancers and two-person teams | Credit ceiling arrives fast if you lean on generation |
| One team, unlimited files | Mid tier, 3,000 AI credits/mo | Product teams with a shared library | Advanced prototyping and dev handoff are the selling points, not the credits |
| Cross-department libraries | Org tier, 3,500 AI credits/mo | Agencies centralising assets | Admin and compliance tooling is the real cost driver |
| Multiple brands or products | Top tier, 4,250 AI credits/mo | Enterprises with several design systems | Scalable systems and admin management, priced accordingly |
Motion is beta, and beta means beta
Figma Motion is listed as beta and available on Full seats. That’s the whole of what the pricing page commits to. If you’re on a lower seat type, don’t plan a motion deliverable around it yet — check your seat before you promise anything to a stakeholder.
Figma also notes that at Config it launched the ability to build custom generative plugins and shaders. That’s a platform story more than a daily-workflow one unless you’re already writing plugins.
What to do this week
If you maintain a component library, test the opacity variable change on one real component set — a disabled button state is the fastest honest test. If your team produces campaign or localisation variants, try one Figma node workflow with a frame you already own, and check whether the sync-back behaves the way the notes describe on your file structure.
Leave Motion alone until your seat qualifies and you have a project that needs it. Leave Community publishing alone until you have a repeatable image or vector generation you’d actually run twice.
And if you’re comparing this against the rest of your stack, it’s worth reading our Figma directory entry alongside the alternatives before you commit a team to a credit tier — the AI credit ceiling, not the seat price, is the line that surprises people.
Sources
- Figma release notes — Weave node, Community publishing, opacity variables, generative plugins and shaders.
- Figma What’s New — same September 2026 entries, used to confirm dates.
- Figma pricing — AI credit allowances per plan, Motion beta on Full seats, shared credit purchasing, comment access on paid plans.
122 ready-to-use AI prompts — organised by discipline and category, each copyable in one click, free and no sign-up needed. Browse the prompt library →