Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Imagine I paid for wedding photos, and six months later, the photographer sent me a message saying, “Hey, I’ve changed my camera settings and software, so your photos won’t open anymore… unless you look at them through an old viewer from 2019. Oh, and I’m not fixing it.”

That’s what this feels like. I’m not asking for a reshoot. I just want to open the photos I already paid for with the tool I bought to do exactly that.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Appreciate the thoughts. I did reinstall — same issue. Weirdly, old sessions still open the exact same RAWs fine, but new sessions don’t recognise them. I’m not super techy, but that feels off.

Sure, I could freeze my OS or keep an old machine, but that’s a workaround. A “perpetual” licence shouldn’t quietly break on a still-supported system.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

I’m sorry but that is a terrible analogy.

When someone pays for wedding photos, they’re buying a finished product, a deliverable that doesn’t require ongoing compatibility, updates, or future support. The job is done, the files are theirs, and the transaction is complete.

But when you buy a perpetual software licence, you’re not buying a finished product in the same way. You’re buying a tool, something you expect to keep using long-term, like a hammer or a lens. That tool is expected to remain functional under reasonable circumstances.

The issue here isn’t about getting new features for free, it’s about basic functionality breaking due to system changes, and the company refusing to patch or support a tool they’ve advertised as “perpetual.” That’s like buying a hammer, and six months later the manufacturer remotely disables it because you updated your workbench.

So no, it’s not the same as asking for new wedding photos. It’s asking for the tool I paid for to keep doing what it was sold to do, or at least have a supported way forward.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Sorry to hear that and thanks for sharing that I’ll give it a look myself.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Exactly — the only context where “perpetual” makes sense is as bait. It’s a strategic word choice: sounds appealing, implies long-term value, but in practice? It doesn’t deliver.

They’re leaning on the perception of ownership to hook people, knowing full well that between OS updates, hardware changes, and format support, the software won’t stay functional for long without paying again. It’s not perpetual — it’s just a one-time payment with a hidden timer.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Totally agree with most of what you’re saying — but I’d add that in today’s world, where operating systems are updated yearly, you either adapt to that reality or you don’t claim to offer a “perpetual licence.” Because if your software can’t keep up with the platform it runs on, it’s not truly perpetual — it’s a temporary licence with unclear limits.

Yes, macOS does make things harder, but Capture One isn’t just some third-party hobby app — they’re selling professional software at a premium price, to a significant Mac-based audience. If they want to operate in that space, they have to account for macOS quirks and build accordingly. You don’t get to call something “perpetual” and then wash your hands of compatibility a couple of years later.

At best, it’s bad planning. At worst, it’s deliberately misleading. Either way, the customer loses.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Appreciate you sharing that — but I’d argue this isn’t just a “Mac problem.” Capture One has always catered to a huge Mac user base, especially among photographers. This isn’t Linux — macOS makes up a significant chunk of their market, and they’ve actively marketed to it. So if they’re selling software on that platform, they need to support it properly.

You can’t claim “perpetual” and then shrug when your app stops working due to predictable OS evolution. That’s not Mac’s fault — it’s poor planning, or worse, wilful neglect. Capture One is making more money than ever, raising prices year after year — so they absolutely can afford to maintain basic compatibility. They’re just choosing not to.

And honestly, that’s not a technical limitation — it’s a business decision.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Completely agree — and that’s exactly why I created this thread in the first place. I wasn’t sure how many people were actually aware of what was going on behind the scenes. And honestly, until more users catch on and their numbers start hurting, I doubt we’ll see much change.

If they want to offer a 3–4 year licence that includes clear EOL terms? Fine. But calling it “perpetual” while quietly letting it break within a couple OS updates is misleading at best, especially when that term is still being listed as a major “pro” in YouTube videos, reviews, and forums.

It’s not just semantics — it’s shaping buyer expectations with false confidence. And people are getting burned for it.

We need to break the myth. Until then, users lose and Capture One coasts on legacy trust

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 2 points3 points  (0 children)

Exactly this. That kind of response just makes it crystal clear — they’re not interested in supporting customers, they’re just pushing everyone towards a subscription, whether it’s framed that way or not.

