Suggest a Feature

Maybe the overlay functionality was originally designed to simulate modals. But two (unnecessary?) limitations limit their power for other applications: The fact that I cannot have more than one overlay open The fact that I cannot interact with the area outside the overlay is very limiting Please allow for having multiple overlays and for interactions outside of an active overlay. If you need regular modal behavior, you can still have that by checking a checkbox (off by default) in the Figma UI. Limitations like this mean I have to back & forth between Figma & Protopie. I fully realize that Figma may not be aiming for HiFi prototyping (text fields, conditionals and even sensors). But just a couple of well designed tweaks and features will enable me (and probably others) to do 90% of my prototyping in Figma… Example: Image you have an image grid with smaller images. Clicking a

I was surprised to notice today that the long awaited Connected Projects is now available in Figma but also very disappointed to see the absurd limitations on how many connected projects each plan can have. I can somewhat understand the limitation of being able to connect with one company at a time for technical/admin reasons in the first release, but WHY do we need the limitations of how many connected projects we can have if all parties are already paying for their licenses? The max 3/6 in Professional and Organization is ridiculous, as it also counts the projects that are shared our way. Please remove these artificial limitations, or at least make them a lot bigger like 20 / 40 / 80 so they make some sense in the real world.

Describe the problem your experiencing and how your idea helps solve this We need to control access to various areas of Figma, and Closed teams help, but it’s painful to have to add people individually. I would love the ability to group users into user groups (aha!) and bulk add them to teams with the correct permissions. Individual users could be added with more permissions, as a local override, but for the most part, we could just add these groups. This would help immensely with change management and onboarding, as well as maintaining access guardrails where appropriate. Add as much context as possible (screenshots, Figma files, mockups, etc.) Example: I want to add Designer X to our UXD user group. By default they gain edit access to all working teams. However, as part of that group, they’re only given view and library access to the Design System team. Ask questions to bring the community into the

Currently, you can only set the default mode of a workspace by enabling the library for everyone in the workspace. It would be helpful to be able to set the default mode without enabling it for everyone. The use case we have is that we have two different libraries. One library with all of our theming variables, and one with just the semantic variables we want our designers to use. We do not want all designers to use the theming variables library but the theme is controlled by that library. Can we please add the ability to change the default mode without enabling the library?

Problem Statement:Currently, for the handoff file, designers duplicate the frames to show the designs in other modes like dark mode/tablet size.When they do that, the file obviously bulks up. Also the prototypes break. After the file bulks up, designers make changes on any one mode, and might forget to make the same changes in the other modes. Solution:Dev mode should have a preview option for developers to switch between modes and screen sizes. This way, the designers only need to share a limited number of screens and the maintenance becomes easier.Since this will be in preview mode, any change developers make can only be visible to them. They can have a reset option for after they are done previewing. For developers to change screen sizes (based on min and max width set by designers), an auto-layout option might be needed for sections. So that other frames move gracefull

I’d love to see Rive embeds working live in Figma. Currently, in Notion you can embed a rive animation and then interact with it directly in the Notion window, this is also available on Twitter feeds. Here is an example of some Rive animations running in notion → RIVE EXAMPLE I am currently creating motion design standards to complement a design system and giving the engineers the ability to interact with the component they are building would be phenomenal. I’d love to see Rive animations incorporated into prototypes as well.

I would love the ability to set a background color in the layer list. I’d like to be able to set this on an individual layer or group of layers. I often have trouble finding important groups of layers. I’ve resorted to using emojis which helps. But imagine that we could color the background color of the labe

When creating hand-off documents I like to showcase user flows by using arrows between different UI elements. I have to use plugins to create these arrows at the moment. When playing with Figjam I notice it had a connector option - this is great. I would love it if we could also have this connector option inside Figma as it would be a HUGE timesaver for hand-off. I would like to think this would be a super easy update given that we can already edit connectors inside Figma. We just need a connector button in the toolbar like so:

Hi Figma team,As a UI/UX designer using Figma Sites CMS, I would love to see some enhancements to support richer content workflows. Specifically:Embed video links directly: It would be great to insert a video URL (e.g., from YouTube or Vimeo) as a field in the CMS and bind that video to a module on a page. This would allow teams to manage video content from the CMS without touching the design and would enable more engaging pages. Bind CMS text fields to embed modules: Currently embed modules don’t appear to support binding to CMS text fields. Allowing modules to use CMS text fields as their source would let us reuse structured content (such as code snippets or other text fragments) across multiple pages and keep everything in sync.These capabilities would make Figma Sites CMS more flexible for content-heavy websites and simplify collaboration between designers and content editors. Please consider adding these features in a future update.

I’m having trouble exporting PDFs of frames. Do you know if the export functionality embeds the fonts? I will import the generated pdf frame into another work that requires to be PDF/A compliant, so I need the font embedded in the frame in the first place. I tried with Adobe Reader, and it does not say “embedded”, which is usually a sign that it’s not. I tried with another software (Okular), and it does say “fully embedded”.

Inputs are one of the most common UI design elements out there. But when you have to use them in a prototype there isn’t a good way to show what they look like when entering text. It’d also be great if we could trigger validation events like on a password input for example. This would bring more fidelity to my prototypes than just about anything.

Miro has a very useful tool to be able to select an entire area and then only select items of a type.Specifically, this is really useful for selecting an entire board, then filtering to just the stickies on top of a board to move them and leave the image or diagram underneath untouched.This would be great to add to FigJam for feature parity, and I really miss it coming from Miro.

