Frame.io's Photoshop Panel, for Stills Photographers

What Frame.io's Photoshop integration actually does

Frame.io grew up around video review — frame-accurate timecode comments, Camera to Cloud ingest straight off a camera on set, a Premiere Pro panel for browsing and importing project media as editing bins. The Photoshop piece is much smaller. Share for Review uploads the active document to a Frame.io project and hands back a review link; anyone with the link can drop comments on it. Those comments surface back inside Photoshop through the Comments panel, and saving a new version re-uploads and keeps the review thread attached to the latest file.

That is genuinely useful for a specific case: a document that needs eyes from people who do not have Photoshop open, fast, without a separate upload step. A creative director on a call can pull up the link, drop three pins, and the retoucher sees them without anyone exporting a JPEG and dragging it into Slack. It is also, by Adobe's own description of the feature, restricted to Creative Cloud Enterprise accounts — a solo retoucher or a small studio on a standard Creative Cloud plan does not have the option, and the workflow it is designed around assumes the reviewer already lives in Frame.io for other, larger deliverables.

That framing matters for what comes next. Frame.io's product is a review and collaboration platform first, with Photoshop as one of several applications it reaches into — Premiere Pro and After Effects get the deeper panel, with project browsing and bin import; Photoshop gets the comment link. The feature was not designed around what a still-photo retouching round needs on its own terms. It was designed to extend an existing video-review product one application further, and the shape of that decision shows in what the panel does and does not do.

Where the loop breaks for a retouching round

Comments are not markup. A Frame.io comment on a Photoshop share is a pin and a text box floating over a flattened preview of the file — it never touches the document itself. Getting from "client said this" to "pixel changed" still runs through a human translating a comment into a selection, a mask, a crop. None of the steps a retoucher actually repeats every round are in the panel:

None of that is a knock on Frame.io generally — where the fit breaks for stills review covers the broader mismatch between a timecode-first tool and a photo workflow. The Photoshop panel specifically is the video-review model transplanted with the video parts removed, and what is left is a comment thread with a nicer entry point.

The gap shows up hardest on the two note types that make up most of a real retouching round: a crop and a colour match. A crop note in a comment thread is a sentence — "tighten in from the left, keep her hands in frame" — and the retoucher still has to interpret where "tighten" stops. A colour note is worse, because a comment thread has nowhere to attach a second image for the retoucher to sample from; "match the tone in the reference she sent" means someone digging through an email or a text thread to find the reference and eyeballing the difference on a monitor that may not be calibrated the same way the client's was. Neither problem is really about Frame.io specifically. It is what happens whenever the review surface and the editing surface are two different places connected by a link.

What a panel built for retouching does instead

Appruva's Photoshop panel starts from the opposite direction: not "let people comment on this file" but "put the note where the pixel is, and let the retoucher act on it without leaving the app." It runs as a UXP panel docked next to the document in Photoshop 2023 (24.0) or newer, on macOS or Windows, and everything below is built and has been run end to end in a real Photoshop.

• It knows which frame is open. An XMP stamp identifies the document first, then filename matching, then it asks — it never guesses which shoot it is looking at.
• Markup goes on the file as a layer — a vector overlay sized to the document, transparent everywhere there is no markup, optionally split one layer per note and named after what the note asks for. That is the difference a comment-on-a-preview cannot close: the note is on the document, not floating above a screenshot of it.
• Accept crop takes a crop guide drawn in the app and crops the canvas in one click, nothing outside the guide lost, ticks the note, and re-maps every remaining markup shape so the rest of the round still lands on the right pixels.
• A note's reference image — "match this skin tone" — opens beside the document as its own file, so the eyedropper actually has something to sample.
• Deliver exports by the studio's recipe, uploads, stacks a new version, closes the ticked notes, and posts a delivery note saying what was addressed. Every open document can go through that as one batch.

What a Photoshop panel can do that a web gallery cannot goes further into where the line sits between a review surface and a place work actually happens; the short version is that a gallery, and Frame.io's Share for Review is a gallery with a Photoshop doorway, ends at the note. A panel built around retouching starts there.

The honest gaps

Two things are worth saying plainly rather than skating past. First: Appruva's Photoshop panel is not on Adobe Exchange or the Creative Cloud plugin browser. It installs as a .ccx file today, which needs developer mode enabled on the machine — a real step, and the honest way to get it is through the app itself, not a walkthrough on a blog post that will drift out of date the moment either side changes. Second: this is a Photoshop panel, full stop. There is no equivalent for Lightroom or Capture One, and delivery out of the panel is JPEG or PNG, not a TIFF or PSD round-trip. If a studio's retouching lives entirely in Lightroom's Develop module, or a print workflow needs a layered master handed back and forth, this does not reach that workflow, and no amount of feature comparison changes that.

There is a real trade happening here, and it is worth naming instead of hand-waving past: Frame.io's Enterprise Photoshop integration sits inside a platform that also does frame-accurate video review, Camera to Cloud ingest from supported cameras, and asset management across an entire production. A panel built specifically for photo retouching does one job and does not try to be the review tool for a video edit. Which one is the right fit depends entirely on what the rest of the job looks like, not on which panel has more rows checked in a features table.

Counting the actual hops

Lay the two loops next to each other for one client note that says "warm up her skin tone and tighten the crop on the left."

The count is not a measured average across shoots — it is the steps each loop actually requires for the same instruction, and it is why "comment on a file" and "note anchored to a pixel" are different categories of tool, not two brands of the same one.