Straight answers.

How does SKU matching work, exactly?

In a flat folder, InfiniteSync reads the SKU out of the filename — the part between sku_ and __idx_ — and looks for a variant in your store with that SKU. In per-product folders it doesn't need to: the folder itself is tagged with a hidden reference to the product when it's created.

The match is exact, so the safest habit is to copy the SKU from your product rather than retype it. A file whose SKU doesn't match anything is left alone rather than guessed at — a typo costs you a rename, not a wrong photo on a live product.

You can stack SKUs to put one image on several variants — sku_TSHIRT-RED__sku_TSHIRT-BLU__idx_9__size-chart.jpg — and products with no SKU are handled by product ID instead, as pid_8241__idx_1__hero.jpg. The full breakdown is on the How it works page.

Which image formats are supported?

JPG, PNG, WebP, and GIF. Anything else in the folder is ignored rather than rejected loudly, so you can keep your working files, backdrops, and a stray PSD in the same place without it becoming a problem.

Do I have to rename all my files first?

No. If you're on per-product folders, filenames are yours — the folder does the linking, so hero.jpg is a perfectly good name. The sku_ convention is what a flat folder needs, because there the filename is the only thing carrying the connection to your product.

And if you already have a catalog in Shopify, you don't name anything: run a full sync and InfiniteSync writes the folders and files into your Drive for you, correctly named, from what's already there.

What if the same image changes in both places at once?

The most recently edited version wins — the same rule you'd apply yourself. If you crop a photo on your desktop at 2pm and someone replaced it in the Shopify admin at 11am, your 2pm crop is the one that survives.

In the rare case both were touched in the same sync window carrying the same timestamp, Shopify's copy is kept. There's no merge and no coin flip — one version wins, and it's the newer one.

Does it touch anything besides images?

Product titles, yes — on purpose. Nothing else. If you're using per-product folders, the folder name and the product title are the same thing kept in step: rename the folder in your Drive and the product is renamed in Shopify, and vice versa.

That's two-way sync working as intended, and it's worth knowing before you tidy up your folder names — a rename in Drive is an edit to your live catalog. On flat folders there are no product folders, so nothing renames anything.

Beyond images and titles, InfiniteSync reads your product and variant list so it knows which SKUs exist, and that's it. Descriptions, prices, inventory, collections, and orders are never written to.

Can I switch between flat and per-product folders?

Yes, but it's a decision, not a toggle. It's one mode per store, and changing it makes InfiniteSync migrate your whole Drive structure to match — so it's worth picking based on how you actually shoot rather than switching back and forth.

Rough guide: flat if a photographer hands you hundreds of files at once, per-product if you want your Drive to read like your catalog and to be able to rename things from your desktop.

What counts as a product for pricing?

A product in Shopify — not an image, and not a variant. A product with 6 variants and 30 images is one product. The tiers count products, so a catalog of 80 heavily-photographed items is a Starter store, not a Scale one.

Google says this is an “unverified app”. Should I worry?

You shouldn't see that screen at all. The “unverified app” interstitial — the one with the way forward hidden behind an Advanced link — is what Google shows while it reviews apps that ask for broad access to your data. InfiniteSync asks for the narrow Drive scope, and narrow-scope apps don't trigger that review.

What you will see is Google's ordinary consent screen, and it's worth reading: it lists exactly one Drive permission — files the app created. Not your Drive, not your documents. Just the InfiniteSync folder we set up, which is where your product images live.

What can InfiniteSync actually see?

The InfiniteSync folder and everything you put in it. Nothing else — not your documents, not your photos, not the rest of your Drive, ever. That's enforced by Google's permission model, not by our promise: the app runs on the narrow drive.file scope, which only lets it open files and folders it created itself.

Your uploads reach us through one visible grant: the InfiniteSync folder is shared with our dedicated sync account, which can see that folder and nothing else. The share sits in Drive's own sharing dialog, where you can remove it whenever you like. The long version is on the How it works page.

What happens to my images if I uninstall?

Nothing happens to your images. They're in your Google Drive, in your folders, under your Google account. Uninstalling revokes our app's access and removes the sync account's share on your InfiniteSync folder — and we check the removal actually took effect rather than assuming it did. It never touches your files.

If Drive turns down every route we have — say the folder's owner switched off editor re-sharing and our Google authorization is already gone — we don't pretend it worked: we mark the share as pending removal and chase it, and you can lift it yourself in Drive's sharing dialog at any time. Want to cut that access without uninstalling? Remove all access in the app does the same thing.

This is the part worth being blunt about: a backup that disappears when you stop paying isn't a backup, it's a hostage. Yours sits in a Drive you already owned before you found us.

I run several stores. I'm an agency. How does that work?

Each Shopify store installs InfiniteSync separately, with its own plan and its own Drive folder. The app is scoped to a store.

For agencies, have each client connect the Google Drive they own for that store. The folder-only permission and visible sync-account share keep each client's catalog in its own Drive, without a separate account workaround.