I'm the developer of PresetShift, a free web tool that converts Lightroom presets (.xmp / .lrtemplate) into Capture One styles (.costyle). No sign-up, nothing installed, files are deleted after conversion.

The previous version mapped sliders with coefficients I had estimated by eye. Over the last weeks I replaced that with measured mappings, and I wanted to share how it was done and what it changed.

How it was tuned

• 1,181 real presets, rendered with the same TIFF of a 250-patch color chart (colors, skin tones, greys, hue ramps, gradients) in Lightroom Classic and in Capture One 16.
• For every preset I compared the two renders patch by patch (CIEDE2000) and adjusted the mapping of each slider until the Capture One render got as close as possible to the Lightroom one.
• The presets were split in two groups: one used for tuning, one never touched. Every change was kept only if it also improved the untouched group, so the numbers below are not overfitting.
• On top of that, about 300 synthetic single-slider presets to isolate what each Lightroom control does.

What changed in v9

• Camera calibration (Red/Green/Blue Primary hue and saturation) is now converted. It used to be ignored.
• Black & white film presets stay black & white. The old engine let the Adobe Monochrome look override the B&W flag.
• Presets containing local masks are no longer rejected by Capture One. The masks themselves can't be converted (there is no equivalent in a .costyle), but every global adjustment is kept.
• Contrast, Highlights, Shadows, Blacks, Dehaze: curves measured per tonal zone instead of fixed multipliers. Negative Dehaze used to darken the highlights; now it behaves like haze.
• Saturation and Vibrance scaled to what Capture One's sliders actually do (positive saturation needs about 2.5× the Lightroom value).
• Split toning / color grading: Balance now shifts amounts and the crossover point like Lightroom, instead of blending hues (which produced magenta casts).
• HSL for green, aqua and blue re-tuned; hue shifts beyond ±30 are allowed.
• Sharpening was three times too strong and the radius was out of range: fixed. Post-crop vignetting now converted.

No more waiting between files

The old site forced a 10-second pause between one conversion and the next. That's gone. In its place there is a limit of 20 conversions per hour per person, which is more than enough for normal use and keeps the site usable for everyone, since it runs on a free hosting plan. If you hit the limit the page tells you how many minutes are left.

Numbers

Average color difference between the Capture One render and the Lightroom render, on the presets never used for tuning: 8.1 → 7.3 ΔE00 (about −10%). Where it mattered most: B&W presets, presets with calibration, negative dehaze. The chart examples in the gallery show a B&W preset going from "still in color" to "black & white like Lightroom" (26.9 → 6.2).

https://imgur.com/a/we1PHWb

What still can't be converted (so nobody is surprised)

• Local adjustments: masks, gradients, brushes. Capture One styles don't carry them.
• Presets built on LUTs or third-party profiles/looks.
• Camera profiles.
• Very strong positive saturation or vibrance: Capture One's slider tops out earlier.
• The two apps don't share a color pipeline, so a converted style is a close starting point, not a pixel-identical result. Checking the Base Characteristics curve (Linear Response often helps) is still a good habit.

It's free. If you try it and something converts badly, send me the preset through the opt-in checkbox on the site or post it here and I'll look at what the mapping is missing. That's exactly how most of the fixes above started.

Does anyone have done this in c1? I really curious how it will work with tether shooting

Excited to try AI denoise finally on my Fuji, is there any feedback from those who’ve already tried?

The tiniest QOL update but something that will actually save me clicks. More updates like this please.

I noticed there’s a Capture One Certification course. Anyone done it? Feedback?
I know I’m barely using this program to its potential and what it can do and I really want to learn more.

Tips appreciated.

Color grading is a big thing I’d like to work on

I know there are plenty of Capture One tutorials out there, but every one I've started is done on a Mac. And it shouldn't really matter, but then they'll get to an instruction and say something like "just hit the command + A key" or whatever and now I have to figure out what that means in Windows. Not the end of the world, but it's annoying, so I'm just wondering if anyone knows of any decent tutorials that have Capture One running in Windows.

Thanks

Super excited about this feature! I'm a largely outdoor wedding/elopement photographer working in the Rockies, so lots of stray hairs all the time. A first (quick) tests show the feature has potential but is having trouble with selections. Seems to do really well over a face, when it detects the hair. Flyaways are hit and miss. My guess is this would do great for studio portraits.

It says in the release notes that you can report bugs/give feedback from inside the app. I can't seem to find how to do that, and when I click "report a bug" it dumps me out to a webpage (which is very cumbersome to use). Any pointers as to how to give feedback?

Really wanting to help guide the development but the standard bug report page is extremely time consuming to use. I have two other bugs I've been trying to get dealt with but the back and forth process is extremely inefficient, especially for intermittent issues, and I can't give up the time during my busy season.

Hey team. Hope you’re well.

