Share Your Thoughts

Dear Figma official team,Hello!We are a formal enterprise located in Chinese mainland, and we intend to purchase your Figma enterprise version service. Now we consult you about invoice related issues:Can your company issue formal valid invoices for enterprises in Chinese mainland? What types of invoices can be provided? Can it be used for domestic enterprise financial reimbursement and account entry? What are the specific steps and requirements to apply for invoices after payment? Can the invoice be issued with our full Chinese company name and complete enterprise information as the invoice title?Please tell us the relevant detailed rules of invoice issuance, so that we can complete the subsequent payment and financial procedures.Looking forward to your reply, thank you very much!Best regardsYour nameCompany nameContact information

There is a great feature in Notion called “close redirecting browser tabs” This is a setting that, when toggled on, automatically closes a browser tab when a page open in the desktop app. It would be great if Figma had this feature as well. When I click on Figma links, I end up with lots of browser tabs like this, because the pages open in the Figma desktop app. I would love if these tabs auto-closed.

Hello,I always enjoy using Figma Design and FigJam.I use FigJam for organizing Minecraft addon development and system design, and as projects become larger, I’ve started encountering difficulties balancing “the amount of information inside nodes” with overall readability.Currently, FigJam is extremely effective for:mind mapping organizing ideas visualizing dependencies structuring systems and architecturesHowever, as projects scale up, each node tends to require a large amount of detailed information, such as:identifiers recipes geometry references technical notes implementation status tags JSON-related information various propertiesIf all of this information is displayed at all times, the overall board quickly becomes difficult to read and manage.Because of this, I would love for you to consider adding:“Expandable / collapsible node functionality”For example:Normally, a node would display only a simple summary Pressing a button would expand detailed information A larger text area or s

Make a copy button is prominent and copy button is almost ununderstandableI have been using Figma Make a lot recently and keep running into the same UX issue.On the top-right of the interface, there are two very similar actions:Copy Design (small icon button) Make a copy (large primary button)The problem is that visually, “Make a copy” is much more prominent, so muscle memory makes me click it almost every time when my actual intention is to copy the generated design into my working file.Instead of copying the generated design, it creates a completely duplicated file, which is not what I want most of the time.Why this feels confusingBoth actions are essentially “copy-related” actions:“Copy Design” → copies the generated output into my file “Make a copy” → duplicates the whole fileBecause of this:the terminology feels overlapping the hierarchy feels inverted the more destructive / less frequent action is visually emphasized moreSuggestionsI think this could be improved in a few ways:Opt

It is quite frustrating that there is no search function in the expanded available frame list when adding the open overlay action to a trigger. When numerous frames are created, locating the target frame for linkage becomes difficult. Dragging to set interactive links is convenient, yet cumbersome when working on an oversized canvas. Additionally, a single trigger supports multiple actions, and dragging fails to create interactive links when adding a second action.  I really wish there was a search function for available overlays.

The function to lock to a current zoom percentage (usually 100%) to keep the sense of scale consistent. I don’t think I’m the only one that has a difficulty with the sense of scale when designing and I believe that the ability to prevent zooming may help this or build a better sense of scale throughout a design.

As written in the documentation (Prototype interactions and animations) the destination of a Scroll to action can only be an element of the same top-level frame. But with this limitation it is impossible to prototype a common navigation pattern. On one-pagers there are often floating menu for intrapage links. E.g you have an hamburger icon that opens a menu overlay from where you can scroll to a specific page section. This can’t be realized with an Figma overlay because of the restrictions mentioned above. There is a workaround, but it seems that it only works because of a bug: You can set the menu overlay as an child of the top-level frame of the one-pager, define the Scroll-to actions and then move the menu outside the frame (as an separate top-level layer) to show it later as an overlay. By doing this all the Scroll-to actions still work, but when you change an action the target will be rested and the navigation is broken. Working Example Maybe you can remove the restrictions that t

I’m sharing the Figma Buzz link but it always go back to Asset View.It would be nice to toggle and decide which default view the viewer see from the link. 

This is really strange to me. I have a “Team”, apparent only from the URL, none of the UI elements show whether or not I’m dealing with an organization or a team. This team has members, whom I pay for, and the seats are set up for each one of them. They are all listed under the URL “…..team/<id>/team-admin-console/members...”, and show up properly.When I access “...team/<id>/all-projects….” and press the small down-arrow next to the Team name, and select “show members”, only my account is visible.The experience is this: all of the people in the team(shown under the team-admin-console) need to be manually approved/invited to each file for editing, even though they have been invited and accepted into the team.According to the documentation: “For example: if you invite someone to a team, they’ll have access to the projects and files in that team, based on the permissions you give them (can view or can edit). If you invite someone to a specific file, but not the team, they get

It would be great if you could add support for audio files in Figma Slides — with options like play on click, autoplay, and loop.At the moment, we need to convert audio files into video files just to make them work.

