Dilemma: Exported JPGs look more contrasty than intended edits in LR/PS
p.1 #1Dilemma: Exported JPGs look more contrasty than intended edits in LR/PS
I've been wrestling with this issue for a while. I've tried to adhere to best practices I've learned over the years when it comes to Color Management:
But despite this, the resultant JPG (when viewed in most basic image viewing apps) looks darker and more contrasty than my intended edit.
- More importantly, it looks more contrasted in Instagram (on my phone) - which is usually the final display medium for most of my "work", for better or worse.
This is definitely not a problem unique to me (just a few of many such threads on the internet):
With a little digging, I was able to find out what's happening:
- It seems most image viewers (such as FastPictureViewer) are by default, not "Color Managed".
- In one specific viewing app (FastPictureViewer), I can change this to enable Color Management, and have it support ICC profiles.
- Then the results look exactly the same as in LR and PS. Nice.
While this is illuminating, I can't go and manually set the "Color Management" options of every possible image viewing app (including Web Browsers, if that's even possible) on all my devices.
- Most importantly, I can't set Color Management on my "audience" in Instagram.
So it seems to me that the best practice is probably to:
- At the end of my processing workflow, make a final virtual copy that is brighter and less contrasted, so that end-devices will display it closer to my actual intended edit.
Just curious if anyone has thoughts/ideas about this. Maybe I missed something?
- I calibrate my monitors with a hardware calibrator, and apply a custom ICC profile from the calibration.
- Lightroom / PhotoShop: Color Space = ProPhotoRGB, 32bits (bit depth)
- LR Export color space = sRGB IEC61966-2.1
But despite this, the resultant JPG (when viewed in most basic image viewing apps) looks darker and more contrasty than my intended edit.
- More importantly, it looks more contrasted in Instagram (on my phone) - which is usually the final display medium for most of my "work", for better or worse.
This is definitely not a problem unique to me (just a few of many such threads on the internet):
- When I export an image it looks more contrasted an saturated than the one in develop (a lot)
- Why image becomes darker and too much contrast when exporting to jpeg
- Contrast Difference after LRC/PS Export
With a little digging, I was able to find out what's happening:
- It seems most image viewers (such as FastPictureViewer) are by default, not "Color Managed".
- In one specific viewing app (FastPictureViewer), I can change this to enable Color Management, and have it support ICC profiles.
- Then the results look exactly the same as in LR and PS. Nice.
While this is illuminating, I can't go and manually set the "Color Management" options of every possible image viewing app (including Web Browsers, if that's even possible) on all my devices.
- Most importantly, I can't set Color Management on my "audience" in Instagram.
So it seems to me that the best practice is probably to:
- At the end of my processing workflow, make a final virtual copy that is brighter and less contrasted, so that end-devices will display it closer to my actual intended edit.
Just curious if anyone has thoughts/ideas about this. Maybe I missed something?
Sep 19, 2026 at 02:02 PM
p.1 #2Dilemma: Exported JPGs look more contrasty than intended edits in LR/PS
It sounds like the problem is that your OS/applications aren't color managed properly (are you using Windows? If so you might want to turn on automatic color management under display settings -> color profile -> color management). Good news is that pretty much all modern smartphones (iOS and Android) are properly color managed out of the box, as are MacOS devices so if your intended audience consumes Instagram through those devices then they're likely seeing your images as you intended them to be seen.
Sep 20, 2026 at 10:19 PM
p.1 #3Dilemma: Exported JPGs look more contrasty than intended edits in LR/PS
You didn't mention it, but I assume that you're running on a Windows computer and you may have a high color gamut monitor. Here is a link to a YouTube video from ArtIsRight that I believe addresses your issue.
As another poster responded, if you export to sRGB, most people other than you that have typical monitors will see a proper rendering of your image. If their app doesn't do color management, it will most likely assume the data is sRGB. If someone has a high color gamut monitor, I'll assume that they spent the extra money to purchase it so they can see better color, and they would know to use color managed programs when viewing photos.
I wouldn't recommend artificially brightening your photos and making them less contrasty because then they will look overly bright and low contrast for the majority of users. You can't control how your audience handles color management, so I think the best that you can do is give them a good file in the sRGB color space.
As another poster responded, if you export to sRGB, most people other than you that have typical monitors will see a proper rendering of your image. If their app doesn't do color management, it will most likely assume the data is sRGB. If someone has a high color gamut monitor, I'll assume that they spent the extra money to purchase it so they can see better color, and they would know to use color managed programs when viewing photos.
I wouldn't recommend artificially brightening your photos and making them less contrasty because then they will look overly bright and low contrast for the majority of users. You can't control how your audience handles color management, so I think the best that you can do is give them a good file in the sRGB color space.
Sep 21, 2026 at 11:55 AM
p.1 #4Dilemma: Exported JPGs look more contrasty than intended edits in LR/PS
@nibunnoichi
Your problem is possibly having 32-bit per channel Prophoto in the main setting. That is by definition HDR and so the conversion is trying to compress it all into 8-bits for the jpeg. Try instead using 16 bit Prophoto -- that's still a huge colorspace. In fact, it's still so big it's largely un-necessary today. I use DCI P3 16-bit as my main editing space as it encompasses what most viewing and output devices can handle.
I would then make sure that in LR your output settings for JPEG are set to sRGB, 8-bit, Perceptual rendering intent with BP compensation if that's an option, and finally any "simulate paper" or similar option is not checked. Do similar settings in PS if you convert the now 16-bit ProPhoto files to jpegs in PS; perceptual rendering intent with BP compensation.
If you work a LR output JPEG further in PS, make sure that View>Proof Color in PS is NOT checked -- otherwise you're editing to whatever profile you've set as your default proof profile. HOWEVER, you can use this effectively for your problem by setting the Proof Color under View>Proof Setup to "Internet Standard RGB" aka sRGB.
Now if you toggle View>Proof Color (cmd/ctrl Y toggles it) you can instantly preview what the sRGB will look like on a basic website and edit it to better match your vision.
Your problem is possibly having 32-bit per channel Prophoto in the main setting. That is by definition HDR and so the conversion is trying to compress it all into 8-bits for the jpeg. Try instead using 16 bit Prophoto -- that's still a huge colorspace. In fact, it's still so big it's largely un-necessary today. I use DCI P3 16-bit as my main editing space as it encompasses what most viewing and output devices can handle.
I would then make sure that in LR your output settings for JPEG are set to sRGB, 8-bit, Perceptual rendering intent with BP compensation if that's an option, and finally any "simulate paper" or similar option is not checked. Do similar settings in PS if you convert the now 16-bit ProPhoto files to jpegs in PS; perceptual rendering intent with BP compensation.
If you work a LR output JPEG further in PS, make sure that View>Proof Color in PS is NOT checked -- otherwise you're editing to whatever profile you've set as your default proof profile. HOWEVER, you can use this effectively for your problem by setting the Proof Color under View>Proof Setup to "Internet Standard RGB" aka sRGB.
Now if you toggle View>Proof Color (cmd/ctrl Y toggles it) you can instantly preview what the sRGB will look like on a basic website and edit it to better match your vision. Sep 21, 2026 at 04:41 PM