Report a Problem

Figjam has the same crummy experience trying to copy a page/board as Figma does...you can’t just duplicate or move a board, you have to open the original, open a new blank file, copy and paste all content manually. It sucks. What is really being annoying right now is that images on the Figjam board are not being copied over even tho they are unlocked.

When I use the /v1/file endpoint to retrieve the file data vie REST request, in the effects property of a node i cant see the relevant properties for the glass effect:{    type": "GLASS",    "visible": true} Is there any option to get the properties that are also available in the PluginAPI or a timeline when this data is present in the REST Api? Thanks, Felix

So, ive been using figma make for a few days now, and everything is absolutely smooth , getting amazing results, creating amazing flows, complex interactions, but starting from yesterday, my figma make became completely DUMB, every simple change that i make on the project, everything breaks, for example, i have a 3 tab design, with everything working fine, i asked figma make to remove 1 item of the accordion on the fist tab and the entire project breaks, the second and third tab simply lost their funcionalities just by doing this, ive tried just edit a text and still gettin this behaviour, everything breaks.Ive been asking consistently to figma make does not interact or interfere with anything else that im asking , but gettin the same faulty results.Dit anything change? why is this happening? do the IA getting dumber ?

If I use CMD+B shortcut on any Frame/Section, it bolds everything inside it, but can’t undo that operation using CMD+Z

Big fan of Figjam, but what drives me crazy, it is impossible to move a line. It is also not possible to copy and past it, without the pasted line having a different rotation. It looks like this is a know, but unsolved issue, for the past 3 years:  

Issue:When using the "While Hovering" interaction on a component, the hover state can become stuck — meaning it remains active even after the cursor leaves the element. This is especially noticeable when hovering over multiple instances of the same component in a prototype. The hover state lingers on all previously hovered items instead of resetting properly. Steps to Reproduce: Create a component with default and hover variants. Add a “While Hovering → Change to hover” interaction. Place multiple instances of the component in a layout. Preview the prototype. Hover over several instances one after another. Previous components stay in their hover state, even after the cursor leaves.   Expected Behavior:Only the element currently being hovered should show its hover st

The built in UI-Kits don’t seem to allow for switching appearance modes anymore. when ever I try to switch to dark mode nothing happens. my personal libraries still work.

There is a problem with rendering gradients. Everything looks great in the preview, but in the workspace there are terrible artifacts. the problem also concerns effects and blend mode. redmibook pro 15Есть проблема с рендерингом градиентов. В превью все выглядит великолепно, но в рабочем пространстве - ужасные артефакты. проблема также касается эффектов и режима наложения. redmibook pro 15

Hello,Figma exports some PDF without a lot of elemets, They all  are nested in the frame. They all visible in the preview in the windows browser but not visible in the PDF doc. In all PDF viewer/reader. I did all  - exported one by one, cleaned cache, restarted PC, but it still not visible.  UPD -- FOUND workaround! Ony one color elements were not visible.  I slightly changed it and it worked)))   

Every time i try to publish the library i get this same error and then i cannot publish the new added components. 

When exporting nodes with exportAsync({ format: 'SVG' }), the REST API sometimes generates <g filter="url(#id)"> references pointing to a <filter> element that has no primitives. According to the SVG spec, applying such a filter causes the group to render nothing.This means that shapes with simple fills/strokes (e.g. Polygon, Line, Vector) can appear correctly in Figma, but the exported SVG appears empty in strict renderers. Steps to reproduce: Create a polygon, vector or line. Add a drop shadow effect. Export via plugin using node.exportAsync({ format: 'SVG' }). Inspect the SVG: the node is wrapped in <g filter="url(#filter0)"> but <filter id="filter0"> has no child primitives. Open the SVG in browser → shape is invisible. Exp

I have a number of main components which I’ve set to ‘Fill width’ - however, when I drop an instance of this component into a frame, it goes in as ‘Fixed width’, aligned to the actual width the main component. For example, Main componentContaining frame is 1000px, button is set to fill, so the button is 1000px (responsive). InstanceContaining frame is 500px, button instance is added and goes in as fixed width 1000px - I have to manually set it to fill in order for it to fill the 500px frame. Expected behaviourMain component = Fixed width  ∴  Instance = Fixed width Main component = Fill width  ∴  Instance = Fill

Hello Figma Support Team,I would like to remove my saved credit card details from my Figma account. Please assist me with deleting the existing payment method. Account email: [redacted by forum admin/moderator to remove PII] Workspace/Organization name (if applicable): Sai santhosh If necessary, please guide me through the process to ensure my billing information is fully removed.Thank you for your assistance.Best regards,[Your Name]

