Rolling out: Projects become folders 📂 ✨
Let us know what would make Figma better for you.
Recently active
It would be very useful to have an “Auto” font size option, so the text inside a sticky note automatically resizes based on the note’s dimensions. This is a feature available in Miro, and it makes a lot of sense for sticky notes, especially when working with boards that include notes of the same sizes.
When picking colors I’m always working in the HSL color system. When I want to change a color it makes so much more sense for me to be able to adjust the hue, saturation, or/and lightness rather than thinking about how edits to RGB might work, or trying to mentally decode hex values. Often I’ll want a color of a similar saturation & brightness but a different hue. Or a color of the same hue & saturation but different brightness. But in the Figma UI it defaults to showing hex values in the sidebar (or a color style name where the values are completely hidden unless I drill down): Hex values can be useful for developers (although lately we’ve just been using HSL in our CSS), but is not very useful to me when designing except for the rare case when I’m copy/pasting a hex value from somewhere else. It’s certainly not the primary way I want to see / work with colors. I’d love it if that display of HEX values in the UI was instead HSL. And secondarily, I’d love it if when a color s
When I have a layer or layers selected and I hit ⌥L to Collapse Layers, I always have to scroll up to find my selected layers.Ideally, the scrollport would remain focussed on the selected layers, if not the first.I think this is a regression, I’m sure it previously worked like this.
Ability to flag components as deprecated within Library or Design File Use “check design” feature to audit deprecated instances in current design deliverable. Alternatively use AI to run a similar reviewCurrently we are renaming the component by adding a suffix (Deprecated) so we can search for instances within the page.
Create a way to create short links (URLs) for sharing frames, prototypes, etc.
I'd love to have access to built-in variables that expose a frame's dimensions, allowing them to be referenced anywhere in a design.For example:{width} → 1080 {height} → 1920 {size} → 1080 × 1920This would make it possible to automatically display the size of an asset in labels, documentation, exports, or templates without manually updating the text every time a frame is resized.Besides saving time, this would reduce manual errors and eliminate the need to constantly double-check frame sizes, especially when working with large numbers of assets or ad creatives. It would help ensure that labels and documentation always stay in sync with the actual frame dimensions.Something like this.resized.
When creating hand-off documents I like to showcase user flows by using arrows between different UI elements. I have to use plugins to create these arrows at the moment. When playing with Figjam I notice it had a connector option - this is great. I would love it if we could also have this connector option inside Figma as it would be a HUGE timesaver for hand-off. I would like to think this would be a super easy update given that we can already edit connectors inside Figma. We just need a connector button in the toolbar like so:
Previously, when export the frames, the pdf pages were combined into one pdf file. Now, it suddenly changed with separated pdf files per each pages. So I have to merge the pdf files. I do not understand why it changed to this burden way. Please restore the pdf export function. Any other thoughts?
It doesn’t look like there’s an obvious way to change the order of exposed nested instances. Right now the order seems to be based on reverse layer order. It’d be great if the order can be manually adjusted.
We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.
So, we have Frames, Groups, and Sections, but I am still missing something. The next level of structuring: swim lanes to get a better overview of users in a flowchart. I’ve recorded what I mean from another software, and it’s pretty spot on! The neat feature is that the label of the swim lane remains fixed to the left when zooming and moving up and down the lanes. This makes it very easy to see where I am in the user flow as a specific user. Problem Definition: It is difficult to see which user in a flowchart I’m looking at. There is a need to have a prefix on every Section or Frame that clarifies which user the actual screen correlates to, i.e., Resident login screen, Supplier login screen. Request: Possibility to create a Swimlane, just like a Section but where the name gets fixed to the left when panning/zooming the canvas. And maybe later on, the possibility to collapse and expand swim lanes? And maybe later on, possibility to collapse and expand swim lanes?
Dear Figma Support Team, I am writing to inquire about the current support for color fonts in Figma. As a designer, I greatly appreciate the versatility and creative possibilities that color fonts bring to my work. I have recently been experimenting with various color font formats, such as OpenType-SVG and COLR/CPAL, which allow for intricate multi-colored typography. However, I have encountered some challenges when attempting to utilize these fonts within Figma’s design environment. It appears that Figma currently lacks full support for color fonts, as I have experienced difficulties with the proper rendering and editing of these fonts within the platform. It would be immensely beneficial if Figma could extend its capabilities to fully embrace color fonts, enabling designers like myself to fully explore the potential they offer. Color fonts have become increasingly popular, allowing for more expressive and engaging designs across various mediums. With their ability to incorporate vibr
When rebuilding or refactoring a component set, there's currently no straightforward way to seamlessly migrate existing instances to the new version if the original component set needs to be deleted.I'd love a feature that allows designers to map a replacement component (or component set) before deleting the original. When the updated library is published, Figma would automatically replace all instances of the old component with the new one.To make migration more reliable, Figma could:Match and transfer properties with the same names. Preserve nested content by matching layer names (e.g. icons, labels, badges). Use AI/Figma Make capabilities to intelligently recreate the visual state of the old instance using the new component structure. Provide a migration preview showing any instances that couldn't be mapped automatically.Example:I rebuild an entire Button component set to improve the structure and variants. Rather than manually updating hundreds of instances or maintaining the old c
In dev mode please place the assets panel above the code.because the code takes a second to generate it makes it feel like the assets panel moves right before you click it
Hello! I am a community advocate for FOF, Sofia for Bulgaria and we experience difficulties when we want to use Bulgarian Cyrillic in several fonts with the “Stylistic sets” feature, but Bulgarian Cyrillic just doesn’t work. When I try the same in Adobe Illustrator for example - there are no problems. The only solution we’re able to find is to change the font’s core defaults to this type of Cyrillic, otherwise, it is impossible to use the stylistic set in Figma. Best Regards, Daniel Dungyov
I’m working on motion graphics for a sequence of multiple hints in a video game I work on. I explain the issue in detail in this video: It’s incredibly tedious to have to change the position of the shape and then do the distance math to adjust its height because it’s unwilling to simply grow in a different direction. It really feels like I should just be able to grab the top layer bound and expand the height of the shape upward without all of this tedious crap.
Trying to take advantage of Figma Sites for our agency. It would help to have a pagination in Figma Sites CMS lists. I’m thinking of porting the articles and 100+ items on one page would be a terrible idea. Trying to see if someone else would love to have that feature?
Copy properties does not work as it did beforeBefore if i copied properties from one auto layout to another it copied everything, but if i paste properties onto a square or any other shape and then copied properties of that square - all info about the paddings would have been erased. It was easier this way to just copy the fill color, stroke and corner radius styles to a different looking auto layoutNow even if you copy properties from a shape it still keeps the paddings and gap size
We would love to be able to name a collection and set the default within the collection, rather than having the parent level of the collection be the name or the collection and the default.
Right now, when I export a PDF from figma, I expect it to be like a regular PDF from any other software such as illustrator. However, when I look at the internal structure, some things are in an XFORM object, other things are not, text has redundant copies and are masked by other shapes elsewhere in the hierarchy. things in frames are similarly structured in weird ways.This makes it impossible for screen readers to read it, and it makes it impossible for me to use Figma to design stuff for use in PDFs, even though figma does support exporting to PDF.
Unshareable generative plugin is kinda useless and force every team member to rebuild the wheel.
I couldn’t find a similar thread, so I’ll just post it here. Here’s what’s InVision Studio does great: The idea is to be able to define when each layer is to be triggered when using smart animated. Currently there is only a global switch and all layers will animated in a given time. If this idea is a duplicated of one I didn’t find, please merge it together. A great feature for you PMs and Devs to think about.
I found a usability issue in Figma while working with line objects.When I draw a horizontal line, I can resize it using the “W” (Width) input field in the right-side layout/properties panel, which makes sense.However, when I draw a vertical line, the resize control is still tied to the same “W” field instead of switching to the “H” (Height) field.This feels unintuitive and inconsistent from a UX perspective because a vertical line’s primary dimension is height, not width.I compared this behavior with Adobe Illustrator, and Illustrator handles this much better:Horizontal lines are controlled through Width Vertical lines are controlled through HeightThat approach feels more natural and improves usability during precise editing.It would be great if Figma could automatically map:Horizontal lines → Width (W) Vertical lines → Height (H)
When opening the Text styles panel, it should automatically scroll to the currently applied text style instead of starting at the top of the list. When you have a large list of styles it becomes really difficult to swap between different styles in the same category, such as switch between display styles or body styles
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.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.