
The marketing for cloud culling talks about model accuracy. The clock talks about upload speed. For a wedding of 4,812 frames, a cloud culler's own pages quote forty minutes to three hours before you can look at a single result. Kepla on a MacBook Pro M3 Max, on battery, took 4 minutes 22 seconds. This is a step by step account of where the time goes in each approach, and what each one asks you to hand over.
| By hand | Fully automatic (cloud) | Kepla on your Mac | |
|---|---|---|---|
| Who decides what the client sees | You, across all 4,812 | A model trained on other people's taste | You, across 1,880 clean frames |
| An evening's card | 4 to 6 hours | Minutes to run, then an hour checking what it threw out | 4 min 22 s, while the card copies |
| Why a frame was dropped | You remember, mostly | A score out of ten | One of five words, printed on the frame |
| Where your files go | Nowhere | Often up to a queue, behind other customers | Nowhere. Wifi off, same speed |
| What it can delete | Whatever you delete | Reject flags you have to trust | Nothing, ever. Sidecars only |
| What it costs a year | Roughly 200 hours of your life | $120 to $180, rising | $99, locked for as long as you keep it |
By hand costs your evening. Fully automatic costs your judgement. The third column is built to cost neither.
A cloud culler's timeline for a wedding has four parts, and only one of them is the model. First the upload: a 128 GB card, or several, over whatever connection the venue or your home has. Second the queue: your job waits behind every other photographer who finished a wedding the same Saturday. Third the model, which is fast. Fourth the download of results, and then an hour of checking what it threw out, because a score is not a reason.
The vendors' own pages put the total at forty minutes to three hours for a shoot this size. The range is wide because the upload is wide: it depends on a connection you do not control.
On a Mac the timeline has one part you already do, the card copy, and one part that hides inside it. The copy of 4,812 frames to two drives at 214 MB a second took 24 minutes 10 seconds. Kepla read the JPEG the camera embedded in each RAW, worked in the idle gaps while bytes moved, opened the full RAW on 214 frames where the answer needed it, and finished in 4 minutes 22 seconds, 19 minutes 48 seconds before the copy did. Nothing was uploaded because nothing needed to be.
The second pass is the other place the clock diverges. Add a card or change your mind on a cloud culler and it is another upload. On the Mac every decision is already in a sidecar, so a second run touches only what changed: seconds.
Run a card you already culled. If the sort does not finish before your own copy does, on battery, the founding promise is that you owe nothing. Kepla for Mac is free through the private preview and the first hundred photographers keep it at $99 a year; after that it is $180. Request Founding Access.
Hardware size is not the constraint for blinks, blur and duplicates; those are settled at preview resolution. What bigger hardware does not fix is the upload, which is where the cloud spends most of its time.
Sorting runs entirely on your Mac. Only your decisions sync, if you want them on another device, and they are kilobytes of XMP, not photographs.
The cloud tools in this comparison run $120 to $180 a year and have moved upward. A Kepla founding place is $99 a year locked for as long as you keep the app; after the first hundred it is $180.
Kepla for Mac clears the obvious misses from a card, names the reason on every frame it sets aside, and leaves the choosing to you. Nothing is ever deleted, moved or renamed. Free through the private preview · the first hundred photographers keep it at $99 a year.