It would be great to have a simple toggle to show or hide the layout grid directly in the Properties panel — only for the current frame I’m in or for the ones I have selected.Sometimes I just need to view the design without the grid, and right now I have to go into Styles and manually toggle the visibility there.A quick “eye” icon or similar control for layout visibility per selection would make this much faster and more intuitive.

Having the ability to create subfolders within Projects would be a huge plus. For small to large teams. Please consider this, thank you. 

We love our FigPals, please dont take them away😭

What do you think about having a horizontal scroll on the layers panel? I can’t see the name of the layers and usually widen the panel to be able to see, but since I use a 13", this makes the canvas smaller.

Previously I’ve used the “starred items” function to have a quick way to open key files on projects I’m currently working on (without mixing up copies or branches of the main file, which happens on the “recently viewed” tab). It appears Figma is removing the starred items section from the sidebar. Is there a better way to ‘pin’ specific files that are SHARED with me (not owned by me, and saved within a team I’m not part of), so I can find/access them more easily than going via Recents > Shared Files. Thanks!

Hey Figma team and community! Feature idea: *Figma Wrapped* — a personalized annual stats summary, like Spotify Wrapped but for designers.At the end of each year, every user gets a recap:→ Total hours spent in Figma→ Components & frames created→ Layers named (and not named 😅)→ Top collaborators→ Most-used fonts & colors→ Busiest design day of the year→ Fun personality badges — "Component Factory", "Auto-Layout Champion", "The One Who Names Layers"Shareable cards, team comparisons, the works.The design community already loves this kind of thing — it would drive massive organic sharing and genuinely celebrate the craft. Feels like a natural fit for Figma's brand.Would love to see this happen! Who else is in? 🙌

As a user I want to lock the guides so that I dont accidently select or move them. This is frustrating. There are times when layout grids are are the correct tool to use and a time when guides/rules are the correct tool. When you are zoomed out it’s impossible to select elements without selecting or moving guides/rules. 🙂 …to everything turn turn turn turn…

Stroke is a very basic and commonly used feature. In my workflow, I often need to create multiple strokes on a single object, as shown in the image.Although Figma supports multiple strokes, all strokes share the same property and have only one width value. As a result, even when multiple strokes are added, they overlap completely. This makes adding multiple strokes essentially meaningless.I suggest allowing each stroke layer to have its own independent width property. 

Inside the option “Reset specific changes” the current “Reset Size” eaction only resets dimensions, but does not revert other Auto Layout-related changes such as alignment, positioning. The request is to extend the existing “Reset specific changes” functionality by adding a dedicated option for (Auto) Layout properties. This would allow users to fully reset all Auto Layout modifications in a single step and restore the component to its original layout configuration.  

Today, profile avatars in Figma account settings only display as static images. The Help Center states that GIF uploads are converted to a static image. There is no supported way to use an animated avatar in collaboration surfaces (multiplayer cursors, comments, Community profile, FigJam stamps, etc.).Other design tools in the same market already support animated profile avatars (for example, MasterGo supports APNG for dynamic avatars). Users who want a more expressive personal identity in the product currently have no first-party option in Figma.Proposed solutionAllow animated profile avatars in Account settings (and team/org avatars if applicable). Support at least: APNG (preferred: supports transparency, often better quality than GIF) Animated WebP (optional, good compression) GIF (optional, for backward compatibility — but should actually play, not be flattened to a static frame) Define clear limits, for example: Max file size (e.g. 2–5 MB) Max dimensions (e.g. 500×500 minimum

I’d like the possibility to automatically post an update message on Slack every time an update to a library file is published. Ideally the message includes: Name of the library Changelog (user submitted text in the publishing dialog) List of the impacted components This would make it easier for other designers and developers to notice and discuss such updates.

I have been playing around with creating variables but realized I would rather have groups in separate collections, but cannot move them.I would like to be able to duplicate an entire collection so I don’t have to manually re-create values and can remove what I don’t need from that collection OR simply be able to move groups into other collections.[The title of this post was edited from “LAUNCHED: Copy/Move variable groups into other collections” to “Copy/Move variable groups into other collections” by a moderator on 17-Jan-2026.]

Stamps are a cool feature, but I’m consistently disappointed by them. Straight up, we need:The entire standard emoji library as stamps Ability to add other people’s pfp icons as stickers (you can only do your own) The ability to add custom stamps I think #1 is the most impactful and would address some of the other, similar suggestions. I don’t even want Figma to make their own version of the emojis, they can just be 1:1 with some standard library (google’s, twemoji, etc.)

I propose that Figma introduce a search capability within the “Figma Make” prompt interface. Currently, users who wish to review previously entered prompts must manually navigate through the entire prompt history, which can be inefficient and time-consuming. Implementing a search function would significantly enhance usability by enabling quick retrieval of past prompts, thereby improving productivity and overall user experience.