Laura Fehre, Designer Advocate at Figma, teaches Motion to people who freeze up the moment they open motion software, by letting the Figma agent do the first pass. Prompt the animation, watch it build the keyframes, then refine the curves and springs yourself.
Miggi builds a loading spinner from one ellipse: swap the fill for a stroke with shift+X, sweep the arc tool to 75%, then round the end caps. In Figma Motion, the move is keyframing only the sweep value and deleting the start and ratio keyframes Motion adds by default, so it runs from 0.25 to a full 100%. Duplicate and stagger a few for a nested loader.
Miggi packs two Figma Motion tricks into one tip. Nest your animation inside a frame and the parent becomes a camera you can pan, zoom, and rotate. Separately, J and K jump the playhead to the next and previous visible keyframes.
Until now, screens brought onto the canvas from code landed as raw values, leaving a cleanup pass before anything matched your design system. Figma now auto-binds colors, type, and spacing to the variables already in your file — whether you copy a Make preview, generate from code through the MCP server, or capture a live page with the Chrome extension. More frames also arrive with auto layout enabled, which dovetails with the Flexbox-mapped auto layout update above. Run Check Designs as a second pass to catch anything the matcher missed.
Figma’s AI image editing now runs in parallel. You can kick off multiple edits from the toolbar and keep working while they process, with loading indicators for each. Small change, noticeable difference if you’re doing any volume of AI image work.
A deep dive into the principles that separate intentional motion from decoration: easing and timing, anticipation, overshoot, follow-through, hold, and settle. The piece makes a compelling case for grounding animation in real-world physics and film editing rather than trending motion work, and lands on a point worth keeping: as AI tools make quality motion faster to produce, skill and restraint matter more, not less.
Figma’s microsite for exploring the new Shader Fills feature announced at Config 2026. You can prompt, stack, and customize shader effects directly in the browser, then take what you’ve built back into the canvas. It’s a smart way to onboard people to a feature that could otherwise feel intimidating, and it doubles as a demo that shows off what the feature is actually capable of.
Nikita Prokopov makes the case that great UI isn’t just about nailing the start and end states of an animation, it’s about every frame in between. His rule of thumb: if you freeze the screen at any moment, you should be able to explain what you’re looking at. The post walks through a set of GIF examples — from Safari’s misaligned cursor-and-placeholder animation to YouTube’s inexplicable rectangle transition — showing how mid-animation frames that don’t hold up on their own erode user trust.
Jake Albaugh, Developer Advocate at Figma, walks through setting up Code Connect from scratch — the NPM package, the config file, and mapping design properties to production code properties. The real payoff comes when he shows the before/after through the MCP server: without Code Connect, an agent sees a flood of raw style data; with it, it sees clean, minimal component code it can actually act on. Unfortunately, Code Connect is still not available on the Pro plan.
Rachel from Figma’s Show Your Work series walks through her file and breaks down three categories where slots reshaped her system: repeating elements like menus and tabs (where she keeps nested subcomponents as default content so system-level edits still propagate), free-form areas like sheets and modals (where she often ships zero default content because designers just delete it anyway), and experimental page-level templates that “start to feel a lot more like code.”
Gavin Potenza’s image layout engine for Figma hit v3.0. Select images on canvas, pick one of four layout modes — Grid, Editorial, Masonry, or Cluster — and it composes a moodboard in one click, up to 40 images. The new release adds video support, subject-aware crops that keep faces and focal points in frame, and remixing to re-roll a composition within the same layout family.
Video upload cap goes from 100 MB to 300 MB across Design, FigJam, Slides, Sites, and Buzz on paid plans.
The Community profile redesign adds role, experience, tech stack, pinned work with images and links, and social channels. Combined with the FigPal customization, it reads less like a profile page and more like a creator landing page. Figma clearly wants Community to function as a discovery layer for designers, not just for resources.
Slots in Figma Design just got a set of guardrails: min/max layer counts, instance restrictions to limit what can go inside a slot, an empty-slot default so slots stay visible on canvas, and auto-fill behavior. Slots are now generally available, and these controls make them genuinely safe to use at scale.
A few updates to Grids – reorder columns and rows by dragging, automatic positioning, and automatic rows – the last one is my favorite!
Lauren Budorick, a software engineer at Figma, walks through six optimizations behind a recent “10x faster vector editing” announcement.
Name slide rows, drag to reorder them, and jump between sections directly from Presenter or Audience View. Sections also show up in the layers panel in Design Mode, which keeps long decks navigable as they grow.
Buzz’s spreadsheet-driven asset generation gets the obvious next step: multi-select cells in the table view to edit copy, swap brand imagery, or change sizes across hundreds of variants at once. Resize works on a single asset or the full set, with preset or custom channel sizes to fan out a campaign in one operation.
Variable Sync to Repo, from Luis Ouriach, pushes and pulls variable collections between Figma and Git in both directions. Worth pairing with his “Adoption is a Red Herring” essay above — both are arguments for treating the design system as infrastructure that has to meet people where they are, including the engineers consuming tokens through a package manager.
The May edition is mostly a demo of Figma’s MCP server, with Amy Lima and Anthony DiSpezio walking through three workflows: code-to-canvas import of a vibe-coded prototype, round-tripping a dark mode so variables stay in sync between code and Figma, and using the pre-installed figma-use-scale skill to generate first-pass directions on a production dashboard. The closing update reel includes vector editing up to 10x faster, memory warnings down 92%, macOS eyedropper now samples anywhere on screen, FigJam MCP can read and write boards (ERDs, architecture diagrams), Make Kit packages your design system’s code for Figma Make, and Weave gets a timeline for video.