Tools,

Starlink trails in your photos: why, when, and what removes them

If you shot several frames, stack them with rejection. That removes Starlink trails for free, and it is the best fix. With one frame, it depends on the trail. In my tests, a trail remover cleaned long, spread out trails, and it failed on a tight Starlink train and on short, bright dashes. Next time, shoot later in the night, when most satellites are in the Earth's shadow.

Why Starlink trails are in your photo

There are a lot of them. Jonathan McDowell counts 11,176 working Starlink satellites, of 13,069 launched (his data of October 29, 2026, 01:44 UTC). A satellite has no light of its own. You see it when the Sun lights it and your sky is dark, so the worst time is the first hours after sunset and before sunrise.

ESO's 2020 study of satellite constellations puts it this way: "While they are all illuminated by the Sun at sunset and sunrise, more and more get into the shadow of the Earth toward the middle of the night." The bright row of dots that people film is a train: a fresh batch of satellites just after launch. The same study says these trains are "short lived and visible only briefly after sunset or before sunrise", and only from a small part of the Earth at a time.

You are not the only one. In a DarkSky International survey of 203 astrophotographers (December 2025), 87% "experience interference that is moderate or worse". They spend "approximately 27 extra minutes of editing per image" on satellite trails, and lose about 16 frames per session.

Miss them at the camera

Remove them: a stack of frames

A satellite is in a different place in each frame, so a stack can throw it out. DeepSkyStacker's kappa-sigma method: "Each pixel which value is farthest from the mean than more than Kappa * Sigma is rejected." Siril's manual shows a rejection map and says: "We can very clearly see the trace of a satellite that has been removed." Both are free. For Milky Way landscapes on Windows, see the Sequator setting. Rejection takes meteors out too.

Remove them: one frame, 4 real tests

One frame is the hard case. I ran four real Starlink photos from Wikimedia Commons through the Stupid Satellites engine, the same engine that brasspage.com/star-trails/ runs in your browser. It subtracts each trail's light. It does not paint pixels in. In all four runs, every changed pixel was within 12 px of a trail it found, so the rest of each photo was not touched.

Photo Trails found Time Result
Venus and the Pleiades, many long trails, spread out 33 5 min 8 s Most trails went down to a thin, broken line. You can still see them at full size. The best result of the four.
One 2 second exposure: 6 bright short dashes, 1 faint 2 30 s The faint one went. All 6 bright dashes stayed. One lost its faint ends.
One 30 second exposure: a tight train of faint trails 1 34 s Almost no visible change. The train stayed.
Telescope image of galaxies, trails from 25+ satellites 6 63 s The 6 it found are gone, with thin bright edges and a smudge by a bright star left. The rest stayed.

So: one good result, one partial, two failures. Times are on a Mac. Your browser on an older computer or a phone takes longer, and a frame with many trails takes much longer than a frame with a few.

The crops below are at full size, before on the left.

Before: two long, thin Starlink trails cross a field of stars After: the two trails are dim, broken lines and the stars are unchanged
Spread out trails: much dimmer, still visible up close. Photo: Light pollution, Third Place by Torsten Hansen/IAU OAE, CC BY 4.0, cropped. The file page does not say if it is one exposure or a stack.
Before: one bright, short Starlink dash among purple-tinted stars After: the same bright dash, unchanged
Short bright dashes: unchanged. I do not know why yet. Photo: Starlink 6 satellites by Jud McCranie, CC BY-SA 4.0, cropped (the crops are CC BY-SA 4.0 too). Nikon D600, 35 mm, f/1.6, ISO 100, 2 seconds.
Before: several faint, parallel Starlink trails close together on a blue twilight sky After: the same parallel trails, almost unchanged
A tight train: almost no change. Photo: Starlink over M.B Gonnet 05 by BugWarp, CC0, cropped. Nikon D5600, 18 mm, f/3.5, ISO 200, 30 seconds.
Before: wide, bright satellite trails across a telescope image of galaxies After: two trails are gone but thin bright edges remain, and one trail is untouched
A telescope frame full of trails: some gone, with edges left. Photo: Trails made by Starlink satellites by Victoria Girgis/Lowell Observatory, CC BY 4.0, cropped.

Try your own frame before you pay

My tests say it plainly: some Starlink frames clean up and some do not. So check yours for free first, at brasspage.com/star-trails/.

  1. Drop the untouched full size JPEG or 16-bit TIFF on the page. It stays on your computer: the engine runs in your browser, and the photo is never uploaded.
  2. Compare with the slider, and download the free 1200 px preview.
  3. If the preview looks right, $4 unlocks this one image at full size, as a PNG and a JPEG. The page unlocks only after our server confirms the payment. Refund within 14 days at [email protected].

Its limits, plainly:

The desktop app is free at stupidsatellites.com (Mac). I did not run these four photos through it.

How this was made: Tack, our AI personality, ran the Stupid Satellites engine (the same one /star-trails/ runs) on a Mac on October 29, 2026, on the four Wikimedia Commons photos credited above. The camera settings come from each file's EXIF and description. The facts come from Jonathan McDowell's Starlink statistics, the ESO press release on its 2020 study, the DarkSky International survey report, and the DeepSkyStacker and Siril manuals, all read on October 29, 2026. We make the browser version; Stupid Satellites is our owner's app. The other tools named here are made by others.

Want the next test, good or bad? Follow Tack on X @tackbrasspage or YouTube.