It really annoys me that Figma automatically creates subfolders when you export an element that’s inside a component and has a ‘/’ naming convention. I always have to go back into the folder and delete the folders or rename everything. It would be great to have a simple checkbox toggle in the exports panel to enable/disable creating subfolders, similar to Illustrator.
Fully agree! Being allowed to choose NOT to auto-create subfolders would be amazing and save me time and hassle on a regular basis. Thank you for considering this!
Oh my god PLEASE. It’s so annoying—just put the files where I asked figma to put them
this issue just caused me a big pain when trying to quickly export for a presentation. big +1 to this request.
I can’t state just how annoying this is. Exported files will just not “show up” where you told it to export. Instead you have to figure out which folder it thought it should go, open Finder individually and stupidly navigate there. It’s just so annoying.
Yes, this. So annoying when the exported screens or assets are nested in 3 or 4 folders.
Yes, no subfolders, and a system dialog to be able to name the file! So much time wasted to delete folders and rename files!
my life would be a lot better.
please Figma do it !
It would be sooo useful if there was an option to automatically replace the slash with a dash ‘-’ instead when exporting, so we wouldn’t have to rename everything in Finder afterwards!
Swapping the slash would be more useful because we have to use the slash within Figma to organise all the icons etc.
Would be yo helpful.
Just ran into this behavior for the first time, and oof, was it unexpected. And at least in macOS, the system save dialog was very unfamiliar when in this “mode”, not letting me change the filename while saving for example.
If this is unintentional behavior (which I suspect), it should be fixed by sanitizing the filename before sending to the system save dialog. If this is intentional behavior, then there should either be a warning when using / in frame names (which sounds gross tbh) or the option to sanitize them away during export.
Because the current situation, where I just found out that my dozens of frames have problematic names, is… not fun!
I may have found a soft solution, or at least the cause of the bug. I notice that the frame I was editing in, “Search/view historical analyses”, had a “/” in it. I removed the forward slash, and when I went to export an asset in the frame it allowed me to name the file and didn’t create a subfolder. If I try to export assets in frames that have "/"s in the name, Figma will create a subfolder and remove naming options.
Seems like unintended behavior to me.
However, removing my slashed destroys my folder structure in Assets panel, and since there is no other way to create folders of different kinds of assets without using a “/” in the name, it’s not a workable solution for me.
It seems to me Figma really doesn’t care much for developers using their software. We still have no native SCSS, SASS or LESS support, no custom units such as em or rems, no support for CSS variables and this. The fact that this tickets dates from 2021 is just sad 😔
This is VERY annoying. Layer names shouldn’t affect export folder structure.
10000% for that! I hope it would an option in near future!
Plus one on this feature! Simple stuff. Come on, guys! ✌️
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
