YouTube Thumbnail Downloader

YouTube Channel Art vs Video Thumbnails: Two Servers, Two Formats

People say "channel art" and "thumbnail" as though they were the same kind of object at different sizes. They are not. A video thumbnail is a JPEG at a fixed set of pixel sizes on img.youtube.com, addressed by an 11-character video ID. A channel's avatar and banner are PNG images on yt3.googleusercontent.com, and the avatar's address carries a size you can change. We measured both on 19 October 2026. The short version for this tool: it fetches the first kind only. A channel ID, a handle and a whole channel URL were all rejected by the thumbnail host with the same 404 and the same 1,097-byte grey JPEG, and its /channel/ and /ch/ paths do not exist at all. This page shows the requests, then shows where the channel pictures really live and how their size is actually set.

Three ways to name a channel, all rejected by the thumbnail host

Each of these was pasted where a video ID normally goes, in the same URL shape, one request each. All three returned 404, 1,097 bytes, image/jpeg, 120 × 90 — and the same SHA-1 every time, which is the fingerprint of the placeholder rather than three different failures.

What was put in the video-ID slotLengthStatusBytesSHA-1 (first 16)
channel ID244041,0976e902fa6302eb30c
channel handle174041,0976e902fa6302eb30c
whole channel page URL564041,0976e902fa6302eb30c

Then we tried three path shapes that a channel slot might plausibly use, in case the problem was only the address shape. None of them exist:

Path triedStatusBytesType
/vi_webp/<channelID>/maxresdefault.webp404552image/webp
/channel/<channelID>/maxresdefault.jpg4041,097image/jpeg
/ch/<channelID>.jpg4041,097image/jpeg

Note the 552 bytes on the first row: a miss on a .webp address returns a different placeholder from a miss on a .jpg address — two grey squares, chosen by the extension. Both are misses. So the honest answer to "how do I download channel art with a thumbnail tool" is that this host has exactly one working path, /vi/<videoID>/, and nothing else. A tool built on it cannot reach channel images no matter what you paste.

Flat vector illustration: on the left a small stack of rectangular picture frames labelled by shape alone; on the right a separate round portrait frame and a wide strip, connected to the rectangles by a broken dashed line
Different slots, different hosts, different formats — and no path from one to the other.

Where the channel pictures actually are

We fetched our own channel page on the same day (that request returned 200 and 1,150,129 bytes of HTML) and read the image addresses out of it. Twelve distinct avatar addresses were present, all on yt3.googleusercontent.com — a different host from img.youtube.com, serving PNG, not JPEG. That is the structural reason a video-thumbnail tool cannot fetch them: it is not a permissions problem or a naming problem, it is a different service.

One caveat we will not paper over: in that same fetch we found no banner address at all — zero matches for a banner-shaped URL in the HTML. The banner is almost certainly loaded by script after the page renders, which means the static HTML does not contain it. So this page makes no claim about what a banner address looks like, because we did not capture one.

The avatar size is in the address, and it works

An avatar address ends in a suffix like =s900-c-…. The number after =s is not decoration. We took one avatar address, replaced only that suffix, and fetched it six times. Every request returned 200, and the pixel dimensions came back exactly as asked:

SuffixStatusPixels (measured from the file)Bytes
=s8820088 × 88413
=s176200176 × 176654
=s400200400 × 4001,562
=s800200800 × 8003,891
=s12002001200 × 12007,035
suffix removed200512 × 5122,071

Two useful consequences. First, asking for a bigger avatar is a real possibility here — unlike a video thumbnail, where the slots are fixed and you cannot request 2000 × 1125 by typing it. Second, the file is a square PNG at every size, while video thumbnails on the other host are JPEG in 16:9 or 4:3 rectangles. If you are assembling a page that mixes both, the shapes and the formats will not match, and the avatar will need to be cropped to a circle by you — the site renders it that way, the file does not.

Which slot is which — and which ones this tool does not fetch

Four different pictures get called "a thumbnail" in conversation, and they have four different answers here. The sizes in the right-hand column are YouTube's own upload requirements, read from its help pages on 16 October 2026 — not measured by us, because they describe what you are asked to upload rather than what a server hands back.

SlotWhere it livesThis tool fetches it?Upload size (YouTube's requirement)
Video thumbnailimg.youtube.com/vi/<videoID>/yes — fixed set of names, JPEG1280 × 720 recommended, minimum 640 px wide
Shorts thumbnailsame host, different names in the same slotyes — the upright file is oar2.jpg1080 × 1920
Channel avataryt3.googleusercontent.comno — different host, PNG, not reachable from /vi/800 × 800 recommended, square
Channel bannerloaded by script; address not captured in our fetchno — and we did not record its address, so we do not claim oneminimum 2048 × 1152, 6 MB or less

The two upload figures that catch people out are worth repeating because they are not interchangeable with the fetch side: an avatar is stored square and displayed as a circle, so anything in the corners is cut off, and a banner is cropped differently on a phone, a computer and a TV, which is why YouTube specifies a safe area of 1235 × 338 inside the 2048 × 1152 minimum. The change-a-thumbnail guide has those figures in a table alongside the upload steps, if that is the side you need.

What to do with this, practically

Questions people actually ask

"Why does a channel link give me a grey square in a thumbnail downloader?"
Because a channel link contains no 11-character video ID, and the host answers a bad token with 404 plus a valid 1,097-byte grey JPEG rather than an error you can see. Measured 19 October 2026 on three different channel-shaped inputs: identical 404, identical byte count, identical SHA-1.

"Is channel art just a bigger thumbnail?"
No. Different host, different format (PNG rather than JPEG), different shape (square avatar, 16:9 banner rather than the 16:9-or-4:3 thumbnail set), and a different addressing scheme. Nothing about a thumbnail address can be edited into a working channel-image address — we tried three path shapes and all returned 404.

"Can I get a 1200-pixel avatar?"
Yes, by editing the suffix. =s1200 returned 1200 × 1200 at 7,035 bytes, and =s88 returned exactly 88 × 88 at 413 bytes. The number is honoured precisely at every size we tried. That flexibility does not exist on the video side, where the slots are fixed.

"Does removing the suffix give the original upload?"
No — it returned 512 × 512 at 2,071 bytes, which is a default render, not an original. If you need the largest honest copy, ask for the size you actually need rather than assuming no suffix means full resolution.

Every figure on this page comes from a request we made ourselves on 19 October 2026 and the status, byte count, content type, SHA-1 and pixel dimensions we read back from the response. The channel page fetch, the twelve avatar addresses, the three rejected token shapes, the three non-existent path shapes and the six avatar size variants were all measured in the same pass; the raw record is in our working notes and the upload-side sizes are YouTube's published requirements read on 16 October 2026, labelled as such wherever they appear. Two things we did not measure and therefore do not state: the address shape of a channel banner, and how the site chooses which video's picture to show on a playlist. Nothing on this page is an estimate. One channel was used, identified by ID only; no channel name appears here and no image from it is hosted on this site.