YouTube — Search results

Search & DiscoverySee it liveyoutube.com

Video results pair large thumbnails with titles and metadata, while a persistent search bar, filters, and side navigation support refinement.

YouTube — Search results — captured interface — Viewport capture · opening screen

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

Search & discovery Content & media

Why this pattern works

Media search results where viewers compare content visually before opening an item.

Design notes

Surface: YouTube public results for “design systems,” signed out.
Navigation: Persistent left navigation and top search, with filtering controls above the results.
Layout: Vertical result rows place thumbnails beside a title, channel, and supporting metadata.
Density: Moderate to high, with clear repetition across results.
Color: White, black, gray dividers and metadata, varied thumbnail imagery.
Type: Prominent video titles above smaller channel and view information.
Pattern: Make each result scannable as one image-and-metadata unit and keep the active query available.
States: Populated public search results; recommendations and rankings may vary over time.
Don't: Avoid copying individual thumbnails or treating the observed result order as a stable ranking.

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: YouTube — Search results
Source: https://www.youtube.com/results?search_query=design+systems
Swipefile reference: https://swipefile.design/ref/popular-youtube-video-discovery/
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: YouTube public results for “design systems,” signed out.
- nav: Persistent left navigation and top search, with filtering controls above the results.
- layout: Vertical result rows place thumbnails beside a title, channel, and supporting metadata.
- density: Moderate to high, with clear repetition across results.
- color: White, black, gray dividers and metadata, varied thumbnail imagery.
- typography: Prominent video titles above smaller channel and view information.
- pattern: Make each result scannable as one image-and-metadata unit and keep the active query available.
- states: Populated public search results; recommendations and rankings may vary over time.
- dont: Avoid copying individual thumbnails or treating the observed result order as a stable ranking.

Useful for: Media search results where viewers compare content visually before opening an item.

## 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: Media search results where viewers compare content visually before opening an item.

YouTube — Search results

Make it your own

Keep exploring