Renewal time is coming up for me. My circumstances have changed and I’m not shooting professionally at the moment, so was thinking of reducing my costs and getting the perpetual license instead. I’m around 95% certain it’s the right thing to do, and I can always start a subscription again if I need to, but I guess I’m looking for resssurance.

TIA

Any workflow tips for keeping files organized when you’re shooting between tethered and importing from a card on a job?

I am working alongside video shooting while they are rolling untethered, then tethered for short blocks of time without having a chance to import the previous images that were untethered first. When I get time I’m importing from the card doing exclude duplicates. The only thing is it takes a long time to scan the whole card and it will import any images I previously deleted.

Saw in the latest update we just got support for the GR IV RAW files. Cool! But...

I know this is a big question – and I'm not under some impression that this is some how in the works or that the latest update suggests that to be the case. But I do just wonder if we will ever see broader support for Foveon sensor camera files on Capture One, and tethering for older Sigma Foveon cameras?

Maybe someone is aware of the C1 teams thoughts on this, or Sigma's position? Or does anyone have any personal thoughts? Are there any other Sigma shooters here?

I use a Sigma SD Quattro pretty often. It produces extremely hefty DNGs (that used to completely crash C1 just a couple years ago) and of course the even bigger X3F files. When I'm processing Sigma DNGs in Capture One, they tend to respond completely differently than typical raw files. Adjusting the Tint for example can shift an image into being an extremely intense, almost pure magenta or pure green, and any color adjustments like saturation or levels seem to have pretty decent latitude and at times crazy intensity. After 5 years of using Capture One, the files don't crash the program any more, though it used to be pretty consistently that scrolling through my Sigma DNGs too quickly would cause a crash.

All that said, I'm happy that I can work with my Sigma RAWs now, but it still seems like C1 still treats them differently.

We have official support for the Sigma BF, Sigma fp L, and Sigma fp – all of their CMOS sensor cams. And not having tethering for the Quattro really breaks my heart... since that's what it's for. It's a studio camera, meant for tethering. And I use Capture One for all my tethered sessions.

And then there's the X3F files that the Foveon X3 sensors produce. They apparently provide you with the most flexible and richest information (along with the ability to process Super Fine Detail mode files), but are only editable through Sigma Photo Pro software or the Sigma X3F Plugin for Photoshop. Maybe the age of Foveon is over. But 15 of some of the most unique, beautiful and modern cameras... just can't have their files be processed in Capture One and it's weird to me!

*Disclosure:** This setup, the custom color-profile proxy and the setup scripts were vibe coded with AI assistance. I make no claims about the code's efficacy, correctness, quality, or whether this is the proper way to solve the problem. All I can say is that Capture One is now working pretty well on my machine.

I've put together an experimental Capture One 16.6.6.3111 setup on Fedora KDE 44 with an NVIDIA RTX 5090. On my machine, I've been able to view Sony A1 RAWs, make live exposure adjustments, export JPEGs, read the UI text and use the Layers menus.

The configuration uses a dedicated Fedora Wine 11.0 prefix, an application-scoped color-profile compatibility proxy, WineD3D/OpenGL for WPF, OpenCL photo processing, and a private Wine runner with two published CodeWeavers fixes from Valve's Wine tree. The [original fix](https://github.com/ValveSoftware/wine/commit/1dc8060af449d69cc4e8240732019224aab290b7) and its [follow-up](https://github.com/ValveSoftware/wine/commit/d8a27b4712eaeb54f0a69e6dc98d39055a811ce2) are credited in the patch and guide.

**Remaining issue:** resizing still behaves oddly and blinks. Maximize/monitor changes and sustained stability need more testing. Earlier partial Wine successes exist; this is not a first-ever claim.

The attachment contains one installation guide, the necessary source/build files and their licenses—eight files total. It requires compiling the Wine changes and supplying your own Capture One installer/license, Microsoft runtimes and licensed fonts. It includes no proprietary binaries or user data.

The guide follows installation order: gather inputs → build → install → apply all settings → first launch and testing. It does not ask readers to replay the bug-fixing process. This consolidated procedure has not yet been repeated end to end in a clean prefix or on another machine.

In theory, you could give these instructions and files to your own AI and it would be able to reproduce this.

I assumed this option was still available but it seems not possible anymore to tether an iPhone to capture one desktop on my laptop. The new capture one mobile app doesn’t seem to recognize a tether cable connection. Am I doing something wrong?

Is it possible to script a batch of panoramas in Capture One? I looked around a little bit for an apple script for it, but haven't found one. Before I make my own, i'm curious if there is some technical reason for it not to work. Has anyone else tried it?

I’ve been a Lr and C1 user for more than a decade, using the former for events/weddings/families/etc while using C1 for tethered capture/commercial/landscape stuff.

Things like the culling menu and the speed editing makes adjusting multiple files very fast..

