Suggest a Feature

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

Right now, it's impossible to left-align stacked text layers with different font sizes inside Auto Layout.Because Figma aligns to the text bounding box instead of the actual glyph bounds, font sidebearings create an awkward visual gap. For instance, if you place a heading above some body, the stem of the headline won't line up with the left margin of the body text. It works for letters like T and A, but not for letters with a flat vertical stem like L and B. See attached screenshot below.You can't manually nudge text layers inside Auto Layout. Negative padding shifts the whole container, not individual layers. Community plugins like “Text Visual Alignment” don’t work with auto layout.Suggested solution:Add horizontal trim to type settings (right next to vertical trim) that crops the sidebearings to the outer edge of the glyph bounds.This would be a massive improvement to type in Figma!

Currently exported .PDFs out of Figma are not accessible, because the text is flattened as images. I would like to request an option for exported .PDFs to have editable text. This would be a game changer for our team to move off of Sketch! 😃 (Sketch allows for .PDFs to export with editable text, but Figma does not)

It is imperative that Figma address the issue of editable text in PDF exports. Clients, legal teams, accessibility—all need editable/scannable live text. Please!

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

This is a common mobile interaction so it feels like a big miss to not include it. This has limited my ability to test some things in the app I’m designing which is a bummer.

We currently can only Rename, Delete or Create a collection. Can we have an option to Duplicate an existing collection? This would allow users to quickly create copy of an existing collection of variable, then select a new design and switch from one collection to another without having to type everything. Example use case: Brand 1 (Collection) Colors (Group) Light (Mode) Dark (Mode) Fonts (Group) Light (Mode) Dark (Mode) After duplicating: Brand 2 (Collection) Colors (Group) Light (Mode) Dark (Mode) Fonts (Group) Light (Mode) Dark (Mode)

Right now, in order to link out of a file, the link has to be attached to a Text layer. It would be great if I could add a link out to any layer, like a button or a Card.

While cleaning up my file, I hid a frame that I didn't want visible at the time. I didn’t want to delete it because it was still useful. Months later, I needed that screen again. I tried searching for it using keywords, browsed through pages, and even looked through the version history.I ended up reviewing five months of version history, scanning for keywords to locate the screen. I eventually found it—it had been hidden all along. The content was never deleted. But because it was hidden, it didn’t show up in search results.This was frustrating. Search is supposed to make it easier to find things. Just because an object is hidden doesn’t mean it stops being part of the file. Excluding it from search reduces the usefulness of the feature.Request: Please make sure hidden elements are still indexed and searchable. At the very least, give users an option to include hidden content in search results.

If I could toggle all hidden layers to be seen together, it would make certain workflows a lot simpler

This would be handy if I want to mass-select and find hidden layers to show altogether. Unless this is a technical limitation, I am shocked that this is not integrated as an option from the get-go.

Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%). Interestingly …You can use a variable for letter-spacing ( which accepts a number variable - but reads it as a percentage) - the challenge remains that line heights by default are absolute not percentages - even though you can input a percentage. Percentages allow greater flexibility and less calculations Word around would be to allow formula in a variable e.g. =[variable] * 1.5 Or figuring out a way for the line height to be toggle between absolu

In the Figma UI, you can create a color variable that references another color variable (alias) and override its opacity — producing a "composed color" value. This is extremely useful for building semantic color systems where, for example, surface/overlay = palette/neutral/900 at 54% opacity.However, the Plugin API currently does not support writing these composed color values via setValueForMode(). Attempting to do so throws:Uncaught Error: in setValueForMode: Composed color variable values are not supportedMinimal reproduction scriptRun this in the Plugin API console or inside a plugin: // Step 1: Create a variable collectionconst collection = figma.variables.createVariableCollection("Semantic Colors");const modeId = collection.modes[0].modeId;// Step 2: Create palette/neutral/900 — a base colorconst paletteNeutral900 = figma.variables.createVariable("palette/neutral/900", collection, "COLOR");paletteNeutral900.setValueForMode(modeId, { r: 0.07, g: 0.07, b: 0.07 }); // Works fine ✅//

I’d love the option to save open tabs and tab groups to my Figma account and access them across computers.I work on two computers: one at the office and one at home. Tabs and groups stay local to each computer, so when I switch devices, I have to reopen files and recreate my workspace manually.It would be helpful to: Sync open tabs, their order, and tab groups across devices. Preserve group names and organization. Pick up where I left off when signing in on another computer. Ideally, this would be optional, so people who prefer separate workspaces on each computer could keep them.Having access to the same files is useful, but having the same working context would make switching between home and office much smoother.Does anyone else run into this or would find this helpful?

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 label. I’d also like to edit the label name so that in my document “Blue” would represent to my developers that it’s grids.

I use ‘N’ as my push to talk key on Discord which in Figma goes to the next frame.I just want to be able to unbind/remap the key in the figma app so this doesn’t happen.

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.

When working with multiple shapes, you currently cannot edit the anchor points of multiple shapes at once whether they are unionized or not. At my studio, we are working on incredibly complex UI for vehicles, and products, and this feature would be much appreciated, and would greatly increase the speed of our workflow.

Please vote this up!We really need to be able to drag and position lock annotations and connect to any layer within a nested layer or instance. This has been asked for many times (Examples below) and would eliminate designers time making their own local components and ignoring the use of the built in annotations. and 

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

Fundamental to using any digital whiteboard, is being able to hyperink image elements.Please consider adding this to the pipeline! It’s a huge setback to using Figjam and lags behind competitors for a basic requirement. Community, I’m not alone. Please chime in! 🙏

Color variable aliases were recently given the ability to define a new transparency value without detaching the actual color from the source variable. However, only the opacity can be set and even that’s only if the source color is solid, instead of allowing existing opacities to be offset.It would be really cool if that system could be extended to also allow modifying the other axes, not just the transparency. Since you can’t define a color with a hue and saturation but no lightness, adding this would also ripple out to the opacity by allowing offsets to the existing color’s opacity, instead of what currently happens where if the source is not solid, the feature gets disabled altogether.The use case for this is absolutely massive, letting you far more deeply align your color palette to a single source of truth. It strongly fits the ideals expressed by the recent “Control opacity at scale” feature. It further reaffirms the vision that Figma can be the gold standard for creating actuall

Today: As an agency, we’re frequently starting new projects for new clients. We’ve evolved a set of best practices for Figma file organization, per-client design systems, etc. These best practices have been captured in a Starter Project project in Figma. However, to use this Starter Project each designer must duplicate each file in the Starter Project individually and then move them over into a new project. Idea: We’d love to see Figma support duplicating projects in addition to the existing file duplication functionality. This would be a small but noticeable improvement in efficiency for spinning up new client projects.

Hello, I will mention the problem to solve, then I will explain how my idea could solve it. Please vote for it if you need it as well, thanks. 1) The problem to be solved The precise Creation Date of a file is a key information for many users. It is not easy to find, and not available for every plans… Currently, the only way to find it is through the “History version”: The mental model of the user has to be “Thinking: Past version” instead of “Thinking: Metadata of the file”, which is an incoherent mental model for many users. Because, if the creation date is indeed a past version, it is actually the pillar version, not just a past version. This model is incoherent with many users’ habits as well, because a lot of softwares and OS include the Creation Date in basic metadata, often under the same Properties menu than “Author”, “Modified Date”, “Extension”, etc. A Paid Plan is often needed to scroll through many revisions. Though, this basic metadata should be available for every plans.