TBH you could really do with a breakdown for this. Is there a way to get the details of the threads that are taking the most size?
Us just guessing random threads based on images is probably not the best idea.
I assume there isn’t a lower tier storage option you can really aim for so we’re looking at just bringing it down 10-20GB to give us some overhead so if we find there’s like one monster thread causing it all (it’s gonna be the Simpsons one isn’t it?) then we might just kill that and we’ll be fine.