Discord Banner Grabber

Profile banners require Nitro to set, so most accounts return a null banner hash. That is not an error and not a rate limit - there is genuinely no image, and no request will produce one.

A lapsed subscription does not delete the banner. Discord keeps the hash but stops displaying the image, so a lookup may return a hash for an account whose profile currently shows only the accent colour.

Server banners are a different thing entirely, stored against the guild rather than the user and unlocked by boost level rather than Nitro. A tool for one will not fetch the other.

A user banner lives at `https://cdn.discordapp.com/banners/{user_id}/{hash}.{ext}`, following the same pattern as avatars. The hash is assigned by Discord and changes on every upload, so a saved link stops resolving once the user changes their banner.

As with avatars, a hash beginning with `a_` marks an animated banner and must be requested as `.gif`; everything else is `.png`. Requesting the wrong extension either errors or returns a single frozen frame.

Not every account has one. Banners require Nitro to set, so the banner hash is null for most users, and a null hash means there is genuinely nothing to fetch rather than a failed request.

Accounts without a banner image may still have an accent colour, returned as a decimal integer on the user object. Discord draws that as a solid band where the banner would be, which is why some profiles have a coloured strip rather than a blank one.

The accent colour is derived from the avatar automatically unless the user overrides it, so it usually harmonises with their picture. It is a colour value rather than an image, so there is no file to download - only a hex code to copy.

Banners live on Discord's CDN at a fixed URL. The banner hash from the users endpoint is all you need to construct the direct link.