For designers Adobe left behind

Adobe XD to Figma.

A designer I spoke to last week had been on Adobe XD since 2019. Her agency told her on a Monday they were moving to Figma by the end of the month. Adobe had stopped updating XD. She had three weeks. She'd been avoiding the switch. Adobe forced it for her. This page is for people in her spot.

What actually happened to XD.

A short timeline, for anyone who lost the plot.

  • September 2022. Adobe announces a 20 billion dollar acquisition of Figma.
  • May 2023. XD quietly moved into maintenance mode. No new features.
  • June 2023. XD removed from the Creative Cloud launcher. New users can't buy it.
  • December 2023. Regulators in the US, EU and UK push back. Adobe abandons the deal.
  • January 2024. Adobe confirms "no plans to further invest in XD."

Translation. Adobe bet the farm on Figma, lost, and left XD on the shelf. It's not coming back.

You know more Figma than you think.

You've been designing in XD for years. Adobe muscle memory for bezier tools, alignment, layers, and boolean operations carries over cleanly. The core concepts map across.

  • Artboards become Frames, with one twist. More on that below.
  • Components become Components. Same name, more powerful.
  • Stacks become Auto Layout. Same idea, better execution.
  • Character Styles become Text Styles.
  • Document Assets become Local Styles and Libraries.
  • Repeat Grid becomes Auto Layout plus Components. Different workflow, same result.

You're not starting over. You're translating.

What actually trips XD users up.

Auto Layout is Stacks done properly.

If you used Stacks in XD, you're already most of the way there mentally. Auto Layout works on the same principle. The container handles spacing, padding and sizing. The difference. It's more powerful. You can nest it. Mix horizontal and vertical. Set alignment per child. Use absolute positioning when you need to break out.

It's the single biggest productivity gain in Figma. Don't skip it.

Components got serious.

XD Components were okay. Figma Components have variants, properties, nested instances, and can be published across files and teams. You can override almost anything on an instance without detaching. Component properties replace what used to be duplicated components for every state.

The shift in thinking. Components in Figma aren't just reusable artwork. They're reusable behaviour.

Everything is browser based.

XD was a desktop app. Your files lived on your machine. You shared by generating links.

Figma runs in Chrome. Files live in the cloud. Everyone with access sees the current state in real time. No "which version is current." No "did you save it to Creative Cloud." No install, no sync, no waiting.

Takes about twenty minutes to adjust.

What doesn't transfer.

  • Auto Animate. XD's signature interaction doesn't come across. Figma's Smart Animate is close but you'll rebuild the interactions. For complex motion, use plugins like Figmotion, or move serious prototyping to ProtoPie.
  • XD plugins. All gone. Figma has a bigger, more active plugin ecosystem, but your specific plugins need replacing.
  • Adobe Creative Cloud file management. Figma's version history is automatic and continuous, not checkpointed. It takes some adjustment.

How to actually import your files.

Three paths, in order of effort.

  1. Figma's native XD import. File, Import. Opens .xd files directly. Covers most cases. Text, shapes, basic components. Misses Auto Animate interactions and some plugin specific content.
  2. Convertify plugin. Third party, paid. More reliable on complex files and design systems.
  3. SVG export. The bulletproof fallback. Export layers as SVG, drag into Figma. Loses component links, but nothing breaks.

For most people, native import plus cleanup is fastest. For complex design systems, rebuilding from scratch in Figma is usually quicker than fighting the import. It's also a chance to clean up what's accumulated.

How long it actually takes.

  • One session. Oriented. Files, pages, frames, components, basics of Auto Layout.
  • Two sessions. Productive on real work. Building things, not fighting the tool.
  • Week two. Shortcuts replace Adobe muscle memory.
  • Month one. You wonder why Adobe held you back this long.

The shortcut.

If you've been designing in XD for years and Adobe has essentially shut the door on you, a beginner course isn't for you. You need someone who can translate Adobe workflows into Figma workflows. Someone who can answer "but how do I do X" while you're doing real work.

That's what tutoring is for. Sessions run on your real files, your real patterns, your real clients. Not a generic curriculum.

See how tutoring works

Questions people ask.

Is Adobe XD dead?

Effectively yes. Maintenance mode since May 2023. Removed from the Creative Cloud launcher in June 2023. Adobe confirmed in January 2024 it has no plans to invest further. Existing users can still open files. No new features, no new purchases, no roadmap.

Why did Adobe stop developing XD?

Adobe tried to buy Figma for 20 billion dollars in September 2022. Regulators blocked it. The deal collapsed in December 2023. Adobe paid Figma a 1 billion dollar termination fee and abandoned XD rather than revive it.

Can I import my Adobe XD files into Figma?

Yes. Figma has native XD import via File, Import. The Convertify plugin handles complex files more reliably. SVG export is the bulletproof manual fallback.

What happens to my Auto Animate prototypes?

They don't transfer cleanly. Figma's Smart Animate is close but not identical. You'll rebuild the interactions. Plugins like Figmotion help with complex motion, or use ProtoPie for serious prototyping.

How does XD Stacks compare to Figma Auto Layout?

Stacks was XD's version of the same idea. Auto Layout is more powerful. It supports nesting, absolute positioning, flexible alignment, and behaves like CSS flexbox. If you used Stacks, you're already most of the way there.

How long does it take?

Productive in a session or two. Muscle memory takes a few weeks. A full design system rebuild takes one to four weeks depending on complexity.

Coming from Sketch or the Adobe Suite as well?

See the Sketch to Figma and Adobe Suite to Figma guides.

Sources and further reading.