Skip to main content
Question

Figma make is losing assets. Is this a hallucination or system error? Losing assets is not acceptable.

  • January 25, 2026
  • 1 reply
  • 21 views

PeterSpev

The “assets” referred to by Claude were a series of five pngs placed into individual files, autoframe assigned and converted to components. Each were added to the Figma Make Claude through the “+” UI. Two worked. Three were lost.

Directly quoting Claude within Figma Make:

Perfect! I've identified the issue - the Figma asset images for Round, Flat, and Socket Cap are not available in the asset system (the figma:asset imports are failing to resolve).

I've created placeholder graphics using CSS gradients and SVG for these three missing screw types:

  • Round: Purple gradient with a circular design
  • Flat: Pink/red gradient with a flat-head screw design
  • Socket Cap: Blue gradient with a hexagonal socket design

All five screw types should now be visible in both the test rows and the wheel picker. Once the actual Figma assets become available, we can easily swap the placeholders back to the real imported frames.

...

I’ve added an asset test component above the wheel picker. Please check:

  1. Visual check: Do you see the three screw images (Round, Flat, Socket Cap) in the gray boxes at the top?
  2. Console check: Open your browser's developer console (F12) - you should see messages indicating whether each image loaded successfully or failed.

Let me know what you see - if the images appear in those boxes, the assets are now available and we can update the wheel picker to use the real images instead of the placeholders.

...

Confirmed - the assets for Round, Flat, and Socket Cap are still not available in the Figma asset system. The wheel picker will continue using the colorful CSS/SVG placeholders I created earlier, which are fully functional. When the actual Figma assets become available in the future, we can easily swap them in by updating the NormalizedFrames.tsx component.

1 reply

Celyn_L
Figmate
  • Figmate
  • January 26, 2026

Hi ​@PeterSpev — Celyn from Figma Community Support here.

Thanks for flagging this and for sharing such detailed context, including the Claude output. Sorry you’re running into trouble adding assets to Make. I understand how frustrating this can be, and we’d like to take a closer look to better understand what’s happening on our end.

I’ve created a support ticket on your behalf so our Technical Quality team can investigate further and assist you directly.

Please check the inbox associated with your Figma account for a message related to case number #1707705, and reply directly to that case with the following:

  • A screen recording showing the behavior end to end, with the full Figma window visible

  • A link to the affected file(s), and an invite to support-share@figma.com with edit access so our team can test on our side
    (Don’t worry, adding @figma.com users will not affect your billing.)

This should give the team what they need to dig into the asset resolution issue more closely.

Thanks for your patience, and we appreciate you taking the time to report this and work with us as we get it resolved 🙏