Suggest a Feature

Hello all 👋 I was wondering if it’s possible to make a frame adaptable to the browser screen height dynamically when prototyping. I found a plugin (Auto resize height) but no sure if it’s for this purpose, anyway, it’s seems to be broken. Thanks for your help!

From what I see, Figma is struggling with variable heights, especially the ones relative to the viewport (heights of design elements vs height of the prototype and its elements when previewing, relative to the viewport). For example, you can’t have a section on a homepage be 100% viewport height both in the design and when previewing (which is the MOST ESSENTIAL, BASIC necessity in web/app design). Suggestion to fix this:A new option for Frames, a separate set of dimensions called “Viewport dimensions” These dimensions will NOT affect frame dimensions. Instead, these dimensions will provide variable boundaries which design elements can refer to, and adjust accordingly in both design view and when previewing a prototype.For example, your main frame is 1920 x 8000 in design mode and you have a section (auto layout) which should be “full screen height”. This can be a 1-click solution, here’s how:You select the main frame and set its “Viewport Dimensions” to 1920x1080 You select the sectio

I want to display the newest created blog post in a section of a Figma Site. I’ve connected the CMS collection to the frame and set the limit to be 1. It then only shows the top item of the collection list. But when I create a new item in the collection (a new blog post), it’s added to the bottom of the list. Then trying to reorder it and drag the new list item to the top, it stays there for a millisecond, but then the item slides down to the bottom again. So I guess that’s a bug. A workaround is to drag the new item to row 2 and then take the top row and place it below. That way I manage to make the newest item end up at the top of the list. But will be more cumbersome as the list grows. So a feature request for the future would be to set which sorting order you would want in the frame itself. So there I can select “Newest to oldest” or “Top to bottom”. Then I wouldn’t need to maintain the order of newly created items all the time if I were to use the list as blog posts. Alternatively

Currently, Figma Sites only allows publishing to either a base domain or a custom domain, but not both at the same time. It would be highly beneficial to support publishing to both domains simultaneously—using the base domain for internal testing/sharing and the custom domain for live access.This would enable smoother staging workflows, reduce reconfiguration effort during updates, and align with platforms like Framer that support multi-domain publishing. Use Case:Teams often want to: Use the base domain for internal reviews, testing, or quick sharing Use the custom domain for public/live access During iterations or updates, having both domains active helps avoid disruption to the live site

In Sketch, holding Option + Command allows users to drag a selected object from anywhere on the canvas, without needing to hover directly over the object. This feature significantly enhances workflow efficiency, especially in complex designs where objects may be obscured or challenging to click precisely. In Figma, dragging an object requires the cursor to be directly over the object or its bounding box, which can be limiting in certain scenarios. Introducing a similar functionality in Figma would streamline the design process, reduce unnecessary clicks, and improve overall usability for designers accustomed to this behavior in other tools. Implementing this feature would be a valuable addition for users transitioning from Sketch and would enhance Figma’s user experience by providing more flexible object manipulation.

Hi Figma Team, Why can’t user set preferred screen size as default in 'Options menu"? can we have this feature in future?

There is no shortcut button for copy link to selection Copy link to selection is imprtant for working with llms - it’s become a high priority feature - need to have a shortcut  

When creating an Open Session link, I would like to only allow certain email domains to use it. Our institution does not allow Guests and a link that will allow anyone access is not allowed. We only want our authenticated users to have Open access. 

Engineers on my team just noticed that they can’t see and export local variables unless they have edit permissions. This is a huge limitation since not everyone on my team can have edit permissions due to licensing/cost. My ideas is to keep local variables visible to View Only collaborators. They should not be able to edit the variables.

In the new UI, the Figma tabs aren’t readable on the lighter ver.Could you please add the option for a darker tabs line like in the old UI?See example below.  

Currently, only Preview and Code edit modes are visible. Are additional editing modes accessible?

It used to be that when you changed the fill on a shape from solid to a gradient, it would make the second gradient color the existing solid color with an opacity of 0%. This was great and really sped up my process. In the last update they changed this behavior so now it makes the second gradient color some arbitrary darker shade which just adds more clicks to my workflow and some annoyance especially since it used to work better… Is anyone else having this problem?

ngl, the new ui3 is pretty good. the only thing i dont like is the toolbar position. im still not used to it. maybe add an option to move it to the top?

