Why Isn't My Lightroom Classic Publish Service Showing Up?

By David · July 27, 2026 · 8 min read

I build publish-service plugins for a living - Google Photos, Google Drive, and a hosted portfolio service all live in the exact panel you're staring at right now. Most forum advice stops at "check the Plug-in Manager." That's step one, not the whole answer.

Why did my Lightroom Classic publish service disappear or stop showing up?

A publish service that was working yesterday and is gone today almost always traces back to one of these:

• The plugin got disabled or threw an error. A red or gray status dot in the Plug-in Manager means Lightroom stopped loading it.
• The .lrplugin folder moved, got renamed, or was replaced mid-update. Lightroom stores an absolute path, not a live link.
• A Lightroom Classic update changed something the plugin depended on. This is the case generic advice skips, and it's the one worth understanding at the SDK level below.
• The service is still there, but you're looking in the wrong place. Publish services live in the Library module's left panel, not in Plug-in Extras or the File menu.

Notice what's not on that list: your published photos are never at risk. A publish service is a pointer Lightroom keeps in the catalog - photos already sent to Google Photos, Drive, or wherever stay exactly where they landed, regardless of what happens to the plugin registration.

Is the whole Publish Services panel hidden, or is it just one plugin?

Figure out which problem you actually have first - the fix differs.

Most people land in row two. That's a single plugin, not the whole feature, and it's fixable in under a minute.

How do I check the Plug-in Manager for a disabled, broken, or "can't find plug-in" service?

1. Open File > Plug-in Manager.
2. Look at the status dot next to each plugin. Green means loaded and running. Gray means disabled. Red or a warning triangle means it hit an error.
3. Select the plugin and read the status message under its name - "can't find plug-in" means the stored folder path is broken; a Lua error points at an actual script failure.
4. If it says "can't find plug-in," click Remove, then Add and browse to where the .lrplugin folder actually lives now. This is the single most common fix.
5. If it's just gray with no error, select it and click Enable.

"Can't find plug-in" doesn't mean the folder is corrupted. Lightroom stores an absolute path string when you first add a plugin. Move the folder, rename it, or sync it through a cloud drive that changes the path, and that stored path breaks even though the folder itself is fine sitting one level over.

Why do publish-service plugins break after a Lightroom Classic update?

This is where generic advice falls short. A publish service registers through Lightroom's LrExportServiceProvider API, declared in the plugin's Info.lua manifest. Three specific failure modes show up after a Lightroom Classic update:

• Info.lua's declared SDK version falls out of range. Every Info.lua declares an LrSdkVersion. If a plugin hasn't been updated to declare compatibility with the new Lightroom version, Lightroom can refuse to load it entirely - quietly, with no dialog, just an absent entry or a gray status dot.
• Cached plugin metadata in the Preferences folder goes stale. Lightroom caches parsed plugin manifests to speed up startup. After a major version update that cache sometimes doesn't invalidate cleanly, so Lightroom reads an old registration that no longer matches the folder on disk. A full quit and relaunch - not just closing the catalog - usually forces a fresh read.
• The export service provider table throws during registration. If a plugin's Lua code references an API that changed or was deprecated, the exportServiceProvider table fails to build and the service silently doesn't register - this happens before Lightroom has a UI context to show an error in.

None of this shows up in the Plug-in Manager's status message, which is why "just check the Plug-in Manager" only gets you halfway. If re-adding the plugin doesn't fix it, get the latest version - a maintained plugin ships an updated Info.lua within days of a Lightroom Classic release that breaks compatibility.

How do I re-authorize a publish service without starting your collection over?

If the service shows up but is grayed out or asks you to log in again, that's a credential problem, not a registration problem - and it's the easy case. Every well-built publish plugin separates two things that live in completely different places:

• The OAuth token or API credential - stored by the plugin, often in your OS keychain or a small local preference file. This is what expires or gets revoked.
• The publish collection structure and photo state - stored inside your Lightroom catalog itself: which photos are in which published collection, and whether each one is New, Modified, Published, or Deleted.

Re-authorizing only touches the first one. Click the service, follow the login prompt, grant access again, and Lightroom reconnects the existing collections to the refreshed credential. Your published history and republish queue come from the catalog and were never at risk. The one way to actually lose history is deleting the publish service and choosing to remove its collections - a separate confirmation step, so it's hard to do by accident.

Publish service troubleshooting checklist

In order, fastest fix first:

1. Restart Lightroom Classic fully (quit, don't just close the catalog).
2. Open File > Plug-in Manager and check the status dot and message for the specific plugin.
3. If it says "can't find plug-in," remove and re-add it, pointing at the folder's current location.
4. If it's grayed out with a login prompt, re-authorize.
5. Check you're on the latest version of the plugin, especially right after a Lightroom Classic update - download the current build from the developer's site.
6. If nothing above works, remove the plugin entry (not the collections) and re-add a fresh copy of the .lrplugin folder.

My Google Photos and Google Drive plugins ship Info.lua updates within days of any Lightroom Classic release that changes SDK compatibility, so this checklist stops at step 1 or 2 for our users.

FAQ

Will removing a broken publish service delete my already-published photos?

No. Removing a publish service from the Plug-in Manager or the left panel only deletes Lightroom's local record of the publish relationship. It does not touch photos already sent to Google Photos, Google Drive, or any other destination - those stay exactly where they are.

Why does Lightroom say "can't find plug-in" even though the folder is still there?

Lightroom stores an absolute path to your .lrplugin folder, not a live reference. If the folder was moved, renamed, or sits on a drive that was reformatted with a new volume ID, the stored path breaks even though the folder itself is untouched at its new location.

Does this happen with built-in services like Flickr, or only third-party plugins?

It can happen to any publish service, built-in or third-party, because both register through the same LrExportServiceProvider API. Third-party plugins hit it more often in practice because they live outside Lightroom's own install path and depend on a plugin author shipping a compatible Info.lua after each Lightroom Classic version bump.

Can two publish-service plugins with the same name conflict with each other?

Yes, if you have two versions of the same plugin registered from different folders, Lightroom can load the wrong one or show duplicate entries. This usually happens after a manual reinstall where the old .lrplugin folder was never removed from the Plug-in Manager. Remove the stale entry, keep the folder you actually use, and restart.

Do I need to redo my publish settings after re-authorizing?

No, in almost every well-built plugin. Re-authorizing refreshes the OAuth token or credential the plugin uses to talk to its destination; it does not touch the publish collection structure, the photo-to-album mapping, or the New/Modified/Published state Lightroom tracks per photo. Those live in the catalog, not in the credential.