What OTAs Reject in Hotel Photos, and Why

Sources: OTA partner documentation, Booking Connectivity API, six real Booking.com listings inspected via Playwright in April 2026, and the Cornell eye-tracking study reused from the sibling exterior-photo article.

Key takeaways

Every major OTA publishes a photo policy. The rules look like guidelines. They are filters. A photo that breaks one gets rejected at upload, hidden in your gallery, or down-scored inside the OTA's content score. The cost is a missed click, not a politely worded warning email.

The rules converge on five families across all five OTAs. People as primary subject. Brand surfaces and watermarks. Collages. Below the resolution and orientation floor. Stock and off-topic imagery. Most of the list is universal. Resolution is where they diverge: Booking demands 2048 by 1080, while Vrbo, Google, and Airbnb accept 1024 by 683 ¹²³⁴.

We inspected six Booking.com listings in Bangkok, Phuket, and Vietnam on 2026-04-27. Every single one carried at least one photo that violated a published OTA rule. Booking's own image-recognition labels the violations correctly, in the alt text, while the publishing pipeline waves the photos through. Operators cannot rely on the OTA to catch every bad photo. The fix is a pre-upload audit you run yourself, on every photo, before you push.

Why it moves bookings

Rejected photos never reach the consideration set. Cornell eye-tracking research found that within the seven-property window a traveler typically considers, images are the single most-fixated content type, ahead of price, ratings, and firm-provided descriptions ⁵. A photo that gets silently rejected by the API or down-scored by the content algorithm is a photo that does not pull its weight against that fixation. Photo coverage gaps drag the whole listing down with them.

Booking.com's Property Page Score names photos directly. The Connectivity API exposes five photo-related metric IDs as content-score components: property_photos_3 ("Upload at least 10 photos"), property_hq_photos_3 ("Make sure all of your photos are high quality"), swimming_pool_photo_3, exterior_photo_3, and bathroom_photos_3 ⁶. Booking's community page claims that "properties with a 100% property page score on Booking.com can generate up to 18% more bookings" ⁷. Treat the 18% as a Booking self-claim, not a third-party benchmark. The point holds either way: a photo flagged as low-quality reduces the score, and Booking's own API doc says the score "can impact the property's performance in a positive way" ⁶.

Expedia is harsher. Its Connectivity Hub doc says plainly: "Property API does not send error messages when an image is rejected" ⁸. Operators push 30 photos. They see 18 published. They have no diagnostic. The way to catch the gap is to count: open Partner Central, go to Property Details → Photos, and compare your upload count against your published count weekly. The delta is your rejection signal. Vrbo at least surfaces a named "rejected photos" tray in its dashboard so partners can see what didn't make it in ⁴. Across the others, rejection is silent.

Google Hotel Center inherits its photo rules from Google Business Profile. A photo that fails Google's published checks (over 10% in-image text, EXIF GPS that does not match the registered address, low-resolution image) does not appear in the Prices tab carousel ³. Airbnb's Help Center is the most explicit about consent breaches as hard rejects. A photo that prominently features a person without consent, or a child without an accompanying guardian in the frame for family experiences, does not publish ⁹.

Five OTAs. Five enforcement surfaces. One outcome: violations cost you visibility before any human ever sees the photo.

What stays universal vs what's platform-specific

Four rules are universal across all five platforms.

No collages or multi-panel composites. No watermarks, in-image text overlays, or borders. No photo where a person is the primary subject without consent. Landscape orientation only. Each OTA states each rule in its own words but the rules themselves do not vary ¹²³⁴⁹.

The platform-specific rule is resolution.

Platform	Minimum resolution	Recommended	Max file size	Source
Booking.com	2048 by 1080	4000 by 3000	not published	1
Expedia (Vrbo rulebook)	1024 by 683	3840 by 2160	20 MB	4
Expedia (legacy floor)	1000 px longest edge	2880 px longest edge	15 MB	810
Google Hotel Center	1024 by 683	2048 by 1366	10 MB	3
Airbnb (stays)	1024 by 683	bigger is better	not published	11

