2026-07-27
What marketplaces actually require from a product photo’s background — and what background removal does and doesn’t solve
Search "why was my Amazon image rejected" or "coupang 상품이미지 반려" and you'll find the same complaint over and over: a perfectly good product photo, rejected or quietly suppressed from search, for reasons that trace back to the background. Marketplaces are unusually specific about this one part of a listing photo. Here's what four of them actually say about it, why they bother enforcing it, and — just as importantly — exactly what a browser-based background remover like NearBG does and does not do to get a photo ready for one.
What four marketplaces actually require
| Marketplace | Main-image background rule | Confidence |
|---|---|---|
| Amazon | Pure white, RGB(255,255,255); product fills ~85%+ of the frame; no text, logos, borders, or watermarks. Enforced by automated scanning that can suppress the listing from search. | Corroborated by Jungle Scout's seller documentation and Amazon's own seller forums — not directly quoted from Amazon's help center, which requires sign-in. |
| eBay | White/neutral is recommended, explicitly not required. Lifestyle and colored backgrounds are allowed in any image slot, including the main one. | Primary source — fetched directly from eBay's own Seller Center photo-tips page. |
| Coupang (쿠팡) | White/#ffffff main image is the general-category norm, with apparel and fresh food named as exceptions. Coupang publishes separate guideline pages per category. | The category-guideline hub is confirmed real and live; the exact spec text is corroborated across seller-tool sites, not directly quoted from Coupang's own page. |
| Naver Smart Store (네이버 스마트스토어) | Since Oct 28, 2024: main images showing an option-mismatched or unrelated product, price/shipping text, or promotional text are banned outright, on top of a general "clean, product-only" expectation. | Reported consistently across multiple Korean seller-community reposts of the notice — not the primary Naver URL itself. |
Why marketplaces bother enforcing this
The stated reason, at least for Amazon, isn't taste — it's consistency. A pure white background makes every product thumbnail sit the same way against Amazon's own white search and detail-page background, so a shopper scanning a results grid is comparing products, not photo styles. Naver's October 2024 tightening reads the same way from a different angle: its banned list isn't about background color at all, it's about a main image accurately representing the one product actually being sold, rather than an option photo, a price sticker, or a promotional graphic pretending to be the product. eBay's stance is the outlier precisely because it explains the tradeoff instead of just asserting a rule: white is "always a safe choice" for standing out in a gallery grid, but eBay chooses not to force it, leaving room for lifestyle shots that a plain white product photo can't provide.
What NearBG actually does toward any of this
NearBG removes a photo's background entirely inside the browser — no upload — using the same U2Netp segmentation model covered in this blog's first post. The output is a transparent PNG. After automatic removal, a manual touch-up brush lets you erase anything the model left behind: a patch of background it mistakenly kept, a stray fragment detached from the product, a rough edge along an otherwise clean silhouette. That's directly useful here, because a background remnant sitting near the product's edge is exactly the kind of thing that makes a "white background" photo fail an automated whiteness check, or makes a transparent cutout look unfinished wherever it's placed next.
What it doesn't do — and why that gap matters here
Be precise about what "removes the background" means in NearBG's current, live scope: the result is transparency, not a composited solid-white image. Placing that transparent cutout onto an actual white canvas — or a colored one, or a photographed backdrop — is background replacement, and that's explicitly not something NearBG builds today; it's listed as out of v1's scope, a candidate for a future version, not a silent gap. That distinction matters for exactly the rules above: Amazon and Coupang's general-category norm asks for literal white pixels behind the product, not an alpha channel. A transparent PNG straight out of NearBG is the raw material for that photo, not the finished one — the white-canvas step still has to happen somewhere else, in whatever image tool or upload flow does that compositing for you. Where a marketplace or a downstream tool accepts transparency directly — a catalog system that composites it server-side, a lifestyle mockup, a listing platform that fills the canvas itself — the cutout NearBG produces is usable as-is.
A practical checklist before you upload
- Shoot on a bright, evenly lit, high-contrast backdrop to begin with — fewer ambiguous edge pixels for the segmentation model to guess wrong on, the same guidance this blog's hair-and-fur post covers in more depth.
- After automatic removal, zoom in on the edges and look for a stray background patch or a detached fragment — the touch-up brush erases those directly; it can't restore detail that was never captured, only remove what shouldn't be there.
- Check which rule from the table above applies to your actual target marketplace before deciding whether a transparent cutout is the finished asset or just the first step.
- If the destination needs literal white pixels rather than transparency, plan on a separate compositing step — NearBG's scope currently ends at the transparent PNG.
- Re-check that marketplace's current official policy page before publishing. Rules change — Naver's October 2024 update is a concrete example — and this post is a snapshot of research, not a substitute for the live policy.
The honest summary
Four marketplaces, four different answers on how strict a product photo's background has to be — from Amazon's automated pure-white check to eBay's opt-in recommendation. What's consistent across all of them is that a messy edge or a leftover background patch is the kind of thing that gets a photo flagged regardless of which exact rule applies. NearBG's automatic removal plus its touch-up brush handles that part, entirely in the browser, with nothing uploaded. Turning the resulting transparent cutout into a literal solid-white marketplace image is a separate step NearBG doesn't perform today — not a hidden limitation, just the honest edge of what a background-removal tool that stops at transparency actually does.