Figma 2026: code layers, animations and AI for custom plugins

What changed in the June 2026 Figma update

On June 24, 2026, Figma announced a major update to its platform. As reported by TechCrunch, the changes revolve around three main areas. First: a native code layer. Second: support for motion and shaders directly in the editor. Third: the ability to generate custom plugins with AI.

These are not cosmetic or minor updates. On the contrary, these features tackle critical points in the workflow between design and development. They also arrive at a time when many Italian companies are rethinking their digital production processes.

The code layer: less friction between designers and developers

The code layer is probably the feature that teams working in design-to-development environments have been waiting for most. In essence, it lets designers annotate and structure technical specs directly inside the Figma file. As a result, developers no longer have to read the layout visually to extract CSS properties or style tokens.

One of the most common bottlenecks in digital teams is the handoff: the moment the design is delivered to the developer. With the built-in code layer, this phase gets smoother. Every component carries the technical information it needs, with no separate documentation required.

For digital leads at SMEs and mid-market companies, this means shorter development times and fewer implementation errors. It also makes it easier to adopt scalable design systems, such as structured design systems.

Native motion and shaders: animations without external tools

Support for motion and shaders is an important step toward designer independence. Until now, anyone who wanted to add animations to prototypes had to rely on third-party plugins or separate tools like After Effects, Lottie or Rive. That fragmented the workflow and increased production time.

With the June 2026 update, Figma brings these capabilities directly into the editor. You can now design micro-interactions and interface animations without leaving your main workspace. Teams that produce landing pages, mobile apps and interactive web interfaces in particular will benefit from a more compact process.

Shader support also opens up interesting possibilities for visually rich interfaces. For example, dynamic background effects or advanced transitions can now be prototyped directly in Figma. The gap between prototype and final product shrinks even further.

From a strategic standpoint, this evolution is consistent with a trend Gartner had pointed out: design tools converging toward integrated production environments.

AI for custom plugins: automation tailored to your team

The third change may have the broadest implications in the medium term. Figma now lets you create custom plugins with AI. In practice, a designer or product manager can describe a desired function in natural language, and the AI generates the matching plugin.

This means you no longer need development skills to extend Figma's functionality. It significantly lowers the barrier to automating creative processes. It also lets every team build tools tailored to its own specific workflow.

For example, a team running visual campaigns for LinkedIn could create a plugin that automatically resizes asset formats to match the platform's specs. Likewise, anyone producing content for Google Ads could automate the generation of creative variants.

According to Harvard Business Review, automating repetitive tasks in creative workflows is one of the most effective ways to boost digital team productivity. This Figma feature fits squarely into an established trend.

Immediate impact on Italian creative teams

For marketing managers and digital leads at Italian companies, this update has concrete implications. First of all, if Figma is central to your web development process, you can expect a measurable efficiency gain. And if you're considering adopting Figma, you now have stronger arguments in its favor.

That said, it's important to distinguish between features you can use right away and those that need an adoption period. The code layer, for example, requires the design team to adopt new annotation conventions. You'll need to plan an internal onboarding phase before you can fully benefit from it.

At SHM Studio, we work every day with teams that manage digital interface production, from concept to release. We understand how much these updates can affect the quality and speed of projects. Reducing friction in the handoff, in particular, is a theme that comes up regularly in the process analyses we run for our clients.

What the numbers don't say yet

It's too early for solid data on how these features are being adopted. Still, some structural observations are already possible. The design tool market is consolidating fast. After Adobe's failed acquisition attempt in 2023, Figma has accelerated its independent development. So this update should also be read as a signal of competitive positioning.

The direction Figma is taking, with AI, code and animation integrated in a single environment, also fits the vision of a design tool as a production platform, not just a prototyping one. This changes the skill profile required of designers. A hybrid role is likely to emerge, able to work on both the visual and the technical side.

For companies investing in AI solutions for their digital processes, this evolution of Figma is a signal not to ignore. And if you manage distributed teams or work with external agencies, you'll find the code layer a useful standardization tool.

What to do now: three priorities for digital leads

In light of this update, it helps to identify a few operational priorities. First, check which version of Figma your team is using and make sure the new features are available. It's also worth planning an internal training session dedicated to the code layer.

Second, map your current workflows and identify where native animation support could eliminate redundant steps. For example, if your team uses separate tools for animated prototyping, now is the time to consider moving to a more integrated flow.

Finally, the AI feature for plugins deserves a focused trial. Start by identifying two or three repetitive tasks in your creative workflow and test generating dedicated plugins for them. That way, you get comfortable with the tool before rolling it out at scale.

To learn more about optimizing your digital production processes, check out the resources on the SHM Studio blog or explore our digital marketing services. If you'd like to talk it through with us directly, get in touch via the contact page.

What's next: the design tool as a unified production environment

In the short term, the Figma update strengthens its position as the go-to tool for teams working on digital interfaces. But the real transformation is structural. The convergence of design, code and AI in a single environment is redrawing the line between the work of designers and that of developers.

Looking ahead to 2027-2028, it's reasonable to expect even deeper integration between Figma and the leading front-end development frameworks. As a result, those who invest in adopting these tools today are building a competitive advantage that will be harder and harder for latecomers to catch up with.

If you manage your company's online presence or are in charge of digital content production, you have every reason to follow this evolution closely. Updating your skills and your team's is no longer a discretionary investment, but an operational necessity.