Figma Make accepts uploaded files but cannot access PNG/PDF attachments

Hey hey ​@mriaia 🤩 Thanks for flagging this. 

Can you do the following:

• Grab a full-screen, unzoomed screen recording that captures the whole flow — clicking Add context, selecting the file, the attachment chip appearing in the prompt box, and then sending the prompt and getting Make's response. I want to see is whether the chip stays visible in the message history after you hit send, or disappears at any point
• Access to the Make file itself. Could you share a link to the file, and invite support-share@figma.com as a viewer? Adding that account won't affect your billing or take up a seat on your plan
• Both can be shared in a support ticket if privacy is a concern

A few questions:

• When in the session are you attaching? Is it the very first thing you do in a brand-new Make file, or after Make has already generated something? If you attach the same PNG again on a later prompt in that same file, does it behave any differently?
• Does the attachment chip survive the send, or does it vanish from the prompt box before or after you submit?
• It can’t hurt to check with your admin whether the Make file attachments setting is enabled for your org

Talk soon! — Jaycee

Hi Jaycee — thanks for getting back to me! I’ve done some further testing and can answer the questions.

Unfortunately, I’m not able to share the Make file with support-share@figma.com because I’m working within an Enterprise organisation and our security restrictions prevent us from inviting external users to internal files.

For the same reason, I’m not able to provide a full-screen recording of the existing Make file, as it contains internal content that I can’t share externally.

However, I can confirm the following from my testing:

• The attachment chip stays visible at all times. It remains visible in the message history after I send the prompt and is still there even after many subsequent messages. It never disappears at any point.

• I’ve tested attaching files at different stages of a Make session. I’ve attached a PNG at the start of a new Make file and also after Make has already generated content. The behaviour is the same in both cases.

• I’ve also reattached the same PNG in a later prompt in the same file. This makes no difference — Make still says it cannot access the attachment. For example, I receive:

“I cannot access the attachment. The file is not on the filesystem — no PNG with that name exists anywhere in the workspace.”

It then suggests that I manually place the file into /public/ or provide it as a base64 data URL.

• The same issue occurs with PDFs. The attachment appears successfully in the conversation, but Make says it cannot access/read the actual PDF.

• Make file attachments are enabled for my organisation. Colleagues within the same Enterprise organisation, with the same plan/seat setup, are able to upload images and files to Make without this issue.

So from what I can see, the attachment is successfully being added to the conversation and retained in the message history, but the underlying file itself doesn’t appear to be becoming accessible to Make in my case.

If there are any diagnostics, IDs, logs, browser details, or other tests I can provide that don’t require sharing internal content, I’d be very happy to help investigate further.

Hey ​@mriaia 👋 I totally understand about the privacy issues. I opened a support ticket for you. The ID is 2085356 and the email subject line is Figma Make attachments register in chat but the file never becomes accessible to the agent. Please keep an eye on your email (and spam folder if necessary) for the email and any replies from our team. I appreciate all your help so far! — Jaycee