How it works

Two workflows.One delivery moment.

Studioshare does two jobs end to end. It gets the night’s photos to the people who are in them while the event is still warm, and it gets a client from a thousand frames to a signed-off shortlist without a single zip file. What follows is the workflow as it actually runs today — no roadmap smuggled in.

Get Studioshare Feature detail

Windows desktop app and Android. macOS and iOS in development.

Workflow one

Instant event share

Camera to guest, during the event. Tethered capture, a QR code on the table, one selfie, and each guest walks away with the frames they are in.

Workflow two

Selection and proofing

Shoot to shortlist, after the event. Folders the client can navigate, picks they can make on their phone, notes on the frames themselves.

Workflow one

Instant event share

Six steps, most of which you only do once. The two that matter on the night — the guest scanning a code and the guest getting their photos — do not involve you at all.

01

Create the event

Name it, date it, pick the type. The event gets its own page under your studio’s path, so the link you hand out carries your name rather than a file host’s. It stays unpublished until you say otherwise.

02

Connect the camera

The capture app opens a transfer session for that event and shows you an address and credentials. Point the camera’s network transfer at it, fire a test shot, and you are connected.

03

Shoot

Frames arrive as you work and are processed on the way in. No card swaps mid-reception, and no import step waiting for you at two in the morning.

04

Guests scan one QR

On the table, on a standee, on the back of the menu. It opens your event page in whichever browser is already on their phone — there is nothing for them to install.

05

One selfie

The browser captures a single frame and sends it to our servers, where the face embedding is computed. Guests who have used Studioshare before skip this and continue with the face already on file.

06

They get their photos

We match that face against the event and hand back the frames they appear in — not the whole night, and not a folder they have to scroll. Their photos, on their own page.

Guests who arrive at the page before the photos do can ask to be told when their set is ready, rather than refreshing a dead link.

The pieces this workflow uses

Live

Tethered camera capture

Connect the camera to the Studioshare desktop app and frames sync as you shoot. No card swaps, no import step at the end of the night.

Live

QR + selfie guest access

Guests scan a QR code at the event, take one selfie, and get the photos they appear in. No app install, no account, no waiting for a link.

Live

Studio wall for the venue screen

Every event can have its own wall on its own address, so you open it on whatever drives the screen and walk away. It stays dark until you publish it, and you pick which folders appear.

Where the matching happens

Server-side. Not in your guest’s browser.

An earlier version of this site described face processing as happening on-device, in the browser. That was true of a legacy pipeline which has since been removed, and it is not true of Studioshare today. The browser’s only job is to take one photo and upload it. Everything after that runs on our infrastructure.

We would rather correct a privacy claim in public than leave a flattering one on the page. If where the maths runs is a decision factor for you — and for a school or a corporate client it usually is — read the data handling page before you commit to anything.

How we handle data Ask us something specific

The pipeline

Selfie to matched set

The guest’s browser captures one JPEG and posts it to our API.
Our face service computes a 512-dimension AuraFace embedding — on the server.
That embedding is stored as a vector against the guest’s record.
Every gallery photo is embedded the same way as it is ingested.
Matching is a cosine nearest-neighbour search across the event’s faces, with a distance cutoff we tune.

Workflow two

Selection and proofing

The other half of the job, and the one that quietly eats your week. A client who cannot decide is not being difficult — they are being handed a thousand files and no way through them.

01

Bring the shoot in

The same event object as the instant share workflow. Capture straight into it, or upload a shoot you have already culled.

02

Organise into folders

Ceremony, portraits, reception. The client sees folders as tabs rather than one endless scroll, which is the difference between a decision and a chore.

03

Invite the client

Add them to the event by phone number. If the album is fifty photos, set the cap to fifty and the interface holds them to it instead of you having to.

04

They mark their picks

They open the link in a browser on the phone they already have and select photo by photo. Progress is theirs to pick up and put down.

05

They leave notes on the frames

Comments attach to individual photos, so “crop this one tighter” arrives on the photo it is about instead of three days later in a WhatsApp thread.

06

You get the set

A review screen shows only what was selected, on its own, ready to hand to the edit instead of you cross-referencing a list of filenames.

The piece this workflow uses

Live

Selection & proofing workflow

Create events, organise shots into folders, and invite clients to mark their picks — so you shoot to a confirmed list instead of guessing.

Worth knowing

Both workflows, one event

An event is not one thing or the other. The same wedding can run instant share for the guests during the reception and a selection round with the couple two weeks later, off the same set of files.

Before you plan an event around it

What runs where

One machine at the event runs the capture app. Nothing else in either workflow needs an install — not your client, and not a single guest.

Which part of Studioshare runs on which platform
Tethered camera capture	The Windows desktop app, on the machine at the event.
Events, folders and invites	The desktop app on Windows, or the Android app.
Guest QR, selfie and gallery	Any modern phone browser. Nothing to install.
Client selection and proofing	Any modern browser, on any device the client owns.
Studio wall	A browser on whatever is driving the screen or projector.

Windows — Microsoft Store Android — Google Play

Windows desktop app and Android. macOS and iOS in development.

Not built yet

What the workflow does not do

Both workflows above end at delivery. What happens next — who opened it, who reshared it, which guest became a booking — is not something Studioshare can tell you today. It is what we are building, and it is not shipped.

In development

Guest Graph consent capture

A separate, explicit, easy-to-decline opt-in that lets a guest hear from you later — kept legally distinct from the consent that powers "find my photos".

In development

Earned Impressions tracking

Measure how often guests reshare your branded work, so reach stops being a guess.

In development

Guest-to-Lead dashboard

Your G2L rate per event: how many guests arrived, how many opted in, how many became real enquiries.

In development

Second-order booking attribution

Trace a signed booking back to the event where that client first showed up as somebody else’s guest.

In development

macOS and iOS apps

Android is live on Google Play and the desktop capture app runs on Windows. macOS and iOS are still in development.

Why that layer matters

Run it once and the rest is muscle memory.

Set the capture app up on a quiet afternoon rather than the night before a wedding. We will walk you through the first one.

Create your studio See pricing Talk to us first