Stop Clients From Marking Up Photos in PowerPoint

Why PowerPoint is the default, not the exception

Ask a handful of photographers where client markup actually arrives and PowerPoint comes up constantly, alongside Keynote, Google Slides, and Preview's built-in annotation tool on a Mac. None of these are photo review software, and none of the people using them think of themselves as doing anything unusual. They are doing the only thing available: taking a static image file and adding a shape and some text to it, using whichever app on their machine already knows how to do that.

That matters for how you fix it. A client who reaches for PowerPoint has already decided that circling and annotating is the right way to give you feedback — they've just done it in the only tool they have. Replacing that habit with a plain gallery that only supports a star rating or a one-line comment box is a downgrade they will resist, because it removes the thing they were actually trying to do: point at a specific part of the photo and say what's wrong with it there.

What breaks when the markup leaves the image

Three specific things go wrong once a note is drawn in a second file instead of on the photo itself.

• The pointer separates from the target. A circle in a slide is just a shape sitting over a picture of your photo, not a coordinate on the photo file. Open the original at a different zoom level, on a different monitor, or after a crop, and the circle no longer points at the same pixels — if it ever left the slide at all.
• Version drift. The slide was made against whichever export the client had open that day. If you deliver a new round and replace the file, nothing in the deck knows the export changed. A note that said "fix the highlight on the left shoulder" can now be sitting over a frame that has already been retouched, and there is no flag telling anyone that — the same confusion covered in more depth in how to tell which edit of a photo is actually current.
• Someone has to retype it. The note that lives in the client's file is not the note in your project tracker. A person — you, a coordinator, sometimes the retoucher directly — has to open both, match each circle to a frame by eye, and type the instruction into wherever the actual work gets tracked. That step is where wording gets softened, notes get merged, and the occasional one gets missed entirely because the slide had fourteen shapes on it and the list only shows thirteen.

None of that is a client mistake. It's what happens any time an annotation has to survive a hop from one file format into another before it reaches the place work happens.

What a review link changes structurally

The fix is not a nicer version of the slide deck. It's removing the hop: the client draws directly on the photo, in the browser, and the shape is stored as a position on that image — not as an object sitting on top of a screenshot of it. That one change removes all three failure modes at once. There is no second file for the pointer to separate from. There is no drift, because the note is stamped to the round it was written about, so a delivered version shows exactly what was still outstanding on it. And there is nothing to retype, because the note the client wrote is the note the retoucher reads — the same text, in the same place, numbered to match a badge on the frame.

Where the note lands after the client sends it

The other half of this loop is what happens after the note leaves the client's screen, and it's worth naming because it's usually where the PowerPoint habit gets reintroduced on the studio's own side. If a retoucher opens Photoshop and has to read markup off a slide deck or a PDF export, they're doing the same manual matching the client's deck created in the first place — just one step later in the chain. Appruva's Photoshop panel closes that second gap: it places each client's markup on the open document as its own layer, at the point on the frame the client actually drew it, numbered to match the badge the client saw in the browser. The retoucher never re-locates a note by eye, because it's already sitting on the pixel it describes. For the deeper mechanics of that hop — and why a screenshot pasted into a layer is a worse version of the same problem this section describes — see how client markup gets into Photoshop without a screenshot layer.

What happens when two people mark up the same deck

The three failures above assume a single reviewer. Most client-side approvals involve more than one person, and a slide deck handles that badly in a way that rarely gets noticed until it causes a real problem. Send one PowerPoint file to an art director and a brand manager, and you get two separate copies back — each with its own shapes, on its own timeline, with no way to tell whether the brand manager's circle on frame 14 and the art director's circle on frame 14 are the same note said twice or two different problems on the same photo. Someone has to reconcile both decks by eye before any of it reaches the retoucher, and the deck format gives that person nothing to work with beyond opening two files side by side.

A shared review link doesn't have that problem because there's only one copy of the photo to mark up in the first place. Every reviewer's shape lands on the same image, at the same coordinate space, so two people circling the same spot is visibly two notes on the same point rather than two files that happen to agree. It also means a note doesn't quietly vanish because one reviewer's deck was the one that got forwarded and the other one sat unopened in an inbox — there's no second inbox for it to sit in.

Making the switch without a fight

Clients don't resist a review link because they prefer PowerPoint. They resist anything that adds friction compared to what they already know how to do. So the switch has to win on friction, not just on tidiness:

• Send the link as the deliverable, not as an optional alternative next to a downloadable folder. If a folder of files is still the primary handoff, the client will default to whatever they already do with a folder of files.
• No login. A client who has to create an account before they can leave a note will open PowerPoint instead, because PowerPoint is already open.
• Let the shape be the whole action. If drawing a circle and typing a sentence takes more clicks in your tool than it does in a slide app, you've reintroduced the friction you were trying to remove.

The table below is the same comparison as the loop above, framed by what each note actually needs to survive intact between the client and the person doing the work.