Suggest a Feature

It seems that previously link previews were updated in slack to show what was being shared instead of the entire canvas. I missed that and now my links are just links, no preview. Which is better than previewing the entire canvas still.I have the same suggestion for link previews in Teams. Please stop showing the entire canvas in Teams previews and either show just what is being shared, or just don’t show anything.

subject  UI/UX 

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.

In Finland, we have to attach the invoices to all card payments for bookkeeping. Now I need to every month to go to Favro and manually download the invoice. Please add a feature where I can define an email address for the invoice emails and automatically send new invoices in an email with the PDF invoices attached so that we can automate the download and processing of the invoices. The subject of the email should have the same structure each month ("You Figma invoice YYYY-MM-DD) and the PDF invoice name should be unique and contain the date of the invoice, for example, Figma incoice YYYY-MM-DD

Figma needs an autolayout option for tables, or grids. None of the extensions or apps work well. Designers like me need to make grids all the time. Right now, I make autolayout rows, but they invariably need to be synced with the column header, which I do manually by editing fixed width.  Please add an autolayout for grid that would allow items to be in both a column and a row. 

Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.

Currently, if you copy + paste a figjam flow into a Design file, the Connector Lines stay fully functional – they stretch and adapt as you move their origins and destinations around the canvas, and you can move their origins and destinations to your frames, components, etc. I’ve been using this to show user flows within my UI designs, not only for ease of sharing with other teammates (no need to give in-depth walkthroughs), but also for easily identifying missing states within a flow. It would be great if a) the Connector Line was added as a tool to Figma Design, or b) basic lines and pen vectors had the option to act as connector lines – attaching to anchor points on objects and components, scaling when the endpoints were moved, and able to be adjusted with mid-line handles.

Hey there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

I know that you can crop one-by-one by using the picture crop feature in Figma. But that will be a very tedious work! I also know there’re planty plugins that can crop pictures. After doing the work, they’re automatically downsizing the picture and not keeping the original pixels. It makes the developer’s measurement impossible:

Scope VariablesI would like to suggest an improvement.When I apply it to the desired location, first need to remove the "show all" option, but considering that I'm accessing a single item, I'll want to select only that option.If possible, it could display the item without selecting it, and if I need to select everything, I have the "select" option for that.Thank you very much.  

Great to see the addition of dividers. Would really love the ability to add a name for each divider, because this still doesn’t solve the issue where we need to create an empty page titled “{Section Name}” to call out what the divider is actually dividing.

Hi! I upgraded my Figma account from using the free version to the basic plan. Since I did that I can no longer switch to design mode when I could do that with my free account. Please can someone fix this asap. Otherwise I will downgrade my account.

Artificial intelligence is moving fast, and one concept that keeps coming up in real-world applications is the AI agent. Many people understand the theory, but fewer know how AI agents are actually used in real projects. To make things clear, let’s start with the AI agent definition and then look at practical examples.AI Agent Definition in Simple WordsAn AI agent is a system that can observe its environment, make decisions, and take actions to achieve a goal without constant human input. This is the core idea behind the AI agent definition.Instead of following fixed instructions, AI agents: Analyze data in real time Decide what action to take Act independently Improve based on feedback or learning This ability makes AI agents highly useful in real projects across different industries.How AI Agents Are Used in Real ProjectsAI agents are not ju

I would like to highlight all the connectors from a given object in Figjam. For example, if I have a block that has several connectors coming into and out of it to many other blocks, right clicking on the block and “highlight all / highlight incoming / highlight outgoing” options. It would make all the other connectors on the screen transparent or greyed out so that I can easily see which objects are connected to my object and how its connected.

I often work across multiple pages within a single Figma file/project, and I’d love the ability to open different pages as separate tabs in the desktop app—just like I can open different files. Currently, I have to either open and close multiple pages many times to get what I need from other pages, use multiple windows or duplicate the file, which isn't ideal for managing design systems or multi-page projects.This would greatly improve workflow efficiency for designers managing large files or working across different sections (e.g., desktop vs. mobile layouts) simultaneously.Please consider adding support for tabbed views of multiple pages within the same file.

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.

It would be really helpful to be able to use a variable to set a Type Style’s Letter Case (under the Type Settings meatball menu). It could be a String Variable, and the options would be “As entered”, “Uppercase”, “Lowercase”, “Title case”, and “Small caps”. I personally use modes to switch between different brands, and some brand styles require uppercase while others don’t allow it. This suggestion may be a small feature in the grand scheme, but I wonder if others would also find it useful.

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case. We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps). Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1). We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route. Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use c

I just want to adjust the page settings for each page “frame” so to speak so I can make it wider. It’s not clear that this is possible.

hey there! variables seems to be super nice but what i am missing is that if i make a colour alias to a specific collection - i can’t set the opacity separately (e.g. colour 50 with 20% opacity) So basically i want the colouyr to be from another collection and i want to set the alpha seperatly (controlled as rgba - since i dont need it as opacity) Example how we can fix this in token studio:

copy comments from a Figma file to another one while duplicating/copying content/designs.

This is so annoying. I shouldn’t have to use the web version to disable this. FIGMA should allow me to turn this off in the settings. I don’t use Figma every day and I certainly don’t want it to open every time I log in. Clearly, this has annoyed several users but you fail to listen. STOP FORCING ME TO OPEN FIGMA AT LOGIN!!

No brainer. I’ve either had to ask clients to record a loom of themselves going through a Make prototype or me having to screenshot EVERY SINGLE PAGE of the prototype then send them PDFs so they could comment on it.If there’s a new QOL feature that’s gonna be added to Figma Make, it should be commenting.

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.