Suggest a Feature

Multi-edit with text is sometimes similar to a real multi-character-set selection editing but not, and in surprising ways. This is a request that multi-edit with text use real multi-character-set selections. Specifically: If a user with multiple text fields selected presses enter, engaging multi-edit, they would obtain text selections within each text field, visualized as such. (Currently we seem to obtain one primary character-level-granularity text selection but retain the text-field level granularity for other text-fields.) Shortcuts for selection transform (e.g. shift/option arrow) would transform each selection. Text selection style properties (font, weight, letter-spacing etc.) would be distinguished in the property panel from text frame properties like alignment. Text properties would behave like any other case of multiple selections, displaying ‘mixed’ in cases where the text selection properties are mixed. e.g. when one selection includes bold text and another include

I use string variables frequently, but it’s super annoying trying to edit the text of long sentences within the current fixed height field. It should instead wrap the text with the height increasing (or at least a toggle option…). Otherwise I have to write text and copy and paste in variable, which is silly. current With wrap

I have searched the community and Google for an answer to this question, but I have not been able to find one. Perhaps there is no answer. I have found a plugin that supports this functionality, but it does not add the frames to the FRAME panel. For example, I am working with different Zebra devices that have different DPs. As a result, most of the frames do not work. I would like to know if I can create my own frames and have them appear in the frame list so that my organization can see and use them as well. Thank you for your time and consideration.

In the new UI, the “reset scroll position” option is hidden and not enabled by default. Currently, it requires two clicks to add this action. To streamline this process, I suggest either making the option visible by default or enabling it by default. This would improve the user experience by reducing the number of steps needed to access this functionality.

Whenever I hand over a prototype link to a client and they leave comments on the file, it’ll be a mix of design and copywriting (or other) feedback which means Designer and Copywriter need to read through ALL the comments to find the ones appropriate to them. It would be sick to have an option where the client can maybe colour-code their comments or something, so, for example, they’re doing copy feedback only, so they’re in yellow, and then all the design comments are in purple. This way it’s not wasting anyone’s time. 👍

We have a lot of components in our design system (surprise surprise lol), and due to fuzzy matching, everything including the kitchen sink gets returned when search for a specific component. I could work around this if we had exact matching or must include matching, but that doesn’t seem possible either. For example, I’d love to prefix certain components for easier access: Icons: ^ Home OS UI: iOS Status bar

无法退出开发者模式

Idea: Add images and set it as thumbnails (not cover for the file). Allow click on an image to expand/see in full size (perhaps in a modal). Use case: When I need to make app flows, I find flowcharts better than a sequence of screenshots because it is easier to read the flow itself. So I would like to attach screenshot as examples for each different view. However, screenshots takes too much space in a readable size, especially tablet and desktop sizes. Small image thumbnails with click to expand ability would be enough for viewers to get context when needed when reading the flows. What do you think?

I do a lot of presentations in Figma, and usually those PDFs are over 300+ Mb and tough to share. The feature that came in handy is rasterizing selections which can do wonders for file storage. But using it is a real pain. If you have a pres with 50+ slides you have to click manually for every slide choose from dropdown, rince and repeat… the new ui didn’t help with it either. inb4 why dont you add a custom shortcut bla bla bla Navigate to: System Preferences > Keyboard > Shortcuts > App Shortcuts > click “+” Select Application: “Figma.app” and set shortcut for plugin commands by pasting in the “Menu Title” in this format: Plugins->Plugin Name->Plugin Command. CBA – So please Figma, add a shortcut for Rasterize selections feature.

It would be super helpful formatting and hyperlinking could be retained when copying and pasting component properties!

It would be great if component set bounding boxes (purple dotted border) auto-sized when the border is double-clicked, similar to how Sections auto-size to it’s contents when the edge is double-clicked.

In UI3 the clip content function is now a dropdown rather than a checkbox. Seems like an unnecessary extra click that is hidden in a dropdown rather than a simple checkbox toggle. Wondering why this was changed

