Short-Term Rentals
Photo Naming Conventions for Property Portfolios
Streamline your hospitality workflows with a standardized file naming system that helps your team locate, manage, and update listing images in seconds.
By Hospitality Lens · · 14 min read
The best photo naming convention for a rental or hotel portfolio is a short, fixed pattern that any teammate can apply without thinking: property code, space, sequence number, and a status tag only when your workflow needs one. For example: oak-apt12_kitchen_01_enhanced.jpg. Lowercase letters, numbers, hyphens and underscores. No spaces. One pattern for every property.
That sounds small. It is not. Once you manage ten or more listings, photos arrive from owners, cleaners, co-hosts and photographers, each named by a different habit. A consistent filename is what lets you find the right kitchen image in seconds, hand a batch to an editor without a call, and know which file is the original and which is the published one.
This guide gives you a template, a room vocabulary, folder rules, and the mistakes we see most often.
HospitalityLens
Refresh Listing Photos Without a Photoshoot
HospitalityLens enhances existing property photos with realistic lighting, color, and perspective corrections while preserving the real property.
TL;DR
- Use one pattern for every property, such as
[property-code]_[space]_[sequence]_[status].jpg, and write it down.
- Stick to letters, numbers, hyphens and underscores. Pad sequence numbers (01, 02, 10) so files sort correctly.
- Keep filenames short. Put amenities, captions, rights and edit history in metadata or your asset system, not in the name.
- Never rename or overwrite an original. Save enhanced versions as separate files.
- Check each platform’s current upload rules before a bulk export. A good filename does not guarantee a successful upload.
Table of Contents
Why a filename matters more than it seems
Your phone or camera names a photo something like IMG_4587.jpg. That name records a numbering event inside a device. It says nothing about which property, which room, or which version you are holding. Wikimedia Commons’ naming guidance asks for names that are meaningful, specific, precise, correct, concise and understandable. A camera default meets none of those.
For a hospitality team the useful question is not “which device made this?” but “which property, which space, and which approved variant is this?” A filename should answer that, even when the file has been emailed, downloaded into a messaging app, or dropped into a shared folder with no context.
That last point is the reason folders alone are not enough. U.S. National Archives guidance warns that descriptive context carried by a folder can be lost once a file moves out of it. A photo called kitchen.jpg inside a folder called Oak Apt 12 is fine until someone attaches it to an email.
The pattern we recommend
A practical template for property teams is:
[property-code]_[space]_[detail]_[sequence]_[status].[extension]
This follows the principle in library digitization guidance of a consistent pattern with controlled terms and a limited set of status values. Here is what each field does.
Property code
This is the anchor. Use a short, stable code that never changes even if the listing title does: oak-apt12, denver-04, villa-bay-07. Do not use the street address. Addresses are long, they change in formatting, and they expose location details in every file you share with vendors.
Space
Use a controlled word for the room or area: exterior-front, living-room, kitchen, primary-bed, bathroom, balcony, view. The word list matters more than the pattern, and we cover it in the next section.
Detail (optional)
A second descriptor helps when a property has several shots of the same space: kitchen_island, bathroom_shower. Skip it when the sequence number is enough. The shorter the name, the more likely your team is to use it correctly.
Sequence
Use leading zeros. 01, 02, 10 sorts correctly, while 1, 2, 10 can sort as 1, 10, 2. Columbia University’s photo library guidance recommends padding to fit the quantity you expect, so fixing filenames later is never necessary. Two digits works for most single-room sets. If you number across a whole property, use three.
Status (only if you use it)
Keep status values few and real: original, enhanced, web, archive. If your workflow does not distinguish them, leave the field out. A tag nobody reads is clutter.
A full example: oak-apt12_kitchen_island_01_enhanced.jpg.
The guidance is consistent across sources. The National Archives recommends letters, numbers, hyphens and underscores, and avoiding spaces and punctuation that operating systems treat specially. The reason is practical: different systems handle special characters differently, and a name that opens fine on your laptop can break in a web upload, a script, or a shared drive.
Our rules, in plain terms:
- Lowercase everything. It avoids case-sensitivity surprises between systems.
- Pick one separator style and keep it. We use hyphens inside a field and underscores between fields, so
oak-apt12 reads as one unit.
- Leave out spaces, ampersands, apostrophes, accents and parentheses.
Kitchen (final) 2.jpg is the kind of name that causes trouble later.
- Keep the extension honest. A
.jpg should be a JPEG. Renaming an extension does not convert the file.
Lowercase and hyphenated names are also a conservative choice for listing platforms. Rules vary by destination. A U.S. MLS support guide, for instance, lists approved image formats and rejects certain special characters. Before any bulk export to Airbnb, Vrbo, Booking.com, a hotel CMS or an MLS, confirm that platform’s current requirements. Naming rules and upload rules are separate questions.
Build your room vocabulary first
The most common failure is not a bad pattern. It is inconsistent words. One person writes primary-bedroom, another master, a third bedroom-1. All three mean the same space, and none will turn up in the same search.
Columbia’s guidance recommends agreed names and abbreviations, and archival guidance recommends consistent patterns across a project. In practice, that means a one-page vocabulary written before you onboard the next property. A starting list might look like this:
| Space |
Approved term |
Do not use |
| Front of building |
exterior-front |
outside, front, facade |
| Main living area |
living-room |
lounge, sitting-room, lr |
| Cooking area |
kitchen |
kit, cooking |
| Main bedroom |
primary-bed |
master, bedroom-1 |
| Additional bedrooms |
bed-2, bed-3 |
guest-room, spare |
| Bathrooms |
bath-1, bath-2 |
wc, restroom |
| Outdoor space |
balcony, patio, pool |
terrace, deck (unless you use it everywhere) |
| Window or outlook |
view |
scenic, ocean-view |
Your list will differ. What matters is that it is short, written down, and the same for every property.
One caution belongs here. Do not put claims in filenames that the image does not show. A file named ocean-view should only exist if the photo actually shows the ocean. Names get copied into descriptions, exports and vendor briefs, and an unsupported label can travel into a listing. Describe what is in the frame, nothing more.
Dates: decide what the date means
Dates help when you shoot the same property across seasons. Use a sortable, unambiguous format: YYYYMMDD or YYYY-MM-DD. Columbia recommends YYYYMMDD. NASA’s imagery standard permits a four-digit year or YYYYMMDD, and says the acquisition date should not change just because a file is migrated.
The question to settle is which date you mean. A capture date, an enhancement date and a publication date are three different things. Pick one for the filename, and keep the others in metadata or a clearly defined suffix. For most operators we would put the capture date in the name only when seasonal sets matter, for example 20261020_oak-apt12_living-room_02.jpg, and leave it out otherwise.
The U.S. format of month first (10/20/2026) sorts badly and confuses international teams. Year first avoids both problems.
Filenames are identifiers, not databases
It is tempting to cram everything into the name: room, view, bed count, season, photographer, edit notes. Resist it. NASA’s standard and archival guidance treat the filename as an identifier, with richer context held in associated metadata.
The Society of Photographers makes the same point from the working photographer’s side: a date, a project or property identifier and a sequence number are usually enough, and detailed descriptions belong in keywords and metadata once names get unwieldy.
So what goes where?
- In the filename: property code, space, sequence, and status if you use it.
- In metadata or your asset system: captions, amenities, view descriptions, accessibility text, rights and usage terms, photographer or source, and edit history.
- Not in either, if avoidable: guest names, door codes, exact addresses or anything sensitive. Files get shared widely, and a filename is the first thing a stranger sees.
A caution on metadata too. Federal digitization guidance notes that batch processing is efficient for shared fields, but data unique to a single image should be checked individually. Otherwise a caption or location can be copied across an entire batch. If you bulk-apply a property name, review the captions one by one.
Filenames also do not replace alt text or listing captions. They help you internally. Guests and platforms see the fields you fill in on the listing itself.
A folder structure that holds up at 10 or more listings
Folders still matter, as long as filenames do not depend on them. A structure that scales:
/Properties/[property-code]/[asset-type]/[year-or-season]/
Under each property, create separate areas for Originals, Enhanced, Published, Archive and Marketing. For example: /Properties/oak-apt12/Originals/2026-fall/.
The filename still repeats the property code. That redundancy is deliberate. Files get downloaded, attached and moved, and the name is the only thing guaranteed to travel with the image.
A second reason for the Originals folder is protection. Never rename or overwrite the owner-submitted or cleaner-taken image after it is enhanced. Keep the original untouched and save each edit as a separate export. That protects rollback, makes it clear which file was edited, and stops a polished export from becoming the only surviving copy. Archival guidance supports preserving originals and recording relationships between files.
Three ways teams get this wrong
They let each person invent names. Photography practitioners consistently find that a convention the whole team can remember beats an elaborate one. For onboarding staff and vendors, a short template plus a controlled vocabulary is more reliable than asking anyone to describe each photo from scratch. Put the template in your onboarding document and in the brief you send owners and cleaners.
They mix systems inside one portfolio. IMG_4587.jpg, Oak Apt Kitchen 1.jpg and oakapt_kitch_01.jpg in the same property folder is a real example of what to avoid. The goal is not the perfect convention. It is one convention.
They rename after the fact. Renaming a thousand files later costs far more than naming them correctly at intake. Even Wikimedia notes that old files do not need to be renamed to fit new guidance exactly, because of the cost. Apply the new standard to new properties and new batches, and migrate older ones only when you touch them.
Applying it to owner and cleaner photos
Owner-submitted and cleaner-taken photos are where naming falls apart. They come in as phone defaults, often dozens at a time, in a chat thread or shared album.
A workable intake routine:
- Download everything into the property’s
Originals folder exactly as received. Do not edit yet.
- Rename the files with your pattern and vocabulary, in the order you plan to show them. Use the padded sequence.
- Discard nothing at this stage. Mark unusable shots in your tracker rather than deleting them.
- Send the renamed set for enhancement. Enhanced files return as separate exports with the
enhanced status.
- Move the approved files to
Published, and note the export date and platform in your asset system.
If you need help deciding which images are worth keeping, our guides on phone-first photo style for rentals and professional listing images cover how many shots to use and what each should show. Once the set is chosen, our listing image optimization process walks through the steps from raw files to published images.
What we think about naming, as a team
We see portfolio photo sets in every condition: dark, crooked, cluttered, taken by an owner on a phone or by a cleaner between turnovers. The pictures are only half the problem. The other half is that nobody can tell, a month later, which file is which.
Our view is simple. A naming convention should be boring. It should take seconds to apply, be impossible to misread, and never require a meeting. If your pattern needs a decoder ring, your team will drift away from it, and it will not survive the next onboarding wave.
We also think the filename should be honest in the same way a listing photo should be honest. It should describe what the image is, not promote what you wish it showed. That is the same principle we apply to enhancement: improve lighting, straighten perspective, clear clutter, and keep the real property intact. We do not invent rooms, views or amenities, and we would not want a filename to suggest them either.
Plain names, clear originals, clean exports. That is what makes a large portfolio manageable.
— The HospitalityLens Team
Where enhancement fits into your naming flow
If your photos are already named and sorted but look dark, crooked or cluttered, enhancement is the next step, and a clean naming system makes it faster. You upload the renamed originals, and the returned files keep your property codes and sequence, so nothing needs to be matched by hand.
Free watermarked preview. Pay only if you like it. No card is required to create the free watermarked preview. See current pricing for unlocks, one-time packs, and subscriptions.
A professional photographer is still the better choice for flagship launches, architectural work, new angles, or situations where the original photos are unusable. Enhancement works when the raw material is there.
A starter standard you can copy
Here is a one-page standard you can paste into your onboarding document and adjust.
| Element |
Rule |
| Pattern |
property-code_space_detail_sequence_status.jpg |
| Characters |
a-z, 0-9, hyphen, underscore only |
| Case |
lowercase |
| Property code |
short, stable, never an address |
| Space |
from the approved vocabulary only |
| Sequence |
two digits, three if numbering across a property |
| Date |
optional, YYYYMMDD, capture date unless stated |
| Status |
original, enhanced, web, archive |
| Originals |
never renamed over, never overwritten |
| Context |
captions, rights and amenities live in metadata |
Test it on one property before you roll it out. Rename a full set, hand it to a colleague, and ask them to find the second bathroom photo. If they succeed without asking you anything, the standard works.
FAQ
What is the best way to name listing photos?
Use a fixed pattern that starts with a short property code, then the space and a padded sequence number, such as oak-apt12_kitchen_01.jpg. Stick to lowercase letters, numbers, hyphens and underscores. Consistency across the whole portfolio matters more than which exact pattern you choose.
Do photo filenames help listings rank on Airbnb or Vrbo?
Image quality can influence how people evaluate a listing, but there is no universal performance uplift that applies to every property. Measure clicks, inquiries, bookings, or sales on the individual listing. Treat filenames as an internal tool for finding, sorting and handing off images. The captions and fields you complete on the listing are what guests and the platform see.
Should I include the date in the filename?
Only if you manage seasonal sets or repeated shoots. Use YYYYMMDD so files sort in order, and decide in advance whether the date means capture, edit or publication. Keep any other dates in metadata.
Should I rename the original photos from owners or cleaners?
Keep an untouched copy of exactly what you received in an Originals folder. Rename a working copy to your convention, and save enhanced versions as separate files. That way you can always roll back and prove what was changed.
Sources
Recommended