Share Your Thoughts

Describe the problem your experiencing and how your idea helps solve this Screenshot and sample file below. I’m using an iMac sized frame with extended height. This issue is exacerbated by the fact that this is the now the default view when using multiple flow starting points and is the only way to actually change the flow starting point. So you have a constant trade-off of whether you want to see the Figma controls or your prototype’s. Annoying as hell. EDIT: When sidebar is hidden, the fixed header is visible but inaccessible. As soon as the cursor hovers near it, the Figma UI appears over the (clickable) website header. Wow… Add as much context as possible (screenshots, Figma files, mockups, etc.) https://www.figma.com/file/WlYbWyHwtBGEFZihdMt2az/Bug-Obscured-fixed-header?node-id=0%3A1

"Please add support for fully custom workspaces in Figma, similar to Adobe Illustrator or Photoshop. Users should be able to move, dock, and save custom panel layouts to fit their personal workflow and make designing easier."

This is functionality I used to use in Sketch, and I really miss it! Now that Adobe owns Figma, I wonder if this feature could be implemented. I work with a team of visual designers and we use Figma for all our design files now (we love it!). But we still do more complex compositing in Photoshop. Rather than the hassle of saving a PNG every time I make a change to a graphic and re-linking it in Figma, I’d like to be able to import the .PSD and have it update as a dynamic link. Let me know if anyone has questions about this. Thanks!

Hi everyone,I'm learning Figma Variables and I'm facing an issue that I can't figure out.My setup:Figma in Google Chrome Free (Starter) plan Personal Draft file Latest Figma UI (UI3)What's working:✅ Color variables work perfectly. ✅ I can create String, Number and Boolean variables. ✅ I have set the correct scopes (e.g. String variable includes Text content).The problem:String Variables I created a String variable (e.g. Sign In Button with the value Sign In). According to tutorials and the Figma documentation, I should be able to bind it to a text layer's Text Content. However, when I select a text layer, I only see variable options for typography properties like Font Size, Font Weight, Line Height, etc. There is no option to bind the actual text content. Number Variables I created Number variables. They don't appear for properties like Corner Radius, Padding, or other numeric properties where tutorials show they should. Boolean Variables I created Boolean variables, but I can't

I am quite certain I am not a robot. However, when creating an account just now using a work-specific email so that I could accept an invite to a Figma team, registration was a very frustrating affair. The CAPTCHA was far too long (5 questions), the instructions were maddeningly vague, and I failed multiple times. Each failure meant having to do the entire 5 question CAPTCHA again from the beginning. I attempted to switch to the audio version, hoping that might be easier for me to understand, but I failed that too. As a result, registering a new account took at least 15 minutes, and had it not been necessary for a work assignment, I would have given up altogether.Please consider changing your CAPTCHA to something that can be more easily completed by humans. While I certainly understand the desire to avoid spam signups, other websites with similar challenges have found approaches that require a user to, at most, click a checkbox. Perhaps Figma could follow a similar model.

Our design system leverages mix blend modes for hover states so our icon buttons appear on any background color and remain accessible, without needing separate hover–on-primary, hover–on-secondary, etc tokens. We use multiply for light theme, and screen for dark theme. It would be really awesome if we could apply blend modes directly to the color variables, OR support blend modes as variables in general. Our current work around is to apply the blend mode directly on each component variant, but this requires us to define separate light and dark theme variants. would be great if we could use variables here to have it automatically switch between light/dark.

Je suis assez déçu de Figma ces dernières semaines/mois.Beaucoup de mises à jour qui changent la prise en main des habitudes. Pas grand chose mais chercher tous les 3 jours ce que l’on a l’habitude d’utiliser c’est exaspérant.Sans parler des regressions en chaine sur les slots, le comportement des autolayouts, les ratios qui recommencent à se comporter n’importe comment alors que c’était devenu un super outils.On sent bien que vous êtes en train débattre contre l’arrivée des iA mais s’il vous plait. Continuer de proposer un soft de qualité.

