Can Figma replace Adobe? Sorry, Adobe...

Figma is really starting to make Adobe feel redundant.

For years, making creative meant a fixed sequence: design in one app, animate in another, export, rename, download, upload. Adobe built that road, and we’ve all put plenty of kilometres on it. So can Figma replace Adobe? For most of what we make, it’s getting very close.

Figma keeps paving a different one. Layout and prototyping came first. Now motion design and export are in the toolbox too, so a static frame can become a moving asset without leaving the file. When one tool covers design, motion and handoff, the gaps between tools (where time and file names go to die) start to disappear.

Another Figma feature we’re loving: the Klaviyo plugin

The new Klaviyo plugin for Figma is a huge time saver. It replaces the old clunky workflow of exporting each PNG one at a time, saving it to your computer, logging in to Klaviyo and uploading everything again, not to mention the file naming issues. Now, you just connect the plugin in Figma and upload your files directly in the app. Our designers are now using it for Figma-Klaviyo uploads and loving it!

Why the Klaviyo plugin matters if you juggle brands

You can connect multiple Klaviyo accounts and choose the destination per export, with no signing in and out. If you run more than one brand, you know the real risk: the right image in the wrong account at 4:55pm on a Friday. A dropdown beats a downloads folder every time.

So, can Figma fully replace Adobe?

Not just yet (that’s a story for another time). Adobe still owns heavy retouching, serious video and print-heavy work. But the default is moving: about 80 to 90% of our campaign work now starts and finishes in Figma. The last 10% is when we call in Adobe to get the job done properly.

Our tools are only half the story: our Creative team finds the best approach by collaborating with our clients, developing a strategy through to final product that accommodates goals, timelines and budget.

‍