UMBRA

Supported cameras.

Umbra fires multiple cameras through an eclipse on one contact-relative script. This list is kept honest. A body is only marked verified once it has actually controlled real hardware. Everything else is where I honestly think it stands, and it updates as beta testers confirm bodies. If yours is not listed, it very likely still works through the universal driver, so tell me your model and I will add it.

Verified: confirmed firing on real hardware Expected: should work, not yet tested Fixing: known issue, in progress Not expected: no driver support

Built for multiple bodies that recover on their own

Umbra pins each camera's name to it by serial number, so a body keeps its name, and its place in your script, across a disconnect and re-detect. If a body drops mid-run (a knocked cable, or a power-cycle during totality) Umbra reconnects it automatically and resumes firing, on LUMIX and on every universal-driver brand.

Multi-camera USB tip: plug each body straight into the Mac or a powered USB hub. A docking station or an unpowered hub shared with other devices splits one USB link across everything on it, and cameras that all connect can then fail to fire, or only one works at a time (a real tester saw exactly this until they removed a dock). One camera per port, powered hubs only.

Panasonic LUMIX

Driven natively over a reverse-engineered PTP path, the same control layer behind my NASA launch-pad rigs and the bodies I run myself. Listed here are interchangeable-lens LUMIX bodies from roughly 2015 on; most older USB bodies should work too. One setup note: keep the drive dial on single. On a burst or continuous setting, a long (bulb) exposure presses and holds the shutter, so the body fires a burst instead of one frame.

Camera	Driver	Status	Notes
DC-G9 II	Native PTP	Verified	Multiple bodies fire in parallel; proven through a full C1 to C4 run.
G9	Native PTP	Verified	Fires reliably; same control path as the G9 II.
GH7	Native PTP	Expected	Same control path as the G9 II.
GH6	Native PTP	Expected	Same control path as the G9 II.
GH5 II	Native PTP	Expected	Same control path as the G9 II.
GH5S	Native PTP	Expected	Same control path as the G9 II.
GH5	Native PTP	Expected	Same control path as the G9 II.
G95 / G90	Native PTP	Expected	Micro Four Thirds over USB.
G100 / G110	Native PTP	Expected	Micro Four Thirds over USB.
GX9	Native PTP	Expected	Micro Four Thirds over USB.
GX85	Native PTP	Expected	Micro Four Thirds over USB.
GX8	Native PTP	Expected	Micro Four Thirds over USB.
S1R II	Native PTP	Verified	Full-frame S line; fires reliably.
S1R	Native PTP	Expected	Full-frame S line.
S1	Native PTP	Expected	Full-frame S line.
S1H	Native PTP	Expected	Full-frame S line.
S5 II	Native PTP	Expected	Full-frame S line.
S5 IIX	Native PTP	Expected	Full-frame S line.
S5	Native PTP	Expected	Full-frame S line.
S9	Native PTP	Expected	Full-frame S line.

Sony

Newer bodies use the fast native SDK; the A7 III, A7R III and older use the universal driver. Umbra chooses automatically per body, with nothing to configure. Two setup notes that matter more on Sony than anywhere else. First, set the camera's USB connection mode to Remote Shooting (on older bodies this is called PC Remote; it is not MTP, Mass Storage, or USB Streaming). The native SDK only claims a body in that mode; in the others Umbra falls back to the slower universal driver and the body shows up with a generic name like "Alpha-A7III (Control)". If you see that, switch the mode and Detect again. Second, keep the drive dial on Single. Sony has no single-frame command over USB, so on a continuous or burst dial a single fire sprays a whole burst (not one frame) and the body can wedge writing to the card mid-totality. Umbra reads the dial at detect and flags both of these before you arm, but Remote Shooting + Single is the combination you want. Also worth doing before the trip: keep the camera's System Software (firmware) current. Sony's remote-control protocol assumes the latest firmware, and Umbra shows each body's version at detect and records it in the run log. And run Manual Focus: on autofocus a Sony can refuse the remote shutter until focus locks (a half-press with no photo). Umbra warns at detect when a body is in AF.