When working with variables it is really annoying that the Variables window closes on esc. I want to dismiss sample color or selecting another color from my styles as examples, but instead it closes the Variables window.

I’d love a toggle to turn Motion off in Present mode while I’m still storyboarding.This would be a great option for when I am just testing things out and don’t want to present just yet. Or when I want to make sure storyboards and frames flow well before getting distracted by the motion. Maybe this means I work backwards, but does anyone else feel this need?

With the admin updates that came out on March 11, there is one new feature that we would like removed or able to be turned off by an org admin.When a user requests an upgrade in Figma, this new feature allows the user temporary access to the functionality of that seat for 3 days (unless the admin replies to the upgrade request sooner). Here is the description from this article:To ensure users aren’t blocked from collaborating while admins review their seat request, they’ll be able to use the functionality of the seat they requested temporarily for up to three days. During that time, they can create new files and edit any files where their teammates have given them edit access. They will not be able to edit files they do not have edit access to. The temporary access ends immediately if the request is denied or expires.Prior to the updates on March 11, this was the behavior for dev mode requests -- users would get temporary dev mode access for a short amount of time while they waited for

Need a way to update padding numbers in sections instead of manually resizing it every time. The current padding of 80px look very small in some cases, hence the request. Or if we have any way to do it today, please let me know.

Is there a way for someone to download the presentation as a PDF when they are viewing Figma slides in presentation mode?Maybe I’m missing it, but wondering if this feature exists? Would help our org out a lot as many clients wish to have PDF versions of our pitches. TY

Hi Figma team,I'd love to see the following three improvements added to Figma Slides:1. Linked slides across presentationsAllow a slide to be "linked" from one presentation into another, so that editing the source slide allows updates it everywhere it's linked. This would be huge for teams that reuse boilerplate content (title slides, team bios, product overviews, legal disclaimers) across multiple decks; right now, updating that content means manually editing every deck it appears in.2. Copy selected slides to a new presentationAdd the ability to select a subset of slides and generate a brand-new presentation from just those slides. This would make it much easier to spin off a lightweight, audience-specific deck (e.g., pulling just the relevant slides to send to a vendor or client) without having to duplicate the entire deck and manually delete everything that doesn't apply.3. "Send slide to end of deck"Add a quick action (right-click or keyboard shortcut) to send a slide to the end o

With the latest UI panels updates, I now lost the ability to directly select a HEX value straight from the Fill layer. A huge downgrade, now I need to open the color panel, switch from HSB (that I use frequently) to HEX, and copy from there. Please bring back direct input field in the Fill layers to have ability copy color value directly.  

Request: Add option to import multiple Jira issues at once in native Jira Widget. Story: We started to use FigJam for our team collaboration (±20 ppl). We have feature breakdown in Jira, we need to import Jira issues to board. It is possible to now either insert one by one or whole project. I need something between. Either import this list of issue Keys or import this JQL result. Jira projects usually contain hundreds of issues, so importing whole project is useless. Doing it one by one for 40± issues at a time is real pain.

For audits i am often adding hyperlinks to sections and thought it would be a great feature to be able to add a hyperlink to the heading instead. 

Hi, I wanted to suggest preset colour options for Sections in Figma, similar to FigJam. The default grey colour blends into the default canvas background meaning I always need to choose a custom stroke + fill after using it. It’s an easy task but it breaks my flow to have to stop and change the colour of a section in the middle of whatever I’m doing. To be honest you could improve this just by changing the default colour from grey, but having some of the FigJam presets makes it a lot easier if you have different colour sections for categorisation.

Let us be able to add audio to the slides to give it more life. Imagine that after creating a presentation with your prototype embedded into it and some animations. You can finish it up with some amazing audio!

