Nikon Remote SDK

How the app talks to Nikon cameras

The app uses Nikon Remote SDKs to connect to Nikon cameras, change camera settings, start live view, and capture images.

There are two Remote SDK choices:

  • Legacy Remote SDK: the older Nikon camera-control SDK family.
  • Unified Z SDK v2: Nikon's newer Remote SDK path for Z-series mirrorless bodies.

Most users do not need to think about the SDK unless they are changing the Body setting, testing a newer Z body, or troubleshooting a camera connection.

Which one should I use?

Use the Legacy Remote SDK when:

  • You are using a DSLR.
  • Your Z body already works well in legacy mode and you need the broadest proven feature coverage.
  • You are troubleshooting and want to compare behavior against the older path.

Use Unified Z SDK v2 when:

  • You are using a supported Nikon Z-series body and want Nikon's newer Z SDK path.
  • Your Z body is newer than the legacy SDK support in the app.
  • Support asks you to test the v2 path and send logs.

The v2 SDK is for Z-series bodies. It is not the DSLR path.

Why are there two Remote SDKs?

For many years Nikon shipped separate Remote SDK modules for individual bodies or small body groups. That is the legacy path. It is mature, well understood, and remains the right path for DSLR bodies.

Nikon now also ships a newer unified Z-series Remote SDK. Instead of one body-specific module per camera, it uses a common Z SDK payload and Nikon's current Z-series support model. That makes it the more likely long-term path for newer Z bodies and firmware changes.

Tradeoffs

Legacy mode is the most proven path for older supported bodies and DSLRs. If a camera works well there, it can be the simpler choice.

Unified Z SDK v2 is newer. It supports the current Z-series SDK direction, but some behavior is different because Nikon changed how the SDK reports capture, live view, camera state, and saved files. The app keeps the normal workflow the same where possible, but v2 may still expose different supported settings on a specific body.

Runtime camera capabilities always win. If the connected body does not report that a setting is available, the app cannot safely force it on.

Still-image capture in Unified Z SDK v2

When v2 saves images to the computer, Nikon first writes the original files to a staging folder. The app then audits the capture and copies the originals through the normal Path rules to your final destination.

This keeps the familiar Path behavior, including filename tokens, counters, group folders, and duplicate-safe final names. It also preserves the Nikon-produced staged originals for recovery. The app does not automatically delete those staged originals.

Card-only capture stays card-only. In that mode the app waits for the camera-side capture to finish, but it does not copy files to the PC Path.

Capture safety

When the app is expected to save a capture to the computer, that save is treated as a capture transaction. The transaction is not considered successful just because the camera took a picture. The app also has to prove that the final file was saved correctly at the Path destination.

For the user-facing explanation of Legacy proof, v2 staging audit, Guidance alerts, optional disconnect, workflow cancellation, and debug failure tests, see Capture Transactions.

Staged originals

The staging folder is configured in Path settings. Leave it on a local drive with enough free space for the largest session you expect.

Because staged originals are retained, clean them up manually after you have confirmed the final files and no longer need the recovery copy.

Logs

When asking for help, include the log. The log records whether the session used legacy mode or Unified Z SDK v2 mode, the connected body, the reported capabilities, and capture audit details.