Camera	Driver	Status	Notes
A1	Native SDK	Verified	Controls cleanly on the native SDK, the recommended totality path.
A7 V	Native SDK	Verified	Fires reliably with fast exposure changes.
A7S III	Native SDK	Verified	Fires reliably with no dropped shots in testing.
A7 III	Universal	Verified	Not in Sony's SDK, so it runs on the universal driver. Widen the totality bracket (about 1.3s per frame).
A7R III	Universal	Expected	Universal driver (no SDK). A stalled frame is dropped so the run keeps going; widen the totality bracket (about 1.3s per frame).
A1 II	Native SDK	Verified	Confirmed on real hardware: the native driver engages automatically and held a clean shot-to-shot cadence down to 0.1s in testing.
A9 III	Native SDK	Expected	On Sony's SDK supported list.
A9 II	Native SDK	Expected	On Sony's SDK supported list.
A7 IV	Native SDK	Expected	On Sony's SDK supported list.
A7R V	Native SDK	Expected	On Sony's SDK supported list.
A7R IV	Native SDK	Expected	On Sony's SDK supported list.
A7C II	Native SDK	Expected	On Sony's SDK supported list.
A7CR	Native SDK	Expected	On Sony's SDK supported list.
A7C	Native SDK	Expected	On Sony's SDK supported list.
A6700	Native SDK	Expected	On Sony's SDK supported list.
ZV-E1	Native SDK	Expected	On Sony's SDK supported list.
FX3	Native SDK	Expected	On Sony's SDK supported list.
FX30	Native SDK	Expected	On Sony's SDK supported list.
A9 (original)	Universal	Expected	Universal driver; widen totality spacing.
A7R II	Universal	Expected	Universal driver; widen totality spacing.
A7 II	Universal	Expected	Universal driver; widen totality spacing.
A7S II	Universal	Expected	Universal driver; widen totality spacing.
A7S	Universal	Expected	Universal driver; widen totality spacing.
A6600	Universal	Expected	Universal driver; widen totality spacing.
A6500	Universal	Expected	Universal driver; widen totality spacing.
A6400	Universal	Expected	Universal driver; widen totality spacing.
A6300	Universal	Expected	Universal driver; widen totality spacing.
A6100	Universal	Expected	Universal driver; widen totality spacing.
A6000	Universal	Expected	Universal driver; widen totality spacing.

Sony: native SDK vs. universal driver

Umbra drives Sony two ways and picks the right one automatically, with nothing to toggle. Which one a body uses comes down to its generation:

Native Sony SDK (fast)

Sony's Camera Remote SDK, for the A7 IV, A1 and A7S III generation and newer. It sustains a rapid totality bracket, and exposure changes land quickly in a single step. This is the path you want for a dense diamond-ring or Baily's-beads burst.

Universal driver (broad)

A bundled PTP layer for the bodies a native SDK does not cover (Sony A7 III, A7R III and older, plus Nikon and Fujifilm). It works, but it is slower, roughly 1 to 3 seconds per frame, and exposure changes step in 1/3 or 1/2 stops with a brief wait. A very dense totality bracket can outrun it and drop frames, so on these bodies widen the totality spacing.

Canon

EOS bodies now use the native Canon SDK (EDSDK), Canon's official tethering interface, new in this build. It forces save-to-card and fires without autofocus, the right behavior for an eclipse rig. One connection tip: if a Canon falls back to the universal driver, it usually means macOS grabbed the body before Umbra did. The fix is timing, launch Umbra first, then plug in the Canon and click Detect (or, with Umbra open, unplug and replug it and Detect again). The camera card shows a NATIVE or UNIVERSAL badge so you can confirm which driver is live before you arm. Canon testers are confirming now, so these are expected rather than verified. I will mark them verified as runs come in.

