Restaurant Menu Photo File Naming: A Practical Convention Your Team Will Actually Use
FoodPhoto Team
Ops systems · · 3 min read
A simple file naming and folder system for restaurant photo libraries, so you can reuse images across channels without losing track of "the latest" version.
TL;DR
Name files so "what is it" and "is it current" are obvious. Keep one master per dish, then export variants per platform. Store photos where the whole team can access them (and only one place).
The problem this fixes
Most teams end up with: IMG_4839.webp. burger_final_FINAL_v2.webp. "Which one is on DoorDash?".
That creates inconsistent menus and slows down updates.
A naming convention that works
Use this format:
brand-location_dish-platform_orientation_version_yyyymmdd.webp
Examples: acme-downtown_smash-burger_master_square_v01_20260203.webp. acme-downtown_smash-burger_ubereats_square_v01_20260203.webp. Rules: Use master for the best, high-quality source image. Use platform names only for exported crops. Bump v02, v03 when the dish presentation changes.
Free Download: Complete Food Photography Checklist
Get our comprehensive 12-page guide with lighting setups, composition tips, equipment lists, and platform-specific requirements.
Folder structure (keep it boring)
/Menu Photos/Masters/. /Menu Photos/Exports/DoorDash/. /Menu Photos/Exports/UberEats/. /Menu Photos/Exports/Web/. /Menu Photos/Exports/Social/.
The weekly habit
Update masters for new items and top sellers. Export the platform crops. Upload and QA as thumbnails.
Use: /tools/image-requirements
Your menu deserves better photos
Try 10 photos for $3 or subscribe from $3 (20 credits). Try 10 photos for $3 → Plans from $3 → View pricing → No commitment. Credits roll over. Cancel anytime.
Want More Tips Like These?
Download our free Restaurant Food Photography Checklist with detailed guides on lighting, composition, styling, and platform optimization.
Download Free Checklist12-page PDF guide • 100% free • No spam
