We Need to Make FigPals a Permanent Feature! Sign the Petition! đŸ
Alright, guys FigPals were the best (and weirdest) thing to come out of April Foolsâ this year. They follow your cursor, help you design, and love you unconditionally⊠maybe too much.
But hereâs the problemâtheyâre only available for April Fun Week!
We canât let this be just a one-time joke. FigPals deserve to be a permanent feature (with a toggle for those who donât want constant companionship). Thatâs why I made a Change.org petition to show Figma how much we want to keep them!
Sign up the petition and lets make this happen were at 71 votes now
YES IF they take my son from me I will riotÂ
Yesss!! I no longer feel alone on this screen. Â
Â
Please donât get rid of FigPals. Itâs a fun feature.
100%Â Like how can you say NOÂ to this?Â
I agree with â@Lydia Hesterman. Iâve become emotionally attached to my beautiful son Goober; you canât take him away from me, Figma!
100% agreed! LOVE my pal and I want this as emotional support at all times
PLEASE, let us keep them!!!
These are the priorities? There are so many urgent construction sites and Figma is investing huge development resources in a Digital Tamagotchi?
Instead, how about some long overdue features that would dramatically improve Figma:
Responsive Overlays
Shadows are finally no longer inherited from parent elements in the preview
A separate configuration field for tooltips with styles (with alignment, arrows, text, colors, etc.)
Real scrollbars with their own configuration field for styles
THOSE would be areas where resources should flow.
These are the priorities? There are so many urgent construction sites and Figma is investing huge development resources in a Digital Tamagotchi?
Instead, how about some long overdue features that would dramatically improve Figma:
Responsive Overlays
Shadows are finally no longer inherited from parent elements in the preview
A separate configuration field for tooltips with styles (with alignment, arrows, text, colors, etc.)
Real scrollbars with their own configuration field for styles
THOSE would be areas where resources should flow.
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
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.
Beautiful post. 100% agree. Glad they found space to have fun, but also questioning what could have been delivered with those resources from the long backlog of long overdue feature requests. I really hope that Figma redirects more resources to the basics moving forward, but I canât say Iâm hopeful. Based on past updates, I have a feeling itâs going to be more new product launches like FigDocs and FigSheets or something, and less attention to getting the basics in their existing products up to speed. Like, why do I need to rely on 3rd party plugins to export variables for my devs?
While I agree that there are a lot of things to change or fix in figma, I found so much joy in the little figpals. If nothing else, thank you to the team that made them for making my life a little brighter and joy filled this week. Much needed, much appreciated.
I really hope they keep the FigPals around. Iâm going to be so sad if my FigPal is gone when I start work next week
I will cry if i lose my FigPal, itâs my only real friend :(
Hello one and all,
I would kindly ask the Figma developers to keep the FigPalâs feature as it is great and all that hard work should stick permenantly.
I would say that it would be great if we had some more customisation settings, think Clippy on windows XP. Helpful little guy.
I would like the FigPal to stick to my cursor, not have a animation delay, personally I feel like it would be good if you could toggle that so either they are stuck to your cursor, delayed, or you put them back in their house.