YouTube channel ID finder
Paste any channel URL (handle, custom, legacy user or /channel/) and get the parts an API or RSS feed needs, plus which forms carry a real channel id.
Channel URL
How to get the parts you need out of a channel URL
This tool takes a URL apart and tells you what it contains. That is a smaller promise than most channel id finders make, and it is the honest one for something that never calls YouTube.
- Copy the URL of the channel, not of one of its videos.
- Strip nothing by hand. Paste the whole thing, including any trailing /videos, /about or share token, and let the tool discard what it does not need.
- Read which form you pasted. The tool names it, because the four forms behave differently and they look similar.
- If the URL carried a UC id, copy it and you are finished.
- If it did not, use what the tool gives you to go and find the id: open the channel page and look for a /channel/UC link in it.
- Paste the id into whatever needed it, and store the id rather than the URL you found it in.
What each URL form carries, and what to do with an id
Only one of the four channel URL shapes contains an identifier. The other three are labels that YouTube resolves on its own side, which is why no amount of parsing gets an id out of them.
- youtube.com/channel/UC... carries the id directly. It is 24 characters, always begins UC, and is case-sensitive.
- youtube.com/@handle, youtube.com/c/name and youtube.com/user/name carry no id at all. They are names, resolved by YouTube at request time.
- A watch URL carries a video id and nothing about the channel that published it.
- Once you have the id, the RSS feed for the channel is youtube.com/feeds/videos.xml?channel_id=UC..., which needs no key and no quota.
- The uploads playlist for a channel is the same id with the UC prefix replaced by UU, which is the cheapest way to page through everything a channel has published.
- Share links often carry a ?si= tracking token. It is harmless, it is not part of the id, and it should not be stored with one.
What goes wrong
Most bad channel ids are copied rather than parsed. They come from the right page but the wrong part of it, and nothing complains until an integration returns nothing.
- Copying the channel name from the About page instead of the id. They are both identifiers to a human and only one of them is one to an API.
- Using the mobile share sheet, which hands you a youtu.be video link containing no channel information whatsoever.
- Storing the handle because it is readable. It is the owner's to change, and the day it changes every record keyed on it is orphaned.
- Pasting an id that got truncated by a narrow browser tab or a spreadsheet column. It is 24 characters, so count them.
- Assuming a legacy /c/ or /user/ URL is dead. Many still resolve, and they are not a sign that the channel has gone.
When you need an id, and when you do not
A handle is better for humans and an id is better for machines. Choosing badly is not fatal, it just decides who has to fix it later.
- For anything a person will click, use the handle. It is readable, it redirects, and it survives a channel rename in the way a printed id does not.
- For anything a system reads, use the id: an API call, an RSS subscription, an analytics row, a foreign key.
- If you need handle-to-id resolution in bulk, that is a job for the YouTube Data API. Its channels.list endpoint accepts a handle and costs one quota unit per call, which is far cheaper than the workaround it replaces.
- If you only need it once, opening the channel page and reading the id out of it takes less time than getting an API key.
The rest of the job
You just fixed one post. Now do the month.
The youtube channel id finder solves one piece of one post. OctoSpark plans, writes and schedules the whole calendar across every network you use, publishes it for you, and reports what actually performed.
- One calendar for every network
- Schedule once, publish everywhere
- Drafts written in your own voice
- See what actually performed
Open the full sign-up page
No card needed. These tools stay free either way.
Related free tools
- YouTube subscribe link generatorTurn your channel handle into a link that opens the subscribe dialog straight away. Paste it in a description, a bio or an email and save viewers a step.
- YouTube video schema generatorProduce valid VideoObject JSON-LD for a page embedding a YouTube video, so search engines can show it as a video result. Fill the fields, copy the tag.
- YouTube handle checkerCheck whether a YouTube @handle is available or already taken.
- YouTube thumbnail downloaderPaste a YouTube link and get every thumbnail size the video has, up to full 1280x720. Direct links to the images YouTube hosts: no signup, no watermark.
Frequently asked questions
How this tool works, what it cannot do, and what happens to what you put into it.
Why do APIs want the UC id instead of my handle?
A UC id is permanent and assigned by YouTube; a handle is chosen by the owner and can be changed at any time. Anything stored long term (an API integration, an RSS subscription, an analytics record) breaks when a handle moves, so the id is what those systems key on.Why can this tool not get an id from a /@handle URL?
The mapping from handle to channel id lives on YouTube, not in the URL, so reading it requires a request to YouTube. This tool is pure URL parsing and makes no such call. Open the channel page and look for the UC id in the page source or a video link, or use the Data API.What about a watch URL: can I get the channel from that?
Not from the URL alone. A watch link identifies a video, and the channel that owns it is only known to YouTube. The tool tells you this plainly rather than guessing.What is the difference between /c/, /user/ and /@ URLs?
They are three generations of the same idea. /user/ is the original username form, /c/ the later custom URL, and /@ the current handle. All three resolve to the same channel, and none of them contains the UC id.Is my data private?
Yes. This tool does its work in your browser, so whatever you type, paste or upload stays on your device. Nothing is sent to our servers, which is also why it keeps working if you go offline after the page has loaded.Is this really free?
Yes. Every tool here is free with no account, no credit card and no usage cap. They exist so that the people who need our scheduling product find us, which only works if the tools are genuinely useful on their own.Do I need an account?
No. Open the page and use it. An account is only for OctoSpark itself, where you plan, schedule and publish a whole calendar rather than fixing one post at a time.Can I use the output commercially?
Yes. Anything you produce here is yours, including for client and commercial work. We claim no rights over it and we do not watermark it.