Hey Team, Since a few days I have been experiencing this problem where the code generation cuts off mid-way and then I receive this error “Try Again with fewer inputs". Funny thing is that Figma Make shows Version Success on the chat but in the preview section it shows “Build Error” and also “Error Messages” in the console.  When I try to autofix these, the same issue occurs where the code generation process cut-off abruptly. This is happening randomly and at times, this whole cycle keep continuing. I have not been able to code or make any updates because of this. Its like stuck in a constant glitch. Kindly help me out

In any other vector software, Snap to Geometry (or snap to point, depending on the software) means anything will snap to object points or edges. In Figma, Snap to Geometry doesn't allow me to snap a guide to just any vertex (point), only some points that are around the object's bounding box. It's even worse: some points only snap with horizontal guides and others only vertical ones, depending on the point's location. Try to snap horizontal and vertical guides to all points of a T shape, you will see the problem.It also doesn't snap other objects to these points… Actually it doesn't snap anything! Once I deactivated Snap to Objects the guides don't stick to anything anymore.That function is broken and it needs to be fixed.

Hi Figma team,I’m writing because I’ve just noticed a charge of $43.20 on my account, despite having cancelled all paid subscriptions well before the renewal date.To make matters worse, I received absolutely no email or notification warning me that a payment was about to be processed. This lack of transparency is extremely disappointing, especially coming from a company like Figma.On top of that, trying to check or manage my subscription and billing information is unnecessarily complicated. It genuinely feels like the system is designed to make it difficult for users to know where they stand, what’s active, what’s not, and what they’re being charged for.Frankly, it starts to resemble the kind of tactics used by less reputable services, even scammers: no clear way out, no notice, and a surprise charge you can’t easily stop.I’d like this payment to be reviewed and refunded immediately, and I’d also appreciate a proper explanation of how this was

When I use Figma Sites, fonts in the build view looks fine.But when I use Preview, some fonts default to arial. I’m using the latest version of Figma Desktop for Mac. Authoring View - Montserrat Semi BoldPreview - Changes to Arial Bold The fonts are loaded on my system.

Hello! We have been having memory trouble with our Library file and have been working on making it more usable.In the process of doing this I did a test where I duplicated my library, and then proceeded to erase everything from it, every page, every style, every variable, every linked library.At the end the only thing left was 1 empty new page that I had created. After a refresh, the file was still showing 26% of memory usage and over 75k layers. I’m really unsure of what to make of that, over a half of the memory usage of my file is coming from… Nothing? Is this a known bug?

 I’m seeing “An error occurred while copying this file” when I attempt to duplicate a version from the history of a merged branch - see attached. Is this not doable? 

Hello, I encounter a problem with a certain file.Some random square/rectangles/shadows appear on it but only for me (the other user on the file don’t see it), even when I’m connected on the owner acc.Also, the shadows change places when i zoom/dezoom I can’t find a solution or understand where its from  

I have a similar problem, a specific page doesn't open (all the others are working), Figma shows the same error. I just tried to apply textures to the text, and then everything stopped working.

My device is Mac mini m2. 8 GB, 256 GB. When I use Figma, &zoom in, zoom out, or do something, my screen goes back. RAM is 2 GB, and storage is 80 GB empty. What is the problem?

I am using the figma mcp’s get_image config for the image is as follows  when i click on a node and select copy as png the image is clear crisp but when i use mcp to export the image its blurry and not so great

The recent update to Figma's keyboard shortcuts has introduced a significant usability issue that impacts designers' workflow, particularly in image cropping operations. Previously, when working with images, the up and down arrow keys naturally controlled the image position within the frame, allowing for quick and intuitive adjustments during the cropping process. However, the recent change has reassigned these keys to switch between Crop and other modes instead. This modification has disrupted a well-established workflow that designers have relied on for efficient image manipulation.The new behavior requires additional steps to accomplish what was previously a straightforward task, as users must now use alternative controls for image positioning. This change not only breaks designers' muscle memory but also adds unnecessary friction to the design process. The impact is particularly noticeable in tasks requiring frequent image adjustments, where the additional clicks and

I have designed a website in Figma Sites. But after publishing I found that some images are not displayed, only black squares. The problem is only on mobile browsers (Chrome and Safari). In addition, if I minimize and maximize the browser a couple of times, the image will appear, but only the one that was in the visibility zone.There is a feeling that this is a bug, some kind of optimization that should have displayed the image only when viewing.Help me find a solution!Website — joycast.ai.