Share Your Thoughts

title

Feedback: Grid Limitations for Data TablesIntroductionThank you for this Grid update! Features like "hug" and "fractional units" are clearly a welcome improvement for simple cases (galleries, basic layouts, etc.). However, I must share a different experience regarding the creation of data tables, where Grid actually introduces significant friction compared to auto-layout.The problem: loss of structural hierarchyWith auto-layout, you could create a natural and maintainable architecture:Table├── Header (slot / component)│ ├── tr (reusable component)│ │ ├── th (cell)│ │ ├── th (cell)│ │ └── ...├── Rows (slot)│ ├── tr (reusable component)│ │ ├── td (cell)│ │ ├── td (cell)│ │ └── ...│ ├── tr (component)│ └── ...Advantages: Clear parent/child relationships, reusable components, easy to maintain and scale.---Practical Problems with Grid1. Flat and Unmaintainable HierarchyWith Grid, we end up with a flat structure: Table > 70 direct children (for a 7-column × 10-row array).Consequences:- Un

AVIF is already supported by Chrome and Firefox and Safari. It would be good to also have animated AVIF supported for prototypes the same way that gifs play when viewing a prototype.

Just want to easily get Figma Images NodeID without cmd+L and manual copy-paste :)

We really need On scroll trigger when prototyping - please make it happen 

Would be awesome to have full gradient control of the progressive blur map. Right now its essentially a linear gradient with only two knots. I would suggest treating this feature similar to the gradient picker. this would allow for 3 key features:the ability to change it to radial would be fantastic.  the ability to add knots to the gradient would really open up a lot of possibilities being able to quickly reverse the order of the knots would also be a nice timesaverI also saw someone else suggested adding a custom image map option. That could also be pretty sweet, I would imagine it could be a third blur type: Uniform, Progressive, Image.

Figma Make .md Files, ReadM, Summary, Guidance docs are too much.  Is this really necessary.   This really should be an option.   is slowing development.  Can we limit this, or optional settings.

SummaryWhen creating a new shape with the shape tool while a layer is selected, Figma always places the new object at the top of the layer stack within its parent frame or group. This behavior ignores the currently selected layer and creates friction when working inside complex hierarchies.ProblemIn large frames or deeply nested structures, new shapes regularly need to be inserted near a specific layer. Figma’s current behavior forces users to: Manually reposition the new object in the layer list every time Or create shapes elsewhere and use “Paste Here” Or duplicate existing objects just to preserve layer order These are workarounds that break flow, especially during layout construction, wireframing, or when adding utility shapes inside structured components.Why This Matters Slows down designers working with complex design systems Adds unnecessary layer management steps Breaks expected behavior based on other design tools (e.g., Illustrator, Sketch), which insert relative to s

Is there any chance to have the ability to selectively apply string variables to specific words within a paragraph? This can change my (professional) life 🙂

I’ve got a popup window with 2 variants for minimized/maximized which I open as an overlay on the bottom-left of the screen, but with some padding. I cannot use manual position for this because in this mode the overlay positions based on top-left constraint and, when minimized, is anchored to the intended bottom-left point and is instead moved up. My current (dirty) solution is to wrap all my variants in a transparent frame with some left and bottom padding. Then set the overlay position to “Bottom left” which correct anchors the overlay to the bottom-left as well.

In FigJam I often duplicate a sticky that already exist, it can be because it is close by, or I want to create another with the same color. Then I move it where I wanted, often on top of an image, but then I ALWAYS have to “Bring it to top”.I understand the duplicated sticky is maintaining the z-index of the “parent”, but why? If I make a duplicate I would expect the same as adding a new sticky from the toolbar, in that case they are always on top.Thanks.

 Blockchain adoption is shifting from experimentation to enterprise-wide implementation. Modern organizations now demand platforms that ensure scalability, compliance, predictable performance, and secure smart contract execution. Infograins delivers this transformation through advanced engineering models, serving as a trusted Cardano blockchain development company and offering enterprise-grade Binance Blockchain Development capabilities—all aligned with the evolving architecture needs of global businesses.From finance and healthcare to logistics, identity, and decentralized commerce, Infograins engineers blockchain ecosystems that deliver both long-term resilience and immediate operational impact. Cardano: The Enterprise-Grade Blockchain Built on Scientific ArchitectureCardano’s methodical, research-driven approach makes it ideal for sectors that require mathematical security, high uptime, and energy-efficient execution.Why Enterprises Prefer Cardano for Modern Blockchain WorkflowsMult

The layering of modules in Auto Layout cannot be adjusted as freely as z-index in HTML div elements. It would be beneficial to add the ability to control the layer order in Auto Layout, similar to how z-index works, allowing for more flexibility and precision in complex designs.

before 🤗Previously, you could generate a [no expire] tokennow 😔If users rely on tokens to access the figma open api, forgetting to replace expired tokens can cause serious problems.The expiration date of the limited period will cause the figma token to no longer have usage value. 