Camera	Driver	Status	Notes
EOS R5	Native SDK	Expected	Native Canon SDK (EDSDK), new this build; in active testing with beta users.
EOS R5 II	Native SDK	Expected	Native Canon SDK (EDSDK), new this build; in active testing with beta users.
EOS R6	Native SDK	Expected	Native Canon SDK (EDSDK), new this build; in active testing with beta users.
EOS R6 II	Native SDK	Expected	Native Canon SDK (EDSDK), new this build; in active testing with beta users.
EOS R3	Native SDK	Expected	Native Canon SDK (EDSDK), new this build; in active testing with beta users.
EOS R	Native SDK	Expected	Native Canon SDK (EDSDK); R-series mirrorless over USB.
EOS RP	Native SDK	Expected	Native Canon SDK (EDSDK); R-series mirrorless over USB.
EOS R7	Native SDK	Expected	Native Canon SDK (EDSDK); R-series mirrorless over USB.
EOS R8	Native SDK	Expected	Native Canon SDK (EDSDK); R-series mirrorless over USB.
EOS R10	Native SDK	Expected	Native Canon SDK (EDSDK); R-series mirrorless over USB.
EOS R50	Native SDK	Expected	Native Canon SDK (EDSDK); R-series mirrorless over USB.
EOS R100	Native SDK	Expected	Native Canon SDK (EDSDK); R-series mirrorless over USB.
5D Mark IV	Universal	Expected	DSLR over USB.
5D Mark III	Universal	Expected	DSLR over USB.
6D Mark II	Universal	Expected	DSLR over USB.
6D	Universal	Expected	DSLR over USB.
7D Mark II	Universal	Expected	DSLR over USB.
90D	Universal	Expected	Broadly supported by the universal driver.
80D	Universal	Expected	Broadly supported by the universal driver.
77D	Universal	Expected	Broadly supported by the universal driver.
Rebel SL3	Universal	Expected	Broadly supported by the universal driver.
Rebel T8i	Universal	Expected	Broadly supported by the universal driver.
Rebel T7	Universal	Expected	Broadly supported by the universal driver.
1D X Mark III	Universal	Expected	Broadly supported by the universal driver.
1D X Mark II	Universal	Expected	Broadly supported by the universal driver.

Nikon

Z mirrorless and DSLRs over the universal driver. Confirmed firing on the Z6 II, Z8, Z7 II and Z5 II; the rest are expected, and I will mark them verified as runs come in. Nikon had a big reliability pass in July 2026, built against a rented Z6 II over three days: the app now takes PC control of the body the way Nikon's own tethering software does (bodies refuse the shutter until you do, which was behind most of the old "it will not fire" reports), aperture changes no longer force a reconnect mid-run, long exposures record at the seconds you asked for, and a body recovers on its own after a battery pull or a replug. The bench result was a full run from first contact to fourth, 1,249 logged frames with zero drops and every exposure verified correct on the card. Three setup notes: set the Standby timer to No limit (custom menu c3) while tethered, give each body its own USB port rather than a shared unpowered hub, and format your card in the Nikon itself, since a card formatted in another camera makes the body accept the shutter and write nothing.

