Share Your Thoughts

When using the color picker, if the object you’re picking from has a color style applied, the color picker doesn’t apply that style to the selected object — it just applies the hex value (or whatever color model you have set) of the pixel you click. This can lead to messy colors not adhering to your style guide. Instead, the color picker should apply the color style of the clicked object if it has one. (You could click the stroke to apply the stroke’s color style, or the fill to apply the fill’s color style.) If you do want to be able to pick the pixel color instead of the style, there could be an additional modifier key to hold while clicking. With the current functionality, if you want to apply the same color style to another object, you first have to click the already-styled object to see what style is applied (assuming you may have multiple similar shades and can’t eyeball it), then click the object you want to style, and then find that color style in the list and apply it. The pro

Our design system devs asked us designers for a better way to compare changes within our component specs between updates.  We stage our components as instances in a separate spec file from the library file the components are published from.  Each component and variant is contained within an individual section acting as a wrapper.  The wrapper is where we enable a “ready for dev” tag to capture a version history.  Using this method we’ve run into a few obstacles: Sections don’t capture granular changes, we’ve had to switch from wrapping our component instances in sections to frames for a version history to be recorded within the compare/diff window. Ready for dev version history can only be viewed by first entering dev mode, then entering focus view on the versioned frame (it doesn’t show if you enter focus view from design mode). `Compare changes` within the standard dev mode view does not show this information and instead compares against the original component or shows version histor

Dear Figma Team,I would like to provide feedback regarding the behavior of stroke and padding when exporting designs for CSS implementation. While Figma offers excellent design tools and helpful CSS hints, there is a notable inconsistency between how strokes are visually represented in Figma and how they translate into CSS code. This discrepancy can lead to confusion and extra work during the development process.Issue DescriptionWhen designing input fields in Figma, strokes (borders) are measured separately from padding, and padding is displayed as starting from the outer edge of the element's frame. However, when exporting to CSS or implementing designs manually, borders are treated differently due to the CSS box model: In CSS, padding is measured from the inner edge of the border (stroke). Figma suggests using box-sizing: border-box for correct border inclusion in dimensions, but it does not account for the fact that stroke thickness affects the visual padding. Example ScenarioIn m

Context: In Figma Design file, setting padding requires adjusting both sides (top +bottom, right+ left). While having the ability to combine longitudinal sides as one and latitudinal sides as another is helpful - it still requires to insert the same number two times(individually) for the times when the padding is same for all 4 sides for anything, which can be time-consuming and frustrating.Idea-suggestion: Introduce an option to apply equal padding to all sides with a single input, streamlining the process and improving efficiency.

If I open a file and accidentally make a change, then immediately undo it, I still get a new entry in the list of file versions. Now everyone else thinks something’s happened and has to figure out what it wasn’t.As one example of an easy accidental change, it’s not uncommon to accidentally move something when you select it to inspect it.If I undo changes back to the first change I’ve made in that session, no new file version should be shown. I didn’t make any changes; there’s no new version. Including a version in the list is confusing.

Silakan hubungi Call Center agoda 0831_21288181, tlpn/WhatsApp Layanan pusat bantuan resmi agoda

We have a navigation bar component in our shared library. We want the basic dropdowns and user profile info to overlay when clicking these menu items. Currently all overlays break when bringing in a component, and we have to make a local version of the library component. It would be great if the overlay from the library can work wherever it exists, rather than having to duplicate the overlays in every location.

make duplication of frames and other forms not horizontally, but in the visibility area of ​​the canvas, because it often happens that I duplicate something, and then look for this something, if I duplicate it next to another frame, which is out of the visibility area, while vertically there is space for duplication next to the duplicated frame, and the vertical enters the visibility area

Selling resources on the Figma community could be optimized  with these features:Break down of purchases per subscription type setup by seller in resource Metrics tab eg. Monthly vs Annual Add a notification when someone unsubscribes and detail the subscription type, doing the math each month to measure churn and user count per subscription type is a trrible waste of time.  Show monthly churn: New users per sub scurption type, Lost users per subscription type Trends graphs per sub type Allow retention offers or user feedback triggered by user unsubscribing 