when sharing a Figma Make design there isn’t a place to create comments to others about changes that are needed, or problems with the design. When publishing reviewers can’t leave comments. 

I know that something has changed because I use this shortcut constantly and my muscle memory is failing me.  Expected behavior:With an object selected Press “k” on the keyboard UI switches to Scale tool (if not already there) AND auto-focuses + highlights the value in the #x scale field Type desired scale value “Enter” to confirm Ex: select object with Move tool + “k” + “.5” + “Enter” = item reduced by 50% from center - it’s so easy, I do it all the time. Observed behavior as of 12/13/25 @ 5pm PST: Pressing “k” while on Scale tool behaves as expected Pressing “k” while on Move swaps to the Scale tool, but DOES NOT FOCUS the #x scale field In order to focus the #x scale field from Move, I now have to press “k” TWICE in a row (once to change tools and a second time to focus the #x field). As a result, my muscle memory keeps resulting in an object that is some lower opacity because “k” + “.5” now switches to the scale tool and then drops the opacity to 5 because the #x scale field isn’t

They are so bad, it’s sickening. First, masks go behind the masked object, (?!) Second, if you build a mask out of different compounded shapes (add/subtract), then you can’t select the sub shapes by clicking. You have to go to the layers and navigate through tens of shapes. Please change this, just do it like Illustrator. It’s unbelievable how bad it is. I get dandruff every time I have to use them.

Currently we get the Figma file name as a Tab title when we Run/Present any prototype. Now if on that page I had designed multiple Flows (Start points) then there in no way while having a look on Tab title that which prototype flow is presenting/running.Also while hovering that Tab can we show the full file + Page + Flow name in tooltip ?

Introduce password protection and viewer analytics for Figma Slides to enhance security and provide insights into presentation engagement, similar to DocSend. Key Features: Password Protection: Set and manage passwords for shared slides. Viewer Analytics: Track view counts and engagement metrics (e.g., time spent on each slide). Access demographic data like viewer location and device used (desktop, mobile). Why It Matters: Integrating these features directly into Figma Slides streamlines workflows, eliminating the need for third-party tools and making Figma a more powerful platform for design and presentation needs.

The new additions to the grid layout are really awesome and very helpful! Thanks for that!It is now more like I’m used to having a grid in software.Now I have another proposal to make it even better.Sometimes I need to select all cells in a column, for example set the alignment inside that column.Currently I have to select all items in that column one by one.It would be very handy if columns or rows are represented in the Layers (left sidebar) so selection of cells would be easier. Maybe also add a toggle to switch between row and column seelction.

I haven’t seen many posts about this, only one from 6 months ago that’s now locked for some reason. When working with Auto Layout (fill to width/height) and aspect ratio locked, I’ve noticed decimal points in the element’s height/width (I have pixel snapping on). I tried Round to pixel but it’s not working. It would be so great if the Snap to Pixel Grid function worked with Locked Aspect Ratio! In my example below, I set the frame to fill the width but locked the aspect ratio so it doesn’t stretch the content. Unfortunately, this results in a decimal-point height, and with auto-layout this results in objects below this component to be placed on decimal points. When exporting as an image (which is a technical requirement), the decimals are filled with an odd colour (see last image).Component height results in decimal points when scaled automatically.Aspect ratio locked, and decimal point height.Odd colour fill in the bottom row of pixels when exporting. 

By default, all exports are named after the Board.I am copying the section title when I prepare to export.It seems like a better default rule to have the section title be the filename.

Hi Figma team,At the company I work for, we often send design PDFs to clients who aren't familiar with Figma prototypes. Email is our main channel, but exported PDFs are often way too large—even when using the TinyImage compressor plugin, which is slow and not always effective.It would be incredibly helpful to have:An option to disable font embedding.Basic PDF compression settings (e.g. image quality).A way to export text as vectors without manually outlining everything.Improving PDF export would really ease delivery for teams who rely on email-based workflows. Thanks!

Miro has this down quite nicely. You can create swimlanes there, which serve as a grouping mechanism, and it makes it easier to create complex workflows. My workaround right now is to simply have different sections, which works OK. However, when creating new shapes (through the connector icon next to the shape), it keeps suggesting objects outside the current section. To be honest, if this were fixed, and sections in FigJam could. just be swapped / extended (sort of like a table), this would solve 99% of the drawbacks I currently see in FigJam for that use case! Keep building the best product on earth!  

Hi Figma team,I’d like to provide some feedback on the current Pages and Layers panel experience.Right now, the Pages section and Layers section are stacked vertically. When a file contains many pages and many layers, I have to keep dragging the panel up and down, which is inefficient.Would it be possible to redesign the layout so that Pages and Layers can be displayed side-by-side, or allow them to be expanded simultaneously in a more flexible way? This would make navigation significantly faster.Additionally, could the Pages section support a grouping feature similar to Layer folders? When a project has many pages, the list becomes long and hard to manage.Overall, the main goals: Reduce unnecessary scrolling Allow quick access to all pages and all layers Support grouping/organization for pages Thanks for considering these improvements!