Lightroom Classic to Google Drive: 3 ways that still work in 2026

By David · July 7, 2026 · 9 min read

You finish an edit, you want it on Google Drive to share with a client or keep off-site, and you open the Export dialog expecting a "Google Drive" option. It is not there. Lightroom Classic will happily write to a local folder or a handful of built-in services, but Drive is not one of them.

For years the fix was a free plugin, and the advice on most forum threads still points there. The trouble is that Google tightened its OAuth verification rules in 2024, and the best-known free option stopped working for a lot of people overnight. So the old answers now half-work. Here are the three routes that actually get photos from Lightroom Classic to Google Drive in 2026, what each is good at, and how to choose.

Why doesn't Lightroom Classic export to Google Drive directly?

Adobe ships export targets for your local disk plus a short list of services, and it leaves the rest to plugins. That is by design: the Export dialog and the Publish Services panel are both extensible hooks, and third-party developers are meant to fill the gaps for services like Drive, Dropbox, or SmugMug.

The catch in 2026 is what it now takes to touch a Google account. Any tool that signs into Drive on your behalf has to pass Google's OAuth verification, and that bar climbed sharply in 2024. It is a real, ongoing process, not a one-time checkbox, which is exactly why the pool of working free options thinned out. The plugins that survived are the ones whose authors kept up with verification.

The three routes at a glance

All three end with your photos sitting in a Google Drive folder. Where they differ is effort, and whether they remember what they already sent, which matters the moment you re-edit a photo and send it again.

Route 1: Export to a Drive for desktop folder (free)

This is the no-plugin path, and it is genuinely fine for the occasional export. The trick is that you are not exporting to Drive at all. You are exporting to a normal folder on your computer, and letting Google's Drive for desktop app carry it up to the cloud for you.

1. Install Drive for desktop and sign in. A Drive location appears on your machine, like any other folder.
2. Create a folder inside it for your exports, for example Drive/Lightroom exports.
3. In Lightroom Classic, select your photos and choose File → Export.
4. Set the Export Location to that synced folder, pick your format and resolution (JPEG for sharing, or original/TIFF for archiving), and click Export.
5. Drive for desktop uploads the new files on its own. Check drive.google.com to confirm they arrived.

The honest downside is that this is a plain export with no memory. Re-edit a photo next month and export it again, and you get a second file sitting next to the first, or you overwrite it by hand and hope you picked the right one. For a handful of finals you will never touch again, that is no problem. For a folder you maintain over a season, the bookkeeping adds up fast.

Route 2: A third-party plugin (and the 2024 catch)

For over a decade the go-to answer was Jeffrey Friedl's "Export to Google Drive" plugin. It is a fine piece of work: it supports both Export and Publish, runs on Mac and Windows, and goes back to older Lightroom versions. If you already have it authenticating on your machine, there is no reason to change.

The problem is that many people cannot get it to sign in anymore. When Google tightened OAuth verification in 2024, a lot of users hit authentication failures that were never the developer's fault. Getting a one-person plugin verified to touch a Google account is a heavy, recurring lift. Other multi-service options like the Photo Upload plugin exist and cover Drive alongside Dropbox and the rest, but the same verification reality applies. The practical advice: test it end to end before you rely on it, and have a backup plan if the sign-in wall stops you.

Route 3: A Publish Service that keeps Drive in sync

That gap, a maintained tool that signs in reliably and does not make duplicates, is why I built the Google Drive plugin. It adds a real Lightroom Classic Publish Service: you publish selected photos to a Drive folder at the resolution and format you choose, originals included, and the connection stays live.

The part that saves the most time is what happens the second time. When you re-edit a photo and publish again, the plugin updates the copy already on Drive instead of stacking a new one next to it. That is the whole difference between a plain export and a Publish Service.

It is OAuth-verified with Google, so it does not hit the sign-in wall that stopped the older free plugin. It runs on both Mac and Windows because it is built in Lightroom's own scripting language, and it is $9.99 one-time with no subscription.

Export or publish: which should you use?

It comes down to whether the photos will change again. A plain export is a one-shot copy, and that is exactly right for a final deliverable or a one-time archive you will never revisit. A Publish Service is a living connection, and that is what you want for a set you keep re-editing, a client gallery you refresh, or a portfolio folder you top up over time.

Plenty of photographers use both, and so do I: a manual export for the odd one-off, and a Publish Service for anything I expect to touch more than once. If Publish Services are new to you, I walked through the state-tracking model behind them in a separate post, and it is the same idea I use across the other organizing and publishing plugins.

Don't forget the catalog

One caution before you rely on any of this for safety: none of these three routes back up your Lightroom catalog, and in Lightroom Classic your edits live in the catalog, not the photos. Sending your exports to Drive protects the pixels, not your develop settings. For the full off-site story, including catalog backups and where Drive fits in a 3-2-1 plan, I covered that in the Google Drive photo storage guide.

Common questions

Is there a free way to get Lightroom Classic photos to Google Drive?

Yes, Route 1. Export to a folder that Drive for desktop syncs, and it lands in the cloud for nothing. What you trade for free is memory: each export is a fresh copy, with no tracking of what you already sent.

Does Jeffrey Friedl's Export to Google Drive plugin still work?

Sometimes. It is well built and still installs, but Google's 2024 OAuth verification tightening left many users unable to sign it into their account. If it authenticates for you, it is a solid free option. If it does not, that is the wall a verified plugin is built to avoid.

Can I send full-resolution originals or RAW, not just JPEGs?

Yes. A manual export can copy the original files, and the Google Drive plugin lets you choose the format and resolution, originals included. Drive stores whatever you upload byte-for-byte, which is why it works as real archival storage. There is more on how Drive handles RAW in the storage guide.

Will the Google Drive plugin run on Windows?

Yes. It is written in Lightroom's own scripting language, so it runs on both Mac and Windows versions of Lightroom Classic. There is no separate app to install beyond the plugin itself.

What is the difference between the Google Drive and Google Photos plugins?

The destination. Drive stores your files as files, so it suits archiving and sharing folders, while Google Photos is a gallery built for browsing and search. If Photos is what you are after, I covered sending Lightroom Classic to Google Photos separately.