I use Figma for UI and graphic design but also for illustration and some motion now. And one thing that I miss often is brushes ! Vector ones of course. Not even complicated ones, without transparency, maybe just a pencil, a paint brush and a marker. Maybe just the ability to add automatic variations to the strokes to give them a more natural or hand drawn feel. I tried Variable-Width stroke plugin but i wasn’t convinced. The option could be add to the stroke panel, in the advanced stroke options. Am I the only one who dreams about it ?

So you can loop videos now in prototypes, but I am using them ads backgrounds a lot, where it would be cool if the transition in the loop is more smooth in stead of a hard cut. Maybe it is an idea to add the option to have videos ‘boomerang’ forward and backward in a loop.

I wish that I can turn on or off each properties in nested instance, so that my team will understand which properties are allowed to use in the Component

Suggestion: It would be incredibly helpful to have a status update for variables that have been created but aren’t being used anywhere. Additionally, for variables that are in use, a way to map or locate all their instances across the file would make managing and organizing them much more efficient.

I can’t believe this basic text formatting issue is still unaddressed in Figma in 2025, but I need to indent a full paragraph — every line if it, not just the first line, and not with a quote. Has anyone found a workaround? I know I can give this paragraph its own text box, but that just stinks. Other ideas? Plug-ins anyone has found that work? Thanks! And Figma — for the love of all that is holy, please fix this.

Similar to Figjam, I would love to see sticky notes available from the bottom toolbar maybe under region tools. Currently having to copy them over from Figjam or older Figma projects. Figma toolbar - Region Tools with Note 

I recently did a lot of cleaning up my company's Figma file structure and unfortunately comments can't be moved from one file to another. I've consolidated a lot of files into one to make it easier, but I have to manually re-write the comments so I don't lose them.

Add access to variables in Dev mode. The variables are needed to be visible in the Dev mode, because they want to see all variables when we adding new theme or make any changes, so it’s to hard and impossible to take all changes from the components and the plugins doesn’t match our way and needs.

By smoothing strokes we can make some designs look more soft and clean, it would help a lot.

In case it hasn’t been asked for yet, I’d like the shiny new duplicate bar in Figma AI to work for autolayout elements within a component. Right now it only works outside of components.Here’s an example. Say you want to create a checkbox group component. Right now, you have to do that by duplicating the maximum number of elements you expect to have. If I create a component with 5 checkboxes and you only need 2, you have to delete 3 of them. If you need 6? Too bad, you have to detach. Being able to use the Figma AI feature would allow me to create a group with 2, and let the users duplicate as many as need.As a bonus, if there were some AI smarts around interactivity - think radio buttons, where only 1 should be selected at a time - that would be nice too.

As it’s shown in the attachments, when there is arrows from box to box in FigJam, and each arrow is in different color, the top one show both sides as related to it although each arrow is a regular one with one side of head

It would be amazing to see what slides have been viewed or interacted with. Or even to see if a link has been clicked.

Titile.From my knowledge, you can only wrap a section from two screens, but in my workflow, I often wrap a single screen. This might be just me, but I suggest adding the ability to wrap a single screen.

HiI need to see files people in my team can view. Right now I only see a number and I have to check each project and file one by one.I need to see the accesses and change them in the admin dashboard.

HiFirstly, https://forum.figma.com/submit-feedback is not working but it’s in the application for submitting feedbacks. I have 4 front-end developers and I need to have a role for all of them like @front or @dev when I want to comment something, rather than mentioning all four of my devs. Discord has the same feature and adding it I think would be a great feature. Also, I need to send specific updates when I make something ready for dev to specific people. Right now if you mark as ready for dev, all people in the file get the email update.

Hello, good tidings. In my opinion, its better Ux to have a log out button on the figma work sheet space. This should be listed on the options when the figma icon on the top left is tapped. “Back to files” and then “logout” is  most times extra task. What do you think?!