Hi there. I’ve noticed a not too good thing about images. When you create a blog and upload a picture on the post settings and then click delete image, it never actually deletes the image. It remains in the server.
I think it’s more convinient to have it deleted it. Otherwise is extra space. I uploaded the same image 4 times after modifications, now I have 4 copies 
, I only need 1.
Thank you
The reason Ghost doesn’t delete images now is partly limited by the fact the image can be linked elsewhere.
The idea encompassing this one is Better image/file management & optimisation - #13 by chrisalley
I understand that. Question… when you upload an image to the post, so it can be the feature image that appears at the index page, how can you reuse that image? You would have to manually copy the url, there is no way to just copy the “local” path. Now, how can you reuse that same image in another feature post? You can’t, there is no way to reuse the image for feature posts. I don’t think anyone is going to copy the link of a featured image on the post, and paste it… where on the same post? That wouldn’t make sense. The only thing that I can think of is to share the post and include sort of the link with it’s thumbnail.
Anyway, it’s an idea, if you think it’s best, then keep it 
This idea is similar to the one you gave, that would prob. be best, a media file manager
BUMP!
This is actually a MAJOR security and privacy concern. If I accidentally upload some content with sensitive information to a blog post and publish it, I currently have no way to remove the content from the public web. Sure I can remove the image link from the post (or perhaps delete the post), but it seems like the link to the image asset is live and likely indexable by search engines.
Again, I’m not sure if the security and privacy concern has been fully assessed here. Please update or chime in if there is a way to remove content entirely from the server.
Ideally there should be some sort of a file/asset manager, that shows the reference count to an asset. When the asset has a reference count of 1 it can be deleted without warning. With a reference count of > 1, a warning notification can allow the user to break all existing post links to it and delete it, or just delete it from the current post.
BUMP is there any way to get feedback if this security issue was acknowledged and is there a workaround
?
I can not believe why Ghost has no such important feature.
Hi @afern247 @lessismoreorless @Boryl @HauntedThemes @nuclearpengy @chrisalley @eexit @tpiros @Fatur_F @dsecareanu
Perhaps this prototype file manager can help to solve this situation.
You can support it with a vote or contribute ideas.
Link in Ghost Forum: Prototype: New File Management
Best regards.
Yes please do this I don’t want to pay extra for hosting when I don’t use the files