The practical takeaway is one number. A photo at 2048 by 1080 pixels in landscape orientation passes everywhere. A photo at 1024 by 683 passes Google and Airbnb but fails Booking outright. The "safe-everywhere floor" is Booking's floor, because it is the strictest.

Why every major OTA bans collages is worth a sentence. Search-result tiles, map-view thumbnails, and Google's Prices tab carousel all crop a photo to a small rectangle. A collage at 300 by 200 pixels renders as an unreadable grid of postage stamps. The rendering constraint is identical across platforms. The rule follows.

Common failure modes

Five families. Each draws on at least one named real Booking.com listing where we have machine-readable evidence the photo violates an OTA's published rule.

Failure 1: people as the primary subject

Lead example: Here Hostel Bangkok ¹². The hero image carries Booking's own auto-generated alt text "a group of people walking down a street at Here Hostel Bangkok in Bangkok." Gallery thumbnails carry alt text including "a person in a swimming pool next to a tree," "a man in a suit is opening a door," and "a crowd of people sitting at a bar at night." Booking's image-recognition has labeled the primary subject as people, in writing, on the live page.

Booking's Partner Hub tells operators to "avoid posting pictures like portraits or where people are the main focus" ¹. Expedia's image guidelines tell partners not to use images "where people are the primary subject," and not to use "portrait-style close ups, images where people look overly staged, artificial, or stiff poses" ¹³. Google narrows the people rule to "Only show people in communal spaces" ³. Airbnb requires consent for prominently featured people ⁹.

A secondary example reinforces the point. Homestay Bích Huệ Nova Phan Thiết's hero image carries Booking's alt text "a person sitting in a swimming pool at night at Homestay Bích Huệ" ¹⁴. A single named subject in a pool scene reads as person-as-primary-subject, not communal-space. The rule is published. The hero photo violates it. The photo still ranks first in Booking's gallery.

Failure 2: brand surfaces, watermarks, and in-image text

Lead example: NUN Guest House in Phuket ¹⁵. The gallery contains an image whose Booking alt text is "a guide to splash jungle water park phuket at NUN GUEST HOUSE." The photo is a brochure for an unrelated nearby attraction. Splash Jungle Water Park is a third-party brand. The image surface in the property's own gallery is occupied by another business's promotional content.

Expedia's developer hub names the rule directly: "Logos, maps, floor plans, or illustrations" appear in its rejection list, alongside "Text or graphic overlays" and "Borders" ⁸. Vrbo's prohibited list adds "Watermarked with logos or borders," "Text of any kind," "License plates," and "QR codes" ⁴. Google says photos "shouldn't include promotional text, watermarks, or logos" and Google Business Profile rejects any photo where text covers more than 10% of the frame ³¹⁶. Airbnb's Experiences guidelines forbid "text or logos overlaid on the image" ⁹.

The literal "Netflix logo on a hotel-room TV" variant is a well-attested industry pattern but didn't surface in our Asia-market sample. The rule is identical: third-party brand surfaces in the gallery violate every OTA's policy. NUN Guest House's brochure-as-photo above is the same failure in a different costume.

Failure 3: collages and multi-panel composites

Lead example: AN THINH Hotel & Homestay in Vietnam ¹⁷. Booking's own AI labels two of this property's gallery photos as collages. Image 826948879.jpg carries the alt text "a collage of pictures of a swimming pool at AN THINH Hotel & Homestay" (and renders 768 by 768 square, also failing the landscape rule). Image 826949116.jpg carries the alt text "a collage of photos of a resort with a pool."

Booking publishes "Photo collages" in its avoid-uploading list ¹. Expedia lists "Montage or collage" in its rejection list ⁸. Vrbo prohibits "Collages of multiple photos" ⁴. Google Hotel Center says "Don't make collages" and adds, in its Things-to-do reference, that "images that are animated or that are made up of multiple images (for example, image collages) aren't permitted" ³¹⁸. Airbnb says "Single photos, not a collage" ⁹.

