Journal

Figma adds 3D transforms: what designers should know

Figma's new 3D transforms let you rotate, layer and animate elements in real 3D space, then hand them off as CSS. Here is what shipped and how to use it.

Figma adds 3D transforms: what designers should know

On November 12, Figma started rolling out 3D transforms in open beta. You can now rotate layers on the x, y and z axes, push them forward or back in space, add perspective to a frame and animate the whole thing in Figma Motion. Two days earlier, Figma Motion also picked up physics-based springs and Lottie export previews.

None of this turns Figma into Blender or Spline. What it does is remove a common detour: exporting a card, a phone mockup or a hero element to another tool just to tilt it convincingly. Here is what actually shipped, where the limits are, and how we would start using it on real client work.

What shipped

According to Figma's help article, a 3D transform is a new effect you add from the Effects section of the right sidebar. It works on vectors, images, frames, components and text, and it is non-destructive: the layer stays editable, and text and fills (including shader fills) keep rendering with the transform applied.

  • Rotation: X tilts a layer forward or back, Y tilts it left or right, Z spins it flat on the canvas. You can drag on-canvas handles or type exact values.
  • Depth: moves the layer along the z axis, toward or away from the viewer.
  • Origin point: the pivot the layer rotates around, set by values, by dragging or from presets.
  • Backface: a toggle for whether the back of a rotated layer is visible. When it is, you see a mirrored front.

Figma's launch post describes it as rolling out in open beta, and the help article lists it on all plans for people with a Full seat and edit access to the file.

Perspective and shared 3D space

A rotation on its own looks flat. Depth only reads properly when the parent frame has a Perspective effect. Lower values put the viewer closer and exaggerate the effect; higher values make it subtler.

The second parent-level setting is Keep nested layers 3D. Turn it on and the children share one 3D space, so they can intersect and sort by depth. Figma's own example is a cube built from face layers. There is a trade-off: while it is on, the parent frame loses opacity, blend modes, shaders, other effects and clip content, and its own fills and strokes stop showing. If you need those back, Turn into flat plane flattens the children onto the frame and ends the 3D space at that level.

Treat a 3D parent frame as a stage, not a card. Put the background, shadows and clipping on a wrapper outside it.

Animating it in Figma Motion

In motion mode you can keyframe Rotate X, Rotate Y, Depth and perspective straight from the 3D transform settings. That covers the moves people usually reach for: a card flip, a device turning to face the viewer, a stack of screens fanning out.

The Figma agent can also set this up from a prompt. You describe the arrangement and the motion, then adjust the result on the timeline. A sensible split is to use it to get the structure in place quickly, then do the timing by hand. The easing and pacing are what make a flip feel deliberate.

The Motion update that came with it

On November 10, Figma's release notes added three things to Motion that pair well with 3D work:

  1. Physics-based springs for iOS and Android. You set mass, stiffness and damping, and the duration updates to match. Springs can be saved in a design system and reused.
  2. Style previews. Each animation style plays in the list and on the canvas before you apply it.
  3. Lottie export previews. You can check how an animation will look as a Lottie file before exporting it.

Springs matter for 3D because rotations with a linear or simple ease-out curve tend to feel mechanical. A spring with a little overshoot reads as physical, which is the whole point of adding depth.

Handoff: it maps to CSS

This is the part that makes the feature useful beyond pitch decks. The help article says each setting maps to a CSS property: rotations to transform rotations, Depth to translateZ, Perspective to perspective, Keep nested layers 3D to transform-style: preserve-3d and Turn into flat plane to transform-style: flat. In Dev Mode you select the layer and copy the transform values.

Figma also says a coding agent connected through the Figma MCP server can implement designs with their 3D effects. We would still check the output by hand. The documentation does not go into rotation order, units or how deeply nested 3D contexts translate, and those are exactly where browser output tends to drift from a design file.

Where we would use it first

Some practical starting points for designers and founders:

  • Hero mockups. Tilt a product screenshot inside a frame with perspective instead of buying another mockup template.
  • Card and pricing interactions. Prototype a hover tilt or flip and hand developers the exact CSS values.
  • Launch visuals. Fan out a stack of screens with depth and animate it for a social post or a Lottie file.
  • Onboarding and empty states. A small rotated illustration can add life without a separate 3D tool.

If you build sites in Framer, the CSS mapping is the useful bit: perspective, rotation and preserve-3d are all things you can reproduce there with transforms on a parent and its children, so a Figma prototype becomes a reliable spec rather than a rough idea.

Things to watch

  • It is an open beta, so behaviour and limits may change.
  • Keep nested layers 3D disables several frame properties. Plan your layer structure before you build.
  • Heavy 3D on a marketing page can hurt performance and readability on small screens. Use it for one focal element, not every section.
  • Respect reduced-motion settings when you ship animated rotations.

The short version

3D transforms let you rotate, layer and animate elements in real space inside Figma, and the settings translate directly into CSS your developers already know. Paired with the new springs in Motion, it is enough for most product and marketing depth effects. Try it on one hero or one card interaction this week, check the exported CSS against the browser, and decide from there how far to take it.

Oybek Ruziev

Designer & Framer developer · AidanCreates

Keep reading

All posts