As I have begun to use Figma Make, I have found that a designer is not the best typer and often makes mistakes in typing. Typing also takes so long to do and you want to speed up your time in Figma Make to go even faster. Imagine I can tap a Mic icon and input my prompt with VOICE. It would be so much faster and more accurate. Then hit the SEND button.You would see your text being inputed to the text field as you speak. You would need a way to stop or pause the voice to text.

Whatever I try, I can’t seem to work with .mov or .webm videos with transparent background on Figma. Whenever I upload them, I get a black background. Am I doing something wrong? Or is there a workaround for this?

I often work with many files open at the same time, especially in shared projects, and it quickly becomes cluttered and difficult to manage.Would it be possible to introduce a tab grouping feature similar to what browsers offer? Being able to group related files and collapse those groups would help us keep only the projects we’re actively working on visible, while minimizing the rest.This would significantly improve organization and create a much more manageable and focused working experience.

This would help me organise (merge, divide, archive) files. This would in turn make files more approachable for team members (and clients). It may also go some way to decreasing load times too. It might also reduce anxiety around potentially loosing connections between properties components etc. While it is possible to copy/paste content from one document to another, if you do links to frames will break background colours are lost comments are lost history is lost there’s no record (in history, say) of what you did e.g. ‘Danny moved page ‘Signage’ to file ‘All artwork’.‘ you get an unpredictable mix of local and external styles Also, you have to manually create and name destination pages one at a time. You want to be able to select a bunch of pages and move them all at once. Inspired by this post

ProblemToday, applying edit guidance in Figma Make relies on a manual copy-paste workflow (for example, repeatedly pasting guidelines.md and/or CSS adjustments into each new Make file). There is no native way to save a pre-approved “style set” and re-apply it across prototypes, which adds friction and increases inconsistency risk. Current behavior Designers must manually copy/paste the same edit guidelines (and any related CSS tweaks) into every new Figma Make file. Updates to guidance require repeating the same manual steps across multiple files. There is no centralized, reusable, permissioned style context that can be applied with one action. Expected behaviorProvide a first-class way to create, manage, and apply reusable “Style Sets” (approved guidelines + optional CSS) to Figma Make files.Proposed solutionA

I have a deck slide longer than the slide therefore I want to scroll to see the rest of the slide. I thought I could do this with a prototype as a workaround but you have to click the prototype to view it so therefore it won’t work. Is there any plan to release this feature after beta, as this is a big blocker for me and my team at present when we have longer pages in our slide decks. Thanks guys.

Hello. With all the updates to auto layout, it would be wonderful if when an engineer is reviewing the designs, they could actually resize a frame to see how the designer intended for the responsive breakpoints to work. Especially since CSS now supports container responsive in some browsers which is essentially how Figma works. Right now, the only option would be to copy and paste frames side by side of different sizes to show that interaction but it only gets you so far and letting the actual engineer modify that width to see the responsive intentions you baked into the design would be way more helpful and less “noise” on the screen for them to review.

It’s nice to add ability to change opacity of desktop Figma app. It will help to make pixel perfect designs

I need a good quality PDF export from Figma with at least the following features editable text export with font embed image export settings, dpi, rgb/cmjn/graysacle, image format, image compression, crop hidden parts full gradient and effects support (shadows, blurs, etc…), if not supported by pdf, then rasterize using above compression settings hyperlinks to urls on any object, no only on texts Today, no plugin seems to be doing the job correctly. PDF’s are dramatically heavy and editable text is not supported… Hey guys, Adobe bought you for 20Billions, I really hope it’s not intended to kill Figma’s roadmap… You’ve published a great PDF export roadmap in 2018… five years ago…

Background:When a new image is imported to replace an existing cropped image, the imported image can often be skewed (the workaround is to select Fill for the mage fille and reselect Crop and the skewing issue will go away). This also can happen to copying/pasting image fills.The skewing is often subtle, and can sneak into production before it is caught. Designers should be alerted to the anomaly. Possible Solutions:One of the following options (or all) could alert designers of the issue: Option 1: Bottom of screen message during/after import:Use a standard status message at the bottom of the screen when an imported image will be skewed.Option 2: Indicator on the image/crop tool:

 Dear Figma Team,I’d like to share a small but impactful usability suggestion regarding image adjustment controls (Exposure, Contrast, Saturation, Temperature, etc.).Currently, these values can only be adjusted using sliders. While this works for quick changes, it becomes difficult to achieve precise and consistent values, especially when working on detailed UI or design systems.Suggestion:It would be very helpful if each slider also included: + / – buttons for incremental adjustment, and/or A numeric input field to manually enter exact values This would: Improve precision and control Help maintain consistency across designs Reduce trial-and-error when fine-tuning visuals This pattern is common in professional design and ed

Would be great to have a native skew and shear tool in Figma. Even with plugins, I’m not finding a way to control the skew anchor. Just something simple like Illustrator’s Free Transform, where you can skew an object and choose where the effect starts from.

I know this is already a topic in another thread but maybe adding more threads is the move to get this to be updated?The feature I’m requesting:Just make libraries and color choosing context consistent across the board.For no rhyme or reason we have to jump through hoops to get the colors already defined to show in the library tab in context to the gradient stop color pickers. Why the disconnect? Are we channeling Adobe here? If there’s an original UX reason behind this pattern, I don’t really care - it’s the IMPACT that matters and the impact is: pure frustration.Thank You