Suggest a Feature

I also recommend Figma for creating all kinds of designs, whether digital or print materials. Unfortunately, Figma does not fully support print design. We would love to see this feature added to Figma!

I want to be able to export designs in PDF for print (CMYK/Hi-resolution) For now, I was using the plugin TinyImage Compressor but it’s no longer free and I don’t understand why Figma can have this option on it’s own. I’d have to pay $456 a year. If Figma has paper sizes, why don’t they have this option… you can’t print quality good quality colors in RGB. I’m going to have to go back to Adobe for print files. Is this happening to anyone else?

I do a lot of packaging and print work, and Figma is already my tool of choice for everything up to the moment the file has to go to the printer. That last step is where it falls apart, and I end up rebuilding the layout in Illustrator or InDesign just to hand it off.A few things that would let us stay in Figma end to end:CMYK and spot colour supportRight now everything is RGB, so colours shift the moment the file hits a press. Being able to define CMYK values, assign Pantone/spot colours, and see an out-of-gamut warning would solve the single biggest problem.Bleed, trim and safe areaA document-level setting for bleed and trim marks, with the artwork actually extending into the bleed, rather than everyone faking it with a frame inside a bigger frame.Print-ready PDF exportPDF/X-1a or PDF/X-4 export with crop marks, bleed, embedded fonts and no downsampled images. Today's PDF export is fine for review but printers reject it.Dieline / cut layer handlingFor packaging we work on top of a di

What can you do when you have unattached comments? There should be an option to place it back on a frame or object inside the canvas. Vote here if you have the same issue. (original question here: What do you do with Unattached comments? ) It would be great if @figma can let us reattach lost, unattached comments back to a frame. Even better if the comment automatically falls back to a children frame underneath when you ungroup a frame, to which the comment is attached. That just reduce unattached comments from happening.

The slot feature has been incredibly helpful for enabling components to have modifiable contents and I’m absolutely loving it.  I do consistently find myself running into a thing that I wish was easier/facilitated by the UI.If I have several instances of the same component in a slot, such as rows in a table or cards in a gallery layout, etc., it would be incredibly helpful to have access to a feature similar to the “Select Matching Layers” functionality that’s available for general selection, but to have it apply across the instances in a given slot.  That way if I want to select all of the items in the first ‘column’ of a table row and modify them, or select all of the body text fields on my gallery cards, I could do that with a single button instead of having to manually select each one. This would also be incredibly beneficial when some of those instances appear ‘off screen’ because the area is set to scroll.

Figma Spec announcement this week is brilliant. I already know that of a lot of different things I’ll be able to do with it immediately which will considerably increase and improve my design workflow. These features additions to Figma Spec would hands down flip my design workflow on its head.1. Figma Spec document libraryBasically this would be the same concept as the assets library, but instead having a specs or document library.This would allow you to access all of the spec documents in your design file from a single top level UI navigation element and be able to create folders and sections of all the different spec documents in your design file.Why this is useful is that in very large design files with lots of pages, layers and stuff. You might not actually want to navigate all the design files to find the spec that you need and if you only going to read or updated the content in the spec, having to navigate to it through the files pages is a bit slow and pointless.If you could set

Figma doesn’t support comment deep-linking through URL fragments. Figma’s setRangeHyperlink() API deliberately sanitises and removes URL fragments before storing themFor example, if I add this comment URL as a link on the page, ….........?node-id=7-4524#1967128705, Figma strips the fragment, and the link becomes ….........?node-id=7-4524. One workaround is to replace “#” with “=”, which displays the comment but doesn’t take you to its position.The reason I’m doing this is that Figma’s comment management isn’t great. As a designer, I see each comment as a potential task, so it makes sense to create a plugin to manage comments there. The only limitation is the issue mentioned above. Ideally, Figma could provide better comment management. I’m wondering whether there is another workaround.

I’m building around 40 social media post templates for our marketing team. This is not my first time using Buzz but I’m rather new to it. I am a daily user of Figma Design though. Testing my templates, editing content, changing layouts, swapping variants etc all works, but I cannot seem to open the simplified content editing panel. It used to be shown on the bottom left of the window, and I saw it once or twice while testing, but I’m pretty sure it’s a bug. Clicking edit only opens the ‘Bulk edit’ panel, there’s not even a button for the normal panel showing anymore (square with pencil icon). Wondering if this is a known issue and is being worked on or not. For me it’s not a big issue, but for my marketing team this panel is very easy to use and much preferred over the manual ‘click on the frame to edit’ or bulk edit panel. Thanks!

Currently, importing and using a Community design system (like the Streamlit Design System) in a personal design file has way too much friction. When duplicating a library from the Community, it lands in Drafts, then I have to move it to a Team project, open Library settings, publish the file, and then enable it inside the file I am working on before I can drag and drop a single component.Proposed Solution:Dedicated Libraries Tab on the Sidebar: Add an explicit Libraries element directly on the left sidebar alongside Layers and Assets. One-Click Direct Import: Allow users to import or link any component file directly into their active file from that sidebar tab without maybe add an import to the folder level as well so assets can be easily allocated to an entire project

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

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 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.

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.

Hi Figma team,Our team uses Storybook to implement and document our components and pages in code. Doing this manually takes developers a lot of time: they have to rebuild every Component and Variant in code and write a story for each State.So we built our own agent that converts our Figma designs into Storybook. The results were great: it dramatically sped up our workflow, and the generated code ended up much closer to the original design.To give you a real picture, here’s what we built in our project in just one week:UI Kit: 27 component sets, 2,288 variants, 4 Sidebar components and 1 Chart instance Icons: 1,254 icon sets with 7,520 style variants, plus 259 flags and 3 standalone assets Style guide: 89 color styles and 42 typography styles Design variables: 157 across Primitives (16), Tokens (34), Colors (89) and Typography (18)For a senior developer, implementing all of this manually would have taken around 2–3 months.That experience gave me this idea: it would be amazing if an agen

Your improvements to auto layout are incredible. I can’t tell you how much I love seeing the Figma team tackle these core features. There is a “final boss” of the Grid auto-layout that I’d like to suggest potentially tackling. It looks like you’re heading in this direction, so please carry on if you’ve already started :-)“repeat(auto-fit, minmax())” Responsive grid columns, equivalent to repeat(auto-fit, minmax()).Expose a minimum card/column width in the GUI, with the grid automatically reducing its column count and adding rows as the container narrows. This would make a powerful—but challenging—CSS pattern much more accessible to designers and some developers. 

There’s no visible scrollbar in Figma prototyping mode. Yesterday we’re having user testings and once again this same topic popped out. Some of the users didn’t thought that they could scroll prototype because scrollbar wasn’t visible. One of the user was using laptop’s touchpad and he wasn’t able to scroll with only using touchpad. Guiding user how to use prototype during test can harm testing situations. Atleast it’s sure that if user thought that he can’t scroll it leads to biased feedback about product. If there’s some reason not to have scrollbar it could be atleast optional feature that designer could turn visible scrollbar on from options. It’s not only who has came across with this weakness in Figma. Here’s old Spectrum thread about same topic but Figma hasn’t done anything for this yet and I hope this get more attention here.