Astrophotography Tools

Flat-Frame Setup Calculator

Work out the exposure, ADU target, panel brightness, frame count and calibration frames your flats need — from your actual telescope, camera, filters and light panel.

Telescope & camera

Aperture doesn’t affect flat exposure — focal ratio sets the illumination.

Sets ADC depth, sensor type, shutter & driver scaling automatically.

Colour sensors need the brightest channel measured, not the frame average.

What the sensor digitises at — not necessarily what your software displays.

Most DSLRs & many CCDs do; dedicated CMOS usually don’t.

Optional: gain, measured bias level & read noise

Recorded so the advice echoes it back — flats must be shot at the same gain as your lights.

The mean of a master bias, in the same units your software shows. Not the driver’s offset setting — “offset 50” is roughly 500 ADU on an ASI2600 and 3,200 ADU on an ASI294, and the multiplier differs per model.

As published for your gain setting (an ADC-referenced figure).

Light source & exposure

40–50% is the safe sweet spot.

Filters in your train

01Recommended targets

Based on your setup.

02Suggested exposure per filter

03Warnings & checks

04Frame count & calibration

05How flat frames work — the complete guide

Everything behind the numbers above: what flats do, how to shoot them, and how to read your histogram.

What a flat frame is, and why you need one

A flat frame is a picture of an evenly illuminated blank field — not stars, just uniform light — taken through the exact same optical train as your deep-sky images: same scope, camera, filter, focus and rotation. Because the incoming light is perfectly even, any unevenness in the resulting frame must have been added by your optics and sensor.

That map of unevenness is what calibration software needs. It divides every light frame by a master flat, cancelling the fingerprint of your system: dark corners, dust shadows and gradients. The background goes flat and neutral, so faint nebulosity survives a hard stretch instead of drowning in rings and vignetting.

What flats correct (and what they don’t)

  • Vignetting / light falloff — less light reaches the corners, worst in fast systems.
  • Dust motes (“donuts”) — out-of-focus rings from dust on filters or windows; smaller spots from dust on the sensor.
  • Uneven illumination & internal reflections that create smooth gradients.
  • Pixel-to-pixel sensitivity (PRNU) — the fixed pattern of slightly different pixel gains.

What flats do not fix

Flats correct multiplicative (light-path) effects. They do not remove additive signals like amp glow, dark current or hot pixels — that’s the job of dark frames. Sky-gradient light pollution is handled by background extraction in post, not by flats.

The calibration math

Calibration combines your frames like this:

Calibrated = (Light − Dark) ÷ (Flat − FlatDark or Bias) × k

The dark is subtracted (additive signal), the flat is divided in (multiplicative), and k is the flat’s average level so overall brightness is preserved. The key consequence: because the flat divides into every sub, its noise ends up in every frame — which is why a well-exposed, well-stacked flat matters.

What a good flat looks like — the ADU target

Expose into the middle of the sensor’s linear range: roughly one-third to one-half of the histogram. The actual ADU depends on your bit depth:

Bit depthMax ADU~40% target~50% target
12-bit4,095~1,640~2,050
14-bit16,383~6,550~8,190
16-bit65,535~26,000~32,800

The formula is ADU = offset + (max − offset) × fraction. A common sweet spot is ~25,000–33,000 ADU on a 16-bit scale. Note that many “16-bit” CMOS cameras actually digitise at 12 or 14 bits and bit-shift up — set the bit-depth field to match whatever scale your capture software measures ADU in.

Why short exposures — but not too short

Short flats (a second or two) mean almost no thermal signal and let you shoot dozens quickly. But there’s a floor:

LED flicker (PWM). Most dimmable LED panels flash on and off hundreds of times a second to control brightness. A very short exposure catches only part of that cycle, producing shifting horizontal banding — worse on rolling-shutter CMOS. Keep PWM-panel flats above about 0.5–1 second (some panels need 2–3 s). The fix for “too bright” is always to dim the panel and lengthen the exposure, never to shorten it. EL and constant-current panels don’t flicker.

Shutter shadow. Cameras with a mechanical shutter cast a moving curtain shadow. At very short speeds that shadow is uneven across the frame, so keep mechanical-shutter flats at or above ~1–2 seconds.

Light sources for flats

