Star Stacking With the Sony A7R V: A Field-Tested Workflow

I've dragged the Sony A7R V out to three different dark sky sites this year, and every session reminds me that star stacking with a 61-megapixel body is a different animal than the workflow most guides are still written around, which usually assumes a 24MP sensor and a much more forgiving pixel pitch. The resolution helps in ways people don't expect and it hurts in ways almost nobody warns you about before you're standing in a field at 1am wondering why your stars look mushy. This is what actually works, based on real nights out, not the generic "set it to manual and shoot RAW" advice that gets copy-pasted across half the internet.

What the 61-megapixel sensor changes about stacking

The A7R V's sensor packs its 61 million photosites into a full-frame area with a pixel pitch around 3.76 microns. Compare that to something like an A7 III or A7S III, where the pitch sits closer to 5.9 or 8.4 microns, and you can see the tradeoff immediately: each individual photosite on the A7R V is gathering less light, which shows up as more visible noise per pixel at high ISO when you pixel-peep at 100%. On a single frame, that's a real disadvantage for astro work compared to a lower-resolution, larger-pixel body.

Stacking is where that disadvantage mostly disappears. Once you've combined 40, 80, or 150 sub-exposures and downsampled the result, the extra resolution turns into extra data to average, and the final signal-to-noise ratio often beats what you'd get from a lower-megapixel camera shooting the same total integration time. I've compared a 60-frame stack from the A7R V against a similar stack from an older 24MP body shot the same night at the same site, and the A7R V file held up better once both were resized to match. The catch is that you have to actually stack. A single untracked 61MP frame at ISO 6400 straight out of camera will look noisier than people expect, and if that's your only test before judging the camera, you'll walk away with the wrong impression.

There's a second wrinkle specific to Sony bodies that's worth being honest about: the "star eater" behavior, where in-camera noise reduction algorithms have historically smeared out faint, closely-spaced stars even with Long Exposure NR switched off, particularly around the 3.2 to 4 second shutter range and again past 30 seconds in bulb mode. Sony's changed the sensor readout pipeline generation over generation, and the A7R V is noticeably better than the A7 III era bodies I used to shoot with, but I still see faint chroma smearing on tight star clusters right around that 3.2 to 4 second window. My workaround is simple: I avoid that specific exposure length when I have a choice, going either shorter with a tracker or longer without one, rather than assuming the problem is fully gone.

Getting exposure right before you open a stacking program

Everything downstream depends on getting individual subs sharp, which on a 61MP sensor is less forgiving than people assume. The old "500 rule" (500 divided by focal length equals your max shutter speed) was designed for lower-resolution sensors and cheerfully lets stars trail into visible streaks once you're pixel-peeping a 61MP file. I use the NPF approach instead, which factors in aperture and pixel pitch, not just focal length. In practice, on a 20mm f/1.8 lens, that means something closer to 4 to 5 seconds untracked before trailing becomes visible at full resolution, not the 20-25 seconds the 500 rule would suggest. PhotoPills calculates this for you and it's worth the app price just for that one feature.

If you're using a star tracker (I run a Move Shoot Move on a photo tripod for wide-field work, and switch to an iOptron SkyGuider Pro when I want longer glass), the math changes entirely and your limiting factor becomes tracking accuracy and polar alignment rather than pixel pitch. A well-aligned tracker on the A7R V will comfortably hold pinpoint stars at 60-90 seconds with a wide lens, which means fewer, cleaner subs and less time spent culling afterward.

Menu settings I actually touch for a night of stacking

Long Exposure NR goes off, full stop, for anything I'm planning to stack. It doubles your exposure time by shooting a dark frame after every light frame, which is wasted time when you're going to build your own calibration frames anyway. High ISO NR I leave on the lowest setting rather than fully off, since RAW files are minimally affected by it and I'd rather not fight banding later.

The built-in interval shoot function is the feature that makes a stacking session on this camera actually pleasant to run. I set the number of shots, the interval, and the exposure length once, hit start, and walk away to keep warm instead of standing over a wired remote pressing a button every eight seconds for forty-five minutes. For anything longer than 30 seconds per sub I switch to bulb via the Sony Creators' App on my phone, since the camera's native bulb timer tops out lower than some competing bodies.

Two practical notes that have nothing to do with menus: bring more NP-FZ100 batteries than you think you need, because cold nights and constant sensor activity from interval shooting drain them faster than daytime use, and use both card slots. On a long session shooting 61MP RAW continuously, I've filled a 128GB card faster than expected, and having the SD slot as overflow while the CFexpress Type A card handles the write speed has saved a session more than once.

A typical night, start to finish

A recent session at a reasonably dark site (Bortle 4) went like this: wide Milky Way core with the Sony 14mm GM on the tracker, 90 seconds per sub at ISO 1600, 25 frames before the core rotated too far out of frame, plus five dark frames shot with the lens cap on at the same settings for calibration. Then I switched to the 20mm f/1.8 G untracked for a foreground-inclusive composition, shooting 45 frames at 5 seconds and ISO 4000 to keep pinpoint stars while still getting enough total light for a clean stack. The whole thing, including repositioning and a coffee break, took about ninety minutes and produced 70 usable subs plus calibration frames, which is a manageable number to review by hand but starts to add up once you're doing this every clear night for a season.

