clientgallery.io

Lightroom

ShootProof Lightroom Plugin Keeps Crashing? What Is Documented

ShootProof publishes no crash list. It does publish a reliability disclaimer on every plugin article, a version and compatibility rule, and three failure modes with fixes. Here they are, quoted.

Updated 4 September 2026

If you searched for this, something went wrong in Lightroom Classic and the ShootProof publish service was in the middle of it. This page will not tell you the plugin crashes, because ShootProof does not say that anywhere and neither should we.

What ShootProof does say is more useful, and it is printed at the top of every article it publishes about the plugin. Every quotation below comes from a ShootProof page fetched on 4 September 2026, and each one is listed in the Sources section at the end.

The short answer

ShootProof publishes no crash documentation for its Lightroom plugin. There is no known-issue page, no crash list, and no deprecation or end-of-life notice. Anything you read describing a specific crash is a user report, not a vendor statement, and it should be read that way.

What ShootProof does publish is a reliability disclaimer and three documented failure modes. The disclaimer appears on every plugin article, in ShootProof's own words:

"ShootProof enables some third-party plugins, such as the Adobe Lightroom Plugin, which are developed outside of our platform... While we enable access to these select third-party plugins, we cannot always guarantee their reliability because they are not directly controlled by our team and processes."

That is the important sentence on this whole page. The plugin is how a lot of studios move every frame of a job from the catalog to the client, and the platform it delivers to declines to guarantee it works. Nothing in that is dishonest of ShootProof. It is a clear disclosure of where the plugin sits in their support boundary, and it tells you exactly how much of your delivery workflow you should be resting on it.

Version, requirements and the date on the docs

Before troubleshooting anything, confirm you are inside the supported envelope. ShootProof states the version and the requirements plainly.

What ShootProof publishesVerbatim
Current version"The latest version of the ShootProof Lightroom plugin is 2.10."
Which Lightroom"This publish service works with Lightroom Classic for desktops."
Minimum version"The ShootProof Lightroom Plugin is only compatible with Lightroom Classic CC v6 or newer."
What it isA Lightroom publish service that syncs photos and album structures and lets edits be republished
Album depth"Galleries can have up to 4 levels of Albums/Sub Albums."

One neutral fact worth stating: those articles were last updated in March 2024. That is a date, not a verdict. It does not mean the plugin is abandoned, and ShootProof has published no deprecation notice. It does mean the published guidance predates two and a half years of Lightroom Classic releases, so if your failure is specific to a recent Lightroom version, the help center will not have an answer for it.

The three documented failure modes, and their documented fixes

These are the only plugin problems ShootProof documents. They are worth working through in order, because two of them are silent: they do not produce an error, they produce a wrong gallery.

1. The install error caused by multiple copies. ShootProof documents an install error that comes from having more than one downloaded copy of the plugin on the machine. The published fix is to delete every instance of the plugin and re-add a single one. If you have downloaded the plugin more than once over the years, and most people have, this is the first thing to clear. Check your Downloads folder as well as wherever you keep the plugin permanently.

2. Removing the plugin is destructive, and ShootProof warns against it directly. Verbatim: "you should never Delete the plugin... Deleting the plugin will remove images from your existing Galleries/Albums within Lightroom". This matters because deleting and reinstalling is the reflex fix for anything that misbehaves. Here it is the one action the vendor tells you not to take. Read the install article before you touch the Plug-in Manager, not after.

3. The sync rule: change things on the Lightroom side. ShootProof documents that changes should be made in Lightroom rather than in ShootProof, or "Lightroom will be out of sync with your ShootProof account". If you rearranged albums in the browser and then published from the catalog, the two are now describing different structures. That is documented behaviour, not a fault.

And the structural cap. "Galleries can have up to 4 levels of Albums/Sub Albums." If you are pushing a deeply nested collection tree from Lightroom, four levels is the published ceiling on the receiving end.

Before you blame the plugin

This checklist is useful whether you stay on ShootProof or not. Work down it before concluding the plugin is broken.

