Share Your Thoughts

My Figma files are growing with screens, especially example screens to showcase various states. I’d like to keep them organized by arranging them in separate pages, but the thing is, I need to be able to prototype from one screen to another, over different applications to showcase a complete user flow. Would there be a feature one day where you can prototype between different pages, like Excel for example, where you can refer to cells in other tabs or even files. Would be nice.

I often work with Figma files that look great visually, but SEO performance sometimes drops after development.What best practices do you follow to ensure proper heading structure, clean HTML, fast load speed, and SEO-friendly layouts when converting Figma designs into live websites?I’ve been documenting my workflow for SEO-friendly development here:Rupak ChaulagainWould love to hear how others handle this during handoff and development.

Hi,“Hide prompts when sharing a Make prototype” seems extremely straightforward, but is not yet possible, thus this feature request.I love working with Figma Make and want to integrate it into the prototyping workflow. Unfortunately, sharing Make prototypes turned out to be a real headache. But without being able to share a prototype externally (and temporarily), the whole Make prototyping workflow doesn’t make sense, since copying the prototype pages into design doesn’t copy any interactions or animations. The goal: Share the Make full-screen preview with external viewers, without showing the AI chat history # Problem 1: Prototype viewable for logged-in users onlySharing did not work for not logged-in users, for whatever reason. Figma support couldn’t help either, thus it might be a bug.Workaround: Create a free account for the viewer, then share the full-screen previewTo shorten and speed up the wh

I was pretty impressed with Figma Make. I used 2300 credits on a project.Today I booted it up (same project) and the quality completely dropped off. The work has been unusable.Even simple things like the AI saying they added an SVG to a background of a section. It doesn’t show up, asked it to add it, or change opacity, or change size, and it goes through reasoning, says it’s fixed, and it still doesn’t show up.Other things like using the wrong color palette, even after being told to refocus the design on the color palette.Most things are coming out as cookie-cutter template style generic designs now.Is today a bad day for the AI or some bug behind the scenes? Is it because of the credit limit? If it’s a credit limit situation, why can’t I just purchase more capacity? I shouldn’t have to wait a month to have consistent work produced by the tool.If I can’t purchase more capacity is there any other work arou

Give Figma the ability to display an artboard(s) of one Figma file to another Figma file. So, rather than copying and pasting between two files (detaching it from its source of truth), the designer can “insert/link” the artboard to be displayed on another Figma file. Then, if the inserted artboard is updated, it will also update in the file where it is inserted (or any other instances). Very much like components work today but w/out the need to turn the entire artboard into a component.

An edge case however I’d love to see this update eventually. I have a segmented button component that contains nested button component variants. This segmented button component lives in many different places in my UI, utilising the different forms of the nest button component (text , icon, icon and text) I’d like to be able to set a min width to the nested button components inside my segmented button component instance WITHOUT having to set the min width to the master button component.

The title case isn’t accurate. As it also capitalizes: articles (such as “a,” “an,” and “the”) conjunctions (such as “and,” “but,” and “or”), and prepositions (such as “at,” “by,” “of,” “to,” and “on”). In my opinion, the better naming would be “Capitalize”. Figma team can also consider adding “Title Case” and “Sentence Case” options separately.

I happened upon this quick action: “Debug broken fixed-scrolling layers”. I searched Google and this Forum, and I can’t find any documentation or mentions of this feature at all… Figma team, I would love to see documentation for quick actions! It would help in scenarios like this (I found a quick action and I want to learn more about it). It would also help Figma users discover useful quick actions! I’m sure there are tons

You can embed YT videos into Figma Slides, but appears to lack Vimeo support. Also, we can’t change the Embed settings (turning off suggested videos, etc.) Would love support for these!

It would be really helpful if you could add a setting to Components that allows for “Scale Strokes & Effects.” Doing it at the component level would allow icons to be made with strokes rather than fills which is way more versatile and agile for making updates and modifications. Right now you have to use K Scale to “scale” them which is unfortunately NOT intuitive. It’s all about consistency and efficiency - this would help a lot.

We use pages as rounds of revisions, so it would be nice that in the page. We could just section out the frames we presentation. I know it’s not best practice to use design file as slides function, but it’s just faster to design in design file than the slides. And there are some archives slides in the same page that I don’t want to show in presentation mode of the page, but it could not be done unless I remove them or hide them. So could we have a function to manage what slides to show and hide based on the section, and use section as the prototype link? 