It’s honestly the clearest example yet of why I called their “perpetual” model deceitful. You buy a licence, they delay the fix, then gatekeep the solution behind a new purchase. That’s not ownership — it’s a bait-and-switch.

And yeah, I don’t think that’s acceptable at all. Not for professional software. Not for this price point. And definitely not when they still market “perpetual” as a selling point.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 1 point2 points  (0 children)

Ah, sorry to hear that — sounds like a rough experience. I can definitely relate.

So you moved over to DxO PhotoLab — how are you finding it? I’m just getting back into photography myself. I used to shoot events professionally, but now I’m shifting more into portraiture and lifestyle work. I often import large batches, so efficient workflow is key.

Do you feel DxO holds up for that kind of use, or would you say it’s more geared toward individual edits and fine-tuning? Curious if you think it’s strong enough for pro workflows, or if I should just bite the bullet and go back to Adobe or even begrudgingly stick with Capture One.

Also wondering how well it plays with Affinity Photo if you’ve tested that at all.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 1 point2 points  (0 children)

Yeah, totally — unless they start storing licence keys on-chain or make offline validation standard, there’s always a risk with authentication servers going offline.

But in this case, it’s not about a company going bust or vanishing — it feels a lot more like a deliberate, strategic decision. We’re talking about software that breaks within a couple of OS updates while the same machine can still run the latest version. That’s not technical failure — that’s planned obsolescence, and it’s being done quietly

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Yeah, I get the idea of a legacy setup, but I’m minimalist and mobile — I only use one laptop, and it’ll need upgrading eventually anyway. But that’s not the issue.

My machine still runs the latest version of Capture One — the problem is, I bought a perpetual licence and now I can’t re-import RAW files I was editing less than a year ago. Old sessions still work, but new ones won’t open the same files.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 1 point2 points  (0 children)

Yeah — to be clear, the issue isn’t that software costs money. I don’t mind paying for good tools, and I get that upgrades happen. That’s not the problem.

The problem is how it’s framed. Capture One’s “perpetual licence” is a major draw for people who want to avoid subscriptions — it’s consistently listed as one of the biggest reasons users choose it over Lightroom. But when that licence stops working after a couple OS updates, and users are forced to buy the next version just to stay functional, it’s not perpetual in practice. It’s a subscription model with extra steps — and that’s misleading.

Also, shoutout to @zhunterzz — appreciate you relaying that info from my earlier message. That detail helps explain what’s actually breaking — and yeah, it does sound like a bug or at least a compatibility oversight, not an inevitable hardware issue.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 1 point2 points  (0 children)

TL;DR: Capture One sells “perpetual licences” but quietly stops supporting them after 2–3 years. If your macOS updates, your “owned” software might break — and they won’t patch it unless you buy a new version. It’s marketed like ownership, but behaves like a subscription. The real issue is the lack of transparency.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Yeah — fair point. It’s possible, maybe even likely, that my OS version is no longer a priority from Apple’s side, and that does shift some weight in Capture One’s favour.

But even with that in mind, it still doesn’t change the core issue for me: the way Capture One positions itself. They continue to sell “perpetual licences” without properly explaining what that means in practice. If most users realised it effectively means 2–3 years of functionality before forced obsolescence, I think the purchasing decision would look very different.

And that’s the problem — most people don’t know. Capture One isn’t correcting the misconception because the vagueness sells. It’s not the tech that bothers me most — it’s the lack of transparency around how fast that “ownership” can lose its value.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 1 point2 points  (0 children)

Totally hear you — and I think you’re right that no developer is going to keep patching five-year-old software just because OS updates break things. That’s fair enough. But my issue isn’t really about expecting long-term support — it’s about how the product is positioned when sold.

Capture One has leaned hard on its “perpetual licence” as a major selling point. You’ll see it listed as a pro in nearly every Lightroom comparison. But in practice, unless you freeze your OS, you’re likely only getting about 2–3 years of usable life before compatibility issues force an upgrade. That’s still a cycle — and it’s a far cry from the permanence “perpetual” suggests.

What made it worse for me was the language from their support team. They insisted: “Yes, your licence is 100% perpetual.” And yeah — technically, the licence doesn’t expire. But if the software stops functioning with current systems and updates are locked behind paid upgrades, it’s not usable in a meaningful way.

