Img.vision uses permanent links that include the image’s filename. The folder an image sits in is not part of that link. Because of this, every filename in your drive needs to be unique, no matter which folder it’s in.
This is different from how Windows and Mac work, where you can have two files named the same thing as long as they’re in different folders. In Img.vision, the folder structure is just for organizing your images. The link only cares about the filename.
Table of Contents
What happens with duplicate filenames
If you upload or import an image with a filename that already exists somewhere in your drive, you’ll be asked what to do. You can overwrite the existing image, keep both by adding a small unique suffix to the new filename, or cancel the upload.
When importing a folder (through a cloud import or a direct folder upload) and the batch itself contains duplicate filenames, a unique suffix is added automatically so every image gets uploaded. Nothing gets skipped or lost.
If you have the setting enabled to always force filenames to be unique, the unique id is now added as a suffix at the end of the filename, before the extension, rather than as a prefix at the start. This keeps your filenames in the same order they were before the suffix was added, which matters if you rely on filename order for things like flat file uploads to eBay.
Why this matters for your links
Image links don’t mention the folder they’re in. If you’ve already used that link somewhere (a listing, a marketplace, an external page), moving that image to a different folder, or renaming the folder, would break the image link. Keeping folders out of the links from the start avoids that problem entirely.
