Improve Capture One

Request a new feature, or support for a camera/lens that you would like to use in Capture One.

Add a new idea Subscribe
Status Awaiting review
Workspace Feature requests
Categories Capture One Pro
Created by FirstName LastName
Created on Dec 7, 2025

RELATED IDEAS

Make “Add Existing Folder (no copy)” explicit and predictable

Idea description

Capture One supports referencing existing folders without copying (Add), but this workflow is not treated as a first-class UX path.

Core problem

  • Whether Add or Copy is used depends on how a folder is introduced (import dialog, drag-and-drop, session context).

  • In some cases, Add happens silently, with no confirmation of what action was taken.

  • The same user intent (“reference this folder, don’t move it”) leads to different or missing UI feedback.

This creates uncertainty and mistrust, especially for file-first users migrating from catalog-based systems where hidden duplication is a real concern.

Suggestion

  • Make “Add existing folder (no copy)” an explicit, consistent choice wherever folders are added.

  • Use clear confirmation or status messaging when Add is applied implicitly.

Capture One technically behaves correctly — it simply doesn’t explain itself, and that undermines confidence in an otherwise file-respectful workflow.

Current workaround

To safely use an “Add existing folders (no copy)” workflow, users must avoid the standard import path and instead rely on undocumented behaviors:

  • Drag existing folders from Finder into Capture One and rely on implicit Add behavior

  • Manually verify that no files were copied into the Session folders

  • Avoid “Import to Session Folder,” even when the intent is only to reference files

This workaround works, but requires prior knowledge and manual verification, which should not be necessary for a valid, non-destructive workflow.
  • Post comment
  • Admin
    Capture One Product Manager
    Dec 8, 2025

    Hi there, thanks for the suggestion.

    I'm not sure I fully understand the request here, could you help clarify:

    • are you working with catalogs or sessions?

    • can you tell us what you are trying to do with files? pinpoint the exact workflows in which feedback is missing?

    (As a side note, I would suggest against using ChatGPT or other large language models for getting help with Capture One, they are unfortunately not as good as they make it look)

    Reply