Share Your Thoughts

Hi there.I create a new thread because this one is closed: Like many, I do my resumé with Figma. And I’ve seen that the text exported PDFs have undesirable spaces inside the words.Example:Copy/paste this text and you get:“with 2 0 + years of e xperience”, which is wrong!! Of course, the MKitFPDF plug-in solves some problems but brings some others, without to say it’s not free.Did someone got a real fix for this?

what about having lines to represent if the colors are accessible or not in color picker, so it’s easy for designers to check for accessibility before even choosing the colors, and when getting colors from styles there a filter in the dropdown for accessible ones

Hi there!I embeded Figma prototypes into a SharePoint Teams website. I successfully hid the Figma UI, but I’m noticing some white padding around the prototype. Is there a way to adjust or remove this padding by tweaking the iframe code, or is there another method I could try?The extra white space is affecting the website layout, especially on smaller screens. I appreciate your help with this!Thank you! A

What problem does this solve?Kiro (by AWS) is already listed on the Figma MCP Catalog as a supported client for Figma Design and FigJam. It connects to the remote MCP server at mcp.figma.com and works great for the design-to-code direction using get_design_context, get_screenshot, get_variable_defs, etc.However, the generate_figma_design tool (Code to Canvas) is currently restricted to only Claude Code and Codex by OpenAI. This means Kiro users can pull designs from Figma into code, but can't push generated UI back into Figma — breaking the bidirectional workflow that makes Code to Canvas so powerful.What's the use case?Developers using Kiro generate HTML mockups and UI prototypes as part of their development workflow. Being able to send those directly to a Figma Design file would let designers review, iterate, and refine without manual recreation. This is the same workflow Claude Code and Codex users already enjoy.What's the ask?Add Kiro to the approved client list for generate_figma_

Type sizing consists of mainly dropdown presets, and manual input (type the size) There is a 3rd option, but it so difficult to select, and that is resizing using drag. When placing the mouse over the border to the left of the type size, a double arrow appears and you can drag up and down on the size, but the active area is only about 1px wide and it’s almost impossible to use. Can you widen the active drag area like on the layout width box?  This is particularly useful when a selected work can be resized dynamically to match the width of a different word above or below. 

I have been playing around with Figma Motion since it launched, and I am really enjoying it. It already feels like a solid first release, but there are three features that I wish it had.Voice-over recordingBeing able to record voice-overs directly in Motion would make creating walkthroughs, presentations, and design reviews so much easier. Right now, you have to export your animation and finish it somewhere else.Audio importI would also love to import audio files into the timeline. Whether it is voice-overs, sound effects, or music, audio is a huge part of motion design. Keeping everything in one place would make Motion much more practical for demos and marketing content.Morph animationsMorph animations do a lot of the heavy lifting in presentations and motion graphics. They are probably one of the biggest reasons PowerPoint is still the go-to tool for so many presentations. They make transitions feel intentional, help tell a story, and add polish without requiring complex animation sk

Dear Figma Team,I am a designer who regularly works with 750px-based design files (a common standard in mobile design, especially for iOS @2x/@3x export workflows).Currently, when I need to export assets at different scales, I have to manually add export settings in the Export panel each time. This is time-consuming and error-prone, especially when working with many assets.Feature Request:I would like to suggest adding Plugin API support that allows plugins to: Programmatically add export settings to a selected node's Export panel Set custom suffixes (like @2x, @3x) for each export configuration Configure export scales and formats through the API Use Case:When working with 750px design files, I need to export: 0.5x scale (375px) with @2x suffix 0.75x scale (562.5px) with @3x suffix If plugins could modify the Export panel, designers could create custom plugins to automatically set up export configurations based on their design file dimensions, significantly improving workflow eff

I am building agents that are generating lots of designs, and I need to be able to organize those designs automatically instead of them just kind of gallivanting in my drafts. 

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Make. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet? A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Make — this helps everyone follow along.

https://developers.figma.com/docs/rest-api/library-analytics-intro/ I’m a sole PIC of design system, I’m conducting quarterly Design System Health Score to determine whether the design system actually works and used by the design team, it helps us quantitatively measure the impact of our design system. Currently my team uses organization plan and I think I can’t access the library_analytics:read permission in this plan, while the organization plan supposedly mature and big enough to actually uses analytics data as primary data, so my suggestion is to open the library_analytics permission to organization plan.

It would be really great if can add tools like Eraser, Pencil tool supports to illustrating(current one does not support when customizing existing elements). Basically tools from Illustrator. Figma is way more easy than using Adobe illustrator, but with the current tools its limited.

I think Figma's Brush tool has a lot of potential, but currently feels quite limited compared to dedicated painting tools.I'd love to see a more advanced Brush system that could include features such as: Adjustable brush size, hardness, opacity and flow Pressure sensitivity Stroke smoothing Spacing, scattering and rotation controls Custom brush shapes Eraser and smudge/blending tools The ability to create, save and organize personal brushes Brush presets and custom brush libraries Community Brush LibraryI think the biggest opportunity would be connecting custom brushes with the Figma Community.Designers could create their own brushes or brush packs and publish them to the Figma Community. Other users could then discover, install and use those brushes directly in their Figma projects.This could create a whole ecosystem around brushes, similar to other Community resources.For example, the community could create: Texture and grain brushes Ink and pencil brushes Pixel-art

