Share Your Thoughts

This should be off by default. I was not aware this crap was on. I did not and do not approve. F- for sneakiness.

People have been complaining about this for years. I have to add ® and ™ to strings of text in my artboards. The superscript version of the character must be the same size as the rest of the text string, or it will not be vertically aligned properly with the rest of the text. The ®™ symbols are much too large, especially in headlines, but if you reduce the font size of that character, it drops down too low and is no longer in the superscript position. In Sketch or any other proper app, you can adjust the baseline of the specific character (baseline shift) so that you can re-align it properly. You can EASILY accomplish this in CSS and create specific styling for the “sup” tag which handles this in code. Why is it nearly impossible to replicate what is easy in any other app in Figma? I’ve seen people complaining about this since 2018, so I take that as an assumption that Figma will never fix this issue? The only way to get a properly aligned and sized ® or ™ in a line of text is to creat

Description:When using Find and Replace in Figma, the search scope (Search in this file / Search in all pages) can be clearly visible and configurable before the search begins.Currently, if “Search in all pages” remains selected from a previous search, users may unintentionally perform a broader search than intended. Suggested Improvement: Display the search scope options before executing the search. Make the currently selected scope clearly visible. Allow users to switch between “Search in this file” and “Search in all pages” before execution. Consider defaulting to the current page/file scope when appropriate, rather than retaining a broader scope without sufficient visibility.   Rationale:This would improve user control, prevent unintended broad searches, and potentially reduce unnecessary processing time in large files. Expected Outcome:Users can make an informed scope selection before each search, improving predictability, efficiency, and overall usability. 

Hi Celine- Are there any plans to remove this constraint? We have container frames with a handful of separate screen specs in them and would like to designate certain screens as ready, but not the entire set. It’d be great to not have to have the frame or instance top-level, but allow nesting and still mark contained elements ‘ready for dev’. Thanks!

The issue being faced today:I want to have preferred values only show up under the instance swap feature. Not searchable in the assets panel, as these are typically sub-components that I don’t want to be used on their own (examples: a dropdown menu used in a global navigation component, the vector for an icon used to instance swap in an actual icon component to control the sizes via icon properties, a single segment used inside a donut chart, pre-configured links or buttons commonly used inside a bigger component to make it easier to select from a pre-set). Why this isn’t possible:Unpublished and hidden components are treated the same in Figma. Hiding/unpublishing a component in Figma is currently the only way for it to not show up in the assets panel. Hiding/unpublishing a preferred value leads to additional issues: Preferred values cannot be selected by library consumers if they are unpublished. Preferred values must be published in order for updates to be available to library consu

Hi all,Figma motion is incredible and is becoming my go-to motion tool. Only a few things are holding it back:High-quality export: bitrate control, 4K, .mov with transparency, and correct colour tagging. The current exports are fine for social, but too low quality for more serious uses.  Visibility control: let me show or hide a layer at a set time on the timeline, instead of faking it with opacity keyframes. Speed graph: Just a really good way of interacting with easings, would be good to have alongside cubic bezier and springs. Better resizing: scaling an animated frame or instance should scale its keyframes too. At the moment elements drift out of place, which makes it hard to reuse one animation component across different uses. Variant export: export every value of a component property (e.g. 16 headlines × 3 sizes) in one job, without first building an instance for each combination. And bring the API/MCP video export up to the same level as the UI’s multi-layer export. This feature

