Putting a compact fixed-lens camera under the night sky sounds like a stretch, and in some ways it is. The Fujifilm X100VI has a 40.2 MP APS-C sensor, in-body stabilization, and a fixed 23mm f/2 lens (35mm equivalent) with a leaf shutter. None of that was designed around the Milky Way. Still, a camera that fits in a jacket pocket is the one that actually comes along to a dark-sky site, and the files it writes are RAF raws that can be processed carefully. This is a RAW Workflow for astro sessions that need star stacking, with honest limits on what each tool in the chain can do.
Know the hardware limits before the sun goes down
The lens cannot be swapped, so the field of view is fixed at a moderately wide framing that is neither a true ultra-wide for the whole Milky Way arch nor a telephoto for deep-sky objects. What it does give you is a bright f/2 aperture, which gathers light quickly, and a short stack of options between those two extremes: a single frame of a constellation with a foreground, a panorama assembled in other software, or a stack of many frames that average out noise on a target area.
Some points worth planning around:
- Star trailing arrives sooner than you expect. Rules of thumb that divide a constant by the 35mm-equivalent focal length give a ballpark exposure time, but a dense 40 MP sensor shows trailing at the pixel level earlier than the old rules imply. Treat any rule as a starting point and check at full zoom on the rear screen.
- Stabilization should be off on a tripod. The in-body stabilizer is built for handheld work; on a locked tripod the usual advice is to switch it off so it cannot introduce tiny corrections during a long exposure.
- The leaf shutter is quiet and low in vibration, which helps with sharpness on a tripod, but it does nothing to lengthen the useful exposure.
- Filters are awkward on a fixed lens, so the foreground and sky usually get blended by technique, not by hardware.
Capture plan: lights, darks and why they matter
Star stacking works by combining many short exposures so that random noise averages out while stars, which are consistent, accumulate. That makes the quality of every individual frame less important than the consistency across the set. Here is the order in which sessions tend to go well.
- Focus manually on a bright star using magnified live view, then confirm the focus after a test exposure. Tape the focus ring if you can, since the ring is easy to nudge when handling.
- Set a fixed exposure, aperture and ISO. Do not use any auto mode for the sky frames; changes between frames make stacking harder.
- Shoot a series of light frames, the actual sky exposures, as long as the sky rotation allows. A run of a few dozen is typical for a modest stack.
- Without moving anything, cover the lens and shoot dark frames at the same exposure, ISO and roughly the same temperature. These capture the sensor's own fixed-pattern noise and hot pixels.
- If your stacking software supports it, shoot flat frames against an even light source to correct vignetting and dust shadows.
The camera also has a long exposure noise reduction option that makes a dark frame after each exposure. For stacking, many astrophotographers prefer to turn it off and shoot their own darks, since in-camera subtraction doubles the time per frame and can interfere with the stack's own calibration. Check what your stacking software expects before deciding.
What imagic does in this chain, and what it does not
It is better to be direct about this. imagic does not do astro star stacking, and it has no layers, retouching or generative fill. It is a local desktop app for culling, batch editing and exporting, and for astro that means a supporting role. It handles the stage before and after the stack:
- Culling the light frames. Quality scoring on sharpness helps flag frames with trailing, wobble or a passing cloud, and duplicate grouping keeps a long sequence manageable. Star fields are an unusual image for a scorer built around faces and composition, so skim the flagged rejects rather than trusting them blindly.
- Batch tone work on single frames. For non-stacked shots, such as a wide scene with a foreground, a consistent one-click style across a set keeps the series coherent.
- Final export. After stacking elsewhere, a TIFF or JPEG output can be sized and delivered. imagic exports JPEG and TIFF.
The photos stay on your computer, because processing is local. RAF is on its supported raw list.
A practical pass through a long light-frame run
A night of unattended intervalometer frames can produce hundreds of files that look almost identical as thumbnails. A workable method is to view them at a size where a satellite streak, an aircraft light or a visible smear stands out, then reject whole stretches rather than single frames when something obvious happened, such as dew forming on the front element or a cloud bank rolling through. Frames just before and after a disturbance are suspect too, so trim with a margin. Keep the rejects in a folder instead of deleting them straight away, because a frame with one satellite trail can still be useful if the stacker uses a rejection algorithm that removes outlier pixels.
Dew deserves a special mention for a fixed lens. There is no hood to extend and no filter to swap, so a slowly fogging front glass shows up as a gradual loss of contrast across the sequence. Spotting where that began is easier with the frames sorted in capture order than with any scoring system.
Handing frames to a stacker: raw or TIFF?
This is the decision that surprises people. Dedicated stacking programs often prefer raw input, because they calibrate against darks and flats at the sensor-data level. If you pass them developed TIFFs, you lose that, and you can bake in a color treatment that fights the stacker's own calibration. There is a counterweight, though. Fujifilm's X-Trans sensor uses a different color filter pattern from the common Bayer layout, and support for that pattern varies between programs. Before the trip, test one short sequence through your stacker of choice and look for odd color artifacts or zippering around stars.
A useful rule is: if the stacker handles RAF cleanly, give it RAF files directly and keep imagic for culling and for the final export. If it does not, develop the light, dark and flat frames identically as linear-looking TIFFs without sharpening or noise reduction, and let the stacker do the heavy lifting. Whatever you choose, process all frames in a calibration set the same way.
Hot pixels, long exposures and noise
Long exposures on any modern sensor make hot pixels more visible, and a sensor with small pixels is no exception. Hot pixels appear as tiny colored dots in the same positions in every frame, which is precisely what dark frames are meant to remove. Without darks, a stack can turn those dots into a fixed pattern that no amount of averaging cleans up, because the dots are in the same place each time.
Noise at high ISO is a separate matter. Because an APS-C sensor collects less total light than a full-frame one at the same field of view, a deeper stack is the usual way to compensate. That is a patient route: more frames, more storage, longer processing. The single SD card slot is worth thinking about here. A long sequence of raw files is a risk on one card, so carry a spare and swap before the card fills, rather than watching it run out mid-sequence.
Foreground and sky: separate shoots, merged by hand
Because the sky needs a short exposure to keep stars sharp and the foreground needs a long one to show up, many night images combine two exposures. imagic has no layers and no HDR or panorama merge, so that blend belongs in other software. What the app can do is prepare each half evenly: keep the foreground frames in a separate folder, develop them with consistent exposure and white balance, and export with generous bit depth where TIFF is an option. The sky, once stacked, returns from the stacker as its own file for the final blend.
Moonlit foregrounds and artificial light are different problems. Light pollution tints the sky orange or gray, and white balance at the raw stage matters more than any later adjustment. Choosing a balance close to a neutral sky and then toning in your editor is easier than undoing a heavy cast.
A tidy folder structure for night work
Stacking creates more files than most workflows, so a rigid structure saves headaches.
| Folder | Contents | Notes |
|---|---|---|
| 01_lights | Sky exposures | Cull obvious failures first |
| 02_darks | Lens-cap frames | Same settings and temperature as lights |
| 03_flats | Even-light frames | Same focus and aperture |
| 04_foreground | Single exposures of the land | Developed consistently |
| 05_stacked | Output from the stacker | Keep the settings used |
| 06_final | Delivered JPEG or TIFF | Named by target and date |
Date the session folder and note the sky conditions in a text file. The details that make a later reprocessing easier, such as the moon phase or whether a front was passing, are the kind you forget within a week.
Realistic expectations for a pocket camera at night
The X100VI is not a deep-sky instrument. It can produce a pleasing wide star field, a short stack of a bright constellation with foreground, or a travel image of a dark-sky site. What it cannot do is replace a tracker-mounted setup with a longer focal length when the target is a nebula or galaxy. Treat it as the camera you will actually have with you, and plan the workflow around frames you can realistically collect in a single night. If you want to polish one finished image, the free web editor works on a single photo. More background lives in the camera hardware category.
Frequently asked questions
Can the Fujifilm X100VI be used for star stacking at all?
Yes, as a source of raw frames. Its fixed 23mm lens limits the framing to a fairly wide field, which suits constellations and landscapes with a sky rather than small deep-sky targets. The stacking itself happens in dedicated astro software, not in imagic.
Should in-body stabilization stay on for tripod astro shots?
The common advice is to switch it off when the camera is locked down, because a stabilizer can make small corrections that a stationary camera does not need. Check a test frame at full zoom if you are unsure how it behaves on your setup.
Does imagic open X100VI RAF files?
Yes, RAF is a supported format and files are read by imagic's own built-in RAW engine on your computer. Use the desktop app for culling and final export, and run the stack in a program built for that job.