We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Find solutions, get advice, help others.
Can someone please tell, was is moved somewhere else or is it completely removed for auto layouts?
Background: I am a developer, and I use Figma exclusively in Dev Mode via the web interface. I don’t have (nor do I want) any edit access to the designs I’m implementing. That’s for the designers. When the Measure tool appeared (the ruler icon on the upper left toolbar), I latched onto it very quickly. It greatly improved my speed of accurately implementing a design. There are certainly other ways to measure things in Figma, but they are all transient. The best part of the new tool was that I could quickly measure many different things and have all the measurements persist so that I could then just refer to them during development. It was a simple yet well-conceived tool. Then the Measure feature suddenly and completely disappeared on April 10! (Nooooo!!!) Other developers on my team can’t see it either, but the designers and anybody with edit access can still see it. Has there been a change that means that edit access is required to enable Measure? I hope not, because if you asked my
Hi! I’m testing a site built with the new Figma Sites feature. I’ve set the top navigation bar as a sticky element and made sure it’s positioned at the very top of the layer tree. In the Layout panel, canvas stacking is set to “First on top.” Canvas stakcking settings It looks fine on Figma and Chrome(desktop & laptop) On Safari and mobile browsers, the sticky navigation bar appears underneath the hero section content, even though it’s set to be the topmost layer in the design. On Chrome (desktop & laptop): everything works as intended — the GNB stays sticky and always remains on top. On Safari (desktop & laptop) and all mobile browsers (Safari & Chrome): the GNB is sticky, but appears underneath other layers and is partially or fully hidden. Is there a workaround or fix for this issue? Thanks in advance!
Is there a direct phone number where someone will actually answer?
I'm experiencing an issue with the brush tool in Figma's drawing environment. I have a simple drawing tablet with a pressure sensor. When I was drawing, I noticed that the stroke was responding to pressure – the harder I pressed with my pen, the thicker the line became, which was great! However, this functionality suddenly stopped working. Now, no matter how much pressure I apply, the stroke remains uniform. Has anyone encountered this problem before, or does anyone know what might have happened or how to fix it?
Since the last Figjam update on the Ipad app, I cant see which color is selected on the pen/highlighter/etc.
I’ve made a flow diagram of a simple user task, i’ve adjusted the connectors to better fit the layout and available space. I then wrapped it in a section component and pressed the hotkey to resize the section to fit the flow diagram. However, when I do this, it always changes the positions of the connectors which i then need to adjust again. This usually happens when I move the connectors from their default. Attached a before and after: For a simple diagram this is annoying but not a big deal. but for a large, very intricate diagram … this is a nightmare
(NVM resolved)
Dear Figma Team, There is a problem that is causing me a lot of trouble lately… When I add drop shadow on top of an outside stroke with no variable the drop shadow start after the stroke. The problem is that when I add a variable stroke width, the stroke goes above the drop shadow 😫. There is 3 diffrent behaviors for the exact same frame and same shadow. See screenshot attached It is really jeopardize a hard deadline for me , please help… (PS : the shadow is raw number so its not an interaction between 2 variables of the same mode in case you were wondering)
Great to see the addition of dividers. Would really love the ability to add a name for each divider, because this still doesn’t solve the issue where we need to create an empty page titled “{Section Name}” to call out what the divider is actually dividing.
When I export a frame or component at any scale factor (@2x, @3x, or custom), Figma sometimes adds an extra 1 pixel to both the width and height. For example: A 100×100 frame exported at 3x should result in 300×300, but instead, I get 301×301 or 300x301 or even 301x300 . This does not always happen, but when it does, it's consistent across devices and files. Affects both PNG and JPG exports, regardless of pixel grid alignment or stroke presence. 🛠️ Workarounds I’ve Tried (with partial success): Creating a new frame, copying content into it, and exporting again — occasionally works. Manually scaling the frame by the desired factor (e.g., scale by 3x), then exporting at 1x — this consistently avoids the 1px error. However, these are not ideal for batch exporting or asset automation.
Figma prototypes have become incredibility slow and take eternity to load.Is anyone else facing this issue?
I'm encountering an issue with the Variables API endpoint when attempting to export local variables. The endpoint returns all remote variables from shared files, making it impossible to export only local variables. Current Behavior: The endpoint returns all remote variables from shared files Unable to filter or export only local variables Receiving a 400 error with "Request too large" message Error Response: { "status": 400, "error": true, "message": "Request too large. If applicable, filter by query params." } Technical Details: The error message suggests using query parameters for filtering However, the endpoint documentation doesn't list any available query parameters The endpoint lacks pagination capabilities This limitation makes the endpoint essentially unusable for files with many variables Expected Behavior: Ability to export only local variables Support for filtering variables (local vs. remote) Pagination support for large variable sets Impact: This issue significantly impact
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.