Share Your Thoughts

I'm excited for Bulk Create in Figma Buzz. It’s a lot more intuitive for our marketers to use, but at its current stage it’s actually more time consuming than our existing workflow, mainly because it doesn’t have the ability to bulk rename frames or the exported filenames. That means we still end up having to manually rename "Frame1.png" all the way to "Frame175.png".Here’s our use case: we need to create OpenGraph images for a website with over a hundred pages. We have two design templates: one with page title only, one with page title and a subhead.Currently, the marketing & web dev team maintain a spreadsheet of all the pages currently exist.We have the 2 designs set up as components and use a plugin called Scribe - Dynamic data in seconds to pull in the CSV and use a column we choose for naming the frames / files.I can see Bulk Create doing this as well, and even adding some common renaming & conditional naming options (i.e. case options, removing + replacing + appending ch

Hi, I've been working on a prototype, and animating the chat bubbles turned out to be quite a tedious task. To create the animation, I had to duplicate multiple frames and apply individual delay animations to each chat bubble.I'm wondering, is there a way to apply a delay animation to a group of elements collectively and adjust the timing for each, similar to how you'd stagger animations when loading a collection of cards?With Figma's current capabilities, the only workaround seems to be creating multiple frames and manually adjusting the opacity and timing for each element to simulate delayed appearance which becomes repetitive and time-consuming when applied across multiple components.Would love to know if there’s a more efficient approach or if this is something the team is planning to improve in the future.

Introducing an Invisible Mode for Figma to enhance user privacy. This feature allows users to work without showing their online status, preventing others from following their activity. Perfect for focused, distraction-free design sessions.

Hi Figma team,I work in Figma with Claude through the Figma MCP server. While the agent works in my file, it shows up in the avatar list as “Third-party agent”. The avatar used to be a robot icon, and now it shows the Claude logo.The Claude logo is clearer than the robot icon. Still, I’d like some control over this, because I often share files with teammates and stakeholders who see these avatars too.It would help a lot if we could:choose the avatar or icon an agent uses in a file, or at least pick from a few neutral options rename the agent (for example “Design assistant” instead of “Third-party agent”) set this per team or per file, so everyone sees the same thingRight now I couldn’t find any setting for this in the app or in the MCP documentation.Thanks!

Is there a way to turn off the AI chrome when sharing the prototype in "Make"? When sharing in the prototype view, I was expecting it to just share the screens but when I shared the link, it showed the make file with the AI chrome. Is this a big? Or will this be an enhancement?

As I was looking for a way to do this natively in Figma, I came across this concept article on Medium. In the article, Андрей Насонов (Andrey Nasonov) describes adding the option to choose alignment in the image settings beyond the default centered. This would be a simple but huge improvement to image settings, especially for responsive design. Here’s his example of how that might look on the Properties Panel for images: If anyone has found any way to work around this other than individually cropping images for different container widths, pls hmu! 🙏

If I have a team with some members not spending their Make credits, I want to commandeer those as an admin. Or even better, I’d like an admin setting to put the sum of all the credits for our full seats into one shared bucket.

Setting durations, easing curves, delays, especially for Smart Animate animations are essential tools when making presentations in Figma in order to make fluid ‘Keynote-like’ transitions. Unfortunately these are completely absent in Figma Slides at the moment, making it pretty much useless to our team. We will keep making our presentations in Figma Design and linking everything by hand🥲 until these crucial settings are implemented in Figma Slides…

