We Need to Make FigPals a Permanent Feature! Sign the Petition! 🐾

Indeed, knowing this project is just a temporary Easter egg comes as a relief for me. I'm surprised Figma would allocate resources to developing seemingly useless features rather than addressing the productivity-critical functionalities we urgently need

Not everythihng needs to be about being productive. I’m happy they found the space for a little fun. It is very refreshing. For me those tiny details move me as user from like, to love the software. 

Figma if you’re seeing this please!! Our Figma Pal innies have very real lives and we have to save them!!!

Signed.

Everyone on my team absolutely loves these. So cute when we’re in the same file. Really hoping they stay! Listen to the people Figma!

pleaseeee 😭. think about all the merch u can sell :P 

These are absolutely adorable, me and my classmate had a good laugh about them. Makes homework more enjoyable. I named mine Cheese. 😂

I’ll be honest, FigPals was a delightful surprise. It was light hearted, unexpected, and a great example of how a design tool can have personality. I loved seeing the community respond with joy, humour, and genuine attachment to their little floating sidekicks. It was refreshing to see something designed purely to bring a bit of fun into the workflow in a field that can sometimes feel fast-paced and high-pressure.

But that’s also why I think now is the perfect time to have a slightly broader conversation.

FigPals clearly showed what the Figma team is capable of the attention to detail, the interactivity, the animation polish, the emotional nuance. That same care, when applied to core features, could solve some of the most persistent friction points that so many of us experience on a daily basis.

Because as fun as FigPals were, the reality is that the basics still feel incomplete in many areas. We’re still working around issues with component management, where updates don’t always propagate properly unless published. Detaching and editing nested components creates confusion. Auto layout remains unpredictable with vertical stacking, scroll regions, and frame resizing often requiring more troubleshooting than they should.

Variables and modes introduced an exciting direction, but the experience of using them at scale is still clunky. You duplicate variable collections. Countless bugs and errors occur when linking and moving them around, and there are no simple and easy ways to apply variable values, which leads to lower adoption. Applying them in prototypes is limited. Even basic light and dark mode transitions still don’t feel fully supported or smooth across the system.

Style and asset management across libraries is often harder than it should be. Something as simple as copying or duplicating does not exist, and you'll have to perform a cut and undo workaround to achieve what should be a straightforward copy-paste task. Adding variables to style is challenging, requiring workarounds that feel outdated in 2025.

Prototyping remains a limiting factor for anyone attempting to communicate complex interaction design. Scroll behaviour is inconsistent in preview mode, smart animate seldom functions as needed, and the precision of animation timing is still lacking. Moreover, once you move beyond the design surface into development workflows, the gaps widen further. Dev Mode’s licensing model divides teams, APIs lack essential flexibility, and plugin developers continue to encounter stability and documentation challenges.

And all of this sits on top of ongoing performance issues, lag in large files, crashes that still occur mid-work, font rendering differences between browser and desktop, the kind of things that chip away at confidence when trying to build at scale.

Even collaboration workflows, which should be seamless, still leave a lot to be desired. Commenting on large files is difficult to manage. Sharing and access flows are too rigid.

These aren’t edge cases. They’re not wish list items. They’re the everyday workflows we all rely on. They’re the foundation. And when that foundation doesn’t feel stable, it makes it harder to enjoy everything else.

So my hope is this: that the spirit and craft behind FigPals, the joy, the detail, the polish, becomes a signal for what’s possible across the rest of the platform. That the same thoughtfulness is given to the fundamentals we use every day. Because when the foundation is strong, everything from the fun features to the mission-critical ones becomes more meaningful, impactful, and trusted.

We don’t need to lose Figma's playful side. But we do need to pay the same attention to the parts of the product that are holding teams back, not because they’re not innovative, but because they’re not yet finished.

Thanks to the Figma team for pushing the boundaries of what’s possible. I just hope what comes next is a doubling down on the basics, not because they’re simple but essential.

Please please please let them stay! I’m already attached to my FigPal, and my heart will ache if she’s gone :(

Please remove it, Distracting my attention. Not useful. It takes space from toolbar. Every element makes the app heavy and eats RAM.

if figma wants to keep that thing, then give an option to remove/hide from settings. I don’t want to see useless elements