SourceEvennessFlickerVerdict
EL / constant-current panelExcellentNoneBest — any exposure
Quality dimmable LED panelExcellentPWM (keep ≥0.5–1 s)The practical standard
Sky / twilight flatsVery goodNoneFree, but changes fast
White T-shirt over apertureFairNoneCheap starter
Computer / tablet screenPoorPWMNot recommended

A dedicated flat panel is the most repeatable option. Motorised panels double as a dust cover and can be driven directly by N.I.N.A., SGP and Voyager so flats run automatically.

Wanderer Astro Flat Panels

Motorised panels with a self-locking cover and fine 255-level brightness — bright enough for narrowband and driven directly by N.I.N.A. and SGP. Doubles as a powered dust cover.

Shop Wanderer Astro

Pegasus Astro FlatMaster

The FlatMaster 120 Neo is a flat-field generator with software-controlled brightness, natively supported in N.I.N.A. for fully automated, repeatable flats.

Shop Pegasus Astro

Filter by filter

Shoot — and calibrate — flats separately for every filter. Each filter carries its own dust in its own positions and passes a different amount of light. Narrowband is the big one: an Hα, OIII or SII filter passes only a 3–7 nm slice of the spectrum, so its flats run 5× to 50× longer than luminance — often many seconds even at full brightness. That’s normal. Auto-expose to a fixed ADU target per filter rather than reusing one exposure time.

One-shot colour: measure the brightest channel

On a colour sensor, the red, green and blue photosites see wildly different amounts of light from the same panel — because the panel isn’t spectrally flat and the Bayer filters aren’t equally efficient. Your capture software reports the average of all of them, and that average hides the spread.

We measured a real flat to see how bad it gets. On an ASI294MC Pro shooting a panel through a Takahashi FS-60 at f/5.9, the whole-frame mean was a healthy-looking 43.9% of full scale — but underneath:

ChannelMean ADU% of full scale
Red14,35121.9%
Green33,26250.8%
Blue34,30452.3% — already clipping
Whole frame28,79543.9%

Blue sat 2.4× higher than red, and a measurable population of blue pixels had hit the ceiling at 65,534 — while the frame average still looked comfortably mid-range. Those clipped pixels divide badly into every light frame.

So on an OSC camera: split the frame into its Bayer channels and put the brightest one at 40–50%. PixInsight’s SplitCFA, Siril’s channel statistics, or ASTAP will all do it. If your software only gives you a frame average, aim lower than you otherwise would — on the rig above the brightest channel ran about 19% above the frame mean, though that ratio depends entirely on your panel’s colour and your filters, so measure it once for your own setup rather than trusting a rule of thumb.

One consolation: because calibration divides channel by channel, an uneven level across channels is harmless in itself. It only matters because the brightest channel is the one that clips, and clipping is not recoverable.

How many flats, and the combined noise

Stacking N flats reduces their random noise by √N (25 flats → ÷5; 100 → ÷10). Because the master flat divides into every light, that noise doesn’t average away later — so shoot 20–30 per filter for most rigs, and 40–50 for fast optics or narrowband. Beyond ~50 you hit diminishing returns.

Dark flats vs bias frames

Before the flat is divided in, its own pedestal (offset, read noise, and for longer flats a little dark current/amp glow) must be removed with either bias frames (shortest exposure) or dark flats (darks matched to the flat’s exposure, gain, offset and temperature).

  • CMOS: prefer dark flats — many CMOS sensors have unstable bias at ultra-short exposures or show amp glow. Stable IMX571-class sensors (ASI2600/QHY268) also work with bias.
  • CCD: stable — bias is fine under ~30 s; dark flats for longer flats (Adam Block’s 30-second rule of thumb).
  • DSLR: matched dark flats are safest since the sensor is uncooled.

Don’t double-subtract

Pick one scheme. Calibrating lights with both a bias and matched darks that already contain the bias over-subtracts the pedestal and clips your data.

Match everything, and re-shoot when it changes

Keep gain, offset, temperature, binning, filter, focus and rotation identical between flats and lights. Re-shoot flats whenever you rotate the camera, refocus, pick up new dust, or change filters/spacing/reducer. “My flats made it worse” is almost always a train that changed between lights and flats.

06Frequently asked questions

What is a flat frame, and why can’t I skip it?

A flat is an image of an evenly lit blank field through your exact setup. Software divides it into your light frames to cancel vignetting, dust shadows and gradients. Without flats, a hard stretch reveals dark corners and dust rings that are almost impossible to remove cleanly afterward — so flats are usually the single biggest quality jump for a given amount of imaging time.

