Camera Settings for Milky Way Photography
Camera settings for Milky Way photography are simpler than most people think. There are really only three variables, and once you understand the logic behind each one, you'll be able to dial them in on any camera in under a minute.
If you've planned your shoot and you're standing in the dark with a camera on a tripod, this is where things get practical. Camera settings for Milky Way photography are simpler than most people think. There are really only three variables, and once you understand the logic behind each one, you'll be able to dial them in on any camera in under a minute.
I remember standing in a field in Colorado on my second real Milky Way outing, cycling through settings and hoping something would work. I'd read a dozen articles that all gave slightly different numbers. Once I understood why the numbers are what they are, I stopped guessing.
The Three Settings That Matter
Milky Way photography uses manual mode exclusively. Auto settings don't work because your camera's meter has no idea what to do with a dark sky full of pinpoints of light. You're controlling three things: shutter speed, aperture, and ISO. They all interact, and the goal is simple: collect as much light as possible in the time you have.
Shutter Speed: Beyond the 500 Rule
You'll see the 500 rule mentioned everywhere. Divide 500 by your focal length to get your maximum exposure time before stars trail. At 24mm, that's about 20 seconds. At 14mm, roughly 35. It's been the standard quick-math answer for years, and you should know it exists because people will reference it constantly.
The problem is that the 500 rule was created for film cameras and lower-resolution sensors. Modern cameras with 30, 45, or 60+ megapixels resolve star trailing much earlier than the 500 rule predicts. On my full-frame camera with a 24mm lens, the 500 rule says 20 seconds, but I see visible trailing at anything over 15. Higher-resolution sensors are less forgiving.
The 500 rule also ignores where you're pointing the camera. Stars near the celestial equator (which is where the galactic core sits during prime season) move faster across your sensor than stars near the poles. That 20-second exposure that looks fine aimed at Polaris might show obvious trailing aimed at Sagittarius.
The better approach: use a spot stars calculator. PhotoPills has a Spot Stars calculator that accounts for the variables the 500 rule ignores. You enter your specific camera body, lens, focal length, and declination (where in the sky you're pointing), and it calculates the exact maximum exposure time for acceptably sharp stars on your specific setup. It factors in pixel size, sensor resolution, and star movement rate for your target area of sky.
This is what I use now instead of mental math. The results are more conservative than the 500 rule (often 2-5 seconds shorter), but they're accurate. You get genuinely sharp stars instead of "probably good enough" stars. The PhotoPills app costs a few dollars and is worth it for this feature alone, though it does a lot more for astrophotography planning.
If you don't have PhotoPills, you can still start with the 500 rule and then test. Take a shot, zoom in to 100% on your LCD, and look for any elongation. If you see trailing, drop your exposure by 2-3 seconds and test again. But if you're serious about this, get the app and use the calculator. It removes the guesswork.
Aperture: Open It Up
Shoot wide open or close to it. If your lens is f/2.8, shoot at f/2.8. If it's f/1.4, try f/1.4 or f/1.8.
Every stop you close down cuts your light-gathering in half. At night, you need every photon you can get. Yes, most lenses are sharper stopped down a bit, and you'll see slightly softer corners at maximum aperture. For Milky Way photography, that trade-off is worth it. You can't process detail that wasn't captured in the first place.
If you're using a kit lens at f/3.5 or f/4, that's fine. You'll compensate with ISO. It won't be as clean as f/2.8 or faster, but it absolutely works. I shot with a kit lens for my first year and got images I'm still proud of.
ISO: Higher Than You Think
This is where most beginners are too conservative. Modern cameras handle high ISO far better than you'd expect. For Milky Way photography, I typically shoot between ISO 3200 and ISO 6400. On newer cameras with good high-ISO performance, I'll push to 8000 or even 12800.
The logic: would you rather have a clean, dark image with no visible Milky Way, or a slightly noisy image that actually shows the galactic core's structure? Noise can be managed in processing. Missing detail can't be recovered.
Start at ISO 3200 and take a test shot. If the core looks faint and the image is mostly dark, bump to 6400. If it's still underexposed, go higher. You'll find the sweet spot for your specific camera after a few test frames.
My Starting Settings (Copy These)
If you want a starting point to get shooting quickly, try these:
| Setting | Full Frame | Crop Sensor |
|---|---|---|
| Focal length | 14-24mm | 10-18mm |
| Aperture | f/2.8 (or widest available) | f/2.8 (or widest available) |
| Shutter speed | 15-20 seconds | 15-20 seconds |
| ISO | 3200-6400 | 3200-6400 |
| Focus | Manual (see Lesson 5) | Manual (see Lesson 5) |
| White balance | ~4000K (or Auto, adjust in post) | ~4000K (or Auto, adjust in post) |
These are starting points. Take a test shot and adjust based on what you see.
Other Settings to Check
A few things that trip people up:
Shoot RAW. Not JPEG. RAW files contain far more data, which matters enormously when you're processing Milky Way images. The shadow detail and color information in a RAW file is the difference between a good result and a great one. If your camera supports it, shoot RAW exclusively for astrophotography.
Turn off long exposure noise reduction. Your camera may have a setting that takes a "dark frame" after every long exposure and subtracts the noise pattern. This doubles your shooting time. A 20-second exposure takes 40 seconds total. You don't need this because you'll be shooting your own dark frames separately (exposures taken with the lens cap on, which capture your sensor's noise pattern) and subtracting them in post-processing. This gives you the same noise correction with more control, and you won't lose half your shooting time waiting for the camera to do it automatically. Turn this off.
Turn off image stabilization. When your camera is on a tripod, image stabilization can actually introduce vibration as the system tries to correct for movement that isn't there. Switch it off for tripod-mounted shooting.
White balance: set it manually, never use Auto. Set it to around 4000-4200K for a neutral starting point, or use a preset like Tungsten or a custom Kelvin value. The specific number matters less than picking one and sticking with it. Auto white balance shifts between frames as conditions change, even in the dark. If you're stacking multiple exposures or blending sky and foreground from different frames, inconsistent white balance between shots makes combining them difficult. Pick a value, lock it in, and adjust in post if needed. Any fixed setting is better than Auto.
When Settings Aren't the Problem
After a few sessions, you'll have your settings dialed in and they'll rarely change. If your images still aren't looking like the ones you see online, the issue is almost certainly one of these:
- Not dark enough. Settings can't compensate for light pollution. If you're at Bortle 5 or higher, no amount of ISO will give you a clean galactic core.
- Wrong timing. If the galactic core isn't in your frame (or is too low on the horizon), your settings don't matter.
- Processing. A raw Milky Way image straight out of camera looks flat and underwhelming. That's normal. Processing is where the drama comes from, and that's Lesson 7.
The settings get you the raw material. Everything else is planning and processing.