Feedback: Decouple File Management from AI Credits in Figma Make

I ran out of AI creds so I’m trying to replace the auto generated leaf icon with my company logo manually. Using the file browser i created a new file called DuritasIcon.tsx which imports the logo from Duritas_Logo-removebg.png, which i had no issue just dropping into the project. However when I try calling DuritasIcon.tsx from my navigation.tsx it cant find it because DuritasIcon.tsx isn’t in my src/app/components folder. I’ve trying dragging and dropping it with no luck, it just stays in root. Any tips on how i can move the file to the correct dir. Or alternatively anyone have a workaround for ussing my custom image? 

Hey ​@GwenFred — thanks for taking the time to lay this out. The distinction you're making between file management actions and AI-powered actions is a really useful framing, and I've shared it with the team.

I don't have access to a timeline to share on this, but your feedback is noted and will be part of the conversation as we continue to improve this experience.

We'll keep this resource updated with the latest releases: Figma product news and release notes.

Let us know if any other observations come up or any questions remain!

Hey ​@Kazuriah - thanks for your post!

I just moved your post over to this thread on this topic. My teammate ​@Tom Reem actually shared this with the team earlier, too!

For your specific need, have you tried importing the PNG directly into your navigation component and creating your component directly in the same file? That might work for you while you until your credits reset, and then you can just have the AI move the code to a separate file. Feel free to reply back if that works for you or if you got it work in a slightly different way.

Thank you for looking into this. Context: I learn this through multiple iteration and find that it's better to have different files (AI chats) focus on specific tasks and then I move these tsx files from the smaller files into a larger file. I find this to be most efficient to control my design execution and debugging without npm. (Cart before the horse)

I am creating a bunch of different .md files for my Make Kit and am uploading them. However, when it uploads, it goes to an ambiguous area. I want it to be in a folder, but for some reason, I cannot drag and drop that file into a folder. 

[Moderator note: This post was merged from Can't move uploaded files in structure on Make Kit into Feedback: Decouple File Management from AI Credits in Figma Make on 27-Apr-2026.]

Hi ​@Joanne Wong, welcome to Figma Forum, and thanks for raising this.

You're not alone here — a few other designers have shared similar feedback. I've merged your post into a thread where we're tracking this so the product team has visibility across all reports.

I don't have a timeline to share, but your feedback is noted. One quick question — is the main concern that file management actions like moving assets require going through the prompt box? Any additional detail on how this impacts your workflow would be helpful to pass along.

[Moderator note: This post was merged from Can't move uploaded files in structure on Make Kit into Feedback: Decouple File Management from AI Credits in Figma Make on 27-Apr-2026.]

Hey all thank you for the prompt reply to my inquiry.

​@adamsmasher My components are all tsx files auto generated by the AI. So I wasn’t sure what exactly you meant when you said “have you tried importing the PNG directly into your navigation component and creating your component directly in the same file?” Especially because when I press the Create new file button in Figmas file explorer it doesn't seem to give me a choice where it places the new file and automatically creates it root dir.

However you question did make me think if importing was so easy perhaps i could just drag my local version directly to the dir i wanted and that did seem to work. Now you can see the png and DuritasIcon.tsx both in the components folder, and that does resolve  everything so thank you all for the help!

Hi ​@Tom Reem! Thanks for flagging this other thread. 

One quick question — is the main concern that file management actions like moving assets require going through the prompt box? Any additional detail on how this impacts your workflow would be helpful to pass along.

I think there are two reasons of why this impacts my workflow:

1. Waste of credits. Similarly to the OP here, it seems like a huge waste of credits just to move files through the prompt.
2. Unexpected UX. In other file managers, dragging and dropping files within the tree is expected. I was pretty surprised to see that I was unable to do this within the Make Kit.