Photo naming standard
Replace generic camera filenames with meaningful names using date, event, and sequence numbers.
Organize thousands of photos so you can actually find them.
For photographers, content creators, and marketing teams
12k photos renamed with this pattern by photography studios and marketing teams using renamed.to.
Photo naming standard
Name photos as YYYY-MM-DD_Event_Sequence.jpg to replace camera defaults with names that sort chronologically and describe what is in the image.
- Lead with date from EXIF data (YYYY-MM-DD) so photos sort chronologically regardless of import order.
- Add event, session, or client name to group related photos.
- Use sequence numbers (001, 002) instead of camera-generated filenames (IMG_1234).
- Keep the original file extension (.jpg, .png, .raw, .tiff) — never change it.
12k photos renamed with this pattern by photography studios and marketing teams using renamed.to.
Recommended patterns
Standard photo pattern
The universal pattern for any photography workflow. Date from EXIF ensures chronological sorting. Event name provides context. Sequence numbers keep images in capture order within a session.
YYYY-MM-DD_Event_Sequence.ext2025-10-15_SmithWedding_042.jpgClient photography pattern
For professional photographers managing client work. Client code groups all work for a client. Subject type helps quickly find what the client asked for.
YYYYMMDD_ClientCode_Subject_Sequence.ext20251015_ACME_Headshot_001.jpgLocation-based photo pattern
For travel photography and location-based shoots. Location in the filename supplements GPS EXIF data with a human-readable name.
YYYY-MM-DD_Location_Subject_Sequence.ext2025-10-15_NYC-CentralPark_Autumn-Trees_007.jpgCore principles
Preserve EXIF date in the filename
The date in the EXIF metadata is the most reliable timestamp. Use it as the date in the filename. Do not use the import date, edit date, or upload date — those change with every workflow step.
Use sequence numbers, not camera filenames
Camera filenames like IMG_1234 or DSC_5678 reset across memory cards and cameras. They are not unique across your archive. Sequential numbers within a session (001, 002) provide stable ordering.
Separate client work from personal photography
Professional photographers should use client codes for work and event names for personal shots. This keeps billing, licensing, and delivery organized.
Never rename away the file extension
The file extension (.jpg, .raw, .tiff, .png) tells your OS and editing software what type of file it is. Always preserve the original extension. Do not change .jpg to .jpeg or vice versa.
Batch-rename immediately after import
Rename photos right after transferring from the camera, before editing. Editing creates derivatives (edited versions, exports) and tracking becomes exponentially harder with each step.
Common mistakes
Keeping camera default filenames (IMG_1234.jpg)
Camera filenames reset (IMG_0001 appears on every new memory card), are not descriptive, and cannot be searched. After a year, you have hundreds of IMG_xxxx files with no context.
Fix: Rename immediately after import: 2025-10-15_SmithWedding_042.jpg
Losing EXIF data during rename
Some bulk rename tools strip EXIF metadata. Without EXIF, you lose the camera settings, GPS location, and original timestamp permanently.
Fix: Use rename tools that preserve EXIF metadata. Renamed.to preserves all metadata during the rename process.
Using no sequence numbers
If you shot 200 photos at a wedding on the same day, they all have the same date. Without sequence numbers, the sort order within a session becomes random.
Fix: Add zero-padded sequence numbers: 001, 002, ... 200. Use three digits for most sessions, four for large events.
Renaming edited exports with different names
The original is 2025-10-15_SmithWedding_042.jpg but the edit becomes "smith wedding final edit.jpg." Now you cannot match originals to edits.
Fix: Keep the same base name and add a suffix: 2025-10-15_SmithWedding_042_Edit.jpg or place edits in a separate /Edited/ subfolder.
Using special characters or spaces
Spaces in photo filenames break web publishing, CDN URLs, and many editing pipelines. Characters like &, #, % cause issues on different operating systems.
Fix: Use hyphens for word separation within fields, underscores between fields: 2025-10-15_NYC-Central-Park_042.jpg
More naming guides
View all naming guides →Frequently asked questions
Should I use the EXIF date or the file creation date?
Always use the EXIF date (DateTimeOriginal). File creation dates change when you copy, move, or download files. EXIF dates are embedded in the image data and stay accurate.
How do I handle photos from multiple cameras on the same shoot?
Sync camera clocks before the shoot. When renaming, the EXIF timestamps will interleave correctly. Add a camera identifier if needed: 2025-10-15_SmithWedding_CamA_042.jpg.
What about RAW + JPG pairs?
Use the same base name for both: 2025-10-15_SmithWedding_042.raw and 2025-10-15_SmithWedding_042.jpg. This keeps pairs together when sorting by name.
Should I include keywords or tags in the filename?
No. Filenames are for identification and sorting. Use your DAM (Digital Asset Management) tool, Lightroom keywords, or OS tags for searchable metadata. Filenames should be structured and concise.
How many digits should sequence numbers have?
Three digits (001-999) for typical sessions. Four digits (0001-9999) for large events like weddings or conferences. Always zero-pad so files sort correctly (002 before 010, not 10 before 2).
Can I automate this for photos imported from my phone?
Yes. Set up a watched folder for your phone sync (Google Photos export, iCloud download, or Dropbox camera upload). Renamed.to reads the EXIF data and renames as photos arrive.