u/Some-Ad5503

What do you still do manually in Google Photos that should be automatic?

Every trip ends the same way for me: 200 photos on my phone and grandparents waiting for the album. All I want is to hit Enhance on the whole thing before sharing. Google Photos makes that enhance, save, enhance, save, one photo at a time, for half an hour.

Apparently I'm not alone. There's a Google Help Community thread asking for bulk editing that was opened in February 2019, collected 347 "I have the same question" votes, and was locked with no resolution. Bulk share, archive, and delete all exist. Bulk edit never shipped.

There's no Google API for editing photos, so I built Batch for Google Photos, a Chrome extension that automates the same workflow you would normally do by hand. It runs on your device, inside Chrome, and drives Google Photos' own editor across your selection. Pick your photos, choose an action, and it repeats the edit for you: Enhance (Google Photos' own one-tap fix), filters, crop, rotate, add or replace descriptions, and custom presets (edit one photo the way you like, then apply that look across the rest). Visual edits remain reversible through Google Photos' own Revert to Original.

To be clear about what it's for: Batch isn't for the one photo you'd carefully edit by hand. It's for the 200 you'd never edit one by one. A single edit is easy; two hundred is the problem. It gives the whole album a decent baseline, and you can still hand-finish the few that deserve it.

A few things worth being upfront about:

• For editing, your photos never leave Google. Everything runs on your device inside Chrome. Batch never uploads, stores, or processes your photos on a Batch server.
• It's automating the real editor, so a big batch takes real time. It works through the photos while you do something else.
• It also includes library-wide tools to convert live photos to stills, download full-quality copies, or move the main library to Trash.
• There's a free tier for trying the selection tools; larger usage and whole-library actions are paid.

What I'd genuinely like from this community: what batch edit would you actually use? I built the ones from my own trips, but wedding albums, scanned-photo cleanups, and listing photos all seem to want different things. And if you try it on your library, tell me what breaks.

https://chromewebstore.google.com/detail/bulk-edit-delete-download/fnhlolpmhhjdjdlialajdlmlfblchkkh

A lot of us are bumping into Google storage limits. Deleting large videos helps, but I noticed another hidden culprit: live/motion photos.

They look like normal photos, but they often include a short video clip too. Some of mine were several times larger than the still version, and in testing many shrink roughly 70-80% when converted to stills.

So I built Convert to Stills inside Batch for Google Photos.

It automates the annoying workflow: create a still copy, keep the photo, preserve the original date and time, remove the motion, and move the original live/motion photo to Google Photos Trash for 60 days.

You can run it on selected photos, or let Batch work through live/motion photos across your Google Photos library.

A few tradeoffs:

• Location and camera metadata do not carry over
• The original date and time are preserved
• The motion is removed
• Empty Trash when you’re ready to permanently remove originals and reclaim storage
• Start with a small selection before running it more broadly

If the motion is the memory, keep it. But if you mostly care about the still image, this is a much faster way to reclaim space than doing it one by one.

Would love feedback from people fighting Google Photos storage limits. I’m especially curious if you’d use this on selected photos only, or let it work through your live/motion photos across the library.

https://chromewebstore.google.com/detail/bulk-edit-google-photos-w/fnhlolpmhhjdjdlialajdlmlfblchkkh

I’ve been lurking here for a while, and today I finally have one of those tiny launch milestones to share: I got my first paying customer 🚀

The extension is Batch for Google Photos. Google Photos lets you select a bunch of photos for share, delete, archive, and download, but not edit. If you come back from a trip with 300 photos and want to Auto Enhance, filter, crop, rotate, Add Description, or Revert them, you’re still doing it one by one.

Batch adds a button inside Google Photos: select photos, click Batch, pick an action, and it runs Google Photos’ own editor across the selection. No exports, no uploads, no backend photo processing.

The build side is probably more interesting for this sub:

- Plasmo, Manifest V3
- TypeScript and React
- ExtensionPay for payments and Stripe
- Claude Code as a build partner for architecture, iteration, debugging, and refactors
- chrome-devtools-mcp for inspecting the live Google Photos DOM
- No Google Photos editing API, so the extension works by driving Google’s own editor

The hardest part was reliability. Google Photos is a dynamic web app, so this became less of a normal “call an API” project and more of a careful DOM automation workflow: finding the right controls, waiting for UI states, handling failures, and making the extension feel predictable enough that people would trust it with their photo library.

The first payment was small, but it felt different from installs or nice comments. Someone I don’t know paid for a thing I made. That was a cool moment.

It’s live on the Chrome Web Store as Batch for Google Photos. Free tier is 25 photos/month if anyone wants to try it.

I’d love feedback from other extension builders on the listing, onboarding, permissions, pricing, or anything that feels unclear.

https://chromewebstore.google.com/detail/batch-for-google-photos/fnhlolpmhhjdjdlialajdlmlfblchkkh

I built this, sharing that up front.

Google Photos still does not let you edit multiple photos at once. If you want to Auto Enhance, apply a filter, rotate, crop, add captions, or revert a group of photos, you have to open each photo and repeat the same edit one by one.

I got tired of doing that, so I built Batch for Google Photos.

It adds a Batch button to the Google Photos selection toolbar. Select a group of photos, click Batch, choose an action, and it runs the edit across the selected photos using Google Photos’ own editor.

What it supports today:

• Auto Enhance
• Apply Filter
• Auto Crop
• Rotate
• Add Caption
• Revert to Original

A few important notes:

• No uploads
• No downloads
• No server processing
• Your photos stay in Google Photos
• The extension runs in your browser

There’s no Google API for editing photos, so Batch works by driving the existing Google Photos editor for each selected photo.

I would genuinely love feedback from this community. What breaks in your library? What feels confusing? What batch edits would you want next?

I’ll put the Chrome Web Store link and a short demo in the comments so the post itself does not get too link-heavy.

https://reddit.com/link/1tvziwq/video/lawcu07v945h1/player

Building a Chrome extension with three tiers via ExtensionPay: Free, Plus, and Pro. I’m stuck on the upgrade flow between paid tiers.

Here’s what I’m seeing:

extpay.openPaymentPage("pro-monthly") works fine for a new user and opens Stripe Checkout for Pro.

But for an existing customer who previously had Plus and then cancelled, the same call opens the Stripe Customer Portal instead of Checkout. It looks like the planId argument is ignored once a Stripe Customer ID exists.

Stripe Customer Portal plan switching also rejects adding Pro alongside Plus because the plans share the same Product and billing interval. ExtensionPay puts all four paid plans under one Stripe Product, so portal-based switching across tiers does not seem configurable either.

Net result: a Plus user cancels, clicks Upgrade to Pro, lands in the portal, and has no path to subscribe to Pro. The standard flow of “click Upgrade in-app, Stripe prorates, done” does not seem supported.

Has anyone:

1. Found a way to force openPaymentPage to start a fresh Checkout session for an existing or cancelled customer?
2. Restructured ExtensionPay to use multiple Stripe Products, one per tier, while keeping getUser() tier resolution working?
3. Shipped a Chrome extension with multiple paid tiers another way, such as Paddle, Lemon Squeezy, or direct Stripe with your own backend?

I emailed Glench already, but figured someone here may have run into this.

Thanks!