If a finished headshot looks warm on one screen and cool on another, establish whether you are comparing the same file under comparable viewing conditions. A colour difference does not automatically mean the portrait needs another retouch. The image, its colour profile, the software displaying it and the screen all belong in the investigation. Identify the mismatch before changing the photograph to compensate for it.
One portrait can acquire several different-looking previews
Imagine a Toronto business owner who approved a portrait in the photographer’s delivery gallery. The downloaded image looks satisfactory on a laptop, but a colleague sees a noticeably warmer face in a messaging application. The colleague suggests reducing warmth in the file. That instruction sounds specific, yet it assumes the messaging preview represents the same image in the same way as the approved view.
Begin by identifying the copies. A delivered JPEG, a screenshot of its preview and an image saved from a conversation are separate files, even if they show the same pose. Ask which copy each person opened and where it came from. Keep the original download available. Repeatedly saving previews can make it harder to discover whether the difference arose before or after the file left the delivery system.
Then identify the viewing situation. Record the application and device used for each observation. “The colour is wrong on my phone” leaves out whether the person opened the delivered attachment, looked at a web preview or saw a copy inserted into a presentation. Those routes can involve different handling. A useful account describes the observed difference without announcing that a particular device or application must be defective.
Try to isolate one change at a time. Opening the same delivered file in two applications on one device asks a different question from comparing two devices in different rooms. If both the copy and the device change together, the result cannot tell you which difference mattered. You do not need a laboratory to keep those comparisons understandable; you need to know what stayed the same.
Be cautious about using a screenshot as the sole evidence of a colour complaint. It can show where an image appeared and help describe the interface, but another person’s screen will still display that screenshot in its own conditions. Send the identified image file as well. A screenshot of an application is useful context for a technical enquiry, rather than a universally accurate colour reference.
A colour profile supplies meaning for the image’s numbers
Adobe’s explanation of colour management describes why the same file can appear different across devices. Document profiles describe an image’s colour space, while device profiles describe how a display or printer handles colour. The numbers stored in an image need that interpretive context. Treating every RGB file as though its numbers have identical meaning can produce misleading comparisons.
For the portrait owner, this is a reason to preserve the delivered file and ask a precise technical question. It is not a reason to start assigning random profiles until a preview looks pleasing. A changed interpretation and a deliberate colour conversion are different operations. Someone responsible for preparing the image should determine which operation, if any, is needed for the intended destination.
Describe that destination concretely. A portrait for a web biography presents a different production question from an image being placed in a printed brochure. The photographer, designer or other responsible specialist can advise on the file needed for that use. Avoid prescribing a profile because a colleague remembers seeing its name in a tutorial for another application or another kind of output.
A colour-managed workflow can improve consistency without making every screen identical. The display itself and its viewing conditions still matter. That limit should keep expectations realistic: approval is not a promise that every recipient’s device will show precisely the same warmth or brightness. Equally, the existence of device differences is not a sufficient explanation for every unexpected result. A reproducible discrepancy is still worth investigating.
Keep aesthetic preference out of the first technical exchange. “This portrait is too warm” and “this exact file appears warmer in this application than in the delivery view” ask different things. The first requests a creative change; the second reports a rendering difference. If the team changes the image before deciding which question it is answering, it may introduce a new problem into the version that was already working.
Send the discrepancy back with a reproducible comparison
A concise enquiry can identify the delivered filename, the application where it looks as expected and the application where it changes. Include the actual file through the provider’s normal contact route, along with an explanation of how it was obtained. Report whether the same behaviour occurs when the identical file is opened elsewhere. That gives the recipient something more useful than several colleagues’ competing descriptions of skin tone.
For an existing commission of Indigo Visual’s finished headshots, the owner can return to the delivery correspondence with that comparison. The request concerns the preparation and display of one supplied portrait. It need not reopen the expression selection or ask for a different photograph. Attach the observation to the actual order so the team can locate the relevant delivery rather than infer it from the public website.
Suppose the technical response identifies a file-preparation issue for the intended web use. Obtain the corrected export and compare that export in the destination that exposed the problem. Keep a clear distinction between a new export of the approved portrait and a new creative treatment. The business should know whether it received a differently prepared file or a changed interpretation of the person’s appearance.
If the difference instead belongs to one viewing arrangement, record that finding beside the reference used for approval. Avoid creating a warmer version for one colleague and a cooler version for another without a defined production purpose. Those copies can later enter the same staff directory and make the inconsistency worse. A preference for a particular device’s appearance does not, on its own, justify multiplying approved masters.
The useful outcome is a portrait with an understood source and a defensible viewing reference. The owner can explain which file is approved, where an apparent shift occurred and whether any export was corrected. Future comments then begin from that shared information. They no longer send the face through another round of colour changes every time it appears on a different screen.