What ADU or histogram level should I aim for?

Aim for roughly 40–50% of full scale — the middle of the sensor’s linear range. Percentage is the reliable way to say it, because the ADU number depends on how your driver packs the data: most cameras report a 16-bit range (0–65,535) no matter what the sensor digitises at, so 40–50% is about 26,000–33,000 ADU for nearly everyone. Only if your software shows the sensor’s native range does that become ~6,500–8,200 on 14-bit or ~1,640–2,050 on 12-bit. The calculator prints both. Avoid clipping the bright end (over-exposed flats mis-correct) and avoid very low levels (noisy flats inject grain into every light).

I have a colour camera — is the average ADU good enough?

No, and this is a common way to clip a flat without realising. On a one-shot colour sensor the red, green and blue photosites sit at very different levels, and your software reports their average. On a real ASI294MC Pro flat we measured, the frame average was a comfortable 43.9% of full scale while the blue channel was at 52.3% with pixels already saturated at 65,534 — blue was running 2.4× higher than red. Split the frame into its Bayer channels (PixInsight’s SplitCFA, Siril, or ASTAP) and put the brightest channel at 40–50%.

How do I check what ADU range my camera actually reports?

Open one raw frame and look at the spacing between pixel values. If every value is a multiple of 16, your camera is digitising at 12-bit and the driver is multiplying by 16 to fill a 16-bit file. Multiples of 4 mean a 14-bit sensor scaled by 4. No consistent spacing means you’re seeing native 16-bit data. This is worth doing once, because the answer isn’t always what the camera’s spec sheet implies — we tested an ASI294MC Pro whose data came out in steps of 16 (12-bit) even though the camera is published as 14-bit, because the capture software was set that way. On a colour camera, check a green pixel: red and blue may have white-balance multipliers applied that hide the pattern.

Why are my flats showing horizontal banding or lines?

That’s almost always LED flicker. Dimmable LED panels use PWM (rapid on/off flashing) to control brightness, and short exposures catch only part of that cycle. Dim the panel and lengthen the exposure past about 1 second rather than going shorter, or use an EL / constant-current panel that doesn’t flicker. Shooting more frames also helps residual banding average out.

Why do my narrowband flats need such long exposures?

Narrowband filters only pass a 3–7 nm sliver of the spectrum, so they transmit a tiny fraction of the panel’s light compared with a broadband L filter. To reach the same ADU target they need much longer exposures — commonly 5× to 50× luminance, often many seconds even at full brightness. That’s expected. Auto-expose each filter to the target rather than reusing one exposure time.

Should I use dark flats or bias frames?

For most modern CMOS cameras, use dark flats (darks matched to your flat’s exposure, gain, offset and temperature) — they’re the safe, always-correct choice, especially for sensors with amp glow or long narrowband flats. CCDs are stable enough that bias works for flats under ~30 seconds. DSLRs are best with dark flats. The calculator recommends one based on your camera and exposures.

How many flats should I take, and how often?

20–30 per filter suits most setups; 40–50 for fast optics or narrowband. Re-shoot your flats whenever anything in the light path changes — a camera rotation, a refocus, new dust, or a filter/spacing change — and ideally at the start or end of each session without disturbing the train.

Is any of my data sent anywhere?

No. Every calculation runs entirely in your browser. Nothing you enter is uploaded, stored or sent anywhere.

Reviewed July 2026 by Ontario Telescope & Accessories.

All calculations run locally in your browser — nothing is uploaded. Questions about flats or flat panels? Get in touch.

Recommendations are starting points based on widely-used community and software guidance. Optimal values depend on your specific sensor, panel and sky — always confirm the histogram on your own frames. Basic-mode exposures are ballpark estimates; use Advanced mode with a measured flat for accuracy.

The software packages named on this page (N.I.N.A., Sequence Generator Pro, Voyager, ASIAIR, SharpCap, DeepSkyStacker and any others) are referenced for educational purposes only. Ontario Telescope & Accessories does not recommend or endorse any software package, and has no affiliation with any of them. All trademarks belong to their respective owners.

© 2026 Ontario Telescope and Accessories Inc. All rights reserved. The calculator, its explanatory text and the compiled equipment database may not be reproduced without permission.