CheckWhat you are confirming
One copy onlyDelete every instance of the plugin file, then add exactly one back in the Plug-in Manager. This is ShootProof's documented install fix.
Lightroom Classic, v6 or newerNot the cloud Lightroom. The publish service is documented for Lightroom Classic on the desktop, CC v6 or newer.
Never delete to fixDeleting the plugin removes images from existing galleries and albums inside Lightroom, by ShootProof's own warning.
Edit on the Lightroom sideStructural changes made in the ShootProof browser interface put the catalog out of sync with the account.
Album depth under four levelsFour levels of albums and sub albums is the published maximum.
Your photo capAn upload that will not complete may be an account at its plan limit rather than a plugin fault.

The last row is the one people miss, so it deserves the detail. ShootProof plans are capped by photo count today, and the cap is a live ceiling, not a yearly budget. Verbatim: "The photo count in each plan is the total number of photos you can have online in your ShootProof account at any given time... Upload new photos, and you'll begin using that space." Deleting photos frees that space back up. The current tiers run 100 photos on Free, then 1,500, 5,000, 25,000 and Unlimited.

Be careful how you reason about this, because ShootProof does not publish what happens at the moment you cross the line. No help article states whether uploads are blocked, whether overage is billed, or whether there is a grace period. So treat the cap as something to rule out, not as a diagnosis. Check your photo count in the account before you spend an evening on the plugin.

One more thing changes soon and is worth knowing while you troubleshoot. ShootProof has published that "Our plans will transition from photo-count-based storage to GB-based storage on September 23rd, 2026", with "Our plan prices are not changing". Accounts holding too much data for the equivalent new plan are automatically moved up, with a one-year discount to the old price, and the remedy ShootProof offers is "You can archive your photos to free up space." Archiving is not free below the top tier, and archived galleries stop being live for clients, which is covered in our guide to what ShootProof archiving actually costs.

How the clientgallery.io plugin behaves

Our Lightroom Classic plugin is first-party. It is built and maintained by the same people who run the galleries it publishes to, so there is no third-party boundary to disclaim. What follows is behaviour, described exactly as the plugin works today.

It installs two things: a clientgallery.io destination in Lightroom Classic's Export dialog, and a clientgallery.io Publish Service in the left panel.

The key is validated before the export starts. You paste your studio key once and press a Check button. It confirms the key against the account there and then, so a typo surfaces immediately instead of 300 photos into a render. That single button is the difference between a five-second correction and an evening.

Publishing pushes deltas. The gallery appears as a published collection. Lightroom tracks which photos are New and which are Modified, and one click of Publish pushes exactly those. Develop edits mark a photo Modified. Metadata-only changes do not trigger a re-push. Re-publishing updates the same gallery rather than rebuilding it, so the link you already sent the client keeps working.

The collection is the gallery. Removing a photo from the published collection removes it from the live gallery. Renaming the published collection renames the gallery. Deleting the published collection deletes the gallery. That is powerful and it is sharp, and you should know it before you tidy up your catalog. It is the mirror image of ShootProof's warning: there, deleting the plugin strips images from albums inside Lightroom; here, deleting the collection removes the gallery on the web.

Picks come back in. From the Library menu, Plug-in Extras, Import clientgallery.io Picks. Paste the studio key and the gallery link you already sent the client. The plugin matches by filename against the catalog. Likes come in rated 3 stars. Loves come in rated 5 stars and flagged as Picks. The client's colour labels become Lightroom colour labels, filterable in the Library filter bar and usable in smart collections. Everything found is gathered into a collection named after the gallery. It is re-runnable at any time. The guide to pulling client picks back into Lightroom walks the whole round trip.

Where we are behind ShootProof. Galleries in our Publish Service are flat. There are no nested collection sets. ShootProof documents four levels of albums and sub albums, and on that specific point ShootProof does more than we do. If your delivery depends on a deep album tree published straight from the catalog, that is a real reason to stay. Two other limits are ours and we state them plainly: a gallery holds 1,000 photos, and the plugin tells you to start a second one when it fills, and a free account holds one gallery, which the plugin says before it fails rather than after.

The rest is the flat plan behind it. One price, 10 $/month or 100 $/year, with unlimited galleries, photos and clients under fair use, your own subdomain and no platform branding on any client-facing page. Fair use in figures, because a page arguing against caps owes you the numbers: uploaded photos are browser-compressed proof JPEGs of about 0.6 MB each, hosted for as long as the account exists, with abuse tripwires of 1,000 photos per gallery and 250 GB of proofs per paid account, which is hundreds of thousands of photos. Free accounts hold 5 GB and one gallery. Full-resolution delivery is a paid feature: you upload a full-resolution ZIP per gallery, it stays live for 3 days per handoff and can be re-uploaded any time, with 100 GB of standing ZIPs per account.

