AI Culling & Search

A single wedding or event can produce thousands of photos. Going through every one by hand to find the keepers, or to pull out every photo of one guest, is the single biggest time sink in a photographer's workflow. Peasier has two AI features that solve two different parts of that problem.

AI culling: sorting the keepers from the rest

Culling is the first pass through a shoot — throwing out blinks, blur, and obviously bad frames before you sit down to edit. Peasier looks at every photo in a shoot and flags the ones with visible quality issues (blur, poor exposure, awkward framing), so instead of reviewing 2,000 photos one by one, staff review a shortlist the system has already narrowed down.

You can also show it a handful of your own examples of what you'd normally keep, and what you'd normally throw out, so its suggestions line up with your studio's own standard rather than a generic one.

Face search: finding every photo of one person

Once a gallery is delivered, both staff and clients can search a gallery by person instead of scrolling through hundreds of photos — useful for a bridesmaid who only wants her own photos, or a corporate client who only needs the CEO's shots pulled out.

This depends on recognizing faces across photos, which is more sensitive than the quality-scoring culling does, so Peasier gives every studio three ways to run it. It's important to understand when to use each.

Consent applies to all three modes, not just Cloud. Generating and using someone's face data to identify them is treated as sensitive personal data under most privacy laws (including GDPR and NDPR), regardless of whether that happens on a server or on the photographer's own device. Running face search offline does not remove the need for consent — it changes where the data is processed and who can see it, which is a real privacy benefit, but it isn't a way to skip asking. Studios are responsible for getting their clients' consent before enabling face search in any mode, and should check what their own local law requires.

Cloud

Face recognition runs on Peasier's servers, off the photographer's own device. It's the fastest option and works well for large libraries.

Use it when: you need face search to work quickly across a large library, your client has given consent, and you're comfortable with face data being processed on Peasier's servers rather than only on your own device.

Offline

Face recognition runs entirely in the photographer's own browser. Nothing about anyone's face is sent to or stored by Peasier's servers — it never leaves the device.

Use it when: you want to minimize where face data is stored and who can access it — for a sensitive or high-profile client, or in a jurisdiction with stricter biometric-privacy rules — while still having your client's consent to run it at all. It's slower than Cloud, since your own device is doing the work, so it suits smaller galleries better than very large ones.

Disabled

Face search is switched off entirely for that gallery or studio. No face data is generated or stored, and the "search by person" option doesn't appear for clients.

Use it when: face search isn't something your clients need, a client doesn't consent to it, or you'd rather not deal with biometric data at all. This is a genuine off switch, not a hidden default — nothing runs in the background.

Choosing a default

Most studios pick one mode per gallery, or set an organization-wide default and only switch to Offline or Disabled for specific clients who need it. Whichever you choose, it only ever applies going forward — switching modes doesn't retroactively process or delete photos that were already handled under a different mode.

None of this is legal advice — biometric privacy rules vary by jurisdiction and change over time, so studios should confirm their own consent obligations with their own legal counsel rather than relying solely on this page.