Photo proofing for clients, without the client accounts.
To proof photos with a client, upload the selection to a project and send them one share link. They open it in a browser with no account to create, zoom the image to print resolution, and either pin a comment to the exact spot or draw on the picture itself. When they are happy they approve it, and that approval is recorded against their name and that specific version of the image.
Five steps, and the client does three of them.
Nothing to install on either side. The client is asked for a name only at the moment they first write something, and an email address is optional — so the gap between sending the link and getting usable notes back is measured in minutes, not in password resets.
- 01 Upload the selection to a project — a shoot, a gallery, a single hero image.
- 02 Share one link — the whole project, one folder, or just the files you chose.
- 03 The client opens it in a browser, with no account and nothing to install.
- 04 They zoom to print resolution, pin a comment to the spot, or draw on the image.
- 05 They approve — recorded under their name, on that version — and you deliver the originals from the same link.
"The third one" is not a retouching brief.
Photo feedback by email arrives as filenames and vague directions, and half the retouching time goes on working out which blemish, which edge, which of the two people in shot. A note that is attached to a coordinate does not have that problem.
The client zooms and pans into the image at full resolution, drops a numbered pin where the issue is, and types the note there. If a pin is not enough they can draw — pen, arrow, or box — and the drawing is saved with the comment, so clicking it later brings the mark back over the same spot. Comments you write to your own team are marked internal and never appear on the client's link.
The retouch goes up as a version, not a new file.
Upload the revised image onto the same file and it becomes the next version. The earlier round and its pins stay readable, so the brief that produced the change is still sitting next to the change. Your team can put the two versions side by side to check the edit actually landed.
Approvals are recorded per person and per version, and they do not travel: approving v1 does not approve v2. That is deliberate. It is the difference between "they signed off on the shoot" and "the art director approved this exact retouch on this exact frame".
Photographers rarely deliver only photographs.
There is a behind-the-scenes cut, a slideshow, an audio bed the couple picked, a PDF album layout the client's team has to sign off on. All four formats go into the same project and travel on the same link, so the client learns one surface and you are not running a photo tool alongside a video tool alongside email.
Not a colour-managed print proofing tool.
This is client proofing: does the client accept the image, and is that acceptance on the record. It is not soft-proofing. There is no colour management, no ICC profile handling, and no press preflight — if you are checking a file against a press profile before it goes on a machine, use a tool built for that job and use this one for the client conversation.
It also reviews the exported file rather than a live document, so copy proofing inside the layout application itself is out of scope. Everything downstream of "send it to the client" is what this is for.
Bring everyone. Pay for storage.
Free tier. No card. Your first review link in about two minutes.