Camera	Driver	Status	Notes
D850	Universal	Expected	A tester's D850 answered a full profile read in August 2026: complete shutter ladder to 1/8000 (fractions, the form Umbra sends), ISO 32–51200, and the mounted lens's aperture list. That profile also uncovered a European-locale quirk in how cameras report numbers, fixed for all bodies. First full run pending.
Z9	Universal	Expected	Z-series mirrorless over USB.
Z8	Universal	Verified	Confirmed on real hardware through a full C1 to C4 run. Stacked-sensor flagship; fully electronic shutter, silent and vibration-free. Give totality brackets about 2s per frame on the universal driver.
Z7 II	Universal	Verified	Confirmed firing on real hardware by a beta tester. Confirmed by a beta tester. Covered by the July 2026 Nikon reliability work (PC control, aperture, long exposures, auto-recovery); give totality brackets about 2s per frame.
Z7	Universal	Expected	Z-series mirrorless over USB.
Z6 III	Universal	Expected	Z-series mirrorless over USB.
Z6 II	Universal	Verified	Tested hard on a rented body over three days, and the reference for the July 2026 Nikon reliability work. A full C1 to C4 run logged 1,249 frames with zero drops, every exposure confirmed correct on the card.
Z6	Universal	Expected	Z-series mirrorless over USB.
Z5 II	Universal	Verified	Fires on real hardware, including astro-modified bodies. A newer or modified body can report as a generic PTP device rather than by model name; if the name does not stick after a re-detect, name it once and it holds.
Z5	Universal	Expected	Z-series mirrorless over USB.
Zf	Universal	Expected	Retro full-frame; silent e-shutter plus mechanical-shutter BULB. Priority body for verification.
Zfc	Universal	Expected	APS-C compact Z body.
Z50	Universal	Expected	APS-C compact Z body.
Z30	Universal	Expected	APS-C compact Z body.
D780	Universal	Expected	DSLR over USB.
D810	Universal	Expected	DSLR over USB.
D750	Universal	Expected	DSLR over USB.
D500	Universal	Expected	DSLR over USB.
D7500	Universal	Expected	DSLR over USB.
D5600	Universal	Expected	DSLR over USB.
D6	Universal	Expected	DSLR over USB.

Fujifilm

X and GFX bodies over the universal driver. Expected, not yet tested.

Camera	Driver	Status	Notes
X-T5	Universal	Expected	X-series over USB.
X-T4	Universal	Expected	X-series over USB.
X-T3	Universal	Expected	X-series over USB.
X-H2	Universal	Expected	X-series over USB.
X-H2S	Universal	Expected	X-series over USB.
X-H1	Universal	Expected	X-series over USB.
X-Pro3	Universal	Expected	X-series over USB.
X-S20	Universal	Expected	X-series over USB.
X-S10	Universal	Expected	X-series over USB.
X-E4	Universal	Expected	X-series over USB.
X-E3	None	Not expected	No USB tether-shooting mode in firmware, so no shutter control over USB. (Wireless control exists, but Umbra does not use Wi-Fi.)
X-T30 II	Universal	Expected	X-series over USB.
GFX 100 II	Universal	Expected	Medium format over USB.
GFX 100S	Universal	Expected	Medium format over USB.
GFX 50S II	Universal	Expected	Medium format over USB.

OM System / Olympus

OM-D, OM and PEN bodies over the universal driver. Olympus is the brand where tethered shutter control varies most from model to model. The E-M1 Mark III is now confirmed firing on real hardware, the first Olympus body verified; the rest are expected pending confirmation, and I will mark them verified as testers check in.

Camera	Driver	Status	Notes
OM-1 Mark II	Universal	Expected	Current OM System flagship; tethered capture over USB, pending confirmation.
OM-1	Universal	Expected	With a tester onboarding now. Priority body for verification.
OM-5	Universal	Expected	Tethered capture over USB, pending confirmation.
OM-D E-M1X	Universal	Expected	Tethered capture over USB, pending confirmation.
OM-D E-M1 Mark III	Universal	Verified	First Olympus body confirmed on real hardware. The first frame can take a few seconds, then it holds cadence.
OM-D E-M1 Mark II	Universal	Expected	Tethered capture over USB, pending confirmation.
OM-D E-M5 Mark III	Universal	Expected	Tethered capture over USB, pending confirmation.
OM-D E-M10 Mark IV	Universal	Expected	Tethered capture over USB, pending confirmation.
PEN-F	Universal	Expected	Tethered capture over USB, pending confirmation.

Not currently supported

These bodies do not expose a still-capture control path Umbra can drive. Listed here so the answer is clear rather than missing.

Camera	Driver	Status	Notes
RED Komodo X	None	Not expected	Cinema camera controlled over RED's own protocol (RCP), not PTP. No eclipse-stills control path.
Leica M11-P	None	Not expected	M-mount rangefinder; no tethered shutter control over USB. Leica SL and Q mirrorless are a more realistic future target.

Do not see your body, or want to confirm it? The beta is free and open, and I add camera coverage as people report in. Download the free beta or email [email protected] with your exact model and I will get it on the list.