When pictures, images get corrupted on a Drupal site.
The most evident forthcoming problem with a site in general happen when we notice that images all around gets corrupted.
After we/you have worked hard to configure/set your Drupal site after a while you start to see that on some pages, profiles nodes or om ever node you have the possibility to add images, they get corrupted.
You start trying to analyse any aspect you can to restore the images.
- You go to logs reports to check if you have any relevant indication: no infos
- You remove image and upload new version: no success
- You try to run cron-job for see if the images gets rebuild: no success.
- You empty the default cache and try to reload the page where you got corrupted images. no success
- You disable all compression settings as to see if you get changes: no success
- You start even to try to reinstall all modules that have a direct impact with images: no success
- You start to check folder and file permissions of your Drupal installation: no success
Now those are just some of the action one Drupal newbie will try to take, for sure you can tell me more and add to this list.
Anyway the last guessed reason may be that your ISP backup server did corrupt something with your Drupal installation? Who knows!
If you do not have your own Server Host there are few chances you may able to find out.
Below one of the possible cases Drupal may inform you why there is something wrong with your Drupal Site.

This informations are shown when you start to change all your file and folder permission to the most restricted set: unix file/folder permission 555.
I did that to show you that Drupal just start to give you some information in the worsts cases.
This is one of the worst case scenario to handle this problem because you can start to reassign all default permissions to the files and folder one by one and see if you get the image corruption problem solved.
Note: for more info about another image corrupted case with Server Configuration see:
FollowSymLinks
external Article


Comments
One more case is to have your
One more case is to have your host server or local test server (mostly on windows OS) an incompatibility with
FollowSymLinks, a directive in your web server configuration that tells your web server to follow so called symbolic links
in this case open your .htaccess file in sites/default/files or sites/your_custom_site_name/files and disable
Directives:
adding a "#" before the directive lines like below:
#Options None
#Options +FollowSymLinks
Note: this case happen when FollowSymLinks is already enabled in (your) web-server httpd.conf file, so you might not necessarily need to specify that directive in your .htaccess files.