[wp-trac] [WordPress Trac] #57975: Uploading iPhone JPG images with EXIF data causes unwanted file modifications.

[WordPress Trac]

#57975: Uploading iPhone JPG images with EXIF data causes unwanted file
modifications.
----------------------------+----------------------
 Reporter:  hbaumhardt      |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Filesystem API  |     Version:  6.1.1
 Severity:  normal          |  Resolution:  invalid
 Keywords:                  |     Focuses:
----------------------------+----------------------
Changes (by azaozz):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Hi @hbaumhardt, welcome to Trac!

 All of these are either expected behaviour or depend on what software is
 available on your server. When a "raw" image is uploaded (like a photo
 form a camera or a phone), WordPress prepares it for use on the internet.

 The first thing that happens is to reduce the image size to a max of
 2560px width or height. This also reduces the image file size to about
 700-800KB. Original photos are anything from 3-4MB up to over 20MB which
 is not acceptable for use on internet.

 The second thing that happens is to rotate the image if there is EXIF
 rotation information. This ensures the image and all of its sub-sizes are
 displayed correctly in all cases. If rotated, the `-rotated` suffix is
 added to the file name to distinguish it from the original.

 Preserving EXIF data depends on whether ImageMagick is available on your
 server. This info is available in the Info tab in Tools -> Site Health.

 Don't think the resolution setting affects image sizes. Browsers typically
 assume images are displayed at 96dpi for CSS purposes (even on high-res
 devices/screens), but the images are considered by their pixel dimensions.

 > These are all unnecessary and unwanted actions.

 None of these will happen if you prepare the photos for internet use
 before uploading them, and ensure ImageMagick is available on the server.

 Going to close this as "invalid" as all is expected behaviour or depends
 on the server. Feel free to reopen (with examples, etc.) if you believe
 WordPress is doing something incorrectly.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57975#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform