Why Lightroom CC has no plugins (and Classic does)

By David · August 4, 2026 · 9 min read

I build plugins for Lightroom Classic. Seven of them, at this point. And the support email I answer more than any other goes something like this: "I installed the plugin but I cannot find the Plug-in Manager anywhere."

Every single time, the answer is the same. They are in the wrong Lightroom.

This is not a case of someone missing a menu item. There are two completely different programs both called Lightroom, they ship in the same subscription, they have nearly identical icons, and only one of them can run plugins at all. Adobe's naming has been muddled since 2017 and it is still catching people out in 2026. So here is the whole thing in one place: what the difference actually is, why plugins only work in one of them, and how to tell in about five seconds which one you are staring at.

The short version: there is no plugin SDK in the cloud app

Lightroom Classic ships with a plugin architecture. It is a documented SDK, written in Lua, with a Plug-in Manager under the File menu where you add and remove plugins. Hundreds of plugins have been built against it over nearly two decades, from Jeffrey Friedl's export tools to Negative Lab Pro to my own publish services.

The cloud Lightroom has none of that. No SDK, no Plug-in Manager, no folder to drop a plugin into. It is not that plugins are hard to install there or that Adobe has not gotten around to it. There is nothing to install into.

Adobe's own feature-request forums have threads asking for third-party plugin support in the cloud app going back years. They are still open. Treat plugin support there as a thing that does not exist rather than a thing that is coming.

Which Lightroom do I even have?

Fair question, because Adobe has renamed these apps more than once. Here is the current state.

Lightroom Classic is the desktop program with the Library, Develop, Map, Book, Slideshow, Print, and Web modules across the top. It keeps a catalog file on your drive and your photos stay wherever you put them. Mac and Windows only.

Lightroom is the cloud one. Adobe called it Lightroom CC when it launched in 2017, then dropped the CC, which is why half the internet still calls it Lightroom CC and the other half calls it Lightroom desktop. Same app. It stores your original files in Adobe's cloud and runs on desktop, phone, tablet, the web, and ChromeOS.

The five-second test: open the File menu and look for Plug-in Manager. If it is there, you are in Classic and you can install plugins. If it is not, you are in the cloud app and no plugin will ever appear. A second tell is the left-hand panel: Classic shows Folders and a Publish Services section at the bottom left. The cloud app shows Albums and has no Publish Services at all.

Why Adobe built it this way

This is not laziness, and understanding the reason makes it clear why the situation is unlikely to change.

Lightroom Classic plugins run on your machine, with access to your file system. A publish plugin like mine reads the rendered JPEG that Lightroom just wrote to a temp folder, uploads it, and writes the remote photo ID back into the catalog. Every part of that assumes there is a local disk, a local catalog file, and a process running on your computer that can be handed a Lua script.

The cloud app has none of those things in the same way. Your originals live on Adobe's servers. The mobile and web versions have no file system a plugin could reach, and no way to run arbitrary third-party code. Adobe would have to build and secure an entirely separate server-side extension system, then ship it identically to iOS, Android, web, and desktop. They chose a closed app instead. Whatever you think of that choice, it is an architectural one, not an oversight.

What Classic can do that the cloud app cannot

Plugins are the headline difference but they are not the only one.

Publish Services deserve a callout, because they are the feature most people do not realise they are giving up. A Publish Service is a two-way link between a collection in your catalog and somewhere else. Photos go out, and Lightroom remembers what it sent. Re-edit one and it flips to Modified so you can push the update. Nearly every publishing plugin, mine included, is built on top of that. The cloud app has share links, which is a different thing: a snapshot you send, with nothing tracking it afterwards.

What plugins actually get you in Classic

Since the point of finding out about plugins is presumably to use one, here is the shape of what is out there.

Publishing and backup. Lightroom can export a folder of JPEGs, but it cannot keep a cloud album in sync on its own. My Google Photos and Google Drive plugins add Publish Services that push edits straight up and update the cloud copy in place when you re-edit. Both are $19 one-time. Jeffrey Friedl's donationware exporters cover Flickr, SmugMug, Zenfolio and a long tail of others.