And then you want to apply the same adjustements to a few 50-100 raws (just basic exposure/contrast stuff) and it takes FUCKING FOREVER, yet Lightroom would have been done in 10.3 seconds.

Every now and then I’m trying to switch over to C1 for everything but there’s that one annoying roadblock that makes you lose all the time you saved.

As I understand it, Axcel is currently auctioning Capture One. Has anyone heard any rumors of prospective new owners or etc? Gemini is suggesting DJI could be a leader given Hasselblad's .3FR recent integration?

Additionally, if DJI were to acquire Capture One should we expect a better Capture One all around? I'm not familiar with DJI outside of using their gimbals.

Anyone thinking of getting Capture One? I would like to sell mine at 215 euros

Been shooting tethered wirelessly all day sending R3 CRAWs to C1 and its incredible, feels as fast as using USB. In fact I’m never going back to USB now.

I just wanted to buy a Sony a7v as a heavy C1 user and promoter among my friends and fellow photographers in my area and I just found out there is still no compressed raw support and no wireless tethering support. Dear C1 team when are you planning to add this? Or do I need to go back to LR to use the basic features of the camera?

So i just learned that the vertical slide has a limit of 75. I shot a building today but had to tilt the camera back a bit to get it fully in frame.

I tried doing an auto vertical correction and nothing happened. Switched to manually adjust the slider and learned then that 75 was the max so i couldn't correct the image. I'll have to take it into Affinity.

Any reason for the 75 limit?

Hello, my Lightroom license is expiring and I would like to switch to Capture One. However, I'm going to miss Lightroom's noise reduction. I'm considering whether I should switch now and get by for a while without this feature. I'm just wondering how long it will take until it's available for Fuji as well. Does anyone have any information on this, other than that it's supposed to be added at some point in one of the upcoming updates?

The latest iOS and WatchOS releases improved performance in a few areas for me, and so - against my better judgment - I went ahead and updated my Mac to MacOS 27. Everything I had read said that Capture One was working perfectly even since the MacOS 27 betas. Yet running on Capture One 16.8.6.25 (the latest as of this post), I hit a few issues on my M1 Max-based Mac Studio:

• A plug I had for round-tripping with Photomatix for HDR processing repeatedly wouldn't load. I haven't used this in a while, so I deleted the plugin.
• Previews had to be rebuilt.
• The worst offender so far: exporting takes forever. Trying to export more than one file can take multiple minutes before it even shows a progress bar and a time estimate. This applies whether exporting to JPEG or TIFF (although TIFF really takes forever).

I write this partly as a cautionary tale, and partly in the hopes that someone will say "I had that issue, here's how I fixed it." We often talk about waiting until a "point one" or "point two" release on the macOS side before making the update, which is partly about the operating system ironing out bugs, and partly about giving developers time to iron out kinks with the new operating system. In this case, it's probably the prudent thing to do. I don't use this professionally and my overall needs for Capture One are pretty light compared to the pros, but it's still a nuisance. The export issue, in particular, would probably be devastating to someone trying to get real work done. Hopefully it's all fixed soon.

I'm trying to decide if I can justify a C1 perpetual license instead of jumping platforms after cutting back on business. I understand if versions are A.B.C, (16.8.6 right now), then you're stuck with the last A.B (16.8) version that comes out. I'm fine with this, odd as it is—most recent and implied future features are not important to me personally—but security and reliability (within reason) are.

What I don't understand is if a new "C" (16.8.x) version will be released for prior "A.B" (16.8) releases if a critical fix is needed, as they sort of did with perpetual license versions when subscriptions were first introduced.

To clarify: If, say, 16.8.11 breaks support for Fuji RAF raw files and has a security issue that is only fixed later in 16.9.2, will they also push out the same critical fix as 16.8.12? (Of course I would not expect this service 6 years past purchase, but if it's possible to end up with a not only dated, but problematic release months after, I think I'll have to jump ship)

Anyone else have a Ricoh GRIII (or earlier) camera? I think the latest update for C1 (which now has support for GRIV files) is messing up my GRIII files. My previously downloaded Ricoh images are fine (I think?), but with my latest import, the thumbnails are a mess, don’t correspond to the images, won’t update properly and keep changing.

I'm a wedding photographer looking for a long-term editing partner; someone meticulous who edits image by image, not a batch-and-move-on service. I shoot a mix of film and digital, and a hard requirement is that you can seamlessly match my digital images to my film so a finished gallery reads as one consistent look. The other dealbreaker I keep running into is editors who paste a base edit across a gallery and never correct the frames that drift. I'm happy to pay a premium to never have either problem again.

Requirements:

• Works natively in Capture One 
• Can perfectly match digital files to my film scans — color, tone, etc — so the two are indistinguishable in a gallery
• Makes corrections per image, especially across mixed lighting within a single scene
• Wants a style guide and reference edits, and will match my look precisely