> For the complete documentation index, see [llms.txt](https://docs.feedspring.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedspring.com/introduction/feeds/youtube.md).

# YouTube

Use FeedSpring to display YouTube videos on your site.

This includes video thumbnails, titles, descriptions, and channel information, all available as structured data.

***

### What this feed includes

A YouTube feed contains:

#### Channel data

* Channel name
* Channel avatar
* Subscriber count
* Channel link

#### Video data

* Thumbnail image
* Title
* Description
* Link to video
* Timestamp
* View count
* Like count
* Duration

***

### What makes YouTube different

YouTube is structured and content-driven.

This means:

* Titles are a key part of the layout
* Thumbnails are designed for clarity and click-through
* Videos are often longer and more detailed
* Content is typically consumed as a library rather than a stream

***

### Available fields

#### Video fields

| Field         | Description                  |
| ------------- | ---------------------------- |
| `thumbnail`   | Video thumbnail image        |
| `title`       | Video title                  |
| `description` | Video description            |
| `link`        | URL to the video             |
| `timestamp`   | When the video was published |
| `view-count`  | Number of views              |
| `like-count`  | Number of likes              |
| `duration`    | Video length                 |

***

#### Channel fields

| Field              | Description           |
| ------------------ | --------------------- |
| `name`             | Channel name          |
| `avatar`           | Channel image         |
| `subscriber-count` | Number of subscribers |
| `channel-link`     | Link to the channel   |

***

### Video behaviour

YouTube content is video-first.

* Thumbnails are typically used as previews
* Videos are usually played on click
* Duration is often displayed alongside content
* Layouts may prioritise titles and metadata

***

### Title and description behaviour

Titles are a key part of YouTube content:

* Often longer than other platforms
* Designed to attract clicks

Descriptions can vary:

* Some are short
* Some are long and detailed

Consider:

* Truncating long descriptions
* Prioritising titles over descriptions

***

### Performance considerations

YouTube videos are heavier than images or text.

Consider:

* Using thumbnails instead of auto-playing videos
* Limiting the number of items shown
* Loading content efficiently

***

### Engagement data

YouTube includes engagement metrics:

* Views
* Likes

These values:

* Change over time
* Reflect popularity and performance

***

### Typical use cases

YouTube feeds are commonly used for:

* Video sections on landing pages
* Content libraries or resource hubs
* Tutorials and education pages
* Media or press sections

***

### Summary

* YouTube feeds are structured and video-driven
* Titles and thumbnails are key
* Duration and metadata add context
* Best used for content libraries and structured layouts

***

### Next steps

* Learn how to use these fields with your delivery method
* Explore layout patterns for video content
* View other feed types


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.feedspring.com/introduction/feeds/youtube.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.