Guest Photos: Using Them Without Breaking Trust

A guest's photo is their property, their face and their holiday. There is a narrow, useful band where you can use it and they would still book again.

Last updated: October 28, 2026

A guest sends a photo of the balcony at sunset and says the stay was lovely. You'd like to post it. What you have is permission to look at it. What you need is permission to publish it, and those are two different things. The usable band is narrow: one photo, one purpose, one place, one period — and a guest who can take it back without an argument.

Key Takeaways

• A thank-you isn't a licence. A photo sent in a message is a gift of a picture, not of the rights to use it anywhere.
• Name the use, not the photo. "Can I post this on our account" and "can I use this" are different permissions.
• Reposts outlive the post. A screenshot travels further than the account that published it.
• Keep the message that granted it. The thread is your record, and it's the thing you'll need on the day someone changes their mind.
• Credit only if they agree. A name attached to a photo is a small endorsement, and it isn't yours to give.

What you may ask for

Ask for one specific use, in writing, naming the photo, the account, the format and how long it stays up. That's the unit that works: specific enough for the guest to picture, short enough for them to agree to without a lawyer.

The request should be short, and it should be its own message. A thank-you note with a permissions question buried in the third line gets answered as a thank-you, and then you're both guessing about what was agreed.

Ask for the original file rather than a screenshot, because a screenshot carries the compression and sometimes the interface around it. Ask whether they'd like their name or handle attached, and accept a no without negotiating. Ask before you use it, not after.

What you're asking for is narrow on purpose. A guest who understands exactly where the photo will appear is far more likely to say yes than one who's asked for something open-ended. The ones who agree to a narrow request tend to stay friendly about it afterwards.

There's also a version of this that costs nothing. Your own photographs of your own rooms are yours, and they can be imported with the rest of the listing when you set the property up. localsbnb.com brings a listing's own title, photos, capacity and calendar across from Airbnb, and holds the four connected channels in one calendar, so the gallery you publish is the one you shot.

What you may not reuse

The first thing you may not do is widen the use. A photo sent for a post about that guest's stay doesn't belong in a paid advertisement, on a different listing, in a printed brochure or on a booking page. Agreement to the first doesn't carry to the rest.

The second is to lift pictures nobody sent you. A guest who tagged the property in a public post hasn't handed over the image, and a screenshot of their feed is still their photograph. If you want it, ask, and expect a no sometimes.

The third is to publish a photo that shows more than the room. A picture of a child in the pool, another guest at the gate, a doorway with the entry code visible, a car with a readable plate. Each of those is a reason to crop, blur or skip. The guest who sent it may not have noticed.

There's a fourth, quieter one. Don't imply a relationship that doesn't exist. Using a guest's photo beside a line about how guests love the place turns their holiday picture into a testimonial, and that's a claim they didn't make.

The safe default is the smallest use that puts the picture in front of the right people. A post about the room, on your own account, left up for as long as the listing runs, is usually enough — and it's the version a guest can agree to without thinking about it twice.

Consent that survives a repost

Consent is bound to the use you described. That's why the message matters more than the yes: "sure, go ahead" answers a question you asked, and if you asked a vague question you now hold a vague answer.

Write down four things in the thread — which photo, which account, what it will say, how long it stays — and keep it. Not because a dispute is likely, but because a year from now you'll be the one who can't remember whether the agreement covered the new account you've since opened.

It also helps to say what happens if the account closes, or if the property changes hands. A guest who agreed to a photo on one account hasn't agreed to it on a new one, and the safest reading of a yes is that it covers the thing you described and nothing adjacent to it.

Reposts are where these agreements quietly fail. A screenshot of your post can end up somewhere you never named, and the guest sees their face on an account neither of you agreed to. You can't control that, but you can avoid making it worse: don't repost your own post to a second platform without asking again, and don't hand the image to anyone else.

And build in the exit. Say in the message that they can ask you to take it down at any time, and mean it — same day, no discussion, no "are you sure". A guest who knows they can withdraw is a guest who can say yes honestly.

The credit line that helps

Credit is a courtesy, not a payment, and it only works when the guest wants it. Name them the way they asked to be named, tag the account they gave you, and don't add a title they didn't choose — "guest" is fine, "our favourite guest" is a claim.

There's a simple test before you publish: would the caption still make sense if a stranger had sent the photo, with no stay attached? If it only works because the guest loved the place, it's a testimonial wearing a credit line.

Keep the caption about the picture. "Sunset from the third-floor balcony, sent by a guest in September" does the work. "Guests can't stop talking about this place" turns a shared photograph into marketing, and the difference is visible to everyone reading it.

If the guest asks for the credit to be removed but the photo to stay, do that too. The two permissions are separate, and treating them as one bundle is how a small courtesy turns into a small argument.

None of this is a legal opinion, and the rules differ by where you and your guest are. Image rights, privacy and advertising standards are set locally and revised; if a photo is going into anything commercial, ask a professional in your jurisdiction before you publish it. The habit above keeps you inside the ordinary case, not outside the law.

FAQ

The guest tagged us in their post. Can I repost it?

Tagging is an invitation to look, not a licence to publish. Ask in a message, name the account you'd use, and wait for an answer. Most guests say yes to a specific request, and almost none of them mind being asked.

Do I need a written agreement?

A message thread that names the photo and the use is enough for the ordinary case, and it's better than a form nobody reads. For anything commercial, or anything showing people other than the guest, get proper advice before you publish.

What if the guest asks me to take a photo down two years later?

Take it down the same day and say thank you. The photo has done whatever it was going to do, and the goodwill of removing it quickly is worth more than the picture. Keep the message that shows you did.

A photo is the easiest thing to borrow and the hardest thing to give back. Ask for one use, keep the thread, credit only when invited, and remove on request. localsbnb.com keeps your own listing photos with the property and the four channels in one place, which is the part of the gallery you never have to ask anyone about.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice, and it isn't a statement of image-rights law in any jurisdiction. Rules on likeness, privacy and advertising differ by place and change; confirm them with a qualified professional where you operate before publishing a photo of anyone.