Guides / Technique
Pure white backgrounds 101
What "pure white, RGB 255" actually means, why a background that looks white can still fail a marketplace check, and when software can fix it versus when only a reshoot can.
Updated Aug 31, 2026 · 6 min read
What "pure white" actually means
Pure white is a number, not an impression: every background pixel at RGB (255, 255, 255). Marketplaces that require it, Amazon’s MAIN image above all, do not judge by eye; their tooling samples pixels. A backdrop that looks perfectly clean on your screen can average RGB (247, 245, 244), and that difference is invisible to you and obvious to a measuring script.
That is why Photolint treats whiteness as a measurement. The lint samples the background around the detected subject and reports the share of pixels that are effectively white. The pipeline’s own pass threshold is 98%: below that, the background stage has work to do.
Why 97% white fails a 98% check
Three things quietly pull a white backdrop below the line. JPEG compression adds noise, so flat white areas come back speckled with near-white values. Lighting falls off toward the frame edges, which reads as a soft gray vignette. And any soft shadow under the product spreads mid-gray values across otherwise clean background.
None of these are visible at a glance, and all of them are counted by a pixel check. The practical consequence: "almost white" does not round up. A photo measuring 97% white is a fail on a 98% rule, and an honest report should say so rather than call it close enough.
How the pipeline fixes it, and how it verifies the fix
Photolint’s background stage cuts the subject out with an AI mask (u2netp, optionally a higher-resolution precise mask), composites it onto a mathematically white canvas, and then does the important part: it re-measures its own output with the same lint instrument. Only a result that verifiably passes ships as fixed.
For evenly lit backdrops there is also a deterministic path: the pipeline flood-fills the background from the edge median color to pure white, no AI involved. If neither path produces a verified pass, the photo ships on a white pad and is flagged for your eyes in the artifacts step. Nothing is silently presented as fixed.
When a reshoot beats software
Masking needs contrast. A beige product on a beige backdrop, translucent or furry edges, or a strong shadow baked across the product itself will defeat any cutout, and a bad cutout on pure white looks worse than the original photo. Photolint reports these as "could not verify" or flags the output instead of pretending.
If you are reshooting anyway: light the backdrop separately from the product, keep the product a step away from the wall so shadows fall out of frame, and fill the frame generously. A shot with clean contrast takes the automated path every time.