Booking.com — Stay search

Search & DiscoverySee it livebooking.com

Destination, dates, and travelers form one prominent search bar beneath a clear stays headline and travel-category navigation.

Booking.com — Stay search — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Search & discovery

Why this pattern works

Multi-field searches that must explain the required inputs before showing results.

Design notes

Surface: Booking.com public stays search homepage; sign-in promotion dismissed.
Navigation: Account utilities above a row of travel-product tabs.
Layout: Blue header and introduction, yellow-framed search row, supporting benefit panels below.
Density: Moderate, with the required search fields grouped tightly.
Color: Deep blue, white, and yellow search emphasis.
Type: Bold sans headline, small form labels, clear primary-button text.
Pattern: Group related search constraints into one continuous form with a single submit action.
States: Initial unsigned search state; date selection, validation, and search results are not captured.
Don't: Do not rely on placeholder text as the only accessible field label.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Booking.com — Stay search
Source: https://www.booking.com/
Swipefile reference: https://swipefile.design/ref/popular-booking-com-stay-search/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Booking.com public stays search homepage; sign-in promotion dismissed.
- nav: Account utilities above a row of travel-product tabs.
- layout: Blue header and introduction, yellow-framed search row, supporting benefit panels below.
- density: Moderate, with the required search fields grouped tightly.
- color: Deep blue, white, and yellow search emphasis.
- typography: Bold sans headline, small form labels, clear primary-button text.
- pattern: Group related search constraints into one continuous form with a single submit action.
- states: Initial unsigned search state; date selection, validation, and search results are not captured.
- dont: Do not rely on placeholder text as the only accessible field label.

Useful for: Multi-field searches that must explain the required inputs before showing results.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Multi-field searches that must explain the required inputs before showing results.

Booking.com — Stay search

Make it your own

Keep exploring