It’s the year 2023, and Figma still doesn’t have native table support. I just spent 30 minutes re-jigging all the “cells” in a four-row, six-column fake table because I had to delete one column, add another, add icons, and then manually re-fit/resize all the cells to get things to align properly. I can either fake a table row with a horizontal autolayout, or fake a table column with a vertical autolayout, but it’s still not a table. I want the ability to create a special frame called a Table, that: has an arbitrary number of columns and rows auto-resizes columns evenly based on content width has one or more Header / footer rows can scroll with overflow content (optional) has optional properties for hover / click states (cell, column or row) has optional properties for alternate-line shading can toggle columns or rows to hide as needed can merge or split cells as needed can set text alignment for a column (center, left, right, or currency / decimal) can set to automatically use monospa

I already have two set of position information. [984 | 2000] [ms]984 is where my red line is in the time line of animation, and 2000 is the total time available which is adjustable. I would also like to have the position if I select-drag a keyframe from somewhere within the timeline, sometimes it helps to know where I am.

Description:Currently, Figma Variables only support solid colors. However, many design systems use gradients as core brand tokens (e.g., multicolor accent fills, branded gradient backgrounds).Today, the only way to store a gradient as a reusable token is through Paint Styles, but they don't integrate with the Variables infrastructure — they can't participate in modes (light/dark themes), collections, or scoping.Request: Allow Variables of type Color to hold gradient values (linear, radial, angular, diamond), not just solid colors. This would enable:Gradient tokens that switch between themes/modes (e.g., a vibrant gradient in light mode vs. a muted one in dark mode) Full design-token parity with tools like Style Dictionary and Tokens Studio, which already support gradient tokens A single source of truth for all color tokens — solid and gradient — in one placeThank you for considering this!

it’s different from just using history. we are working on a file that was ongoing for years, some of the frames are old, some are new. we want to see what is the age of each screen to understand the timeline of our work. we could scroll back in time and see, but then we would had to jump between times, trying to discover and guess when a screen was created, rather then the possibility of just clicking on it and see the date of the creation

I think It’d be much better if Figma to stop treating its products (FigJam, Slides, Buzz, Site, Make) as separate file types and start treating them as page types within a single file.Every time Figma releases a new tool, it forces us into another siloed file type. If I’m working on a product feature, I shouldn't need one file for research and flows (FigJam), one for Exploration (Design), one for presenting to stakeholders (Slides), and another for campaign assets (Buzz).It breaks context and creates insane file sprawl for what is ultimately a single project.If these were all just specialized page types inside a single master file, everything would live under one roof: Page 1 (FigJam): Research & User Flows Page 2 (Design): High-Fi Mockups & UI Systems Page 3 (Slides): Stakeholder Deck Page 4 (Site / Buzz): Landing Pages & Marketing I know this clashes directly with Figma's tier/seat pricing model for different products, but purely from a UX and workflow perspective,

Hi Figma team,When creating Text Styles, Figma currently captures properties like font weight, size, line height, and letter spacing, which is great. However, color is not included as part of the Text Style definition.This means that even when a Text Style is applied consistently across a design, the color still needs to be set manually every single time. For teams working with a strict brand identity, where specific text colors are tied to specific text roles, this creates unnecessary extra steps and increases the risk of inconsistencies.It would be really valuable to have the option to include color as part of a Text Style, so that a heading style, for example, always carries its correct brand color by default.If there's already a workaround for this that I'm not aware of, I'd love to hear about it.Thanks for considering this.Justin Eleveld

Community / User RoleDeveloper / Engineer using Dev ModeThe ProblemCurrently, when inspecting components in Dev Mode, developers frequently only need a single line of code (e.g., a specific border-radius, box-shadow, or font-size) from the generated Layout or Style text areas.To get this single line, developers must manually highlight the text—which often results in accidental multi-line selections—or copy the entire code block and manually delete the unwanted lines in their IDE. This adds friction, slows down implementation, and introduces minor manual errors.The Proposed SolutionIntroduce the ability to copy a single line of code by clicking its corresponding line number in the Dev Mode code inspect panel.Interaction: Clicking a line number copies only that specific line to the clipboard. Visual Cue: Hovering over a line number could display a subtle "Copy Line" tooltip or a small copy icon to make the feature discoverable. Success Feedback: A brief "Line copied!" toast notification