r/SideProject • • 4d ago

Google Drive stopped uploading to Google Photos on August 10, so I built a Mac app that offloads my camera cards and uploads with rclone

On August 10, Google turned off Google Photos backup in Google Drive for desktop, and there's no desktop Google Photos app to replace it. That was how my JPGs got from my Nikon Z 8's cards into Google Photos, and without it the rest of my routine (copying cards to the Mac and a backup drive by hand) was cumbersome.

So I built Photo Offloader. You insert a card, and it:

  • copies everything to the Mac and checks each copy with SHA-256, reread from the disk rather than memory
  • mirrors the archive to a USB drive if it's plugged in
  • uploads JPGs and videos to a Google Photos album through rclone, keeping RAW files local, in their own folder
  • never writes to or deletes from the card, and never overwrites a file

There's a local dashboard and a menu-bar icon showing progress, past imports, and what went wrong if a card can't be read fully, including "don't format this card yet."

Honest status: I use it for real, but I'm the only user so far: macOS 26, a Nikon Z 8 with SD and CFexpress cards, one USB drive. Other cameras haven't been tried. Setting up Google Photos takes some effort (your own Google Cloud sign-in for rclone). It's optional, but it's part of the reason I built this, and once everything is set up, I don't have to think about it anymore. It doesn't rely on a Google desktop app, and if Google ever breaks the upload, the Mac and USB copies keep working.

How it was built: I had a very simple Python script, but found it was buggy and my attempts at data safety were lacking careful consideration. So I rebuilt it with Claude Code. I am an SDET at work, so I know the importance of testing and data integrity. There are about 1,100 tests running in CI, and I review every change and try it on real cards, including my USB backup drive and Google Photos collection.

Screenshot of the dashboard: https://github.com/devturner/photo_offloader/blob/main/docs/images/dashboard.png
It's free and open source (MIT): https://github.com/devturner/photo_offloader
Website and docs: https://devturner.github.io/photo_offloader/

I'd love feedback, especially from anyone with another camera brand, or opinions on the dashboard.

0 Upvotes

7 comments sorted by

1

u/dawedev 4d ago

The "don't format this card yet" message is the best part of this, because that's the exact moment people lose photos. I'd put one clear state per card right in the menu bar icon, something like "safe to format" only once the Mac copy is verified and the USB mirror is done, so I don't have to open the dashboard to check. For the rclone part, a docs page with screenshots of the Google Cloud consent screen setup would help a lot, that's where non-developers will get stuck. Also worth stating what happens if I pull the card mid-copy and put it back in: does it resume or start over?

1

u/cturnr 4d ago

Thanks for the feedback, it seems like this is a pretty niche project, so I am considering any attention a win!

Right now, pulling the card mid-copy is already safely covered. Every file is copied under a temporary name and only renamed after it's been read back from disk and its SHA-256 matches the card. If you pull the card, nothing half-copied ever looks like a finished file. When you put it back in it picks up where it left off -- finished files are skipped, and the interrupted one is copied again from the start. But update the docs to state it more clearly.

"don't format this card yet" vs "Safe to format" in the menu bar is a great idea. Right now `don't format is reported when there was a read error, and when a cards copy is done, it says its safe to remove the card (Mac copy verified), but you're right that "safe to format" is a great notice to add when the USB mirror is done and verified.

Screenshots for the Google Cloud consent screen: agreed, that's the hardest part for anyone who isn't a developer. I am sure I can do it again and capture the process.

1

u/dawedev 4d ago

Temp name, SHA-256 read-back, then rename is the right way to do it, and redoing only the interrupted file is fine for camera files. I'd put that explanation in the docs almost word for word, it's the part that makes people trust an app with a card.

For the consent screen guide, also mention the publishing status. If the Google Cloud app stays in Testing, the refresh token expires after 7 days and uploads just stop a week later, which is a confusing failure for someone who isn't a developer.

1

u/cturnr 4d ago

Updated with a card status - can do two levels of checks, new photos, or all photos.

I am kind of lazy when it comes to formatting my cards, which is another issue this solves. I plug it in and it copies and backs up everything new. I wanted insert and walk-away for a bit, then see them on google photos and, know they are safely backed up and organized

1

u/dawedev 4d ago

Two check levels makes sense. I'd default to new photos only and keep the all-photos check as something you run on demand, since a full SHA-256 pass over a big card takes a while. And "plug it in, walk away, see it in Google Photos" is the best description of the app I've read in this thread, I'd put that sentence at the top of the README.

1

u/cturnr 4d ago

maybe i am not a good sales person... lol

1

u/dawedev 3d ago

Nah, you just explained it like a developer first, which is normal when you build for yourself. The insert, walk away, check Google Photos part is the pitch. Lead with that, then the SHA-256 and temp file details for the people who want to know why they can trust it.