Getting from 150 raw files to one finished frame

This is the part that most guides skip, and it's the part that actually eats your evening. Once you're home with 150-300 RAW files from a stacking session, each one 60-120MB depending on compression settings, you have to figure out which subs are actually sharp before you feed anything into Sequator, Deep Sky Stacker, or Starry Landscape Stacker. Wind gusts shake the tripod on individual frames, a tracker occasionally hiccups mid-sequence, and a plane or satellite trail ruins the odd exposure. Stacking software will happily include a soft or trailed frame and quietly drag down the sharpness of your whole composite.

This is where I've started running the batch through imagic before it ever touches stacking software. Its local sharpness and focus scoring flags the handful of subs where a gust of wind moved the tripod or the tracker drifted for a frame or two, so I'm not stacking soft frames into an otherwise clean sequence, and I can pull those culls out in a few minutes instead of scrubbing through 200 near-identical thumbnails by eye at 1am. Because it's a one-time purchase running entirely on-device, a folder of 15-20GB of RAW files from a single night stays on my laptop the whole time, which matters when you're shooting a full season of sessions and have no interest in uploading that volume to anyone's cloud service. If you haven't compared how different culling approaches actually work under the hood, this breakdown of AI photo culling covers the sharpness scoring side in more detail than I can here.

Once the stack is built and I've settled on a color and contrast treatment I like for a given series (slightly cooler shadows, a specific amount of saturation pulled out of the orange light pollution glow near the horizon), I save that as an apply_my_style preset in imagic and run it across the rest of that season's frames instead of rebuilding sliders from scratch every time I process a new stack. It's a small thing, but when you're processing a dozen sessions across a summer, consistency stops being optional and starts being the difference between a cohesive portfolio and a pile of one-off edits. For the culling and sorting side of a big shoot generally, these workflow tips apply just as well to a folder of star subs as they do to a wedding take.

Lenses that actually earn their spot on this body

The Sony 14mm f/1.8 GM is the lens I reach for most, and it's genuinely excellent for astro work: coma control at the edges of the frame at f/1.8 is about as good as I've used, which matters enormously on a 61MP sensor where sloppy corner performance gets magnified. The 20mm f/1.8 G is my second body-and-lens combo for compositions where I want a wider field but still need to include foreground detail, and it's noticeably lighter for nights where I'm hiking a while to reach a dark site. The Sigma 14mm f/1.4 DG DN Art is worth mentioning too, since it's a stop faster than the Sony 14mm and cheaper, at the cost of being heavier and having slightly more visible coma wide open in the extreme corners. For anyone testing manual-focus budget options first, the Rokinon/Samyang 14mm f/2.8 remains a reasonable way to try astro before committing to autofocus glass, though you lose the A7R V's focus assist tools in the process.

Frequently Asked Questions

Do I need a star tracker for the A7R V, or can I stack untracked frames?

You can absolutely stack untracked frames, and it's how I'd recommend starting. The tradeoff is exposure length: without a tracker you're limited to roughly 4-8 seconds per sub depending on focal length and aperture before the 61MP sensor's tighter pixel pitch reveals star trailing, which means you need more subs and higher ISO to reach the same total integration time a tracker would give you in fewer, longer exposures. A tracker becomes worthwhile once you're regularly shooting narrower fields or want cleaner shadows without stacking 150+ frames every time.

Why do my stacked stars look slightly elongated even though each sub was within the NPF-safe shutter speed?

Two usual suspects. First, check your stacking software's alignment mode. Some programs default to aligning on the foreground rather than the stars, which will smear stars into short arcs even when each individual frame was pin-sharp. Second, if you're on a tracker, drift over a long session (polar alignment error compounding over 30-60 minutes) can produce the same effect even when no single sub shows visible trailing at full resolution. Re-checking polar alignment every 20-30 minutes on longer sessions has fixed this for me more than once.

Should I shoot compressed RAW for a session that's going to produce 200+ frames?

I shoot compressed RAW (not lossless compressed) for pure star stacking sessions, since the noise-heavy nature of high-ISO night sky frames means the extra fidelity of uncompressed RAW is rarely visible in the final stack, and the file size difference adds up fast across hundreds of frames. For anything where I'm also keeping a single frame as a standalone shot, like a Milky Way arch over a landmark I might print large, I'll switch to lossless compressed for that specific composition.

Does the A7R V's pixel shift mode have any use for astrophotography?

Not for star fields themselves, since pixel shift requires a completely static scene across all four or sixteen shots and stars move continuously relative to the frame even at short shutter speeds. Where it can help is a static foreground element in a foreground-blend composite, like a tripod-mounted building or rock formation you're compositing with a separately stacked sky, where the extra resolution and reduced noise in the pixel-shift foreground plate genuinely improves the final image.