When I edit code syntax for variables, I want to set default value based on the current layer For Example， I have a blue-1 variable, when I change to dev mode, I want this code syntax change to: var(blue-1, #e6f4ff) for Light mode; var(blue-1, #111a2c) for Dark mode How I can achieve this ? Is there any api to get the current mode value ? Thanks

It is necessary to add the function of setting center anchors. Although plugins can be used for batch copying and rotation, it is more troublesome to modify joints and other areas during character illustration without the freedom of center anchors.

Would be awesome if we could add a “button / link” or even a component in the document body, which could start a plugin directly, as a shortcut.

I use the ‘Swap instance’ feature a lot but it’s really difficult to see what I’m actually swapping to given how small the box is. Different components/icons can look very similar when they’re squeezed down to fit. Can this window be made larger or resizable with the component previews scaling inside? Seems like a small change but would make thing sooooo much easier and save me going in and out trying to find the right component/icon.

It would be great if Figma for Mac matched the MacOS pattern of having the close icon on the left of the tab title. Doing so would help to close multiple tabs by clicking repeatedly rather than having to adjust your cursor depending on the text length.

Testing prototypes often requires opening up access to a Figma prototype. Sharing prototypes outside of our org presents a vulnerability and introduces risk. If designers could use timed access to view prototypes, it would reduce this risk significantly. What this could look like… 24hr access (similar to FigJam but for viewers, not editors) Set periods of access – 24hrs, 1 week, etc. Allow the designer to specify how long access will be open Allow org admins to apply timed access as a rule, for viewers outside of the org

Figma supports setting comment notification preferences at the File level: https://help.figma.com/hc/en-us/articles/360039813234-Manage-your-notification-preferences#:~:text=the%20following events%3A-,File%20comments,-All%20comments%20on It would be nice to extend this functionality to the Page level (within a File).

Hi Figma Community, 👋 I’ve noticed an area for improvement in the way comments are sorted in Figma. Currently, comments are displayed based on the date of the first comment within the thread, not the date of the latest comment. This can make it challenging to follow ongoing discussions or see the most recent feedback, especially in active projects. While I appreciate the blue marker for new comments and the “sort by unread” filter, these options become less useful once comments are read. It would be incredibly helpful to have a sorting option as an additional filter that considers the date of the latest comment within a thread, allowing users to easily access the most recent discussions. I believe this enhancement would streamline the review process and improve communication within teams. Looking forward to hearing thoughts from the community and the Figma team!

When I add a prototype to a slide, it’s automatically placed in the center. If I want to move it (prototype without frame), I can’t, it interacts with the prototype, even in design mode. Instead I have to select another object and use the alignment options to move it. If I want to mask the prototype or adjust the cropping so that it fits within the phone, I can’t. Also moving it to the bottom in layers, doesn’t seem to work. It always stays on top. Anyone having the same issues?

Figma should have a feature where, when we zoom in, we should be able to zoom in to the cursor location, not to the centre. AutoCad does have this feature for instance.

I use a few plugins very often. The new UI has added an extra click to reach to the desired plugin. It will be very helpful if there is an ability to add a few plugins in the bottom toolbar (just like MacOS dock)

I saw sometime Figma lags on dragging the canvas as compared to Miro or Adobe XD canvas im not saying here XD is better… but just this small enhancement maybe can enhance help designers to peek on page canvas faster.

Hello, I will mention the problem to solve, then I will explain how my idea could solve it. Please vote for it if you need it as well, thanks. 1) The problem to be solved The precise Creation Date of a file is a key information for many users. It is not easy to find, and not available for every plans… Currently, the only way to find it is through the “History version”: The mental model of the user has to be “Thinking: Past version” instead of “Thinking: Metadata of the file”, which is an incoherent mental model for many users. Because, if the creation date is indeed a past version, it is actually the pillar version, not just a past version. This model is incoherent with many users’ habits as well, because a lot of softwares and OS include the Creation Date in basic metadata, often under the same Properties menu than “Author”, “Modified Date”, “Extension”, etc. A Paid Plan is often needed to scroll through many revisions. Though, this basic metadata should be available for every plans.