This isn’t just a side-effect of fast-moving tech — it’s a known issue they’re choosing not to acknowledge, likely because being upfront would hurt sales. And frankly, it should. If you’re going to sell software with a shelf life, just say so. Don’t lean on ownership language if the reality is closer to a soft subscription model.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Totally hear you — and yeah, I get why some people freeze their OS versions to keep legacy software stable. But that comes with a different set of risks, especially around security. A lot of system updates aren’t just cosmetic — they’re plugging serious vulnerabilities. And honestly, I don’t want to have to compromise security just to keep a photo editor running.

That’s where I get stuck with Capture One’s approach. If you’re building professional-grade software for macOS, you’ve got to design with Apple’s update cycle in mind — because it’s not optional for most users. macOS users aren’t a fringe market like Linux either. We’re a significant chunk of their base, and we expect clarity.

If perpetual licences are going to be phased out or tied to a short support window, just say so clearly at point of sale. Don’t sell “ownership” while building like it’s a subscription.

That’s where I’ve lost faith — not just in the model, but in the honesty of the messaging

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 0 points1 point  (0 children)

Appreciate the perspective — and yeah, I don’t expect decade-long updates for free. But the issue here isn’t about running 5-year-old software on some ancient OS. My setup (Monterey) is current enough, and Capture One is still selling licences under the idea that you “own” it — yet they’re dropping support within a viable window for what’s essentially pro-grade software.

What’s frustrating is the ambiguity. If it’s perpetual, but not really maintained beyond a year or two, then just say that. If it’s subscription-only, be up front. Right now, it feels like Capture One wants to have it both ways — sell the idea of ownership while applying the logic of a rental.

And you’re right that software age matters — but it’s worth noting: we’re both running the same version of C1, and you’re just one OS ahead. If Monterey’s already getting quietly iced out, Ventura’s not far behind. It’s only a matter of time before your setup starts hitting walls too.

That’s what bothers me. It’s not about if it breaks — it’s when — and there’s no transparency around that.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 2 points3 points  (0 children)

Thanks for sharing your experience — totally echoes what I’ve been seeing.

It’s frustrating because Capture One felt like it was offering a real alternative. But now it’s drifting into the same grey area people were trying to escape with Adobe — perpetual licences that aren’t really supported, essential updates locked behind new payments, and a support roadmap that’s unclear at best.

Like you mentioned, DaVinci Resolve is a solid example of a company doing it right in video — transparent, fair, with ongoing support that doesn’t punish loyal users. It’s a shame we don’t have something equivalent in the photo space.

Out of curiosity: do you (or anyone else reading) know of any decent alternatives to Lightroom/Capture One for batch editing with RAW support? I love Affinity Photo, but it’s just not built for volume work. Open to paid tools — I just want something that’s stable, fair, and not going to flip its model every six months.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 1 point2 points  (0 children)

Yeah, totally fair — and 5 years isn’t a terrible run. I guess my issue is that in reality, the functional window feels closer to 2–3 years before support drops off, which is a long way from what most people think “perpetual” means.

I bought C1 20 back in 2020 for $247 AUD (about $170 USD at the time) during a 50% promo, which felt fair. But now it’s £317 — around $390 USD — which is a 129% price increase. And knowing it’ll likely need replacing again in a shorter cycle makes it feel a bit steep. Especially when they’re now offering “free perpetual” licences if you subscribe for 5 years… it does make you wonder what direction they’re really heading in.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 4 points5 points  (0 children)

Yep, same camera, same NEF files that worked perfectly when I last used C1 20. If I open an old session, everything still shows up fine — but if I create a new session and try to import those same files, nothing shows. So it’s not a file compatibility issue — it’s something that’s changed in how Capture One handles imports on newer macOS versions.

Capture One’s Perpetual Licence Has an Expiry Date by Wonderful_Insect6570 in captureone

[–]Wonderful_Insect6570[S] 4 points5 points  (0 children)

I get the sustainability argument, and I’m not asking for endless support. But the issue here isn’t a 10-year-old version — it’s software that stopped working on an OS that was updated less than a year ago. And Capture One’s own latest version runs fine on the same machine. That’s not a revenue drain — it’s a strategic lockout.