I've had the same thing happening for a long time now. I put in a help ticket and received what I considered a good faith effort to look into it, but since it's more of an annoyance than a priority it's likely been back-burnered due to all the larger issues being worked on. Here is the text of the last response that I got. Being that it doesn't impact my upload quota and that I rarely look in the "recent upload" section once organize a file into a folder I've ignored it. On 9/2/2022 4:48 PM, Support wrote: Thank you for the detailed steps, I was able to reproduce this pretty regularly as a result. Apologies for the delayed response as I spent a good bit of time looking into what was going on (probably more than I should as a support rep...). It seems that the core of the issue is actually in the function "copy to library" which seems to also be duplicated within the "Copy to folder" functionality as well. It seems that this copy actually makes a copy. Which... typing out sounds intuitive, but in practice, seems somewhat odd as having duplicate versions of the same image is not very helpful or useful most of the time (I can see a world where someone wants to sort assets by game and wants to copy an image to two folders). But what causes this to display oddly, is that the "copy" is actually an entirely separate NEW image. Since the NEW image is a full on new image, it ALSO shows up in recent uploads. As such, when you filter images from your art library, it filters the NEW image, but NOT the original image that was uploaded. Because the NEW image is in the folder/library and the original never actually moved from recent uploads. It is a bit difficult to say for certain if this is the intended functionality (given the scenario I outline, in addition to the fact that the copy does not contribute to storage quotas) so I am passing it along to product and development to make that determination. But it is definitely confusion and deserves a look. What I did find, is that you can work around this. If you make the folder and then manually move the original upload from "Recent Uploads" to the folder you made by dragging it, you won't run into this issue. I can't say for certain when the issue will be addressed or fixed, but now we know what's going on and that's a start!