Skip to content
GPU-assistedUpload required

Remove Dust and Specks from a Photo

Dust is not a thing that looks a particular way. It is a small mark you did not want, and the only difference between a speck of dust and a mole, a distant bird, or a star is that you wanted one of them there. Nothing in this workflow can know which is which, so it works from context and probability rather than certainty. That is the whole story of what it fixes and what it takes.

Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.

Add to Chrome — free

Drop an image here, or click to browse

Up to 25 MB. Uploaded temporarily, deleted after processing.

GPU-assisted — results vary slightly between runs.

What it does

  • Repaint at 60 per cent strength
  • Fixed seed, so runs are reproducible
  • Identity and composition explicitly guarded
  • Roughly one megapixel output

How to use Remove Dust

  1. 1

    Scan or photograph as cleanly as you can first

    Every speck removed by a cloth on the scanner glass is one this tool does not have to guess about. Cleaning beats repairing.

  2. 2

    Run the pass

    The image is scaled to about one megapixel and repainted at 60 per cent strength with an instruction to clean specks without smoothing real detail.

  3. 3

    Check the things that look like dust

    Moles, freckles, birds, stars, and snow are the casualties. Compare those specifically against your original rather than judging the picture as a whole.

How it works

Your image is scaled so its total area is around one megapixel, keeping the original proportions. An image-editing model reads that copy along with a fixed instruction: clean small dust spots and scanning specks, while preserving the people, objects, edges, texture, text, lighting, and composition, without smoothing meaningful detail or adding anything new.

A second, negative instruction names what the result must not contain — changed identity, altered composition, plastic skin, added or missing objects, text, watermarks.

The model then repaints the image at 60 per cent strength. The seed is a fixed number, so the same file always produces the same repair.

Dust is not a visual category

This is the thing to understand before judging any result.

Every other kind of image defect can be described by how it looks. Blur is a loss of high frequencies. Compression blocking is a repeating eight pixel pattern. Noise is random pixel-to-pixel variation. A machine can be taught to find them because they have a signature.

Dust has no signature. A speck of dust is a small mark that contrasts with what is around it — and so is a mole, a beauty spot, a freckle, a distant bird in a sky, a star, a snowflake, a stray sequin, a pigeon on a roof, a full stop in printed text. Physically identical. The only thing separating them is that you wanted some of them in the photograph.

So the model is not detecting dust. It is guessing at intent from context: marks that sit on no surface, that cast no shadow, that appear in a region where nothing similar appears elsewhere, that break the grain of the print rather than belonging to it. That reasoning is good and it is not reliable, and it is weakest exactly where the mark is ambiguous.

A local problem solved globally

A speck occupies a few hundred pixels of an image containing a million of them.

The obvious way to fix it is locally: select the spot, sample nearby pixels, paint over it, leave everything else untouched. That is what a healing brush in an editor does, and for a handful of visible spots it is both faster and safer than anything here.

This workflow does the opposite. It repaints the entire image and the specks happen to be absent from the repainting. Every pixel is reconsidered, including the ninety nine point nine per cent that had nothing wrong with them.

That is a genuinely poor trade for three spots on a clean photograph, and a good one for a scan carrying hundreds of them across a complicated surface, where selecting each by hand is an afternoon. Choose accordingly rather than treating this as a general-purpose cleanup.

Sixty per cent, set for the worst case

The strength here is slightly higher than on the noise page, which surprises people who assume dust is the smaller job.

It is set for the hard case rather than the typical one. A heavily flecked scan of an old print needs enough freedom for the model to rebuild surface it cannot see through the damage. A photograph with four specks does not, and at this strength it gets rebuilt anyway.

The consequence is that a lightly affected image is changed more than it needed to be. If your source is nearly clean, an editor's healing brush will preserve more of it than this page will.

The resize may get there first

There is an honest observation here that is easy to leave out.

A dust speck is small by definition — often three or four pixels on a large scan. Scaling that scan to one megapixel is roughly a three-fold linear reduction, which turns a four pixel speck into something close to a single pixel, blended with its neighbors.

So a share of the improvement you see happened during the resize, before the model ran at all. On very large scans that share can be substantial. Downscaling your own copy and looking at it is a fair comparison to make, and occasionally it is the whole answer.

Publication gate

This page ships once the workflow has been run against a flatbed scan with glass dust, an old print with paper flecks, a portrait with visible moles, and a night sky containing stars, with each output compared against the source at full size to confirm what was removed alongside the dust.

Examples

Scanned family print

scan.jpg - 3400x2600, a flatbed scan with visible glass specks
prathom-remove-dust.png - 1148x878, specks cleared

The intended case. Scanner dust sits on a plane the photograph does not, so it has no shadow, no perspective, and nothing around it that agrees with it.

Old print with paper flecks

print.jpg - 2000x2000, white flecks across a sky
clean-print.png - 1024x1024

A plain sky is the easiest surface to repair because there is nothing behind the fleck that has to be reconstructed correctly.

Frequently asked questions

Will it remove moles or freckles from a face?

Sometimes, and this is the failure to watch for. A mole and a dust speck are both small dark marks on a light surface, and the model cannot consult your intentions. The negative instruction guards identity, which helps because a face is recognizable, but a small mark on a shoulder or an arm has no such protection.

What is the difference between this and the scratch removal page?

Scratches are lines and dust is points, and they fail differently. A scratch crosses features and has to be reconstructed along its length, so the repair is a matter of continuity. A speck sits in one place and only needs its immediate surroundings, which makes it the easier repair and the one more likely to catch innocent details.

Will I get the same result if I run it twice?

Yes. The seed is a fixed number rather than a random one, so the same input returns the same output every time. Repeating a run will not give you a cleaner result, and if something was removed that should have stayed, it will be removed again in exactly the same way.

Why is my result smaller than the file I scanned?

The image is scaled to about one megapixel before the model reads it, so a large flatbed scan comes back considerably smaller. This matters more here than on most pages, because the specks you are removing are small enough that the resize alone may already have disposed of some of them.

Is the AI Remove Dust tool free, and do I need an account?

It is free and there is nothing to register for. No account is created, no address is collected, and no reduced-quality preview is withheld for a plan that does not exist. The constraints that do apply come from the workflow itself rather than from billing: 25 MB in, a shared GPU queue, and a thirty-minute window to collect the output.