Booking's image-recognition correctly identifies both AN THINH photos as collages. The publishing pipeline indexed them anyway. The model knows. The gate does not gate.

Failure 4: below the resolution and orientation floor

Lead example: NUN Guest House ¹⁵. The hero image renders 360 by 480 pixels in the page DOM. Portrait orientation. Booking explicitly mandates "Shoot landscape images (horizontal) only, these look best on our platform" ¹. Vrbo requires "Horizontal (landscape) display" and lists portrait orientation in its prohibited list ⁴. Google states "Orientation: Landscape" ³. Airbnb says photos in search results render in landscape, and that "vertical photos won't" render well at search-result size ¹¹.

Secondary example: Chamil House in Thailand ¹⁹. The hero is 768 by 768 (square). Seven gallery thumbnails render at 500 by 500 or 300 by 300. Booking's gallery card surface is roughly 3:2. Square photos render with letterbox crops on either side. The photos pass Booking's resolution floor on the long edge. They fail the orientation rule.

A composition violation rounds out the orientation cluster. Tứ Thiên Homestay's gallery contains an image with Booking's alt text "a white car parked in front of a building at Tứ Thiên Homestay" ²⁰. Booking's published composition rule says "Avoid taking pictures of road signs and parked cars" ¹. Booking's AI tags it. The photo publishes anyway.

Failure 5: watermarks and photographer signatures (in-the-wild gap)

No live watermark example surfaced in our sample. That's a signal in itself: Booking's moderation pulls watermarked photos more aggressively than people-as-subject or orientation violations. Selection bias, but instructive. It tells you which rule the platform actually gates on.

The structural evidence the rule exists is unambiguous. Booking's Partner Hub names "Watermarks or illustrations in photos" in its avoid-uploading list ¹. Expedia rejects "Text or graphic overlays" and "Borders" ⁸. Vrbo's published help page names the dashboard surface where rejected photos appear: "If you upload photos that don't meet these guidelines, they will show as 'rejected photos' in your Vrbo dashboard under Edit Property → Photos" ⁴. Google's 10% in-image text rule applies ¹⁶. Airbnb prohibits text and logos overlaid on images ⁹.

Vrbo's rejection-tray UX is the single OTA surface where operators can directly see which photos failed and why. Every other platform either rejects silently (Expedia API) or publishes the photo and applies a downstream score penalty (Booking small-property inventory). For watermarks, the cleanest verification path for an operator is to upload a watermarked test image to Vrbo and read what the dashboard says back.

Step-by-step fix

Walk every photo through these checks before you push to any OTA. In order.

1. People as primary subject. If a person fills more than a third of the frame, pull or re-frame. The communal-space exception matters: a wide pool deck with several swimmers in the middle distance is fine on Google. A lobby scene where the receptionist is greeting a guest is fine. A bedroom shot with a person in the bed is rejected on every platform. The rule of thumb: would a stranger looking at this photo say "I see a hotel" or "I see a person"? If it's the second, it's the wrong photo.
2. Third-party brand surfaces. Any logo, brochure, sports broadcast, or branded TV channel visible in foreground or middleground? Photoshop out, swap the channel for an Apple TV home screen, or replace the photo. License plates, QR codes, and screenshots from other websites all count. Airbnb names screenshots explicitly ⁹; Vrbo's "copied from another listing" clause covers the same failure ⁴.
3. In-image text and watermarks. Strip photographer signatures, address overlays, contact info, and date stamps from the image itself. Move credit to EXIF metadata. Google's 10% text-coverage rule is enforced automatically. The other platforms publish the same rule but don't disclose enforcement; treat them as if they were.
4. Collages. Reject any multi-panel composite outright. Pick the strongest single panel and upload it on its own. There is no platform where a collage helps.
5. Resolution, orientation, and dynamic range. Below 2048 by 1080 in landscape? Re-shoot. Don't upscale: Booking's property_hq_photos_3 metric flags low-quality output, and most upscalers leave detectable artifacts. Avoid heavy HDR: window halos and crushed shadows trip the same low-quality flag. JPEG, sRGB, file under 5 MB hits every platform's max. If you shoot on iPhone, convert HEIC to JPEG before upload. Expedia and Vrbo enumerate JPG and PNG as accepted formats (Vrbo also accepts GIF); Booking's public spec doesn't enumerate formats, but every Booking example is JPEG. HEIC is on no OTA's spec.
6. EXIF GPS. Strip location metadata if it does not match your registered property address. Google checks this automatically as part of its Business Profile inheritance. Mismatched GPS is a fast path to rejection there.