SummaryI'd like Mistral's MCP client to be added to the Figma MCP Catalog so that Mistral users can connect to the official remote Figma MCP server (https://mcp.figma.com/mcp).The problemMistral's Le Chat, now part of Mistral Vibe (Vibe Work), supports custom MCP connectors. These connect to remote servers over Streamable HTTP and support OAuth 2.1 with dynamic client registration. When I add https://mcp.figma.com/mcp as a custom connector, [describe what happened, e.g. the connection fails with "MCP connection requires additional information or is invalid" / HTTP 403 during registration].From the forum thread "Figma's approach breaks the core promise of MCP", I understand the remote server allowlists client_name during dynamic client registration, and that only clients in the MCP Catalog can currently authenticate. Mistral's client doesn't appear to be on that list.Why it matters- Mistral is a major AI provider with a large user base, particularly in Europe, where many teams choose it

Hi everyone,I’m working on a quick administrative side project to help healthcare staff estimate their take-home pay — essentially a simple web tool based on the latest NHS Pay Scale and a dynamic NHS pay calculator.While putting together the breakdown for Band 5 and Band 6 roles, I ran into a bit of a discrepancy when factoring in London weighting zones and the recent annual pay uplifts. Some of the calculated net take-home figures after pension deductions, tax thresholds, and National Insurance contributions don't quite match up with the official Electronic Staff Record (ESR) payslip examples I’m cross-referencing.Here’s the reference guide and breakdown table I’m currently looking at:https://forum.figma.com/ask-the-community-7/i-built-a-relationship-duration-calculator-looking-for-ui-ux-feedback-57842/ NHS Pay Scale/What I’ve checked so far: Verified the updated percentage brackets for the NHS Pension Scheme tiered contributions. Tested both standard tax codes (like 1257L) and reg

Hey everyone!I've been considering switching to Figma for my design work, and before fully committing to it, I'd love to hear from people who have been using it for a while.I'm trying to understand what using Figma is actually like in practice, beyond the features and tutorials.What do you love most about it? What makes your workflow easier or faster? And just as importantly, what frustrates you, what feels unnecessarily complicated, or what do you wish you had known before getting started?I'm also curious whether there are any limitations you've run into over time, especially when collaborating with others, managing design systems, or working on larger projects.If you could go back to when you first started using Figma, would you make the same decision again? Is there anything you'd do differently?I'd really appreciate hearing your honest experiences, both the good and the bad. I'm trying to make an informed decision before moving my workflow over.

Anybody else really dislike, that when you copy paste a link into FigJam there are horizontal and vertical options for how the link is displayed, but the size is not changeable? Why not? It is usually too big to fit in nicely and could be so simple to make the size adjustable.Hope this can be changed by the FigJam Devs!

你好，新的UI更新之后，原来的AI图像生成和编辑工具出现了三大可用性倒退，严重拖慢了我的工作流程：缺少提示历史：“最近提示”历史（时钟图标）完全从新的浮动工具栏中消失了。每次我需要重用或调整一个复杂的提示词时，我都被迫从头重新输入。 缺少快速参考（+）：以前，当图像生成面板打开时，我只需点击画布上任何图片或画框上的“+”图标，就能自动添加为参考。该选项已被移除，添加参考文献需要更多步骤。 缺少图片尺寸自动识别功能： 以前只需要点击图片，再点击“创建图片”即可按照原图尺寸生成图片。现在默认尺寸固定为 512×512，无法自动匹配原图比例，只能每次手动修改尺寸。如果误点击生成，会直接消耗生成点数并得到错误尺寸的图片，严重影响工作效率。希望恢复图片尺寸自动识别功能。这些变化使得对AI图像的迭代速度和挫败感都比以前慢得多。请尽快恢复最近的提示历史标签和快速画布参考工具、图片尺寸自动识别功能。谢谢！

Hi Figma Support Team,I’m experiencing an issue with the Layers panel in Figma.Previously, I could select multiple Frames and then use the Ctrl key while collapsing one of the selected Frames. This would collapse all the selected Frames at once.However, this behavior no longer works. Now, when I select multiple Frames and try to collapse one of them using the same method, only that particular Frame gets collapsed while the other selected Frames remain expanded.This was a very useful workflow for quickly organizing and managing large Figma files.Could you please confirm whether this behavior has been intentionally changed in a recent Figma update, or if this is a bug?If the feature has been changed, please let me know if there is an alternative shortcut or method to collapse all selected Frames simultaneously.Thanks for your help.

My suggestions is to allow users to include annotations and / or measurements  when they export images. Seems that we can’t currently do thisThe user benefits –allows users to share images with annotations and measurements when creating images to be shared wither wider stakeholders and creating documentation for other platforms. If we can’t export annotations and measurements, then for those instances requiring annotations in an export as an image, users won’t use the annotations feature, and revert to creating “Notes” manuallyHope this makes sense

I’d like to share feedback regarding the implementation of AI credit limits in Figmake. As a designer managing multiple complex projects, I believe credit restrictions would greatly undermine Figmake’s usefulness in real-world design and prototyping workflows.  1. Most AI usage is for fixing bad or incomplete output, not luxury use.  In practice, a large percentage of AI prompts in Figmake are iterative—used to correct layout issues, rebuild misinterpreted elements, or align behaviors with visual intent. Each refinement quickly consumes credits even though the output quality depends on that iteration. Penalizing iteration limits the model’s ability to produce accurate prototypes, especially when the AI output is imperfect through no fault of the user, making credit usage really unfair and frustrating.2. Predictability becomes impossible, discouraging adoption.  With a credit cap that no one knows how to predict and calculate ahead of time, I can’t plan how far my Figmake usage will tak

There is a couple if usability issues related to this window 1 –  Review updates window – lies color modesReviewing components from external library using variable modes for e.g. Dark / Light UI - this window shows fake color modes for sub frames of the component. Thus it makes impossible to validate if specific elements are ok to or not. Example: review window displays Background from Dark mode, but texts from Light mode  In reality components look like thatReal Dark and Light look   2 – Weak usability – Clickology when large number of components to review  Example: To review 250 components I need to perform one thousand of clicks Super annoying workflow Solution proposal:Instead of that, I would recommend using strategy from text editors, commonly known as “find and replace and go to next one”. In our case it could be: “Update & next” or similar.In 99% of cases I use it like that. If there is a second verification needed after update - I can click “< back”  2b – Go to instance

I can’t believe this. Figma ai agent used 1524 credit for an icon creation. An Icon. and it doesn’t even work decent. Half of the icon doen’t even seen in the file. I will never use this again. It is definedly a SCAM.   

Hello Figma,  Im writing to request a missing feature for text edit, currently there are only 4 types of text alignment natively in Figma: Text align Left, Text align center, Text align right and text align justify. Im looking for a Justify all lines, same we have in Illustrator, Im looking to achieve this text look, and so far has been imposible to replicate it in Figma.Hope we can have this small but Important improvement natively in Figma soonCheers!

Example:I have a bunch of elements that intentionally have a fixed height and width applied to them.I want to put them in a grid.When I do so - their width and height changes to fill. This is an unwanted destructive change and should be fixed or at least have a way to override.Is this how flex works in css? I don’t think it is - using display: flex - children keep their intrinsic size unless you explicitly opt into growing.

I can’t believe how equation driven variables aren’t in figma! Ex. establishing a rem size (font size)then Driving type scales and line height based on that rem unit. You can literally do this in css html  --font-ratio: 1.333;--font-size: 1.2rem;--font-size-1: calc(var(--font-size) * var(--font-ratio));--font-size-2: calc(var(--font-size-1) * var(--font-ratio));

Dear Figma team,I love Figma and use it daily for design, so I wanted to share some feedback regarding video exports.Currently, I can import a video into a design frame, design over it with text and graphics, and play the video within the frame. However, I haven’t been able to find a way to export the entire frame as an MP4.This became frustrating after spending time creating graphics with imported videos and text overlays, only to discover I couldn’t export the final design as a video. I ultimately had to move my entire design to canva to complete the export.With the introduction of Figma’s motion and animation features, it would be helpful to have a similarly straightforward way to export design frames containing imported videos as MP4 files. If this functionality already exists, making it more discoverable would also improve the user experience.I use Figma every day and genuinely love the platform. I’d love to see this workflow become more seamless so designers can create and export

Hello Figma Community 👋I wanted to raise a question regarding the monthly AI credit system and also share a suggestion that could benefit many users.Currently, on the Professional plan, we receive 3,000 AI credits per month, and as confirmed by support, unused credits reset at the end of each billing cycle and do not roll over.However, in real-world usage, credit consumption is not always consistent every month. Some months require heavy usage, while others involve lighter workloads depending on project timelines.📌 Example Scenario:Month 1: Allocated credits: 3000 Used credits: 1800 Unused credits: 1200 (expired) Month 2: Project demand increases Required credits: 4200 Available credits: 3000 only Result: Need to purchase extra credits, even though unused credits expired in the previous month.This makes planning usage difficult, especially for freelancers, small teams, and agencies where workloads vary.

We need an option to retain our sort preferences. I notice that this change was made on purpose for people who thought they were missing their projects - but I think there should be a way in each person’s individual preferences if they would like to retain their sort preference every time or not. This is one of my most frustrating experiences when using Figma daily, and I think others agree. Lots of great updates have been made! This one missed the mark.

If I run a plugin that can style incoming text (from Payload, say) and that text has characters that have a <sup> tag, Figma should be able to set anything in the sup tag as superscript. Same for subscript. Seems like a screaming oversight to not allow that. I shouldn’t have to have create a type style for every style where a single character is superscripted. I’m looking at the ® character. I can’t change every typographer, but apps for DECADES have ways of dealing with this. Figma shouldn’t be an outlier. Yay for AI and all, but bread and butter, people.Sidebar: if a registered trademark character is superscripted on plain text or default styled text, when applying type styles, don’t remove that designation; keep the override. You could make it a setting “Honor super/sub script characters when changing or applying styles”. Do I dare to hope? To dream? 

I use Claude on two separate Claude accounts, and both need the Figma MCP connector pointed at the same Figma account. This does not work. As soon as I authorize the Figma connector on the second Claude account, the first one is invalidated and its Figma tools stop working (“The user’s connection to this connector was invalidated”). Re-authorizing on the first account then kicks off the second. The same Figma login can be authorized in Claude Code’s own Figma plugin at the same time without conflict, so the limit seems to be one active authorization per Figma account for the Claude connector client, rather than a general one-session rule. Please allow one Figma account to hold more than one active authorization for the same MCP client, or document the limit and the intended workaround. Reproduced today on the current remote server at mcp.figma.com with two Claude accounts, one Figma account.

Hello. Since the latest UI3 updates, the native AI image generation and editing tool has suffered two major usability regressions that significantly slow down my workflow:Missing Prompt History: The "Recent prompts" history (the clock icon) is completely gone from the new floating toolbar. Every time I need to reuse or tweak a complex prompt on a new image, I am forced to retype everything from scratch. Missing Quick References (+): Before, while the image generation panel was open, I could simply click a "+" icon on any image or frame on the canvas to add it as a reference automatically. That option has been removed, and adding references now takes considerably more steps.Together, these changes make iterating on AI images much slower and more frustrating than before. Please restore the recent prompts history tab and the quick canvas reference tool as soon as possible. Thank you.