Client Photo Markup in Photoshop, Without Screenshots

Why the screenshot-into-a-layer habit costs a round

Walk through what a single note actually takes, start to finish, with no shortcuts and nothing automated:

None of those five steps touch the actual edit. They're the tax you pay before retouching starts, and it resets every round because the screenshot layer never survives past the version it was pasted into — open the file again next week to fix something the client missed, and the markup layer is gone or, worse, still there and now pointing at the wrong version of the crop. If the review itself already runs through a single link instead of an email thread, this is usually the next place the process still breaks down: the notes are organized on the review side, they just aren't in the file where the work happens.

The cost compounds with team size, too. A solo retoucher at least knows their own screenshot habits — where they usually paste, what zoom they usually work at. Hand the same file to a second retoucher, or to a freelancer brought on for a rush week, and step 4 becomes a fresh guess every time, because there's no shared reference for what "lined up" means beyond one person's eye.

What the panel does with the same note

Appruva's Photoshop panel skips the screenshot entirely. It knows which frame is open in the document — an XMP stamp first, then filename matching that's folder-aware and suffix-tolerant, and it asks only when neither resolves. So opening a file straight from a folder of exports still lands on the right note thread, without anyone having to rename anything to match a system.

The client's notes appear inside the panel itself, numbered to match the badges on the review side, so "note 4" means the same thing to the retoucher looking at Photoshop and the art director looking at the browser. They arrive live over a WebSocket where the network allows it, and fall back to a 45-second poll where it doesn't — the retoucher isn't left refreshing a panel to see if a new note landed.

The markup itself lands on the file as a real layer: a vector overlay sized to the document, transparent everywhere there's no markup, with the option to split it into one layer per note, named for what that note actually asks for. That naming matters more than it sounds — a layer called "soften shadow, left cheek" is something a second retoucher can pick up without a handoff call. Clicking a note in the panel jumps to it and marks the area it points at directly on the canvas, so there's no zooming around the frame trying to remember which circle was which.

Crop guides and reference images that land where they're pointed

Two kinds of notes are especially painful as screenshots: crop requests and color references, because both depend on exact placement rather than a general area.

A crop note drawn as a guide in the app crops the canvas in one click — nothing outside the guide is lost, the note ticks itself off, and every other shape on the file re-maps so the rest of the markup still lands on the same pixels after the canvas size changes. Compare that to a crop described in a comment ("tighter on the left, maybe 15%") that gets interpreted once by whoever reads it and often re-interpreted by whoever exports it — fifteen percent of what dimension, measured from which edge, is a question the client never actually answered, and a guide drawn in pixels doesn't leave room to ask it.

A reference image attached to a note — "match this skin tone" — opens beside the document as its own file instead of as a thumbnail in a feedback thread, so the eyedropper can actually sample it. A reference pasted into an email gets described in words by the time it reaches the retoucher ("warmer, like the one from the lobby shot"); a reference opened as a file next to the document gets sampled directly, which is the difference between matching a color and matching a description of one.

Both of these are small on their own, but they're the notes most likely to bounce back for a second round when they go wrong — a crop that's slightly off or a tone that's close but not right reads as a miss to the client even when the retoucher followed the note exactly as written. Removing the interpretation step removes the most common reason that specific kind of note comes back at all.

Closing the loop without retyping "done" three times

In a normal round, a note gets marked done in the panel, then again in a spreadsheet or task board, then a third time in the reply to the client. Three places means three chances for one of them to be wrong, and it's usually the client-facing one that lags, because updating it takes stepping out of Photoshop entirely. The panel's ticks stay local until the round is handed back, so there's one place a note's status actually lives while the work is in progress.

Deliver exports the file by the studio's own recipe, uploads it, stacks it as a new version, closes the ticked notes, and posts a delivery note describing what was addressed and what wasn't — one action instead of four separate ones done by hand in whatever order the retoucher remembers them in. Delivering more than one file works the same way: every open document in Photoshop exports as a batch, sequential because Photoshop's own document operations are single-threaded, uploading three at a time, with one failure never stopping the rest of the queue and a retry that only re-runs what failed. That's the difference between a batch job that needs babysitting through forty files and one you can start and walk away from.

If you're already tracking rounds with a version stack instead of a folder full of _final_v2 names, the version bump on Deliver slots into that same model rather than adding a second one next to it — one system for "which edit is current," not two that can disagree.

Handing files to a freelance retoucher works through a share link scoped to Retoucher access rather than a shared drive folder — revoking it ends their access on the next request, and storage writes stay admin-only, authorized through a server function rather than the retoucher's own session. That's worth a sentence on its own: a folder invite tends to outlive the job it was created for, because revoking it means remembering it exists. A link created for one job and torn down when the job ends doesn't have that failure mode.

What this still doesn't do

Being specific about the edges matters more than the feature list. Delivery out of the panel is JPEG or PNG — it isn't a TIFF or PSD round trip, so a workflow that needs a print master handed back still needs a manual export step alongside it. There's no Lightroom plugin and no Capture One plugin; this is a Photoshop panel and nothing wider, so a studio doing its culling and base adjustments in Lightroom is still moving files between apps by hand at that stage. The other real bridge is Retouchable, where a linked client can pull an Appruva shoot straight into its own retouching flow, but that's a separate product working in its own terms, not another install of this panel, and it isn't a substitute for it.

What it removes is the translation step between where feedback is given and where the edit is made. It doesn't remove the judgment call on what to do with a vague note, and it isn't a claim that any studio has run it as a daily habit — it's built, it has been run end to end in a real Photoshop install, and it works the way this post describes.