What's New in Figma? Latest Features, Updates, and Changes Explained
By Alex Mercer·
Introduction
Figma's latest features fall into four categories: AI tools embedded in the canvas, an expanded variable system that maps to design tokens, a developer handoff layer built around Dev Mode and VS Code, and enterprise controls including Git-style branching. The changes since 2024 are cumulative enough that teams who set up Figma more than a year ago are likely leaving significant workflow efficiency on the table.
Figma ships updates at a pace that makes it genuinely difficult to separate meaningful product changes from minor polish. For developers, founders, and design-adjacent professionals who rely on Figma as the connective tissue between design and engineering, missing a significant update can quietly degrade team velocity or leave powerful capabilities untapped.
This overview distills the latest Figma features and product releases into thematic groups, contextualizes them against the competitive landscape, and offers a clear read on which changes actually warrant action. The variable system alone has fundamentally altered how mature design teams manage tokens at scale, and the AI layer is evolving faster than most teams realize.
What Are Figma's New AI Capabilities and How Do They Work?
Figma's approach to AI has shifted from experimental features to tools that sit directly inside existing workflows. Rather than bolting on a chatbot or a standalone generation panel, the team has embedded AI features into the canvas itself, targeting the repetitive micro-decisions that consume hours of design time each week.
What the AI Layer Actually Does Now
The most impactful additions center on contextual generation and intelligent suggestions. Figma's AI can now propose layout alternatives, auto-populate realistic content, and suggest component swaps based on the design system already loaded in a file. These aren't generic outputs. The suggestions are constrained by your existing variables and styles, which means the AI respects your team's design language rather than inventing a new one.
Smart Populate: Generates contextually appropriate placeholder content (names, addresses, product data) that matches the data shape of connected components
Layout Suggestions: Proposes responsive layout alternatives based on auto-layout rules and frame constraints already defined in the file
Rename Layers: Batch-renames layers using a consistent, semantically meaningful naming convention inferred from the component structure
Component Swap: Recommends component replacements from your library when it detects detached or inconsistent instances
Where Figma AI Falls Short
The generation capabilities are useful but narrow. Complex, multi-screen flows still require manual orchestration, and the AI occasionally misreads intent when components have ambiguous naming. Teams with well-organized libraries and clean variable structures will extract far more value than those with messy files. The practical takeaway: investing time in design system hygiene now compounds the returns from every AI feature Figma ships next.
How Do Figma's Variable System and Developer Handoff Work Now?
If AI gets the headlines, the variable system and developer handoff improvements are where Figma's product releases have the most direct impact on team output. These updates target the gap between what a designer intends and what an engineer actually builds, a gap that has historically cost product teams days per sprint cycle.
The Variable System Grows Up
Figma's variable system now supports scoping, multi-mode configurations, and code-syntax references that map directly to CSS custom properties or platform-specific tokens. This means a single variable collection can drive light mode, dark mode, and high-contrast themes without duplicating components. The guide to variables in Figma is worth revisiting if your team adopted variables early, because the scoping controls introduced in recent updates fix the discoverability problems that plagued the initial rollout.
For teams evaluating how to implement variables across large files, particularly the 78% of product teams in the 2025 Figma Community Survey who reported using variables in production, the key shift is that variables now behave closer to true design tokens. You can alias variables to other variables, creating semantic layers (e.g., "button-primary-bg" referencing "brand-blue-500") that mirror how engineering teams structure their token files. This is a significant step toward a unified design system source of truth that both designers and developers can reference without translation overhead.
Developer Handoff Gets Specific
Figma's Dev Mode has evolved beyond its initial inspect-panel roots. The latest updates introduced code-ready annotations, component documentation surfaces, and framework-specific code snippets that appear alongside visual specs. Engineers no longer need to reverse-engineer spacing values or guess at interaction states. The annotations layer lets designers attach implementation notes directly to frames, and those notes persist through version history.
Perhaps more importantly, Figma now supports VS Code integration that lets developers browse and inspect Figma files without leaving their editor. For US tech teams running tight sprint cycles, this eliminates the context-switching tax of jumping between browser tabs. The handoff workflow still isn't perfect. Complex interactions and conditional logic remain difficult to communicate through static annotations. But the gap between Figma's output and what engineers need to start building has narrowed considerably.
Prototyping, Collaboration, and Enterprise Updates
Figma's prototyping engine and collaboration features received quieter but meaningful updates that affect how teams present work, gather feedback, and manage access at scale. These changes matter most for organizations where Figma isn't just a design tool but an organizational communication layer.
Prototyping Gets Conditional Logic
The prototyping engine now supports basic conditional logic through variables, allowing prototype behavior to change based on user input. A form prototype can show different screens depending on which option a user selects, without requiring dozens of duplicate frames connected by spaghetti wires. This brings Figma closer to tools like ProtoPie in terms of fidelity, though it still can't match dedicated prototyping tools for complex animation sequences.
The practical impact is significant for user testing. Teams can build realistic, branching prototypes that capture more meaningful feedback than linear click-throughs. Combined with the speed improvements to Figma's rendering engine, prototypes now run smoothly even in files with hundreds of components. For teams comparing Figma vs Sketch or evaluating Figma vs Adobe XD, the prototyping gap has essentially closed in Figma's favor. Sketch's prototyping remains rudimentary by comparison, and Adobe XD's development has stalled since Adobe shifted focus to its Figma acquisition.
Enterprise Controls and Branching
On the enterprise side, Figma has introduced branching and merging for design files, a workflow borrowed directly from Git and championed internally by Figma CEO Dylan Field as a core part of the company's enterprise roadmap.
Designers can now create branches of a shared library file, make changes in isolation, and submit those changes for review before they propagate to the rest of the organization. This is a direct response to the pain point that engineering teams have solved with version control for decades, but design teams have historically managed through naming conventions and Slack messages.
The branching system integrates with Figma's existing review and commenting tools, creating a lightweight design governance process. For enterprise solutions in the US and European markets, this addresses a compliance and consistency requirement that has kept some organizations reliant on legacy tools. Figma also expanded its admin controls with SSO enforcement, IP allowlisting, and granular permission tiers that align with SOC 2 requirements. TechBriefed has covered the broader shift toward developer-centric workflows in design tools, and Figma's enterprise push fits squarely within that trend.
Conclusion
Figma's trajectory points clearly toward becoming a full product development environment rather than a standalone design tool. The variable system and design token improvements reduce the translation cost between design and code. AI features eliminate repetitive tasks for teams that maintain clean libraries. Prototyping and developer handoff updates close gaps that previously required third-party tools to bridge. For teams that have not revisited their configuration recently, the accumulated changes since 2024 and through 2026 justify a dedicated sprint to audit your variable structure, enable Dev Mode, and test the platform's AI features against your actual files. TechBriefed continues to track these shifts as they develop, so the investment you make in tooling today compounds as the platform evolves.
Stay current on design tool updates and developer workflow changes by visiting TechBriefed for daily analysis.
Frequently Asked Questions (FAQs)
What are Figma's latest features?
Figma's most recent updates include AI-powered layout suggestions, an expanded variable system with multi-mode support, conditional logic in prototyping, enhanced Dev Mode with VS Code integration, and enterprise branching for design files.
How do I use Figma's new AI features?
Figma's AI features are accessible directly on the canvas and work best when your file uses a well-organized component library and properly scoped variables, as the AI draws from your existing design system to generate contextually relevant suggestions.
How does Figma's developer handoff work?
Figma's Dev Mode surfaces code-ready annotations, framework-specific snippets, spacing values, and component documentation alongside visual specs, and integrates with VS Code so engineers can inspect files without switching to a browser.
Is Figma better than Sketch for US design teams?
For most US-based teams, Figma offers stronger collaboration, more advanced prototyping, and a richer plugin ecosystem than Sketch, which remains macOS-only and has fallen behind in real-time multiplayer editing and developer handoff capabilities.
What is Figma's design token system?
Figma's design token system is built on its variables feature, which allows teams to define aliased, multi-mode tokens (such as color, spacing, and typography values) that map directly to CSS custom properties or platform-specific code references.
Why is Figma adding AI features now?
Figma is integrating AI because the competitive pressure from tools like Adobe Firefly and the broader shift toward AI-assisted design workflows makes it a product survival requirement, not an optional enhancement. The company is embedding AI directly into existing canvas interactions rather than building a separate AI product, betting that contextual automation within a familiar interface will drive adoption faster than standalone AI design tools.
