|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #29878 ImageCreateFromJpeg returns 'not a valid jpeg file'
Submitted: 2004-08-28 23:00 UTC Modified: 2006-02-05 17:09 UTC
From: cyleriggs at kc dot rr dot com Assigned: pajoye (profile)
Status: Closed Package: GD related
PHP Version: 5.0.1 OS: Linux
Private report: No CVE-ID: None
 [2004-08-28 23:00 UTC] cyleriggs at kc dot rr dot com
When calling ImageCreateFromJPEG() on a valid jpeg file it fails and i get errors such as the following in my php error log:

[28-Aug-2004 05:21:29] PHP Warning:  imagecreatefromjpeg() [<a href='function.imagecreatefromjpeg'>function.imagecreatefromjpeg</a>]: '/usr/local/apache2/htdocs/pictures/Before Dad Went to Iraq/IMGP0008.JPG' is not a valid JPEG file in /home/www/pictures/index.php on line 43

however as can be seen through this link the file is a valid jpeg file: Dad Went to Iraq/IMGP0008.JPG

Also i have a memory_limit of 25mb so this cannot be the issue.

Something that might help:

I am writing this code for a picture gallery browser, while most pictures load, about 10% of my pictures cannot be opened through ImageCreateFromJpeg(), however it is always the same pictures that cannot be opened. The only trend i can see is that this does not appear to be happening on small jpegs.

The page that I am having problems with is  The source code for this is at

Expected result:
The image would be loaded and code continue to execute and i get the error message described above.

Actual result:
Sometimes images load sometimes images cannot be opened.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2004-08-29 12:22 UTC]
Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit as this bug system is not the
appropriate forum for asking support questions. 

Thank you for your interest in PHP.

Your jpeg file is not valid. PHP could not take care of each possible failures in image files. Desktop softwares could. Fix your image and replace it.


 [2004-09-30 21:05 UTC] paul at gslip dot com
I disagree. I have used my code successfully on until the upgrade to php 5.0.1. I now get exactly the same results as the original poster.
Images that worked fine on previous versions now do not. I have a sample image that can be provided. I also have code I can share with the PHP team although I cannot post it here as it is lengthy and copyrighted.
 [2004-10-05 04:34 UTC] cyleriggs at kc dot rr dot com
After playing around with the images themselves i have found that converting them from jpeg to png then back to jpeg fixed the problem and yielded no quality loss. I used the linux tool set called ImageMagick to do this. I wrote a short perl script to go through all my images and fix them. Other than this i have found no other way of stopping this. one interesting fact though is that while converting the images with the imagemagick utility it complained about some corruptions, however it was still able to open them fine and convert them. Maybe PHP is being too picky about the images that it opens as despite a few corrupted bytes EVERYthing was able to open these images except for PHP.
 [2004-10-05 09:33 UTC]
PHP only reads non-coprrupted files - there is no bug here.
 [2004-10-07 03:18 UTC] cyleriggs at kc dot rr dot com
Okay, so how about a feature suggestion than, i think that there should be the option in GD that allows you to try and open images that have a few corrupted bytes. If other programs can open them just fine what would be the harm in allowing programmers to choose to live with the corruptions?
 [2004-10-07 09:12 UTC]
Corrupted files are invalid, and may crash an application if attempted to use. That's why we will not implement that. (Actually, it's not a PHP issue either, it has to do with how libgd handles opening files).
 [2004-10-12 17:23 UTC] paul at gslip dot com
Has anyone at php verified that the images are corrupt? In what way are they corrupt?
Here's what I know: 
1- These images were supported with no issues whatsoever before I 'upgraded' to php 5.x

2- Every other piece of software I own, including Windows Image Viewer, Photoshop, Paint, IE, Netscape, Imagemagick, etc. open the files with no complaint.

3- A visual inspection of the files on the byte level show nothing out of the ordinary.

That all leads me to believe that the images are not corrupt and that PHP or GD has a bug.

Please, stop being so stubborn and at least look at the problem. I can show you hundreds of examples of where this is happening on the web. Just do a google search for 'is not a valid JPEG file in' to see for yourselves how many sites are having this issue.

I suspect there's some new twist on the JPEG format that new digital cameras are using ,or something along those lines, that GD and PHP just aren't yet up to speed with.

Let's get this solved folks.
 [2006-02-05 17:09 UTC]
This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
Thank you for the report, and for helping us make PHP better.

You can now allow the jpeg decoder to be more tolerant/weak:

// 0 is the current behavior
ini_set('gd.jpeg_ignore_warning', 1);
$im = imagecreatefromjpeg($file);

Php 5.1.3+ will contain the fix.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Jul 24 14:01:31 2024 UTC