From what I understand it does not provide anything related to file storage. It just allows file header publishing and file integrity confirmation.

Regarding file storage directly within the messages/events I'm a bit skeptical. This could lead to some huge data to download, as the nip-95 would allow keeping messages and events quite small.

I'd rather have anoter kind of event or message that would provide a pointer to the content, be it the content is on another P2P protocol ( hello torrents ). This way clients could configure and fine tune how to handle each different kind of file