FocalMathSupport Us

Understanding Astro Shutter-Speed Limits (500 Rule vs NPF Rule)

Want to compute this yourself? Use the Astro 500/NPF Rule Calculator.

Every other shutter-speed decision in photography is a tradeoff against light or motion blur. Astrophotography shutter-speed limits are a different kind of constraint entirely: even with a perfectly still tripod and a stationary subject, the Earth itself is rotating underneath the camera, so stars — which are, for a night's exposure, effectively fixed points in the sky — sweep across the frame at a rate the camera can't avoid. Past a certain exposure length, that sweep becomes visible as a short streak instead of a clean point. Two different rules exist for estimating where that line sits, and they disagree for specific, understandable reasons.

Why Stars Trail at All

The sky's apparent rotation covers 360 degrees over roughly 24 hours, which works out to about 15 arcseconds of apparent motion per second of time near the celestial equator. That sounds tiny, and at normal viewing scale it is — but a long lens or a high-resolution sensor magnifies that same angular motion into a meaningfully larger number of pixels of movement, which is exactly why the safe exposure time depends on focal length and, less obviously, on how finely your sensor resolves the sky in the first place.

The 500 Rule: Fast, Simple, and From a Different Era

The 500 rule divides 500 by your full-frame-equivalent focal length to get a maximum shutter speed in seconds — 500 ÷ 24mm gives roughly 20 seconds, for example. It's a film-era mental-math shortcut, calibrated originally to what looked acceptably sharp on a printed photograph or a normal-sized screen, not to pixel-level scrutiny on a modern high-resolution sensor. It knows nothing about your specific camera's resolution, because in the era it was popularized, resolution differences between cameras weren't dramatic enough to matter for a rough field estimate. Some photographers use a stricter 300 rule for pixel-peeping standards, or a looser 600 rule when the final output is small (web, social media) and a bit of trailing at full-resolution zoom won't be visible in the delivered image.

The NPF Rule: What It Actually Accounts For

The NPF rule (N for aperture, P for pixel pitch, F for focal length) was developed specifically to close the gap the 500 rule leaves open on modern sensors. This site uses the commonly published simplified form: t = (35 × N + 30 × p) ÷ f, where N is the f-number, p is pixel pitch in microns, and f is the actual — not full-frame-equivalent — focal length in millimeters. Two things the 500 rule ignores show up directly here. First, pixel pitch: a densely packed, high-resolution sensor has smaller individual pixels, and star trailing that would be invisible spread across large pixels becomes visible sooner when magnified onto small ones — so a 61-megapixel body needs a shorter safe exposure than a 24-megapixel body at the identical lens and framing. Second, aperture enters the formula directly, which the 500 rule doesn't touch at all — a narrower aperture very slightly extends the safe window in this formula's model, though the effect is modest compared to focal length and pixel pitch.

Declination: The Part Almost Nobody Accounts For

Both rules, in their basic form, assume every star moves across the sky at the same rate — which isn't true. Stars near the celestial equator (declination near 0 degrees) trace the widest possible circle around the celestial pole in 24 hours, so they cover the most angular distance per second and trail the fastest. Stars near the celestial pole (declination near ±90 degrees) trace a tiny circle, barely moving at all over a normal exposure. A shutter speed that keeps Polaris looking like a sharp point can show visible trailing on a star near the equator in the same frame, at the same exposure. The full NPF calculation applies a correction that divides the base result by the cosine of the target's declination, which is why framing a composition toward the celestial pole genuinely buys real extra exposure time — not a photographer's superstition, but the direct consequence of how much less that part of the sky appears to move.

Why the Two Rules Disagree, and by How Much

