First of all, some tables are seperated but really hold the same kind of data.
For example, video, audio and images are all saved as urls, so you can join them in one table instead of 3.
This will greatly simplify your schema, and allow you to permit several types of content in one collection (for example, a wedding album that contains images & video).
Second, if users upload the content, how come you can keep it in urls? Where is the data actually saved? My first thought when seeing this was that you need to keep a binary object column for the content itself.
Third, did you mean to have a many-to-many connection between content and albums? It means every item can be in several albums. If you would like to limit an item to only one album, you would not use a "connector" table, but instead keep an album id in the content table itself (a foreign-key to the album table).
And last - as a "social media file sharing" schema, it seems to be missing the social aspect (where is sharing information saved?).