When you should stay with ShootProof

Give ShootProof its due, because on the commercial side it is genuinely good and better than several competitors.

ShootProof takes no commission on sales, on any plan. Verbatim: "ShootProof never charges a commission on your sales." The complete official fee list is archiving plus credit-card processing through ShootProof Pay. That is unusual. Several platforms in this category take a percentage of print revenue on their entry tiers.

Your branding, logo and watermark are included on every tier including Free, with no branding-removal upcharge published anywhere. Again, that is better than the norm. A number of competitors put branding removal behind the first paid plan and take it away again if you downgrade.

So the honest recommendation is straightforward. If you sell prints, albums or wall art through ShootProof, stay. You are on a zero-commission storefront with your own branding, and the plugin friction in this page is a smaller cost than rebuilding your sales side somewhere else.

clientgallery.io is for the other studio: the one that delivers finished JPEG galleries and gets paid separately. We host JPEGs. We do not warehouse RAW files or master video, and that is what keeps the price flat. There is no print store, so there is nothing here for a studio whose revenue runs through one. The ShootProof alternative page sets the two side by side, and the alternatives index covers the rest of the field.

Sources

Every quotation and figure above traces to one of these. All ShootProof pages fetched 4 September 2026. ShootProof prices are US dollars as published.

Frequently asked

Does ShootProof publish a list of Lightroom plugin crashes?

No. There is no known-issue page, no crash list and no deprecation notice in the ShootProof help center. What it does publish is a reliability disclaimer on every plugin article, stating that the Adobe Lightroom Plugin is developed outside its platform and that ShootProof cannot always guarantee its reliability because it is not directly controlled by its team and processes.

What is the current version of the ShootProof Lightroom plugin?

ShootProof states that the latest version of the ShootProof Lightroom plugin is 2.10. It works with Lightroom Classic for desktops and is only compatible with Lightroom Classic CC v6 or newer. Those articles were last updated in March 2024.

Why will the ShootProof plugin not install?

ShootProof documents one install error, caused by having multiple downloaded copies of the plugin on the machine. The published fix is to delete every instance of the plugin and then add a single one back in Lightroom's Plug-in Manager.

Is it safe to delete the ShootProof plugin and reinstall it?

ShootProof warns against it directly: you should never Delete the plugin, because deleting the plugin will remove images from your existing Galleries and Albums within Lightroom. Read the install article before touching the Plug-in Manager, since deleting is the normal reflex for a misbehaving plugin and here it is the action the vendor tells you to avoid.

Why is my ShootProof account out of sync with Lightroom?

ShootProof documents that changes should be made in Lightroom rather than in ShootProof, or Lightroom will be out of sync with your ShootProof account. If you rearranged albums in the browser and then published from the catalog, the two are describing different structures. That is documented behaviour rather than a fault.

Could the problem be my photo cap rather than the plugin?

It is worth ruling out. ShootProof states that the photo count in each plan is the total number of photos you can have online in your account at any given time, running from 100 photos on Free through 1,500, 5,000, 25,000 and Unlimited. ShootProof does not publish what happens at the moment you exceed the cap, so check your photo count before assuming the plugin is at fault. Plans move from photo counts to GB-based storage on 23 September 2026, with prices unchanged.

How does the clientgallery.io Lightroom plugin differ?

It is first-party, so there is no third-party reliability disclaimer. A Check button validates your studio key before the export starts, so a typo surfaces immediately rather than 300 photos in. The Publish Service tracks New and Modified photos and pushes only those, and re-publishing updates the same gallery instead of rebuilding it. Client likes come back as 3 stars, loves as 5 stars and flagged, and colour labels as Lightroom colour labels. One limit is ours: published galleries are flat, with no nested collection sets, where ShootProof documents four levels of albums and sub albums.

Your client galleries, under your name

Unlimited galleries, your branding, one-click Pixieset import, and a Lightroom plugin, all on a flat 10 $/month with everything included. Your first gallery is free.

See the Lightroom plugin

Related guides

ShootProof Lightroom Plugin Keeps Crashing? What Is Documented