NearBG

2026-08-09

Fixing the white box around a print-on-demand design with a transparent PNG

Upload a phone photo of your artwork to Printify, Printful, Redbubble, or Korea's own Marpple Shop, and the mockup that comes back sometimes has a flat white or checkered box sitting behind your design instead of your design floating cleanly on the product's own color. That's not a random glitch, and it's not the platform being picky for no reason — it's what happens when a file with no transparency meets a print process that composites your artwork directly onto a colored product. What these platforms actually require, why a JPEG can't satisfy it no matter how "clean" the background looks on your screen, and what a browser-based cutout tool like NearBG does and doesn't do to fix it.

It isn't a rejection — it's what JPEG can't do

A JPEG file has no alpha channel at all; every pixel in it is fully opaque, always. A background that looks white or blank on your monitor isn't transparent — it's literally opaque white ink as far as the file format is concerned, and a printer treats it exactly that way. Printify's own support documentation says this in the most concrete terms possible: a PNG-24 file with a 100% transparent background is what a design with transparency needs, because "JPEGs can't hold transparency, so the printer outputs a solid white box behind your art." Printful's design-file guide gives the same instruction from the maker's side: "Opt for PNG if there's transparency or detailed graphics in your design." And Marpple Shop — the largest goods-printing platform built for Korean creators — states the same underlying fact in its own help center, translated here: "Even a white background gets printed if you make the product from an image that has one." Three platforms, three separate help centers, the same mechanical reason.

What the platforms actually spec

PlatformFormat / transparencyResolutionOther limits
PrintfulPNG recommended whenever the design has transparency or fine detail; JPEG is fine for flat, opaque designs.300 DPI recommended; 75 DPI is the stated floor for paper products.Up to 100 MB for JPEG/PNG.
PrintifyPNG-24 with a 100% transparent background for anything that needs transparency, at 1:1 print scale.300 DPI standard; 120–150 DPI accepted for large-format items like blankets or tapestries.Up to 100 MB for JPEG/PNG.
Marpple Shop (마플샵)Transparent-background PNG is the recommended format for designs meant to sit on multiple product colors.Square (1:1) canvas, roughly 3,000–8,000 px on a side.Under 4 MB per file.

The specifics differ — DPI floor, canvas ratio, file-size cap — but the transparency requirement itself doesn't. All three exist because the same design has to sit correctly on a black hoodie, a white mug, and a red tote bag without a visible box trailing it.

Saving a JPEG as a .png doesn't fix this

A common mistake is renaming or re-exporting a JPEG with a .png extension and assuming that solves it. It doesn't — the transparency has to exist as real per-pixel alpha data inside the file, and a flat photo simply doesn't have that until something removes the background and writes an alpha channel in its place. That's a segmentation problem, not a file-format problem: something has to decide, pixel by pixel, which part of the photo is the subject and which part is background to erase.

What NearBG does here, and what it still leaves to you

NearBG removes a photo's background entirely inside the browser — no upload — using the U2Netp segmentation pipeline covered in this blog's first post, and writes the result as a transparent PNG. That in-browser part matters specifically for design work in a way it might not for a casual photo: an unpublished sticker design or a not-yet-listed product graphic is IP you're choosing not to hand to someone else's server before it's ready to sell, and NearBG's zero-upload architecture means it never leaves your machine during this step. After automatic removal, the manual touch-up brush lets you erase exactly the kind of leftover fringe pixels Marpple's own guide tells sellers to hunt for by hand — zoom in, check the edge, erase anything that shouldn't be there.

What it doesn't do: resize or crop to a platform's exact pixel dimensions, and it can't invent resolution your source photo never had. If Marpple wants 3,000–8,000 px on a side and your original photo is a 1,200 px phone screenshot, NearBG's transparent cutout will still be 1,200 px — upscaling to hit a platform's floor is a separate step this tool doesn't perform. Check each destination's own current size and DPI table before uploading; this post is a snapshot of what three platforms stated at the time of research, not a live substitute for their own docs.

Design photo → NearBG auto remove + touch-up brush in-browser, no upload → Transparent PNG cutout not built in NearBG today resize / DPI to platform spec
What NearBG's pipeline actually produces (a transparent cutout, with a brush to clean up stray edge pixels) versus the separate resize/upscale step a print-on-demand platform's own pixel and DPI spec requires, which NearBG doesn't perform.

A practical checklist before you upload a design

  • Shoot or scan the source art with even lighting and a clean, high-contrast backdrop — fewer ambiguous edge pixels for the segmentation model to guess wrong on.
  • After automatic removal, zoom in along the silhouette and erase any leftover fringe with the touch-up brush — the same manual check Marpple's own guide tells sellers to do by hand.
  • Confirm your source photo's resolution actually meets the destination platform's floor before you upload — NearBG won't upscale a low-resolution source to hit it.
  • Re-check that platform's current file-requirements page before publishing; the table above is a snapshot of research, not a live mirror of their docs.

The honest summary

Printful, Printify, and Marpple Shop each spec their own DPI floor, canvas ratio, and file-size cap, but all three converge on the same mechanical fact: a design without a real alpha channel prints with a solid box behind it, because JPEG has nowhere to store transparency and no amount of visual "cleanness" changes that. NearBG's job in that pipeline is narrow and honest — turn a flat photo into a transparent PNG entirely in the browser, with a brush to clean up what the model leaves behind. Hitting a specific platform's exact pixel dimensions and DPI floor is a separate step this tool doesn't perform today, not a hidden gap.

Sponsored
← NearBG

This page shows ads only if you consent.