Before you push: re-export every photo at sRGB JPEG, max 5 MB, with consistent color profile across the gallery. If you have Booking Connectivity API access, check the photo metric statuses on property_photos_3 and property_hq_photos_3 after upload. If you have Vrbo dashboard access, open the rejected-photos tray.

Self-audit checklist

Run this on your own gallery, every photo, before push.

• No identifiable faces as the primary subject (guests, staff, photographer, passers-by) without consent
• No visible third-party brands, broadcasts, or competitor logos in any photo
• No in-image watermarks, photographer signatures, address overlays, or contact info
• No collages or multi-panel composites
• All photos at 2048 by 1080 pixels in landscape orientation, or larger
• All photos JPEG, sRGB, under 5 MB
• No HDR halos around windows or door frames
• No date or time stamps baked into the image
• No screenshots from other websites or stock-photo placeholders
• EXIF GPS stripped or matching the property's registered address

How OTALift surfaces this

OTALift's listing-audit report runs PhotoQualityValidator across every gallery photo and flags the rejection-risk patterns described here alongside other photo-quality signals. Each flag deep-links into this article, so the operator sees the OTA's own published rule, not just our interpretation of it.

We are extending the validator to compute a per-photo per-OTA pass/fail matrix surfaced by the resolution-floor table above. The operator will see, for each photo, which platforms accept it as-is and which reject it. That is the next signal we are building. Today's flags cover collages, watermarks, low-resolution photos, and people as primary subject; the per-OTA resolution-floor matrix arrives next.

Related articles

• The Perfect Hotel Exterior Photo
• Photo Count Minimums by OTA and Room Type
• The Hero Photo Decision: Which Shot Goes First
• Pillar: How OTA Ranking Algorithms Actually Work

Sources and methodology

Real-listing examples were captured via Playwright direct browse of Booking.com search results in Bangkok, Phuket, and Vietnam markets on 2026-04-27. Booking's own auto-generated alt text was used as machine-readable evidence the photo violates the platform's published rule. The choice to lead with Asia-market budget inventory was deliberate: independent and family-run properties tend to upload owner-shot photos without professional review, so rule violations there are more visible than in major-chain inventory where in-house creative teams pre-screen against OTA specs.

Footnotes

1. Booking.com Partner Hub (verified primary; full text in docs/labs/articles/listings/perfect-exterior-photo/research/data.md). "Understanding photo requirements for your property." Accessed 2026-04-18 via Playwright. https://partner.booking.com/en-us/help/property-page/photos-extranet/understanding-photo-requirements-your-property ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸

2. Expedia Group EG Connectivity Hub (verified primary; accessed 2026-04-27 via WebFetch). "Image learn page." https://developers.expediagroup.com/supply/lodging/docs/property_mgmt_apis/image/learn/ ↩ ↩²

3. Google Hotel Center (verified primary; accessed 2026-04-27 via WebFetch). "Photo recommendations and best practices." https://support.google.com/hotelprices/answer/13483115 ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸

4. Vrbo Help Center (verified primary; accessed 2026-04-27 via WebFetch). "Photo guidelines for Vrbo listings." https://help.vrbo.com/articles/Vrbo-photo-guidelines ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹

5. Noone, B., and Robson, S. K. A. (2014). Using Eye Tracking to Obtain a Deeper Understanding of What Drives Online Hotel Choice. Cornell University Center for Hospitality Research. 32 participants. https://hdl.handle.net/1813/71105 ↩

