Three weeks ago, Dylan Field walked on stage at Moscone Center and told the design world that "code is not the opposite of design. Code is material for design." Six product launches. The biggest expansion in Figma's 14-year history. Every design account on X and LinkedIn had a take within 48 hours.

‍

That's not the useful take. The useful take is the one you can only give with three weeks of actual usage: which of those six announcements is landing, which is still vaporware, and where the honest criticism is starting to build up.

‍

Our team's been testing the new features since Config wrapped. Here's the read.

‍

🧭 Trying to figure out what to actually adopt from Config 2026? Let's talk →

‍

What's Actually Landing

‍

Two of the six launches have already earned their place. The rest are more complicated.

‍

Figma Motion Is the Real Winner

‍

Motion has been in open beta on all plans since June 24, and the reviews are catching up to the hype. The most cited take: 8 out of 10, closes a real gap, canvas-native workflow is excellent. That matches what we're seeing internally.

‍

For product motion, page transitions, micro-interactions, component states, this genuinely replaces After Effects. Because animations reference the same components and variables as the rest of your file, motion travels with the design system instead of drifting out of sync in a separate app. Update a component, the animation updates with it. That was never possible in the old handoff.

‍

The export story matters too. CSS, JSON, React, MP4, WebM, animated SVG, GIF. And critically, Motion is MCP-compatible, so animated frames can be piped directly to Claude Code, Cursor, or any other MCP-connected coding agent. Structured animation context instead of a flat screenshot.

‍

The honest limit: this isn't going to replace After Effects for high-end motion graphics work. If your team ships broadcast-quality animation, that stays. If your team was stitching together After Effects, Principle, Jitter, or Rive to handle basic UI motion, you can consolidate to Figma now.

‍

Weave Tools Are Producing Real Client Work

‍

The Weavy acquisition became Figma Weave, and it's already showing up in real production. The most-cited example: Taxi Studio generated 3D beer renders for a Carlsberg presentation in one day. That work would have taken weeks with a dedicated 3D specialist. That's not a Figma marketing case study, it's a real agency talking about a real deliverable.

‍

For teams doing brand and marketing work inside Figma, this is a meaningful shift. Style transfer, image generation, video, all in the same file where the rest of the design work happens.

‍

‍

What's Still Theoretical

‍

Two of the six launches got most of the press. Neither is actually usable by most teams yet.

‍

Code Layers Is Still in Closed Beta

‍

The headline of Config 2026 was Code Layers. Three weeks later, most teams still don't have access. It's in closed beta with a waitlist, and general rollout doesn't start until July 2026, so we're on day one of that. Every recap treating Code Layers as a done deal is speculating.

‍

The concept is right. Cloning a GitHub repo onto the Figma canvas, converting design layers to code-backed layers, syncing changes back to the codebase, all in a multiplayer file. If it works at production quality, it eliminates the handoff phase. Big if.

‍

The real test is code quality. Generating code from design is only useful if the output is maintainable in six months. We won't have a verdict on that until teams outside the beta start shipping real features with it. Anyone claiming otherwise right now is guessing.

‍

Shaders and Generative Plugins Are Niche for Now

‍

WebGPU shaders and generative plugins both launched to genuine enthusiasm at Config. Three weeks in, the enthusiasm is real but the actual use cases are narrower than the demos suggested.

‍

Shaders are impressive when a designer knows what to prompt for. They're powerful, but the reality is most product teams don't have "custom shader effect" on their sprint roadmap. This is going to be big for the top 5% of visual designers pushing the edges. For everyone else, it's a capability you'll grow into.

‍

Generative plugins are the same story with different framing. Prompt the agent to build a plugin that sorts layers, enforces spacing, or does find-and-replace across a multi-page file, and it works. Whether your team actually needs custom plugins built on demand is a different question.

‍

The Criticism That's Building

‍

Three weeks in, a real critique is emerging from experienced Figma users, and it's worth taking seriously.

‍

Figma just shipped six flashy features. The list of long-requested basics that didn't ship is also six items long: percentage values, better grid controls, variable math, and several others that designers have been asking for since 2022. The comparison being made in design communities right now is unfavorable, some are pointing to Webflow's pattern of shipping ambitious side projects while core product debt piles up.

‍

We think the criticism has a point. Motion and Weave are legitimately useful. But Figma is now competing with Cursor (just acquired by SpaceX for $60 billion), Framer 3.0 (which made the same canvas-plus-code bet within weeks of Config), and the entire AI coding stack. Winning that competition requires more than headline features. It requires the boring foundational work too.

‍

The AI Credit Pricing Question No One's Answering

‍

Every AI feature launched at Config is currently free in open beta. That won't last. The stated plan is for AI credit consumption to kick in at general availability. Given the industry pattern, Framer, Webflow, and others already do this, we know what's coming: metered credits, tiers, and heavy usage getting expensive.

‍

The community reaction is already clear. Users are asking to bring their own Claude or OpenAI keys rather than pay for platform-specific credits. Figma hasn't said whether that'll be an option. That answer matters more than most of the Config announcements. If AI credits get expensive fast, teams will use these features less, and the whole thesis of Figma-as-unified-platform gets weaker.

‍

The Bigger Signal Worth Watching

‍

Framer 3.0 made the same canvas-plus-code bet within weeks of Figma Config. Two of the biggest design tools independently arrived at the same conclusion at the same time: the future of design tooling is a visual canvas with code underneath and an AI agent in the middle.

‍

That's a stronger signal than any individual Figma launch. It means the shift is real, it means Cursor's position (now inside SpaceX) is under structural pressure from a direction the code-editor incumbents didn't see coming, and it means product teams that keep treating design and code as separate disciplines are going to look increasingly outdated.