Finding and tagging. Lightroom's search only matches text you already typed, and People View gets unreliable as a library grows. Smart Search runs a CLIP model locally so you can type "foggy harbor" and get the photo without ever having keyworded it. Face Tagger swaps in ArcFace embeddings for people-tagging. Both $39 one-time, both run on your own machine with nothing uploaded.

Jobs Lightroom simply does not do. Instagram Grid Planner sequences a feed grid by color flow ($19). Look Slots gives you nine develop clipboards instead of Lightroom's one ($29). Keptfolio turns a collection into a hosted portfolio site ($49/year, hosting included).

Editing. Topaz Photo AI, the Nik Collection, DxO PureRAW, LRTimelapse and Helicon Focus all hook into Classic. None of them work in the cloud app either.

If you want the fuller picture, I keep a running roundup of the best Lightroom Classic plugins with what each one is for.

What if I actually prefer the cloud workflow?

Then use both. This is the part people miss: the standard Photography Plan includes Lightroom Classic and the cloud Lightroom together. You are not choosing between two products you have to buy separately. Classic is very likely already sitting in your Creative Cloud app waiting to be installed.

The workflow most photographers I hear from settle on is Classic as the home base, where the catalog, the plugins, and the serious editing live, with the mobile app as a companion for culling on a train or showing a client something on a phone. You can sync selected collections from Classic up to the cloud to get them onto your phone, which gives you most of the mobile benefit without giving up the plugin architecture.

The one case where the cloud app genuinely wins is if you shoot mostly on a phone, edit on a tablet, and never want to think about a catalog file. That is a real workflow and Classic would be a bad fit for it. You just cannot run plugins there, and no amount of wanting it will change that.

How to install a plugin in Lightroom Classic

Once you are in the right app, it is a two-minute job:

1. Download the plugin and unzip it. You get a folder whose name ends in .lrplugin.
2. In Lightroom Classic, open File > Plug-in Manager.
3. Click Add at the bottom left, select the .lrplugin folder, and click Done.
4. Restart Lightroom Classic. A green light next to the plugin name means it loaded.

Two things that cause most of the "it will not load" emails I get. On Windows, unzip with Extract All rather than opening the zip and dragging the folder out, or you end up adding a folder that is still inside the archive. And do not put the plugin in Program Files, where Windows permissions will block it. Anywhere in your Documents folder is fine.

FAQ

Can I use Lightroom CC plugins on mobile?

No. The mobile Lightroom apps are the cloud version, so they have no plugin support for the same reason the cloud desktop app does not. There is no Plug-in Manager on iOS or Android and no way to sideload one. Presets are the only thing you can add, and presets are not plugins.

Is Lightroom Classic being discontinued?

Adobe has kept shipping updates to Classic alongside the cloud app every year since the split in 2017, and it remains the version professional workflows are built on. I would not build a business on a program I expected to disappear, and seven plugins in, I have not seen a signal that it is going anywhere.

I bought a plugin and I am on the cloud app. What now?

Install Lightroom Classic from your Creative Cloud desktop app. If you are on the Photography Plan it is included at no extra cost, so it is a download rather than a purchase. Your existing cloud photos stay where they are; Classic runs alongside.

Do presets work in both?

Yes, and this is the thing that confuses people most. Presets are just saved slider settings, and both versions handle them, syncing through Creative Cloud. Plugins are actual code that extends what the app can do. A site telling you it has "Lightroom CC plugins" is almost always selling presets.

Can I move my catalog from Classic to the cloud version?

You can migrate photos up, but you lose the things that make Classic Classic: your folder structure, collection hierarchy, Publish Services, and every plugin. It is a one-way trip in practice. Sync selected collections instead of migrating wholesale if what you want is phone access.

Which one is faster on a big library?

Classic, once a library gets past a few tens of thousands of photos. It reads from a local catalog and local previews rather than waiting on uploads. Photographers shooting high volume on deadline, weddings and events especially, tend to find the cloud app's upload step impractical as a primary workflow.