Color profile of JPEG's being discarded

zulfiqar tariq

January 07, 2021 14:17

Upon uploading JPEG images we are losing the color profile. Is there any setting to keep the original JPEG color profile intact.

0

• 

  Loic Verger Del Bove

  January 07, 2021 16:23 Edited

  Hi Tariq,

  Can you send me an example image URL so I can check the details and give specific advice?

  You should be able to a specific profile via the 'cs' parameter: https://cloudinary.com/documentation/image_transformation_reference#color_space_parameter

  Best,

  Loic

  0
• 

  zulfiqar tariq

  January 08, 2021 09:28 Edited

  hi this is the original image.
  
  https://uc27d71e454131f84f404acbb3ed.previews.dropboxusercontent.com/p/thumb/ABDMqGt861MoXy23MRFgY9VI_JBF9yl1-yW59tsfEZasXoJX8C0xVgeMTcIrzCeuqjM4QcPgzdBwJ50znZ_p6xN2wGY0dGGFYj3U_DyH_RisAlQIha3XBkJVYZAl7_K5L0-BEcZyaUdFcAkS-elBScnTqbqDkWTE_R39X1oXApgezCN8GbDFk72AlG6gXIxhcznO5Grup_tGgp5BHBiEIPZ6tUITegIds_9n0FEMuiMekXoATWXRhVdKiyuJ0YfB0aq-G_LO8-pBRsZMa-KyBZ5g0GXGoCrw3o5TlinbAN9SC-qFWTXQIBOEjjsvhJn0ls1cENhNLbsa_3dTg97GuOpSQ7a11J51BBKhFECNPxAidw/p.jpeg?fv_content=true&size_mode=5  
  and this the image when it get uploaded to cloudinary.
  https://res.cloudinary.com/dfbe6xcrt/image/upload/expose/qa/images/2a748b6507_2021-01-08-09-26-34_2048_1365.jpg 

  0
• 

  Loic Verger Del Bove

  January 08, 2021 16:24

  Hi Tariq,

  I can't access the link you shared via dropbox and I am reaching a 410 error which seems to indicate that the file has been deleted.

  Would you mind sharing another link to the original image?

  Thanks in advance.

  Best,

  Loic

  0
• 

  zulfiqar tariq

  January 11, 2021 11:30 Edited

  hi this is the updated link 

  https://drive.google.com/file/d/150NA29xiRv8XH8XxxCo_MzLPjkpoJ28G/view?usp=sharing

   

  and this the image when it get uploaded to cloudinary.
  https://res.cloudinary.com/dfbe6xcrt/image/upload/expose/qa/images/2a748b6507_2021-01-08-09-26-34_2048_1365.jpg 

  0
• 

  Stephen Doyle

  January 12, 2021 11:42

  Hi Tariq,

  Thanks for sending the link, although after checking the details it appears that the file you sent on the Google Drive link is not the same file that's in your Cloudinary account.

  The image from your Google Drive link is 344,988 bytes, and has an MD5 checksum of f3ec2e8fb52edd6101d6478f6b6a05ae. The metadata indicates that it has a Color Profile of "ProPhoto RGB" and was created with "Adobe Photoshop 22.0 (Macintosh)"

  The image in your Cloudinary account (2a748b6507_2021-01-08-09-26-34_2048_1365.jpg) is 1422 kB and has an MD5 checksum of 48152ec02d96b6b0469efceb717881af. There's no metadata about the Color Profile in the file itself, but the metadata indicates it was created with "gd-jpeg v1.0 (using IJG JPEG v80), quality = 100". That creator information may indicate that the file was created by the `imagejpeg` function in PHP code, if that helps you to find where the image was created on your side.

  To give a general answer, when you access a link that contains no transformation options (i.e the link to the original file in your Cloudinary account) we will return the exact same file that you uploaded to us, or the result of the Incoming Transformation that you specified as part of the upload, if applicable.

  I checked your account settings and don't see any incoming transformation on your upload presets, so the only way the file in your account could be different from what we received is if the file was uploaded via our API and you specified an Incoming Transformation in the API call parameters.

  That's not the case for this example because you didn't upload the file to us explicitly; we retrieved the file automatically using the auto-upload mapping you configured for the /expose folder, and the remote path configured is an S3 bucket's HTTPS URL path.

  In this case, I've confirmed that the 1422kb image file in your Cloudinary account is identical to what we retrieved from your S3 bucket, and is identical to what's in your S3 bucket now, at the `qa/images/2a748b6507_2021-01-08-09-26-34_2048_1365.jpg` path in that bucket.

  If that doesn't help you find the source of the discrepancy, may I ask you to please open a support request for us directly?

  In a support ticket we can share information from our logs and details about your account information such as the exact remote URL we accessed from your S3 bucket, but we can't post such information here in the publicly-accessible forum.

  Regards,

  Stephen

  0

Post is closed for comments.