How to organize product image files for faster launches
A naming, folder, and versioning system that keeps your assets ready to move at launch time.
Most launch delays do not start with the product. They start with the file.
A brand releases a new vintage. Marketing needs to update the website, email templates, and marketplace listings. The images exist somewhere.
The problem is knowing which folder, which version, and which name was the final one. This is a fixable problem. And fixing it once saves hours on every launch after.
Why asset chaos slows launches
When a brand grows beyond a handful of SKUs, the number of product image files multiplies quickly. Bottle shots, lifestyle images, label close-ups, vintage updates, background variations for different channels.
Without a system, those files accumulate in email attachments, Downloads folders, shared drives with no structure, and across multiple laptops. The next person who needs an image cannot find it without asking.
The cost shows up before a trade show, when someone spends an hour tracking down the correct vintage. It shows up when an outdated label gets sent to a distributor by mistake. It shows up when a new team member cannot do a basic task without a twenty-minute onboarding call.
Good file organization is the infrastructure that makes launches faster. It does not need to be complex. It needs to be consistent.
A folder structure that scales
One principle holds up over time: organize by product, not by date or campaign.
Each product gets its own folder. Each product folder contains subfolders by output type. New files go into the right place on arrival, not sorted later when time is short.
A structure that covers most beverage brand needs:
- /Brand-Name/Product-Name/Original-Files/ — master PNGs direct from Outshinery, untouched
- /Brand-Name/Product-Name/Web-Ready/ — resized and compressed versions for web use
- /Brand-Name/Product-Name/Social/ — platform-specific crops and exports
- /Brand-Name/Product-Name/Print/ — high-resolution files for sell sheets, menus, and POS
- /Brand-Name/Product-Name/Vintage-Archive/ — previous vintages, clearly dated, never deleted
Never use a single flat folder for all your product images. The time spent searching will always cost more than the five minutes it takes to set this structure up once.
Naming conventions that save time
A consistent naming convention solves two problems at once: version control and searchability.
The simplest format that works at any scale:
BrandName-ProductName-Vintage-FileType-v1.png
Example: Heatherwood-CabSauvignon-2023-BottleShot-v1.png
A few rules that prevent the most common errors:
- Include the vintage year in the file name. Never rely on the folder alone to carry that context.
- Always append a version number. Start at v1 and increment on each revision. Never save a file as "final" or "FINAL-USE-THIS."
- No spaces in file names. Use hyphens or underscores. Spaces cause problems across web tools, drives, and email.
- Make the file type descriptive. BottleShot, LifestyleImage, LabelCloseUp. Avoid abbreviations that only made sense on the day they were created.
The convention matters more than the exact system. v3 means something. "final" means nothing to someone who joins the team in six months.
The structure and naming system described above handles the inputs. What follows keeps the library reliable over time.
Managing vintages without overwriting
Every year, a vintage rotates. A 2022 Chardonnay becomes a 2023 Chardonnay. The label changes and the image changes with it.
The previous image should not disappear.
The correct approach: never overwrite. When a new vintage arrives, move the previous file into the /Vintage-Archive folder. Rename it to include the vintage year explicitly.
This takes about two minutes per SKU at rollover time. It saves hours of confusion when a distributor requests the 2021 image three years later, or when you need to review label evolution for a redesign.
One additional habit worth building: name the archive subfolder by year. /Vintage-Archive-2022 leaves no ambiguity about what is inside it.
Channel-specific output folders
The master PNG is the source of truth. Everything else in the library is a derivative.
Within the /Social, /Web-Ready, and /Print folders, file names should embed the intended use and the output dimensions.
Example: Heatherwood-CabSauvignon-2023-Instagram-1080x1080.jpg
When the dimensions are in the file name, the person downloading knows what they have without opening the file.
Five output formats that cover most marketing needs:
- Full bottle, vertical, white background, PNG: DTC product pages, Vivino, Wine.com, and marketplace listings
- Square crop, 1080x1080 px, JPG: Instagram feed, Facebook catalog, Google Shopping
- Wide crop, 1200x628 px, JPG: Email headers, LinkedIn posts, blog featured images
- Label close-up, high-res PNG: Tech sheets, tasting notes, press kits
- Full bottle, TIFF or high-res PNG: Print materials, POS displays, and menus
Exporting these five formats from every new bottle shot turns one master file into a ready-to-use kit for every channel.
When a design agency manages your assets
If a design studio orders images on your behalf, the same naming and folder principles apply.
The agency receives the master PNG and follows the same convention for any derivatives they produce. One addition that saves time: agree on the folder structure before the first order.
When files come back using the same naming convention, they slot into the right place without reorganization.
The annual asset audit
At least once a year, audit the image library against the active product range.
Confirm that every current SKU has a master file in /Original-Files. Check that all active vintages are in the main product folder. Move obsolete files to an archive or delete them.
A useful test: ask a new team member to find the correct image for a trade show submission. If they cannot locate it in three minutes without asking, the structure needs work.
The audit takes about an hour once a year. Without it, ghost files accumulate and the system slowly stops being useful.
How Outshinery fits into this system
The framework described in this guide applies to any product imagery. But it works best when the source files are consistent to begin with.
Outshinery images, from both Studio and Lite, arrive in a standardized format: high-resolution PNGs on a transparent background, consistent lighting and scale, ready for any channel.
Lite delivers every bottle shot at the same spec. Studio matches that consistency across more complex orders, including lifestyle images and multi-bottle compositions.
When your source files arrive in the same format every time, the /Original-Files folder stays clean. You are not reconciling different resolutions, inconsistent backgrounds, or mismatched scales from order to order.
The organization system holds because the inputs are predictable. That is where the real time savings come from.
Use this checklist every time you receive a new Outshinery image:
- Master file saved to /Original-Files? Keep the full-resolution PNG untouched. This is your source of truth.
- File named correctly? Follow the BrandName-ProductName-Vintage-FileType-v1 convention before doing anything else with it.
- Previous vintage archived? If this is a vintage update, move the old file to /Vintage-Archive-[Year] before replacing it.
- Web-ready version exported? Resize and compress for web. Save to /Web-Ready with dimensions in the file name.
- Social crops created? At minimum: square 1080x1080 and wide 1200x628. Save to /Social with the platform noted in the name.
- Print file saved? If you have print or POS needs, keep the high-resolution original in /Print.
- Product page updated? Upload the web-ready version to your DTC store, Vivino, and any active marketplaces.
- Sell sheet updated? Replace the image in your wholesale materials with the new version.
- Team notified? Send the correct file from /Web-Ready or /Print, not a screenshot or a compressed export.
Ten minutes of file management at receipt time prevents two hours of confusion at launch time.