‍

What Your Team Should Actually Do Now

‍

The playbook after three weeks:

‍

Adopt Figma Motion this week. It's ready, it's on all plans, and it replaces real tools in your current stack. Cancel Principle or Jitter if that's what you're using for UI motion.

‍

Join the Code Layers waitlist, but don't restructure around it. Get access when you can, pilot it on one non-critical project, measure the code quality yourself. Don't rebuild your engineering workflow around a feature you haven't touched.

‍

Test Weave tools on a real brand or marketing deliverable. This is the underrated launch. If you're doing image generation or 3D asset work externally, try running it through Figma first.

‍

Don't over-invest in shaders or generative plugins yet. Interesting capabilities. Not sprint-critical for most teams.

‍

Watch the pricing question. If Figma's AI credit model turns aggressive at GA, your total cost of ownership on the platform is going to matter. Budget for it now.

‍

Get your design system honest. Everything Figma launched works better on top of a strong system. Weak systems just produce inconsistent output faster. This is where most of our client work sits right now: making sure the foundation can hold what's getting built on top of it.

‍

Key Takeaways

‍

• Figma Motion is the clear winner of Config 2026. Available on all plans, MCP-compatible, and genuinely replaces After Effects for most product motion work.
• Code Layers is still in closed beta with general rollout starting July 2026. Most teams don't have it. Speculating about production quality is premature.
• Weave tools are already producing real client work. Taxi Studio shipped a full 3D Carlsberg presentation in a day.
• Shaders and generative plugins are niche launches. Powerful, but not sprint-critical for most product teams.
• Real criticism is building: Figma shipped flashy features while long-requested basics (percentage values, grid controls, variable math) still don't ship.
• AI credit pricing at general availability is the unanswered question that matters most.
• Framer 3.0 made the same canvas-plus-code bet within weeks of Config. This is an industry shift, not a Figma story.
• Teams with strong design systems will absorb these changes fastest. Teams without them will feel the seams.

‍

Ready to figure out what your design stack should look like after Config?

‍Contact us today 🚀

‍

‍

FAQs

‍

Is Figma Motion actually good?

‍Yes, for most product motion work. It's canvas-native, MCP-compatible, exports to CSS/JSON/React/MP4/WebM/animated SVG/GIF, and animations reference the same components and variables as the rest of your file. It's not going to replace After Effects for broadcast-quality motion graphics, but for UI motion inside a product, it's the biggest workflow improvement in Figma's recent history.

‍

Do I have Code Layers yet?

‍Probably not. Code Layers launched in closed beta at Config on June 24, 2026, with general rollout starting July 2026. Even that rollout is gradual. If you didn't join the waitlist at figma.com/config-betas, you're likely still waiting. Anyone claiming to have a definitive take on Code Layers three weeks after Config is speculating on limited access.

‍

Should I cancel my After Effects subscription?

‍For product motion, likely yes. Figma Motion covers keyframes, easing, timing, and code export in the same file as your design system. For high-end animation work, motion graphics, illustration, VFX, After Effects still wins. Audit your actual After Effects use before canceling.

‍

What are people criticizing about Config 2026?

‍Experienced Figma users are frustrated that six new flashy features shipped while long-requested basics like percentage values, better grid controls, and variable math remain missing. The comparison being drawn is to Webflow's pattern of ambitious side projects while core product debt piles up. It's a fair critique.

‍

What about AI credit pricing?

‍Currently, Config 2026 features don't consume AI credits during the open beta. That changes at general availability, when standard AI credit usage applies. Users are already asking to bring their own Claude or OpenAI keys rather than pay platform-specific credits. Figma hasn't said whether that'll be an option. Watch this space.

‍

Is Figma really competing with Cursor now?

‍The Code Layers launch is a direct challenge to code editors like Cursor, especially for the exploration and prototyping phases. Cursor was acquired by SpaceX for $60 billion eight days before Config, so the competitive landscape is shifting on both sides. For production code, Cursor and Claude Code still win. For "designers and engineers exploring an interface together," Figma Code Layers is making a real bid.

‍

How does Framer 3.0 fit into this?

‍Framer 3.0 launched within weeks of Config 2026 with a similar canvas-plus-code bet. Two of the biggest design tools independently arriving at the same conclusion at the same time is a stronger industry signal than any individual launch. The future of design tooling is a visual canvas with code underneath and an AI agent in the middle.

‍

What should agencies do about Config 2026?

‍Adopt Motion and Weave this quarter. Join the Code Layers waitlist. Get your design system in shape, everything Figma launched works better on a strong foundation. And rethink the design-to-engineering handoff, because it's going to compress further no matter which tool you land on.

‍

Are the Weave tools worth using?

‍For teams doing brand, marketing, or asset work inside Figma, yes. Taxi Studio produced 3D Carlsberg renders in a day that would have taken weeks with a dedicated 3D specialist. Weave tools are free during open beta and consume AI credits at GA.

‍

Is the Figma agent finally useful?

‍The Skills + Connectors + team-visible chats architecture is a meaningful improvement over previous Figma AI features. The most useful part is the team-visible chats, AI context builds up across the team instead of resetting per designer. As with any agent, the value depends on how well you design the Skills and Connectors to ground it in your actual work.

‍

Can Orizon help our team adapt to the post-Config workflow?

‍That's the conversation we're having with clients every week right now. Teams built around the old design-to-code handoff need to rethink their tools, their workflow, and their design system to actually take advantage of what shipped. If that's where you are, book a call and let's talk.