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 significant update to its platform. As reported by TechCrunch, the innovations are structured along three main axes. First: the introduction of a code layer native. Second: support for motion and shaders directly in the editor. Third: the ability to generate custom plugin via AI.

Therefore, these are not cosmetic or marginal updates. On the contrary, these functionalities address critical nodes in the workflow between design and development. Furthermore, they arrive at a time when many Italian companies are rethinking their digital production processes.

Il code layer: less friction between designers and developers

The code layer is likely the most anticipated new feature for teams working in environments design-to-development. Essentially, it allows designers to annotate and structure technical specifications directly within the Figma file. As a result, developers no longer have to visually interpret the layout to extract CSS properties or style tokens.

In fact, one of the most common bottlenecks in digital teams is precisely the handoff: the moment design is handed over to the developer. However, with the integrated code layer, this phase becomes smoother. Each component carries the necessary technical information, eliminating the need for separate documentation.

For digital managers of SMEs and mid-market companies, this translates to shorter development times and in a reduction of implementation errors. It also facilitates the adoption of scalable design systems, such as design system structured.

Motion and native shaders: animations without external tools

Support for motion and shaders represents an important step towards designer autonomy. Until today, those who wanted to integrate animations into prototypes had to rely on third-party plugins or separate tools like After Effects, Lottie, or Rive. However, this fragmented the workflow and increased production times.

With the June 2026 update, Figma integrates these capabilities directly into the editor. Therefore, you can design micro-interactions and interface animations without leaving your main workspace. In particular, teams that produce landing pages, mobile apps, and interactive web interfaces benefit from a more compact process.

Analogously, shader support opens interesting scenarios for those working on visually rich interfaces. For example, dynamic background effects or advanced transitions become prototypeable directly in Figma. Thus, the distance between the prototype and the final product is further reduced.

From a strategic point of view, this evolution is consistent with what Gartner had indicated as a trend: the convergence of design tools toward integrated production environments.

AI for custom plugins: tailored team automation

The third new feature is perhaps the one with the broadest implications in the medium term. Figma introduces the ability to create custom plugins with AI. In practice, a designer or product manager can describe a desired feature in natural language, and the AI generates the corresponding plugin.

So, you no longer need development skills to extend Figma's functionality. This significantly lowers the barrier to automating creative processes. Additionally, it allows every team to build tools tailored to their specific workflow.

For example, a team that manages visual campaigns for LinkedIn Could you create a plugin that automatically resizes asset formats according to platform specifications? Likewise, those who produce content for Google Ads it could automate the generation of creative variations.

According to Harvard Business Review, automating repetitive tasks in creative workflows is one of the most effective levers for increasing the productivity of digital teams. Therefore, this Figma feature fits into an established trend.

Immediate impact on Italian creative teams

For marketing managers and digital leaders in Italian companies, this update has concrete implications. First of all, those who use Figma as a central tool in their web development process A measurable efficiency gain can be expected. Furthermore, those considering adopting Figma now have stronger arguments in favor of the choice.

However, it is important to distinguish between immediately operational features and those requiring an adoption period. The code layer, for example, requires the design team to adopt new annotation conventions. Consequently, an internal onboarding phase must be planned before fully benefiting from it.

We of SHM Studio We work daily with teams that manage the production of digital interfaces, from the concept phase to release. Therefore, we understand how these updates can impact the quality and speed of projects. In particular, reducing friction in the handoff is a topic that regularly emerges in the process analyses we conduct for our clients.

What the numbers don't say yet

It's too early to have consolidated data on the adoption of these features. However, some structural considerations are already possible. The design tool market is in a phase of accelerated consolidation. Figma, after the failed acquisition attempt by Adobe in 2023, has accelerated its independent development. Therefore, this update should also be seen as a signal of competitive positioning.

Furthermore, the direction Figma is moving in — integrating AI, code, and animations into a single environment — is consistent with the vision of a Design tool as a production platform, not just prototyping. This changes the skill profile required of designers. Subsequently, a hybrid figure is likely to emerge, capable of working on both the visual and technical levels.

For companies investing in AI solutions For their digital processes, this evolution of Figma is a signal not to be ignored. Likewise, those managing distributed teams or working with external agencies will find the code layer a useful standardization element.

What to do now: three priorities for digital leaders

In light of this update, it is useful to identify some operational priorities. First of all, it is advisable to check the version of Figma being used within your team and ensure that the new features are accessible. Additionally, it is worth planning an internal training session dedicated to the code layer.

Secondly, it is appropriate to map out current workflows and identify where native animation support could eliminate redundant steps. For example, if the team uses separate tools for animated prototyping, now is the time to consider migrating to a more integrated workflow.

Finally, the AI functionality for plugins is worth targeted experimentation. Therefore, it's useful to identify two or three repetitive tasks in the creative workflow and test the generation of dedicated plugins. This way, you become familiar with the tool before adopting it on a larger scale.

To delve deeper into optimizing digital production processes, you can consult the resources from SHM Studio on the blog to explore our digital marketing services. For those who desire direct interaction, please contact us through the Contact Us.

Perspectives: Towards Design Tools as Unified Production Environments

In the short term, Figma's update solidifies its position as the go-to tool for teams working on digital interfaces. However, the real transformation is structural. In fact, the convergence of design, code, and AI in a single environment redefines the boundary between the designer's and the developer's work.

For 2027-2028, it is reasonable to expect further integration between Figma and major front-end development frameworks. Consequently, those who invest today in adopting these tools are building a competitive advantage that will be increasingly difficult for laggards to recover.

Who manages the online presence of a company, or is responsible for digital content production, has every reason to follow this evolution closely. Therefore, updating one's own skills and those of the team is no longer a discretionary investment but an operational necessity.