White specks and stray pixels in DTF
If specks, coloured dust or a white edge appear around the design that were not visible on screen, it is almost never the printer: they are near-transparent pixels in the file. In Sapiens CoreFlow RIP you see them, mark them and clean them before printing.
Where they come from
A PNG with a transparent background rarely has only “full” and “empty” pixels. In between there are pixels at 1 %, 3 % or 5 % opacity: leftovers from a cut-out, edge anti-aliasing, AI upscaling or a quick pass of the eraser. On screen you do not see them.
In DTF you do, because the white underbase is computed from opacity: wherever there is a pixel, however faint, the RIP puts white under it and the adhesive powder sticks to it. The result is stray specks far from the design and a light halo around the edge, especially on dark garments.
- Specks away from the design — lost pixels in the transparent area.
- White halo or lip — the semi-transparent fringe left by edge smoothing.
- Coloured dust — remains of a badly removed background, at very low opacity.
Before and after cleanup
The same design with the usual dirt of a badly removed background: stray specks and a faint fringe. On the right, after “Clean marked” with “Defringe”.
How Sapiens CoreFlow RIP fixes it
The first tab of Editor Pro is Cleanup, because in production you clean first and edit afterwards. When it opens, the RIP searches the transparent areas for dirt and marks it in three groups: what will be erased, what sits close to the artwork and deserves a look, and what is kept. One click cleans the marked ones; size does not matter, because a one-pixel speck prints too.
- Automatic cleanup — finds and marks the dirt; you decide what goes.
- Defringe — removes the faint band along the edge, with its width in pixels.
- Transparency threshold — anything below the percentage you set becomes truly transparent.
- Eraser and Restore — brushes with size and hardness for manual cases; Restore brings back the original artwork under the brush.
- Crop to content — removes the spare transparent margin, and the physical size of the job adjusts itself.
Why do it in the RIP and not in the design program
Because the RIP is the one that knows where white will land. Cleaning in the design means guessing which pixels are a problem; in the RIP you see marked exactly the ones that would end up printed, in the same place where the sheet is then built. And the customer's file is untouched: the cleanup lives in the job.
Frequently asked questions
Why do I get white specks around my DTF design?
Almost always they are near-transparent pixels in the file: the white underbase is generated wherever there is opacity, even 2 %, and the powder sticks there. Sapiens CoreFlow RIP detects them in the Cleanup tab of Editor Pro and removes them before printing.
How do I remove the white halo around the edge?
With “Defringe” in the Cleanup tab of Sapiens CoreFlow RIP: it removes the semi-transparent band left by edge smoothing, at the pixel width you choose. If the halo comes from a cut-out background, the “Transparency threshold” solves it in one go.
Can I erase just one area by hand?
Yes. Sapiens CoreFlow RIP has Eraser and Restore brushes with size and hardness, keyboard shortcuts, and every stroke can be undone. Restore brings back the original artwork under the brush if you go too far.
Is the customer's original file modified?
No. In Sapiens CoreFlow RIP the cleanup is stored in the job, not in the source file, and “Restore original” always returns to the image as imported.