I would like to ask: are there plans to introduce such a feature (tool) for Figma Draw as an eraser in the future? For example, it could easily erase unnecessary vector graphics down to the smallest detail. That is, I mean the eraser, which is have for example, in Adobe Photoshop and MS Paint.

Why did Figma choose to remove the type size from the panel.Not a good move. We create styles H3,H4, etc figma used to display: Body copy - 14pxNow… we have to click on style to see what the dimension. Not a good move. No one memorizes what size and line spacing H2 could be…You tried to make the panel minimal and ended up adding extra unnecessary clicks. Knowing a type size is crucial. Bring it back to surface please. 

Working in Motion I have to click back into Design to then get to Prototype but I work closly with Motion and Prototype so it would be great if I could stay in Motion and just click a Prototype button on the top to switch back and forth like I can when in Design mode. 

When presenting in Figma Slides, I would like the smart animate transition to be played even when going back to previous slide. Currently smart animate is only played when advancing to next slide, but not when going back to previous (then it’s just an instant change). This behaviour would not have to be the default, but having the option would be nice.

Hello! Is there a way where we can cherry-pick which changes made in the branch are going to be merged in the main file?

Since Figma introduced vector Pattern fill, it works pretty nice, yet there are some limitations and missing features. API/MCP supportClaude does really good work generating lots of patterns, yet it doesn’t understand well the underlying mechanism around it With further investigations, it looks like the API doesn’t support generating fill type `PATTERN`node.fills = [{ type: "PATTERN", sourceNodeId, tileType, scalingFactor, spacing, ... }] throws a discriminator validation error. PATTERN is absent from the accepted set, which currently lists SOLID, SHADER, the four gradients, IMAGE, VIDEO. Reads work fine, so the type round-trips as data but can't be written back. Even re-assigning an unmodified pattern paint read off an existing node fails. createPaintStyle() accepts the call and silently stores a SOLID instead. The silent degradation is arguably its own bug and worth mentioning separately, since it fails without erroring. clone() preserves pattern fills correctly, which shows the unde

The bottom part of the icon feels too visually dense — all the elements blend together, which creates a lot of visual noise. This makes the icon hard to distinguish and difficult to find quickly among other desktop icons. I think simplifying this area or improving the separation between the elements would make the icon much more recognizable at a glance.

When I have a typography style applied, I want to be able to change to a pre-saved option as easy as I can do it for colors. Now if I detatch the typography style, I want to be able to apply another style right away. I think what can help is to show the “library” select component when clicking on the “apply styles” icon button. When I click there I expect to see Text styles I have saved. However, the ones that are shown on my image I didn’t create and the only one library added to this file is not he first option being displayed. It is so frustrating and difficult to find the ones I have save and added to the library. 

Hello, good day.I’m experiencing serious issues with the new Figma UI update. Many essential tools — such as padding controls — are missing or hidden.Please do not enforce this new version. The previous UI was much better, clearer, and far more efficient for designers.This new version has no advantages, feels confusing, and makes our workflow significantly harder.

So, with the new beta implementation of shaders, I had a question since, you know, typically shaders are coded (which I assume is the work that the figma agent is replacing in this case) Is there any plans to make the Figma shaders coded instead of generative?

I’m posting this as a former paying subscriber because the usability problems became frustrating enough that I cancelled my subscription.My main issue is not what Figma can do — it’s how unnecessarily difficult it is to continue existing work.I’m using Figma for an app project, and something as basic as reopening the same project, finding the correct working file, returning to Figma Make, and locating the AI prompt workspace has repeatedly been confusing.The biggest problems I’ve experienced are:Figma Design, Prototype and Figma Make feel disconnected. It is not obvious how to return to the same Make/AI workspace I was using previously. Similar project cards make it unclear which file is the real working project. Navigation changes depending on which part of Figma you are in. Important controls are hidden or difficult to discover. I regularly spend time trying to find my own project instead of working on it.A user should be able to open Figma, see their active project immediately, clic

The current seat upgrade request process does not provide users or organization admins with enough information to make informed decisions or manage temporary seat requirements efficiently.Three improvements would make the process more transparent and significantly improve license governance: Make the request explanation mandatory Users requesting a paid seat upgrade should be required to explain why they need it. The request should not be submitted if this field is empty.Ideally, the mandatory explanation would cover: The project, client, or internal initiative The functionality for which the seat is required The relevant team or responsible project lead This would give admins the business context required to assess the request and reduce the need to contact users individually for clarification. Explain seat functionality and cost implications The upgrade request interface should clearly explain what each available seat type enables before the user selects it.For every seat type, F

It seems that previously link previews were updated in slack to show what was being shared instead of the entire canvas. I missed that and now my links are just links, no preview. Which is better than previewing the entire canvas still.I have the same suggestion for link previews in Teams. Please stop showing the entire canvas in Teams previews and either show just what is being shared, or just don’t show anything.