Which Product Photos Should Capture One Import After I Reconnect a Tethered Camera?

Establish the disconnected capture set

First record the camera model, Capture One version, connection method and ReTether setting. The official guide describes USB support for Canon and Nikon cameras. Confirm your actual model and version; that family-level statement does not establish support for every camera.

In the documented workflow, a memory card remains in the camera when the USB cable is disconnected. New photographs are recorded to that card, and reconnecting allows their retrieval.

Identify the first and last photographs made during that interval. Older card images, previous-session files and photographs already transferred before disconnection are different sets. A card containing 200 files does not mean this particular reconnection should retrieve all 200.

Treat a counter as a label, not a completeness check

Capture One applies Next Capture Naming and Next Capture Adjustments to the retrieved images. Record the active naming and adjustment configuration before moving to another product.

The documentation also says continued tethered captures in the buffer can take priority over card imports, potentially shifting a capture counter. Consequently, arrival order and consecutive destination names are insufficient evidence of capture order or completeness.

Create a small reconciliation list using the actual disconnected source files and their visible product views. Add original identifiers and capture times where available, alongside the destination filenames. A timestamp or similar-looking thumbnail alone is not a reliable match when several nearly identical frames exist.

If a view cannot be matched, keep it unresolved. Preserve the card and session, check transfer status and inspect the source file before attempting a separate controlled import. Avoid repeatedly reconnecting and renaming files just to make the counter look tidy.

Hypothetical six-frame interruption

Hypothetical planning example—not a camera or Capture One test: a merchant disconnects a supported setup to photograph a tall carton away from the tethered table. The planned disconnected set contains six photographs: two front, two side and two seal-detail views.

After reconnection, the merchant takes two additional tethered photographs. Eight newly visible images would not by itself establish that all six disconnected frames arrived: the eight could include other files or duplicated views.

Instead, match each of the six original disconnected files to its destination and confirm its actual content. Record the two new tethered frames separately. If only five disconnected originals have confirmed matches, leave one unresolved regardless of whether the destination names form a neat sequence.

No actual import count, transfer order or successful recovery is asserted here. The worksheet records an expected set and the evidence still required to confirm it.

Keep version changes separate from today's recovery

Check the documentation for the installed release and connection method. Do not assume a newer or beta workflow establishes the behavior of an older stable setup.

Complete today's reconciliation using the capabilities actually present. Preserve the original session and card until every required view has an identified, usable file and its applied adjustments have been checked.

If the task is importing an arbitrary older card archive, use an appropriate ordinary import workflow instead. That is a different decision from recovering the photographs belonging to one documented tethering interruption.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Capture One Support — ReTether: Documents the USB disconnection workflow, supported camera families, naming and adjustment application, capture-counter caveat and separately scoped beta developments. It does not verify this guide's hypothetical file set.