Check your PNG before you print: the free 10-second transparency test that saves blanks, film and ink

What a ruined print actually costs

Nobody budgets for the halo because each failure feels small. Add them up for a week:

• The blank. An acrylic keychain is cents; an acrylic photo block, a tumbler, a phone case or a slate coaster is dollars each, and a 10-up sheet of them is a real number.
• The consumables. UV ink and varnish per square centimetre, DTF film plus powder plus the press cycle, and the white ink, which is the most expensive channel on most machines and the one the halo wastes.
• The time. Setup, jig alignment, print, cure or press, inspection, then the same again for the reprint. Per failed design, easily 20–40 minutes.
• The order. If the customer saw the halo first, you don't reprint, you refund.

Every one of those costs is paid after the point where it could have been avoided. The file was wrong before you opened the printer software.

Why you can't see the problem by looking at the PNG

The pixels that cause the halo are semi-transparent: alpha values between 1 and 254, left along the edge by Canva, remove.bg, Photoshop's background removal, or plain anti-aliasing. On a screen they blend into the background and disappear. Your file viewer, your design app and your RIP's preview all render them the same forgiving way.

The printer doesn't blend. The RIP asks each pixel "is anything here?", and a pixel that is 4% visible answers yes. White ink goes under it. So you need a view that answers the printer's question instead of the screen's. That's the whole trick.

The 10-second check

1. Open the file. Go to pixelcleaner.net, sign in with Google (free, no card), and drop the PNG in or paste it with Ctrl+V. Processing runs in your browser; the image is not uploaded anywhere, which also makes it safe for client artwork you can't share.
2. Read the green. Every semi-transparent pixel is painted toxic green on top of your image. This is the printer's view of your file. What it looks like tells you what would have happened:
   • A thin, even ring, one or two pixels wide: normal anti-aliasing. Clean and print.
   • A wide band that fades outward: a background remover's soft edge. This is the halo. Clean it, and consider fixing the export too.
   • Green dust or specks away from the design: leftovers the remover missed. They print as white dots. The cleaner drops them.
   • Green over whole areas: a drop shadow, glow or a layer at reduced opacity. A binary-white printer can't print that; it will be cut at the threshold or need redesigning.
   • The entire canvas green or none at all with a solid background: no transparency in the file. Re-export; see below.
3. Preview on your substrate. Set the substrate colour to what you're printing on (black for acrylic, a custom colour for a balloon or a painted surface) and compare the before and after. The after view shows the edge the printer will produce from the cleaned file.
4. Decide. Thin ring: export and print. Wide fringe: export, but also go back to the source so the next file arrives cleaner. No transparency: don't export, re-save the file properly first.

Steps 1 to 3 never touch your credits. Only exporting the cleaned plates counts as a use (3 free to start, then 2 more every day; Pro is unlimited). You can check a hundred files a day for nothing.

A pre-flight checklist for UV and DTF files

The transparency check catches the halo. These five catch the other ways a print gets wasted:

1. Transparent background, really. Checkerboard behind the design in a viewer. If it's white, the export missed the "transparent" option (Canva) or the background layer was visible (Procreate, Photoshop). Canva · Procreate & Photoshop.
2. Size at 300 pixels per inch of final print. A 4 × 4 in print needs 1200 × 1200 px. Scaling up a small file widens every soft edge.
3. No semi-transparent pixels on the silhouette. The green check above.
4. Thin details thick enough to survive. Strokes and text under 2–3 px at final size lose their white underbase after choke and print dark. Zoom to 200% and look at the thinnest line.
5. White plate inside the colour plate. If you supply your own white layer, it must be a subset of the colour; any white outside it is a guaranteed halo. The cleaner's _white.png is built that way by construction. How much choke.

Three real cases

The 10-up keychain sheet

Ten acrylic keychains on one jig, a pet-portrait design cut out in Canva. The check shows a 6-pixel fading band around the fur. Unchecked, that's ten blanks with a white fuzz around every dog. Checked, it's one export and a clean sheet.

The tumbler with a logo

A client logo as a PNG with a white glow effect baked in. The whole glow lights up green. No cleaning setting makes a glow printable on black powder coat; the right move is to ask for the logo without the effect before wrapping a tumbler.

The DTF gang sheet

Twelve designs on one sheet of film, from four different sources. Two of them have fringes, one has a solid white background nobody noticed at thumbnail size. Ten seconds per design finds all three before the film, the powder and the press cycle are spent.

When the check says the file is fine but the print still fails

If the green ring is thin and clean and you still get a white edge, the file isn't the cause:

• White on one side only: registration between the white and colour passes. A 1–2 px choke in the RIP fixes it. Details.
• White layer bigger than the colour everywhere: the RIP is building the white from a different mask or applying a negative choke (spread). Load the cleaned white plate instead of letting the RIP generate one.
• Banding or missing white: nozzles, not files. Run a nozzle check.

Frequently asked questions