Three things change the colour of a jewellery photo after the shutter closes. The screen you judge it on. The colour note carried inside the file. The copy somebody else builds from your file, on WhatsApp or on the marketplace. None of the three touches your photograph.
A fourth thing does, and it happened earlier: the light you shot under. That one is the re-shoot; an afternoon spent re-shooting for any of the other three changes nothing in the file. So the first job is to name the stage that moved the gold.
Three of the four happen after the camera has finished, downstream of everything in photographs of your own stock. Start with the one colour in the frame that carries a number: the ground behind the piece is RGB 255,255,255 or it is not.
Photo upload karne ke baad colour kyun badal gaya?
Each stage leaves its own fingerprint, and reading it is most of the diagnosis. The light at the shutter is the one stage that puts a cast into your own pixels. The other three leave the numbers in your file exactly where they were, and change what is seen, read or built from them.
| Stage | What happened to the pixels | How you can tell | What fixes it |
|---|---|---|---|
| The screen you judge on | Nothing moved. Only what you see moved | The same file looks different on a second device, or once the warm-tint mode goes off | The screen and the room, not the photo |
| The colour note in the file | The numbers stay. The note telling software how to read them is dropped | Rich colour lands flat everywhere, not only on your phone | Save in sRGB before the file goes anywhere |
| A copy somebody else made | A new file is built from yours and sent or served in its place | Save the image off the chat or off your live listing: size and dimensions will not match your upload | Hand over the largest clean original you have |
| The light at the shutter | The cast is baked into your pixels | The piece was already orange on the phone, before any upload | One light, one white balance, re-shoot |
Only the last row is a shooting fault, settled at the shutter, material by material.
Why do two phones in the same shop show the same gold differently?
Put the same photo on the counter phone and on the one in your pocket, late in the day, and the gold will not match. Every screen is built with its own idea of white, and most phones are quietly changing that idea while you look at them.
Three settings do most of the damage. The warm-tint modes come first: True Tone and Night Shift on iPhone, Night Light or eye comfort on Android, each pushing the whole screen warmer at the hour you finish a shoot. Then the picture mode, where a phone set to vivid shows a richer gold than the same phone set to natural. Then automatic brightness, which makes one photo look pale at the window and heavy in the back room.
Your eye is the fourth. Work under a warm tube light and your eye starts to accept that light as white, so the photo begins to look cold. The screen never adapts along with it, so a walk to the door is enough to turn the same photo yellow again.
Before judging a batch, switch the warm modes off, set brightness by hand, and judge in the same spot every time. That gives you one phone that reads the same way every evening. Two phones will still disagree, and nothing free changes that.
What does a wide-gamut file do on a page that expects sRGB?
Every photo carries two things: numbers for each pixel, and a note saying which set of colours those numbers belong to. That note is the colour profile. Web pages, marketplace apps and seller panels are built on the older, narrower set called sRGB, and assume your file speaks it.
Recent iPhones tag their photos Display P3, a wider set, and several Android cameras offer a wide mode of their own. If the profile survives and the software reads it, the photo shows correctly. Where it is dropped in a re-save, the numbers are read as though they had always been sRGB, and colours that only existed in the wider set arrive flatter than you saw them.
On plain yellow gold that shift is small. On a ruby, on rose gold, on meenakari, it is the difference between a piece that looks alive and one that looks printed.
You cannot control every step between your phone and the listing, so hand over a file that is already sRGB and there is nothing left downstream for anyone to read wrong. Any tool that re-saves the photo can do it on the way, and the compressor on this bench writes its output in sRGB.
What does WhatsApp do on a normal send, and what changes as a document?
A normal send builds a smaller copy of your photo, re-encodes it, and delivers that copy in place of the file you picked. Detail softens, the profile does not make the trip, and every hop repeats the loss: a photo sent to a reseller, saved, and sent on again has been through it three times.
Sending as a document is the exception: the other side receives the file as it left your phone. An HD send, where your version of the app offers one, sends a bigger picture than the standard send, and whether it hands over your file untouched is a question only your own copy of the app can answer. Send one photo both ways to a second phone and compare what arrives against the original sitting in your gallery.
| Route | What the other side receives | What it is right for |
|---|---|---|
| Normal send | A smaller re-encoded copy, profile not carried | Showing a customer a piece in chat |
| HD send, where your version offers it | A bigger picture than the standard send; test yours against the original | A buyer who wants to look closely |
| Send as document | The file as it left your phone | Anything that will end up on a listing |
One rule follows, and it is worth saying to your supplier as well as to yourself: anything headed for a listing comes over as a document. For a catalogue meant only to be seen inside WhatsApp, small is correct, and this bench works to about 300 KB there.
What does the marketplace do to my file after upload?
Upload once and the marketplace builds its own copies at its own sizes — one for the search grid, one for the listing page, one for the zoom — and serves those copies to buyers.
So the thumbnail that decides whether a buyer taps is a small re-encode of your photo, drawn by an app you do not control. You own one end of that chain: a large, clean original survives their downsize better than a file you already squeezed. The square, the pixel size and the fill are the other half of the same upload, and the Marketplace Image Resizer settles those against each marketplace’s own rules.
No platform publishes what its pipeline does to an image, and it changes without notice, so read the answer off your own listing: open it on a laptop, save the image the page serves, and compare it with what you uploaded. The gap in size and dimensions is the answer, and it takes a minute.
How do I judge colour against something fixed instead of against memory?
Colour memory is short. Seconds after you look away, your eye is comparing the photo against an idea of gold, which is why the same seller approves a photo on Monday and rejects it on Thursday. Three references replace memory, cheapest first.
The ground
White is the only colour on a listing image with a published number behind it: RGB 255,255,255. Shoot on plain white paper and the background stops being an opinion. The whitener reads the outer border of the frame, where the ground is, and says whether that ground has arrived at white or is still short a few points per channel.
The piece in your hand
Hold it beside the screen, under the light you shot it in, and compare. A jhumka held against its own photo answers in two seconds what an hour of adjusting never settles.
One light and one number
Shoot every piece under one light at the same white balance, and every shoot starts where the last one started, whatever the room was doing that day. The yellow-gold card on this bench carries that number, and it carries a different one for a shop tube than for a window, which is why you tell it your light first. Short of a colour-calibrated monitor, which most sellers will never buy, repeatability is the whole of what you can have.
What is the one check to run before a batch goes up?
Put one piece through the whole chain before you prepare the other forty. It costs one listing, and it is the only way to see the stages you do not control.
- Prepare one photo completely: ground lifted, squared, sized, saved as it will be uploaded.
- Upload that single listing and let it go live.
- Open the live listing on a device you did not edit on, warm-tint mode off, brightness set by hand.
- Hold the piece next to the screen, under the light you shot it in.
- If the two agree, the batch is safe. If not, name the stage from the table above and fix that stage only.
Skipping the check costs forty photos, and a return rate that reaches you long after anybody remembers which folder those photos came from.
Where does compression genuinely cost me, and where does it not?
Compression takes detail. A JPEG saved the usual way holds brightness at full detail and stores colour more coarsely, so the first thing to blur is fine colour at an edge: a red meena line against gold, the join between a stone and its setting. The colour of the piece itself stays where it was.
That distinction decides where your afternoon goes: gold gone pale sends you to the profile and the screen, while a chain gone mushy, with enamel bleeding at the edges, sends you to how many times the file has been saved.
The damage that matters comes from three habits: re-saving the same file again and again, each pass re-encoding what the last already lost; enlarging a small crop to reach a required size; and squeezing far below the cap for nothing. Meesho’s line is 2 MB, and a photo pushed far under it has thrown away detail nobody asked for.
Take the piece you are listing next. Shoot it on plain white paper under one light, lift the ground, save it once in sRGB, size it last, and put that single listing live before you touch the batch. Then read it on the other phone in the shop, warm tint off.