On an older or lower-resolution full-frame body, the 500 rule and the NPF rule tend to land fairly close together, because the pixel pitch on those sensors is large enough that trailing genuinely doesn't become visible much sooner than the 500 rule predicts. On a modern high-resolution body, the NPF number is often noticeably shorter — sometimes by half or more — because the tighter pixel pitch reveals trailing earlier than the older, resolution-blind rule accounts for. Neither number is simply wrong; they're calibrated to different standards of "acceptably sharp." The 500 rule targets a result that looks fine at normal viewing size or a modest print; the NPF rule targets a result that holds up to full-resolution pixel-level scrutiny, which matters more the more you plan to crop, print large, or zoom into your final image.

Worked Example

A 24-megapixel full-frame body at 20mm, f/2.8, pointed near the celestial equator: the 500 rule suggests roughly 25 seconds (500 ÷ 20). The NPF rule, using that sensor's real pixel pitch of roughly 6.0 microns, works out to about 14 seconds before trailing becomes visible at full resolution — close to half the 500 rule's estimate. Point the same lens and camera toward a star near the celestial pole instead, and the declination correction can more than double the safe exposure time again, since motion there is dramatically slower.

What Actually Changes the Safe Exposure Time

  • Wider focal length: more sky per pixel means the same angular motion covers fewer pixels, extending the safe shutter speed under both rules.
  • Lower resolution (larger pixel pitch): fewer, larger pixels mean the same angular motion is less visible per pixel, which only the NPF rule accounts for.
  • Declination closer to the celestial pole: dramatically less apparent motion, extending safe exposure time — again, only modeled by the full NPF calculation.
  • Aperture: has a small effect in the NPF formula's model, but is a far smaller lever than focal length, resolution or declination.

Choosing Which Number to Actually Shoot At

The right choice depends on what happens to the image afterward, not on which rule is more theoretically correct in the abstract. A Milky Way panorama destined for a phone screen or a social feed has real headroom to exceed the NPF number and lean toward the more generous 500 rule figure, since the final display size will never reveal pixel-level trailing that only shows up under close inspection. A single-frame image intended for a large print, or one you plan to crop into significantly, benefits from sticking closer to the stricter NPF number, since both printing large and cropping tight are exactly the operations that turn borderline trailing into visibly trailing stars. Photographers who stack multiple exposures in post-processing to reduce noise have an additional reason to favor the shorter, stricter number consistently across every frame in the stack — inconsistent trailing between stacked frames can produce soft or doubled-looking stars in the final blended result even when each individual frame looked acceptable on its own.

Star Trackers Change the Question Entirely

Both rules assume a stationary tripod. A star tracker physically rotates the camera to match the sky's apparent motion, which removes the trailing constraint almost entirely and lets exposures run for minutes instead of seconds — genuinely different math, not just a more generous version of the same rule. Neither the 500 rule nor the NPF rule is meant to apply once a tracker is doing the counter-rotation; the limiting factor at that point becomes tracking accuracy and, eventually, foreground blur if the ground is also in frame.

Frequently Asked Questions

Should I always trust the NPF number over the 500 rule number?

For a technically accurate limit at full resolution, yes — but the 500 rule remains useful as a fast mental estimate in the field when you don't have your camera's exact pixel pitch handy, and it errs on the safe-looking side for smaller final output.

Does a full-frame sensor always trail less than a crop sensor at the same settings?

Not automatically — trailing depends on pixel pitch and real focal length, not sensor size directly. A full-frame body with very high resolution can have a smaller pixel pitch, and therefore a shorter safe exposure, than a lower-resolution crop-sensor body, even though the crop sensor is physically smaller.

Why does my planetarium app give a slightly different maximum exposure than this calculator?

Several NPF implementations exist with slightly different published coefficients, and some apps default to a specific declination (often the celestial equator, the worst case) rather than letting you set your actual target's declination — small differences in either input produce small differences in the final number without either tool being wrong.

Does cropping in afterward make trailing worse than it looked in the original file?

Yes, effectively — cropping enlarges the remaining pixels relative to the full frame you'd otherwise view, which magnifies any trailing that was already present but too small to notice at full-frame viewing size, the same way printing large or zooming in does.