6. Booking.com Connectivity (verified primary; accessed 2026-04-27 via WebFetch). "Property Scores API documentation." https://developers.booking.com/connectivity/docs/property-scores-api/property-scores ↩ ↩²

7. Booking.com Partner Community (Booking self-claim; access via WebSearch summary, direct fetch returned 403). "Property Page Score." https://partner.booking.com/en-gb/community/booking-advice-and-updates/property-page-score ↩

8. Expedia Group EG Connectivity Hub (verified primary; accessed 2026-04-27 via WebFetch). Silent-rejection note and full rejection list. https://developers.expediagroup.com/supply/lodging/docs/property_mgmt_apis/image/learn/ ↩ ↩² ↩³ ↩⁴ ↩⁵

9. Airbnb Help Center (verified primary; accessed 2026-04-27 via WebFetch). "Choosing great photos for your Airbnb Experience." https://www.airbnb.com/help/article/3024 ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷

10. Expedia Group Photo Guidelines flyer (PDF, 2018-08-15 file stamp). Legacy 1000-pixel rejection floor. https://mslps.expedia.com/images/en_EN_Flyer_EG%20Photo%20Guidelines%20_150818.pdf ↩

11. Airbnb Help Center (verified primary; accessed 2026-04-27 via WebFetch). "Taking great photos of your listing." https://www.airbnb.com/help/article/746 ↩ ↩²

12. Here Hostel Bangkok. Booking.com listing inspected via Playwright on 2026-04-27. Hero image alt text "a group of people walking down a street at Here Hostel Bangkok in Bangkok." https://www.booking.com/hotel/th/here-hostel.en-gb.html ↩

13. Expedia DEG (Destination Experience) Image Guidelines (verified primary; accessed 2026-04-27 via WebFetch). https://ewe-assets.s3.amazonaws.com/media/meso_cm/others/Prototype/EN/deg-tabs.html ↩

14. Homestay Bích Huệ Nova Phan Thiết. Booking.com listing inspected via Playwright on 2026-04-27. Hero alt text "a person sitting in a swimming pool at night at Homestay Bích Huệ." https://www.booking.com/hotel/vn/homestay-bich-hue-phan-thiet.en-gb.html ↩

15. NUN Guest House (Phuket). Booking.com listing inspected via Playwright on 2026-04-27. Hero portrait orientation 360 by 480 in DOM; gallery contains "a guide to splash jungle water park phuket" promotional brochure image. https://www.booking.com/hotel/th/nun-guest-house.en-gb.html ↩ ↩²

16. Whitespark (secondary expert summary; accessed 2026-04-27 via WebFetch). "Why is Google Rejecting My Google Business Profile Photos?" 10% in-image text rule corroborated against gmbbriefcase.com summary. https://whitespark.ca/blog/why-is-google-rejecting-my-google-business-profile-photos/ ↩ ↩²

17. AN THINH Hotel & Homestay (Bình Tú, Vietnam). Booking.com listing inspected via Playwright on 2026-04-27. Booking AI alt text labels two gallery images as collages. https://www.booking.com/hotel/vn/an-thinh-homestay.en-gb.html ↩

18. Google Hotel Center (verified primary; accessed 2026-04-27 via WebFetch). "Things to do content and referral experience policies." https://support.google.com/hotelprices/answer/10723240 ↩

19. Chamil House (Ban Ko En, Thailand). Booking.com listing inspected via Playwright on 2026-04-27. Hero 768 by 768 square; gallery thumbnails 500 by 500 and 300 by 300. https://www.booking.com/hotel/th/chamil-house-chaamil-ehaas.en-gb.html ↩

20. Tứ Thiên Homestay. Booking.com listing inspected via Playwright on 2026-04-27. Gallery alt text "a white car parked in front of a building at Tứ Thiên Homestay." https://www.booking.com/hotel/vn/tu-thien-homestay.en-gb.html ↩