Why Can Capture One Control My Camera but Not Import Photos Already on Its Card?

Identify which USB operation is working

Separate two jobs: controlling the connected camera for new captures, and importing photographs previously stored on its card. They can use the same physical cable without exposing the same file-selection workflow.

Capture One's support article explains that its USB camera connection uses PTP for tethered control. The card is not presented as ordinary storage for the application's normal import operation. This describes Capture One's documented workflow, not a claim that the PTP protocol can never transfer image files.

If camera controls respond but an old card archive is absent from the import browser, first identify that scope mismatch. Do not conclude that the saved images were erased, corrupted or already imported merely because this browser does not list them.

Expose the existing files through the intended import route

The vendor's recommended route is to use a card reader, copy the photographs to a local folder and import that folder into Capture One. Stop capture activity and follow the camera and storage device's normal handling instructions before changing connections.

Keep the source card intact while checking the copy. Confirm the actual source folder, file identities and required product views; a camera connection badge supplies none of that information.

Some cameras offer a separate card-reader USB mode. Use it only where the exact model's documentation provides it. Remote-control mode and card-reader mode represent different tasks; do not invent a universal menu path or assume both operate simultaneously.

If the folder is accessible but particular files still cannot be imported, that is a later problem. Record the exact file type and application version, and investigate their support separately. Moving to a reader does not guarantee every format is readable or every original is intact.

Hypothetical twelve-photo archive

Hypothetical illustration—not an executed camera or import test: a merchant has twelve identifiable product photographs from a previous shoot on a memory card. Capture One can control the camera and receive a new tethered photograph, but the twelve older files do not appear in its normal import browser.

The new photograph establishes only the operation that succeeded. It is not evidence that the twelve archive files were transferred, and its destination does not establish whether a copy was also saved on the card.

The merchant's proposed next step is to inspect the old archive through the documented reader route, make a local copy, and match each required source file to that copy. Import from the identified local folder, then verify the intended images are accessible at full detail.

If eleven of twelve expected originals are confirmed, leave the twelfth unresolved and inspect the card's actual contents. Do not mark twelve complete because another newly captured image brings the application thumbnail count to twelve.

Keep archive import separate from ReTether recovery

ReTether addresses new photographs made during a temporary tethering disconnection. It is a different scope from browsing an arbitrary pre-existing card archive. Check that feature's supported setup before using it for an interruption; do not trigger reconnect cycles to retrieve unrelated older material.

For this archive problem, the useful completion record names the source card folder, copied local folder and confirmed required files. Preserve uncertain entries as uncertain until they can be identified and opened. A successful import of one file does not establish completeness of the set.

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 — Can I import from a camera over USB?: Explains Capture One's PTP tethered-control scope, the recommended reader-to-local-folder import route, conditional camera card-reader modes and the different scope of ReTether.