Copy link to clipboard
Copied
Copy link to clipboard
Copied
My guess is that the image you received from the manufacturer was created in the ProPhoto color space without the profile embedded, or you exported it without checking Convert to sRGB and Embed profile.
Web browsers will assign the sRGB profile to images with no embedded profile (untagged).
If the image was created in ProPhoto (or Adobe RGB), it will display with wrong colors because sRGB is the wrong profile.
When exporting, always check Convert to sRGB and Embed profile.
I opened your screenshot in Photoshop, and it had Adobe RGB embedded. probably because you use Adobe RGB as a monitor profile.
I assigned the ProPhoto profile, which changed the appearance to this:
In the future, please do not attach images, use the Insert Photos button in the toolbar to embed them in your posts.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
The image is untagged – it does not have an embedded profile.
So you have to assign the profile that seems to be correct, my guess is that it's Adobe RGB, but you can try sRGB and ProPhoto as well. (Edit > Assign profile)
If you set the status bar to Document profile you can see at a glance what color space the image is in.
You can also see this in the Info panel, if enabled in the panel options.
RGB is a color mode – meaning that the image has three channels – red, green and blue.
sRGB, Adobe RGB and ProPhoto are color profiles (or spaces), that describe how the colors in the image should be displayed.
When you open an image in Photoshop, the colors will be converted from the document profile to the monitor profile.
This is the basis of color management.
If the image is untagged, no color conversion will take place – and the image will display with wrong colors.
Copy link to clipboard
Copied
What status bar?
Copy link to clipboard
Copied
Bottom left corner of the Photoshop window.
It is only visible when you have a file open.
Copy link to clipboard
Copied
The document profile for the downloaded image is set by default to Adobe RGB (1998) (8bpc). Is that good?
Copy link to clipboard
Copied
The correct profile is the one that makes the image look right, it might be Adobe RGB in this case.
It's not clear to me exactly what happens when you open the image. Do you get a dialog about missing profile?
Also, please post a screenshot of your color settings (Edit > Color settings)
Please do NOT attach the screenshot, use the Insert Photos button as I described earlier.
Copy link to clipboard
Copied
No dialog box upon opening the image file.
Copy link to clipboard
Copied
Your color settings are OK, except you might want to check Ask when opening for Missing profiles.
If you know what color space the image was created in, you can assign the profile right away.
If you don't know what color space the image was created in, choose Leave as is and click OK.
Then use Assign profile to find a profile that looks right. (sRGB, Adobe RGB or ProPhoto)
"No dialog box upon opening the image file."
"The document profile for the downloaded image is set by default to Adobe RGB"
Please explain how this happens. An untagged image should open untagged unless you assign a profile in the Missing profile dialog.
Copy link to clipboard
Copied
How do you know for sure it is provided untagged from the supplier?
And where would I find that "Ask when opening for Missing profiles" checkbox?
Copy link to clipboard
Copied
Post a screenshot of this:
It shows what the embedded profile is, or "untagged" if there is no embedded profile.
Copy link to clipboard
Copied
You posted the image from your manufacturer previously, saying "Find the downloaded file in the attachment."
I opened the image in PS and it was untagged.
The Ask when opening checkbox is in the color settings, bottom left in your screenshot.
Copy link to clipboard
Copied
Interesting that you get an untagged profile upon opening the same image file.
Here's what I get now upon oponing the file:
Copy link to clipboard
Copied
It could be that the profile is stripped out when posting an attachment.
Which would be another reason not to use attachments, but embedding images in posts, which preserves the profile.
The Embedded profile mismatch dialog will not appear with the color settings shown in your screenshot, so it looks like you have changed them.
The Color management policy for RGB is set to Preserve Embedded profiles, which will use the embedded profile to display the image, it will override the working space. This is the correct setting – there is no need to convert the image to the working space.
The working space only applies as a potential fallback for untagged files, and to images you create inside Photoshop.
It will be the default profile in the New file dialog, but you can choose any profile you like.
How does the image look when you choose Use the embedded profile in the Mismatch dialog?
Copy link to clipboard
Copied
>How does the image look when you choose Use the embedded profile in the Mismatch dialog?<
I do not see any difference. When sampling it in the middle of the image, I get this color: f3f3f3.
I'd like to try to use the Color Replacement Tool to go from f3f3f3 to ffffff. But, so far the Color Replacement Tool does nothing. Yes, I've set the foreground color to ffffff.
Copy link to clipboard
Copied
@SSL-ADT IF your image looks OK to your eye - ideally on a calibrated and profiled screen - as an Adobe RGB image, then that's good. BUT if you are planning to save for use on Facebook you'd very likely be best served by making a copy, archiving the original and converting the copy to sRGB before saving (and embed the profile during save).
An sRGB file has the most chance of surviving out there online.
Beware Hex codes, (you mentioned f3f3f3 & ffffff)
Perhaps you are already aware that, like RGB pixel values, Hex values alone are not an unequivocal* way of defining colour.
That is, until the Hex code (or triplet of RGB numbers) is/are associated with an ICC document profile e.g. sRGB IEC61966-2.1, Adobe RGB (1998). The ICC profile makes the numbers unequivocal.
Hex codes are simply RGB numbers expressed in ‘Hexadecimal’. So, rather than RGB 0 to 255 you have 00 to FF.
*(incidentally, L*a*b* values do provide an unequivocal colour definition)