How to Get the RSS Feed for a YouTube Channel

Every YouTube channel publishes an RSS feed, undocumented in the interface but entirely public. The URL is youtube.com/feeds/videos.xml?channel_id=CHANNEL_ID, and it gives you a plain list of recent uploads with no recommendation system in between.

The channel feed needs the channel ID — the UC… string — not the @handle. A handle in that URL returns nothing.

Paste a handle, a video URL or a channel URL and the generator resolves the ID and builds both feed URLs, verified against the live feed rather than assembled blindly.

If you only need the ID itself, that is how to find a YouTube channel ID:

Each entry carries the video title, its URL, the channel, a description snippet and a thumbnail reference. Feeds return the most recent uploads only — typically the last fifteen — and they are not a complete archive. There is no way to page backwards through a channel's history with RSS.

Two other limits worth knowing before you build anything on it: Shorts and regular uploads both appear with nothing distinguishing them beyond the video itself, and scheduled premieres can appear before they are watchable.

Following without an algorithm. A subscription feed shows what a channel actually published, in order, with nothing inserted and nothing suppressed. For research, competitor monitoring or simply following ten channels properly, that is a different product from the YouTube home page.

Automation. An RSS feed is the simplest possible trigger for "when this channel uploads, do something" — post to a Slack channel, add to a reading list, notify a team. No API key, no quota.

Archiving. A feed reader keeps a record of what was published, which is useful when a video is later edited, retitled or removed.

The XML is plain enough to consume directly, which matters if you are wiring it into something rather than reading it yourself. Each <entry> carries a <title>, a <link> to the watch page, a <yt:videoId>, the channel, and a media group with the thumbnail. There is no authentication, no key and no quota, which is the reason to prefer it over the Data API for simple "what is new" cases.

The usual gotcha is polling frequency. The feed is cached, so hammering it every minute returns the same document and achieves nothing except looking like abuse. Every fifteen minutes is more than enough for a channel that uploads weekly, and hourly is plenty for most monitoring.

If you need anything the feed does not carry - view counts, full descriptions, older uploads, comments - that is where the Data API starts, and where quota begins to matter.

If the goal is the opposite — getting other people to subscribe to you — the channel ID also builds a one-click subscribe URL:

See the YouTube subscribe link.

An RSS feed is a reasonable way to render a "latest videos" list without calling the Data API and spending quota. If you are also embedding the player, do it responsively and privately:

See YouTube embed code. YouTube's own API documentation, if you outgrow the feed, is at Google Developers.

Build and verify the feed URL for any channel with the RSS feed generator.