Figma does let us move an object’s rotation origin with Alt + R / Option + R in the design canvas, but Smart Animate only documents support for matching layers plus property changes like position, scale, opacity, fill, and rotation/orientation. Because rotation origin is not listed as a Smart Animate property, prototypes often don’t honor the off-center pivot the way you expect.Use case: Opening door. Pendulum motion.

I’m surprised that after three years, FigJam still doesn’t support vertical text alignment in shapes. This has been a longstanding request (as evidenced by this older forum thread), and it’s a must-have for creating clean and professional-looking diagrams. Being able to align text to the top, center, or bottom of a shape is a standard feature in most design and diagram tools, and its absence in FigJam makes it harder to organize content quickly and consistently. Please consider adding vertical text alignment options to improve productivity and the overall user experience in FigJam.

I think it would be amazing if there is a font filter Option for the style like, Handwriting, serif, sans!

I need to see the full list of a designer files to transfer ownership to new team member

When using typographic tokens and variables that have pre-determined values for the line-height, the only way to alter the line-height is to detach the variable from the text element and then manually edit the values in the "Type settings" palette. This essentially defeats the purpose of using tokens and variables and makes the detached item hard to update quickly in the future.Please consider adding more typographical overrides in the "Type settings" palette so that we can change the values without breaking the variable connection.  

Is there a way to add ‘Match Size’ when using the Paste to Replace function? (CMD+Shift+R) I have tried a few plugins, but Paste to Replace is more smooth and quick.

Right now I’m not able to refresh a page in figma make preview. I have to close the tab and again preview it to refresh it.

Right now it seems like the ‘default’ variant is set based on which variant is ‘upper leftmost’ in the variant container frame. Instead, I suggest decoupling arrangement from precedence, and using the property ordering functionality to determine the default variant. The default variant should simply be the one with the first value for each property, regardless of where it’s placed in the variant frame. This would allow teams to set defaults directly from the properties panel, without having to move components around. See this thread for some more context: How to set defaults / precedence of variants with multiple properties?

Dear Figma,I wanted to bring to your attention that we are in the 21st century, and there are devices specifically designed for designers, such as tablets. I own an iPad, which has an amazing display and can be used with a keyboard and mouse. However, I currently use it only for viewing my designs because Figma, the professional tool I rely on, does not fully function on my iPad. This leaves me with a few options: sell my expensive iPad to buy a PC or laptop, which is less comfortable for me, wait for an iPad update from Figma before GTA VII, or use it solely for watching movies. I wanted to remind you that tablets exist for a reason, and it would be beneficial if Figma could support them more fully.

It would be highly beneficial if we could create Variables for Effects (Drop Shadows, Layer Blurs, etc.) just like we do for Colors and Numbers. Currently, handling different shadow intensities for Light and Dark modes is tedious because we have to switch Styles manually.By adding this feature, switching between Light and Dark modes would become much more seamless and effortless, as shadows could automatically adapt to the active mode.

 I’m building a component library for Figma Slides and ran into some issues:Users can use my published variables / styles inside the components, but they can’t use those same styles directly when creating content themselves in Slides.For example, I built a dark/light mode switch with variable colors. Works great in the components. But if someone adds a new text box, they can’t pick those colors from the library.Would be really useful if published library styles/variables were available directly in Slides, so native content can stay aligned with the rest.

ContextWith the Figma MCP server's `get_design_context` tool becoming a key part of design-to-code workflows, there's a friction point around how variable group separators are handled in CSS output.Figma uses `/` to create variable groups (e.g., `blue/600` creates a `blue` folder containing `600`). This is great for organizing variables in the Figma UI. However, when the MCP generates code, the `/` is preserved literally in CSS custom property names: `--blue/600`.The ProblemIn Tailwind CSS — the default output framework for `get_design_context` — the `/` character is reserved as the opacity modifier delimiter:bg-blue-500/75  →  background-color: rgb(59 130 246 / 0.75)So when MCP output includes `bg-[var(--blue/600)]`, Tailwind's parser interprets `/600)]` as an opacity value, producing broken CSS.The MCP works around this by escaping slashes as `\/`, but JavaScript consumes the backslash in normal strings. This forces every token reference into a `String.raw` template literal:```jsx//