Photos Look Dark on iPhone After Export: What Is Actually Happening

Apple describes an extra layer attached to a photo. In its AppKit documentation the wording is direct: "The Apple HDR gain map is an 8-bit, single-channel luminance map that's stored with an image." It is not the picture. It is a brightness instruction sitting beside the picture.

Apple also documents its shape. The gain map, in Apple's words, "is encoded using the Rec.709 transfer function and is 1/4 the resolution of the original image." A single channel, at a quarter resolution, holding luminance only. That is a small amount of data whose whole job is to say which parts of the frame should be pushed brighter when a display can go brighter.

The rendering is defined as a formula. Apple publishes it as hdr_rgb = sdr_rgb * (1.0 + (headroom - 1.0) * gainmap), and defines the headroom term as "the ratio of the luminance of the image's brightest white to the luminance of standard dynamic range (SDR) white." Read the formula plainly and the answer to your question is already in it.

Set the formula next to the definition of the gain map and the conclusion is unavoidable. An Apple photo of this kind is an SDR base image plus instructions for building a brighter version of itself. A viewer that reads the gain map and applies the headroom shows the bright rendering. A viewer that does not read the gain map shows the SDR base. Same file, two legitimate results.

This is not a corruption, a failed export, or a colour profile being lost. It is the documented design. Apple treats the choice as a real one at the interface level too: its UIKit documentation exposes a property whose entire description is "The preferred treatment to use for HDR images." A preference exists because there is more than one correct way to show the photo.

That reframes the complaint. "The exported photo looks dark" usually means "I am now looking at the SDR base of a photo I had been seeing rendered with its gain map applied." The base was always there. You were simply not seeing it before.

It also explains why the problem resists reproduction on demand. Move the same file between two viewers and the appearance can change without a byte of the image changing, because the difference is created at display time.

The mechanism above accounts for most of these reports, but it is worth spending five minutes ruling out the ordinary causes first. Work through this list in order, and stop as soon as one of them explains what you are seeing.

• Compare the same file, not two files. Open the exported copy in two different apps on the same device, side by side if you can. If the two apps disagree, you are looking at the gain map effect, not an export fault.
• Check what you exported, deliberately. On a Mac, Photos exports with an explicit JPEG Quality setting, a Size menu, a Color Profile choice and an option to export IPTC as XMP. Those are decisions, not defaults you can assume.
• Test against an untouched original. Photos on Mac can export the file as it came in: the documented path is File then Export then Export Unmodified Original, which exports "photos in the original file format in which they were imported." If the unmodified original shows the same shift, your export pipeline is not the cause.
• Try a lossless format for the test only. Apple documents TIFF and PNG as lossless export formats. Exporting one as a control removes compression from the list of suspects, even though neither is what you would deliver to a client.
• Confirm the phone is not the only place you checked. If the photo only ever looked right on one device in one app, you have one data point, not a result.

If every item on that list comes back clean and the photo still reads darker in one app than another, you have found the gain map, and there is no export setting that changes the answer.

Two Apple features get blamed for this constantly, and both deserve a precise description rather than a rumour. Read Apple's own wording closely, because the wording is the whole point.

On the True Tone page for Mac, Apple writes that the feature "uses advanced multichannel sensors to adjust the color and intensity of your display and Touch Bar to match the ambient light, so that images appear more natural." The object of that sentence is the display. Apple is describing an adjustment to the screen in response to the room, not an adjustment to a file.

Night Shift is described the same way. On iPhone and iPad, Apple writes that it "automatically adjusts the colors of your display to the warmer end of the spectrum", and gives the reason as making the display easier on your eyes. On Mac, Apple adds the detail that matters for judging a photo: "Warmer color temperatures show more yellow and less blue." Again, the display is what shifts.

Keep that distinction exact when you explain it to anyone, including yourself. Neither feature changes the photo, the exported file, or your edit. They change what a given screen is doing at a given moment. That still matters, because a client judging your skin tones on a screen that is currently showing more yellow and less blue is judging the screen as much as the photograph. It just is not a reason to re-export anything.

This is the part photographers skip, and it is the part that decides how the conversation with the client goes. A proofing round is a selection exercise. The client is deciding which frames they want. They are not signing off on a print, and the phone in their hand was never a reference display.

Be honest about what a proof is on our side too. Uploads to clientgallery.io are compressed in the browser into proof JPEGs, so a proof is a viewing copy built to load fast in a gallery that can hold up to 1,000 photos. Full-resolution delivery is a separate step: you upload a full-resolution ZIP for the gallery, it stays live for three days per handoff, and you can re-upload it whenever the client needs it again. The plan is one price, $10 a month or $100 a year, with 250 GB of proofs per paid account, 5 GB on the free tier, and 100 GB of standing ZIPs.

That split is useful here. The proof is what the client looks at on a phone, in a room you cannot see, on a screen you cannot measure, in an app that may or may not apply a gain map. The full-resolution file is what goes to the lab or the print. Do not let a judgement made in the first context become a verdict about the second.

If the wider question is on your mind, that a photo looks unlike itself across different screens generally, that is a separate subject with separate causes. We covered it in why photos look different on a client's phone.

The worst response is to promise a fix you cannot deliver. You do not control the client's display, the app they opened the gallery in, or the light in the room. Saying so calmly is more professional than quietly re-exporting a brighter version and hoping.

The second worst response is to argue. The client is describing something real. A photo that renders one way in one app and another way in another app is exactly what the documentation above predicts. Your job is to locate the difference, not to deny it.

Something close to this works, adapted to your voice:

"Thanks for flagging it. A photo from an Apple device can carry two versions of itself, a standard one and a brighter one, and some apps show the brighter version while others show the standard one. Could you try opening the same photo in a different app on your phone, and if you can, on a computer? If it looks different in the two places, that is the display doing it rather than the file. If it looks dark everywhere, tell me which photo and I will look at the edit."

That note gives a true explanation instead of a brush-off, hands the client a test they can run in a minute, and keeps the door open for the case where the client is right and the edit genuinely is too dark. Occasionally it is. Note also what the sentence avoids: any promise about a setting. Pointing a client toward a toggle that may not exist on their device turns one confused message into five.

• Apple Developer, Applying Apple HDR effect to your photos (gain map definition, Rec.709 encoding, quarter resolution, rendering formula, headroom definition). Fetched 23 September 2026.
• Apple Developer, UIImageView.preferredImageDynamicRange (documented preference for HDR image treatment). Fetched 23 September 2026.
• Apple Support, Use True Tone on Mac (True Tone adjusts the colour and intensity of the display to match ambient light). Fetched 23 September 2026.
• Apple Support, Use Night Shift on your iPhone, iPad, and iPod touch (display colours adjusted to the warmer end of the spectrum). Fetched 23 September 2026.
• Apple Support, Use Night Shift on your Mac (warmer colour temperatures show more yellow and less blue). Fetched 23 September 2026.
• Apple Support, Export photos, videos, slideshows, and memories on Mac (Export Unmodified Original, JPEG Quality, Size, Color Profile, IPTC as XMP, TIFF and PNG as lossless formats). Fetched 23 September 2026.