Same as in Slack or Outlook, would like to not trouble my commentees at odd hours and just send the comments I make outside of hours , inside office hours!

Hello everyone! I think having a shortcut to open/close the local variables would be very helpful. For example in cases where I’m prototyping and need to access the local variables to ensure the accuracy of the variable names or values that I’m assigning in the interactions. Currently, if I want to do this, I have to switch between the prototype panel to the design panel in order to open the local variables, check them and then go back to prototype. Note: I am aware that it is possible to keep the local variables window open, but this often leads to numerous bugs in the prototype. For example, when it is open, I am unable to drag the prototype interactions to reorder them.

The font size for Figma’s UI is way too small. I actually get mad every time I use Figma. I can’t believe there isn’t a way to adjust it in settings. There is no way the application complies with ADA requirements.

It looks like there’s only one input field in the settings to set the language, and there isn’t a button to add multilingual variants. What should I do to create a variant in another language? Or can I handle it another way by directing to different URLs? For example, I want users with their system language set to English to open mydomain.com, and Spanish-speaking users to open mydomain.com/es.

Hello 👋 First, I’m happy about the opportunity where I can make an impact on this amazing product. My idea is pretty simple but can make a huge difference in the way we share files with stakeholders and colleagues. I suggest adding the ability to give different access (viewer/editor) for pages within a Figma file. Because in most cases, we’re trying to include a whole project, feature, or function, whether small or big, in one Figma file - it becomes a real pain-point if the lowest level of grant permissions it’s the file itself instead of the pages within the file. I’m sure a lot in this community can agree with me that many times you gave people access - it was relevant to certain areas of the file, and less to other areas. I want to give content writers access to a specific page where they can edit and review content. I want to give developers access to a specific page where they can play

When a text element is set to Uppercase, it shouldn’t spellcheck improper casing.For example, below I’ve typed “THis”, which would be incorrect should it be standard case - however, when uppercase this is irrelevant and slightly distracting. 

Text weight should be allowed as a component property. Not as overrides or manual variants but simple text weight or size switch. I want to stop creating multiple duplicate variants within a component just for a font size change or a font weight change. I don’t think there’s any feature like this yet unless I am missing something.

Whether you search from the left side bar or press Shift + I, the thumbnails are too tiny to display details. Some of the assets would look similar from afar but if we’re able to resize the thumbnails as well as the window, it would reduce time dragging the wrong component.

Hey there.As you know, we can already apply multiple fill color or apply multiple variable color to a single frame. But we can only apply one “style” to a single frame. The problem comes when you want to give a single frame multiple effect. assume I have a focus ring, and a subtle shadow. my elements might sometimes have shadows, and sometimes have a focus ring, and in some cases, they might have both. for now, if I want to create styles, I need to make 3:focus-ring-neutralshadow-smfocus-ring-shadow-neutralI understand that the logic behind the style was to make layers of attributes (styles) all saved as one name. but in cases you want to mix a few things, you have to save all combinations that you might use. is it possible that to be able to add multiple effect style to a single frame instead of creating more customized styles? Image below shows how “Fill” has a plus button and can have multiple values (Varia

There should be a way for Figma Admins and Workspace Admins (and potentially Team Owners) to be able to communicate Figma-specific news and information to members of specific projects/connected projects, teams, workspaces, or the entire organization (and groups, if they are ever added)Currently, organizations have to use email, slack, Microsoft Teams, or other tools to communicate about Figma topics, and these messages are easily overlooked since they are outside of a Figma context.It would be helpful to have a way to message discrete groups from within Figma. Examples of things that need to be communicated:We made a major design system upgrade New sticker sheets/templates are available We have deprecated holiday colors. Please remove any hard-coded holiday colors in your active designs. We have a new Workspace for xyz New reference designs are available in your Connected Project. Please check the comms portal for more ab

When a change is made to an instance, any updates made to the original component after that do not carry over. This is very frustrating and results in me updating each instance. 

I'd like to be able to select a component and see all instances of use in the file. Sometimes my files get so large that I lose place of where I am using certain comps, or I am jumping into someone else’s file and it can be super confusing, if I don’t know where they are using that component. 

I’ve had multiple dev’s ask me where to find the core token to a second-order token value for a color when referencing mocks that use our design system. They are unable to see you can hover over to the more icon, and the only “actionable” thing they appear to be able to do is “copy” the variable name to their clipboard. Just asking to leave the “more icon” visible by default, there’s no real reason to hide it. 

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