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.
🎉 Welcome to the Figma Forum! 🚀
Find solutions, get advice, help others.
I’m signed in under my personal email in standard account. I have tabs currently open on my desktop that I can’t access. Some are drafts some are saved. I used to be associated with a previous company (Accolade) but my personal email would have not been used for that figma account. Some of the drafts that I’ve recently started are also not displaying in ‘recent files’. Please advise.
I share a lot of prototypes with clients who I don't want to access the workspace.Previously, there was an option to share only the prototype. But now I see that they can access the project without the administrator's permission.Is there a way to fix this?
Since yesterday the Figma to Framer Plugin no longer works, it freezes, claiming to be running. Turns out it works well on the web app, but not on the desktop version. A lot of users on the Framer forum are having the same exact issue. Anybody else here? Framer (who i guess developed it) have been notified, but no response (This plugin: https://www.figma.com/community/plugin/1037108608720448600)
Something went wrong Our team is looking into it now. If refreshing the page doesn't work, check our status page for updates.
As written in the documentation (Prototype interactions and animations) the destination of a Scroll to action can only be an element of the same top-level frame. But with this limitation it is impossible to prototype a common navigation pattern. On one-pagers there are often floating menu for intrapage links. E.g you have an hamburger icon that opens a menu overlay from where you can scroll to a specific page section. This can’t be realized with an Figma overlay because of the restrictions mentioned above. There is a workaround, but it seems that it only works because of a bug: You can set the menu overlay as an child of the top-level frame of the one-pager, define the Scroll-to actions and then move the menu outside the frame (as an separate top-level layer) to show it later as an overlay. By doing this all the Scroll-to actions still work, but when you change an action the target will be rested and the navigation is broken. Working Example Maybe you can remove the restrictions that t
The recent Aspect Ratio update has brought with it a frustrating change to the way objects snap to the pixel grid. Previously, when changing the size/position of an object by dragging, it would snap to the nearest pixel. If you needed to get more specific - and have an object at 1.5px width for example - you could change this via the properties panel without having that object snap to the nearest pixel in terms of positioning/size. This felt like a really nice balance between snapping to the nearest pixel with the cursor, whilst retaining control over incremental choices via the properties panel. Now, after the most recent update, we no longer have this control - when you change the size of an object in the properties panel it snaps to the nearest pixel. For example, if I have a rectangle which is 6.5px wide and 1.5px tall, and I use the properties panel to change it's height to 2.5px, it'll automatically change the width to 6px. The same goes for positioning. Of course I can go into t
I created several “simulated overlay” menus and would like the option to prevent accidental clicks on content behind the layer. From a UX perspective, I’d like a checkbox option that says “ignore all interactions behind this layer” when the layer is visible. In my case, I am creating a pseudo overlay experience using my own hack method. You create a modal (for example) on a components page. You put an instance of the modal on another page (separation of concerns from components and prototype pages). You then toggle the visibility of the modal instance on the prototype page where necessary. For example, a command menu that is displayed on button click. Why do it this way? Because the default modal/overlay experience is bad. They lack responsive design support, they have to be attached to every component instance on within a page (rather than just on the master component), and they can be buggy from time to time. There are other cases I would also like pointer events turned off, similar
Hi, we changed from color styles to variables recently. We did this by creating a new library containing the variables and integrated a dark mode there. I manually exchanged all old color styles to the new variables out of the new library. When I want to switch the appearance to dark mode I see two options: I double checked that I don’t use any color styles out of the “Tokens (deprecated)” file. My components only use the new variables from the “Tokens” file. I actually don’t even understand why I can switch between “Light” and “Dark” within the “Tokens (deprecated)” set as there are NO variables in that file. To put it in a nutshell: There shouldn’t be two options to switch the appearance. Is that a (known) bug or did I miss something here? Thank you for your help :) Lucas
The main source of inspiration for this idea was to match the keyboard shortcuts themselves to different keyboard layouts. Right now, users who don’t use US keyboards have to memorize the location of the keys, rather than to use the actual character location to be able to use the shortcuts. Those involving this region are primarily the case: ABNT2 layout (Brazil). And here’s an example of confusing shortcuts: Although this problem could be solved by just rebinding the shortcuts to the actual character and not the location on the keyboard, I’ve noticed there are some other issues concerning key bindings. On this forum post, a member of the community asked for help on backing one layer level with a different shortcut from what Figma has right now. This makes the user adapt their workflow to the tool, and not the other way around — and that hinders efficiency. It would be nice if the tool itself provided some sort of customization on this regard. Although being a workaround, Mac users can
Good afternoon, everyone! I uploaded the video to the project after restarting the prototype, it loses a lot of quality and becomes pixelated. I've tried converting to WebM format and reducing the file size, but it still doesn't help. The frame size and the video are the same. 1920 x 1080 px
Hello, I want to leave a team that was created by an ex-colleague. I don’t see any option to leave it. Can somebody help?
Description: When working with prototypes in Figma, the list of screens quickly becomes very long. This makes it time-consuming to find the correct screen. There is no efficient way to search for a specific screen or better organize the list. Expected Behavior: Ability to search for screens in the prototype list (like for components). For the moment search working not very well and does not recognize naming groups Better organization, e.g., through groups, folders, or favorites (for example: name1/category/)
Hello Figma. This rotated svg does not satisfy the definition of absoluteTransform given by Figma. Here is a public Figma file including this svg. https://www.figma.com/design/zProXoGal9GMYLXSCyu7nX/svg-absoluteTransform?node-id=0-1&p=f&t=avPeqXZs3zNazPe3-0
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.