The announcement of Figma Motion had me excited, but right now it feels like a more advanced prototyping mode. I understand that it’s still in Beta mode and I hope in the future it will actually be usable for integrating motion in a design system.Animation between statesIf I take a button from our brands design system, it would be very helpful to be able to keyframe states and variants. Maybe take a page from Rive’s book and add something like a State Machine.Text animationText animation is non-existent at the moment. If we want to create an animation of text being typed I’m not sure how we achieve this.TokenizationWhen exporting JSON, there are no tokens visible in the JSON file, it’s just raw values.Preset AnimationsThe preset animations are nice and all, but it would help immensely to be able to make a library of our own animations, so we can quickly build out motion components.Styles/ChoreographiesSimilar to how you can add multiple values to a typography and apply it as a style (c

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

The descriptions written in variables should be shown when selecting/picking them in respective pickers - maybe as tooltip? Otherwise I don’t see, how this could be accessed/taken into account by the users of our library.The grid view of the color picker shows the actual name as tooltip for example. This could also be used to actually show the description. 

ProblemWhen creating a Slot property in Figma, designers can define preferred instances through the Select instances popup. However, when working with complex design systems and multiple nested components, finding the right components through a list can take extra time.Designers may already have the desired components arranged on the canvas, making the list-based selection feel less direct than it needs to be.Proposed SolutionIntroduce a “Select from canvas” option within the Slot property's Preferred instances settings.When activated, designers could click eligible components directly on the canvas to add them to the preferred instances list.The workflow could be: Select the main component and open its Slot property settings. Click Select from canvas in the Preferred instances section. Click the desired components on the canvas to select them. Confirm the selection and return to the Slot property settings. Expected Benefits Faster workflow: Reduce the time spent searching and sc

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.

I’d like a way to add a fill to a main component that is visible only while editing the component. It should not appear on instances used in other files through a library.Current behaviorIn a library file, I add a fill to a layer in a component, such as a background or guide color. I turn Show in exports off for that fill. This works, and the fill stays out of exports. I publish the library and use the component in another file. The instance still shows the fill on the canvas. These are client-facing end screens, so the fill shouldn’t be visible there.What I needWhen a fill is set to not show in exports, I want a way to have it also hidden on instances in consuming files. This could be a separate option, for example “Hide on instances,” or the same setting applied to instances.Design systems often need fills that help while building a component but shouldn’t appear in the final screens. The current workarounds are to hide the fill by hand on every instance, or to build a separate varia

I've been really enjoying the new Motion features in Figma. The experience feels intuitive, and creating animations has become much faster and more enjoyable. Even in its current state, Motion shows a lot of potential, and I'm excited to see how it evolves.While testing, I came across a few areas that could significantly improve the workflow: Nested Layers in the Timeline When working with nested layers, child layers currently appear individually in the timeline alongside their parent layer. This can make the timeline cluttered and difficult to manage. It would be helpful if the timeline supported nesting similar to the Layers panel, with expandable and collapsible groups. Dedicated Clipping Mask Workflow Motion currently lacks dedicated clipping mask support. A masking workflow similar to After Effects would make it much easier to create and animate reveals, transitions, and other advanced motion effects without relying on workarounds. Dedicated Alignment Controls Motion currently

I discovered by accident the new ⌥+TAB keyboard shortcut to quick toggle between modes (not sure what that’s officially called?). This seems super useful, except for whatever reason the order the modes are displayed in the quick toggle UI, is completely different from the order they’re displayed in the keyboard. In the toolbar they are ordered: Draw, Design, Motion, Dev Mode. Motion is relatively new, but I’d assume this is the order nearly everybody is used to.After hitting ⌥+TAB the quick toggle UI appears and the modes this time are ordered: Design, Draw, Dev Mode, Motion.This feels unnecessarily confusing to me. I rely heavily on the spatial positions of the active mode icon in the toolbar to see which mode I’m in. The icons themselves are relatively small and visually similar, so I feel like their position is a much stronger visual cue than the icon itself. So when the spatial consistency is suddenly broken, I have to stop and consciously read the labels and think about it for a m

why can’t figma make make components that we can import back into figma. It would be useful to us make to generate a design system, using prompting and be able to import thes eback into figma as components.

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

Currently, when multiple objects are grouped, moving an individual object within that group causes it to be removed from the group. This makes working with groups unnecessarily difficult, as even minor adjustments require users to manually ungroup and regroup the remaining objects afterward.Instead, users should be able to reposition objects within a group while preserving the group relationship, allowing for quicker iteration and reducing unnecessary rework. This would make groups behave more predictably and better support common editing workflows.

I don’t use Figma all the time, I don’t want it to run anything on startup. It’s frustrating to manually remove Figma from Login Items, since it automatically adds itself there again. It would be nice to have at least an option to disable it in settings, or even better - remove that functionality at all, since it’s not user friendly. I want control over what and when the apps do at my workstation. P.S. If it’s needed for updates check - I’m more than okay to update on app start

I strongly request the ability to turn off the Figma agent appearing by default when a new Design draft or file is created, and also to disable the Agent tab completely. In addition, the ability to hide AI options like “Make an image” for image design tools would be nice, as well as the ability to filter tools/plugins by their use of AI in the Tools tab and Community.This could be as simple as adding new toggleable options under Figma > Preferences… labeled something like “Show Agent in new files”, “Hide image generation tools”, and labels for Community assets that use AI and options to hide such assets in their respective categories.I know that these options don’t exist right now, which is why I am imploring them to be implemented as soon as reasonably possible. I understand these things can be helpful for a good amount of people and that’s completely their choice. But you need to understand that a similar amount of people, myself included, have no interest in using the agent or an

The seats section lacks of a registry to know all seat changes history. The only information it shows is the seats taken right now. It’d be great to know since when some seats have full access o collab, is almost useful as it is now if you have to set up a budget or making a billing from it.

I would love to be able to see all my brand’s patterns in the preview of the style panel. Right now they all sport the same generic dotted pattern.I am able to add a “background” colour behind the pattern, but many of my patterns use the same colours in different combinations, so it isn’t a reliable way to distinguish between patterns.  

Connected Projects are a great way to have a shared space between two separate Figma accounts (usually between two organizations). A drawback is that all the files are in a single project.Without some kind of hierarchy (or filtered view) the Connected Project can quickly fill up with all kinds of working files, templates, older “archive” projects that are now needed only for reference, etc.Figma could either extend the “connected” concept to the team level (so there can be more “folders” in the connected space), or provide some other kind of other hierarchical or filtered view.

Can we allow Connected folder to have a sub-folder? Perhaps not 10 levels of nested folder. We can limit it to 1 or 2 levels should be good enough.Thanks!