What a Photoshop Panel Can Do That a Web Gallery Can't
Drawing the line at the point where the actual editing happens
A web gallery gets a note in front of a retoucher. A Photoshop panel gets that note onto the layer the retoucher is already working in. That is the entire difference, and it matters more than it sounds: everything after the note is written — finding the right frame, placing the markup, matching a reference color, checking a fix off the list — either happens inside Photoshop or gets carried there by hand.
The screenshot-pasted-into-a-layer habit exists because most review tools stop at the browser tab. A panel is built specifically not to stop there. This post draws the line precisely: what a Photoshop panel can do that a gallery structurally cannot, and — just as important — what it still can't do, so you don't plan a workflow around a feature that doesn't exist yet.
Where the gallery's job ends
A review gallery is a website. The client opens a link, clicks a point or draws a box on a scaled preview, types a note, and hits submit. That note is now a row in a database, tied to an image URL and a pair of coordinates measured against whatever size the browser happened to render the photo at. It is not tied to a Photoshop document, a layer, or a pixel — because a browser tab has no way to reach into a desktop application. That boundary is not a bug in any particular gallery tool. It's just where the web stops.
Everything that happens next is the retoucher's problem to solve by hand. Open the gallery, read the note, alt-tab to Photoshop, find the file, and translate a scaled-down screen coordinate into a position on a 6,000-by-4,000-pixel canvas. The common workaround is the one this blog has covered before: screenshot the marked-up preview, paste it into Photoshop as its own layer, and eyeball the alignment. That's a minimum of three manual steps per note — export the marked frame, import it, then resize and position the layer so it roughly lines up. A 12-note revision round means doing that translation 36 times before a single real edit is made, and every one of those handoffs is a place the marked-up preview and the working file can quietly drift apart — a screenshot resized a few percent off, or a layer nudged during the paste.
Screenshotting a note into a layer is a reasonable fix for a real gap — a browser tab genuinely cannot place anything on a Photoshop canvas. The fix is expensive per round, not wrong in principle.
What happens when the panel opens the same file
Appruva's Photoshop panel is a UXP extension for Photoshop 2023 (24.0) or newer, on macOS or Windows, docked next to the document. It closes the gap above by starting from the other side: instead of a note that has to be manually carried into Photoshop, the panel opens the same round the client reviewed, inside the app where the fix happens.
It knows which frame is open without being told — an XMP stamp first, then filename matching that's folder-aware and suffix-tolerant, and only asks the retoucher when neither resolves. Once it knows the frame, the notes appear in the panel itself, numbered to match the badges the art director already saw in the gallery, arriving live over a WebSocket where the network allows it and on a 45-second poll where it doesn't. The markup itself lands as a real layer — a vector overlay sized to the document, transparent everywhere the markup isn't, with the option to put each note on its own named layer. Clicking a note in the panel jumps to and marks the area it points at, so see note 4 stops meaning a scroll-and-squint search across a canvas that's several times larger than the screen showing it.
A crop request is the clearest example of what this removes. A crop guide drawn in the gallery becomes, in the panel, an Accept crop button: one click crops the canvas to that guide (nothing outside it is lost), ticks the note, and re-maps every other shape on the document so the rest of the markup still lands on the same pixels after the crop. A note that references a color — match this skin tone — can carry a reference image that opens beside the working document as its own file, so the eyedropper has something real to sample from instead of a thumbnail in an email or a color guessed from a compressed preview. Ticking a note off happens in the panel as the fix is made, not in a separate tab afterward, so the list of what's done never depends on the retoucher remembering to go back and update a gallery once Photoshop is closed.
Delivery without leaving Photoshop
The same logic applies on the way out. Deliver exports the file by the studio's own recipe, uploads it, stacks it as a new version, closes the notes that were ticked, and posts a delivery note describing what was addressed and what wasn't — all from inside Photoshop, without a parallel trip back to a browser to mark the round complete.
For a batch of files, the panel can deliver or export every open document in one pass. It runs the exports sequentially, because Photoshop's own document operations are single-threaded and there is no way around that from a panel, but it uploads three files at a time, so a slow upload doesn't stall the next export from starting. One failed file in a batch of forty doesn't stop the other thirty-nine — it's flagged, and a Retry re-runs only the ones that failed rather than the whole batch again.
Handing a file to a freelance retoucher without a shared Dropbox
The panel also changes who can get access to a round in the first place. A freelance retoucher needs no Appruva account at all — access is a share link created with Retoucher access, and revoking it ends their access on the next request they make. That's a narrower grant than the usual alternative, a folder invite to a shared Dropbox that nobody remembers to revoke once the job is done and that keeps working for anyone who ever had the link, long after the retoucher who needed it has moved on to other clients.
Storage writes on that link stay admin-only underneath: delivery goes through a server function that authorizes the caller's session rather than trusting whatever the client sends. That's a detail worth a sentence in any workflow that hands files to someone outside the studio, freelance or not — the access a shared folder grants and the access a scoped, revocable link grants are not the same shape of risk.
What the panel still doesn't do
None of the above is a reason to stop using a web gallery, and a few honest limits are worth stating plainly rather than discovering later.
| Claim | Status |
|---|---|
| Listed on Adobe Exchange | Not listed — installs by hand today |
| Lightroom plugin | Does not exist |
| Capture One plugin | Does not exist |
| Delivery file formats | JPEG or PNG only, not TIFF or PSD |
| Runs inside Photoshop | Built and working end to end |
It is a Photoshop panel, specifically — there is no equivalent for Lightroom or Capture One, and none is implied. Delivery is JPEG or PNG; a TIFF or PSD round-trip isn't part of it. And because it isn't distributed through the Creative Cloud marketplace, getting it onto a machine today means installing a .ccx file directly rather than a one-click install from inside Photoshop — the honest sentence is that this is a manual step, not the plugin-browser experience Adobe Exchange users are used to, and it's worth checking the current install path on the Appruva site rather than a blog post that will drift out of date. The other real bridge, separate from this panel, is Retouchable, where linked clients pull Appruva shoots directly into its own retouching flow.
Which tool for which stage
The practical split is where the work is happening. Discovery, first-round feedback, and stakeholder sign-off are gallery jobs — that's still the fastest way to get a wide group looking at the same frames and voting on selects, and comparison tools like stills-focused review platforms are built around exactly that. Once a round has notes that need pixels changed, the work moves to Photoshop whether or not any tool is watching — the only question is how many manual steps sit between the note and the layer.
Web gallery
- Fastest way to collect wide feedback
- Notes are screen coordinates on a preview
- No connection to a Photoshop layer or document
- Sign-off and version history live here
Photoshop panel
- Notes appear on the open document itself
- Markup lands as a real, editable layer
- Crop and reference-image handling built in
- Delivery closes the loop from inside the app
Neither column replaces the other. The gallery is where a client or a room full of stakeholders decides what needs to change; the panel is where that decision becomes a pixel. Treating them as competing tools is the mistake — the useful question is only ever which stage of the round you're in — and a studio that tries to force one tool to do both jobs usually ends up rebuilding the other one badly inside it.
Frequently asked questions
Is the Appruva Photoshop panel available on Adobe Exchange?
No. It is not listed on Adobe Exchange or in the Creative Cloud plugin browser. It installs as a .ccx file directly, which needs developer mode enabled on the machine — check the current install steps on the Appruva site rather than a blog post, since that path can change.
Does the panel work with Lightroom or Capture One?
No. It is a Photoshop panel only — there is no Lightroom plugin and no Capture One plugin. The other integration Appruva offers is Retouchable, where linked clients pull Appruva shoots directly into its own retouching flow, which is a separate bridge from the Photoshop panel.
Can a freelance retoucher use the panel without an Appruva account?
Yes. Access is granted through a share link created with Retoucher access, and it needs no account on their end. Revoking the link ends their access on the next request they make.
What Photoshop version does the panel require?
Photoshop 2023 (version 24.0) or newer, on either macOS or Windows.
What file formats can the panel deliver?
JPEG or PNG. It does not deliver TIFF or PSD files, so it isn't a fit for a workflow that needs a print-master round trip.