Image and video decision
Capture One
Do not rebuild — a useful subset is technically possible but Capture One's proprietary color/RAW tuning, tethering/studio workflows, polished ecosystem, and brand value make the paid product hard to match; keep paying unless you only need a very small editor.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Import RAW photos, apply global adjustments and local masks, manage assets in a catalog/session, export finalized images.
What it still won’t have
- Capture One's proprietary color profiles and RAW conversion tuning
- Industry-leading tethering and on-set Live workflows
- Mobile apps, cloud collaboration, and integrated online sharing
- Continuous product updates and priority vendor support
- Polished studio-specific automation (Studio plan features)
What remains hard
- Brand trust
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal desktop RAW photo editor using Python (rawpy + Pillow/OpenImageIO) or Electron with a WASM/raw processor, and a simple SQLite-backed catalog. In scope: import RAW files, generate preview cache, nondestructive global adjustments (exposure, white balance, curves), local mask brush with alpha compositing, batch export to JPEG/TIFF with presets, basic search/filtering, and a simple UI (desktop). Out of scope: mobile apps, cloud sync/collaboration, hardware tethering, proprietary color profile matching. Include error handling, unit/integration tests for import/export and adjustment pipeline, and a README with local deployment steps.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productCapture One product page
- official pricingCapture One Pro pricing
- official productProduct & Food features
- open sourceBitpainter75/FerrumPix
- open sourcencruces/RethinkRAW
Integrity checks
What held up, and what did not.
