When the upload will not take

Discord rejects an image over 10MB outright rather than compressing it, and a full-colour animation at 960x540 passes that limit easily. Every animated file in a pack is already built under the cap, so if you are being refused, check which file you picked.

• If you edited the file yourself, the re-export is almost certainly the cause. Editors default to a full palette.
• If you need it smaller, cut the duration before you cut the palette. Length is invisible, banding is not.
• The still PNG always works and is the right fallback.

This is the single most common surprise. The slot is not hidden by a permission or a setting; it does not exist until the server is boosted far enough.

Until the server reaches Level 2 the still banner is still worth using: as the header image of a rules embed, as a pinned image in a welcome channel, or on your listing page. Nothing is wasted, it just goes somewhere else for now.

Both the server icon and the profile picture are masked to a circle, and nothing changes that. The icon in a pack is designed inside the inscribed circle for exactly this reason, with the corners carrying scene rather than content.

• If you replaced the mark with your own, check it as a circle at 48 pixels, which is the size the sidebar actually draws.
• Leave a margin inside the circle as well. Discord's hover ring eats a few pixels at the edge.

Two different causes, and they look identical from the outside.

1. The slot is still-only. The invite splash is the one that catches people: Discord shows it as a still image no matter what you upload.
2. The slot animates but the server is not boosted for it. An animated server icon needs Level 1; an animated profile picture needs Nitro on your own account.

Work through these in order. The first three are in your config; the fourth is on the machine you are testing from and is the reason people think the first three did not work.

sets banner_detail "https://example.com/banner_detail.png"
sets banner_connecting "https://example.com/banner_connecting.png"

1. The line starts with sets, not set. Without the s the value is server-side only and never reaches the list.
2. The URL ends in the image file itself. A link to a page that shows the image, or to a sharing service, does not work.
3. The URL is HTTPS. Plain HTTP is ignored.
4. The file is publicly reachable. Open the URL in a private browser window with no login.
5. Restart the server so the convar is read, then clear your own client cache before you judge it.

The client caches these images aggressively. After replacing a file at the same URL you will keep seeing the old one until the cache clears, which is why changing the filename when you change the image saves a lot of confusion.

A loading screen is a resource, not a media file. If the manifest does not list an asset, the client never receives it, and the page loads with nothing in it. Locally everything is on disk already, so the mistake is invisible until it is live.

fx_version 'cerulean'
game 'gta5'

loadscreen 'index.html'
loadscreen_cursor 'yes'

files {
  'index.html',
  'style.css',
  'script.js',
  'art/*.png',
  'art/*.webp'
}

• Every asset the page references must be covered by a files entry, including fonts and every image.
• The resource folder goes in resources/ and is enabled with one ensure line in server.cfg.
• Check the F8 console on the client for 404s; they name the missing file exactly.

MP4 cannot be relied on for an alpha channel. The container supports it in theory and almost nothing plays it in practice, so a transparent clip exported as MP4 shows up with its background filled in black.

The watermark in a pack is a WebM for exactly this reason. In OBS it goes in as a media source with the loop option on; in a NUI overlay it is a video element with the same file.

The 96x96 in a pack is cut from the same 1024x1024 render as every other copy of the logo, so it is the same mark rather than a separate drawing. Point the server at it the same way as the banners, and give it a filename that changes when the image does.

• Use the 96 copy, not the 1024. The slot is small and a large file gains nothing.
• Transparency is kept, so it sits on the list background without a box.
• If it still does not appear, the cause is the same cache that hides a changed banner.

320 is a ceiling, not a suggestion. The panel in a pack is rendered at 960x300 and delivered at 320x100, so it is sharp on a high-density display without being scaled by the browser.

• Set the panel's link to your invite, not to your site root. It is the only one-click path from a channel to your server.
• Keep it to two pieces of information: the server name and what happens on click.
• Twitch shows panels as stills. The animated copy is for Discord and listing sites.

YouTube shows three different crops of the same file. The full 2560x1440 appears on television apps, a 2560x423 strip on desktop browsers, and the centre 1546x423 everywhere, phones included.

• Put the server name and one line of description inside the centre strip and nothing else.
• The outer thirds carry scene that frames the centre; they must not contain anything that matters.
• Use YouTube's own preview before saving. It shows all three crops and it is accurate.
• Put the invite in the channel links row under the banner, where it is a real link, rather than as text inside the image.

The plate in a pack is already 1280x720. If an export is being refused, it is usually because an editor saved it as PNG at full quality and pushed it over 2MB, or because an animated file was picked by mistake.

• Export as JPG rather than PNG. At this size the difference is invisible and the file is a fraction of the size.
• Keep the bottom right clear; the duration badge sits there.
• Add the episode title in one weight at one size, every video. Consistency is what makes a channel recognisable in a grid.

The exact figures differ between TikTok, Reels, Stories and Shorts, and they change with app versions. Designing to the middle sixty-five per cent is what makes one file work on all of them, which is how the vertical render in a pack is laid out.

• The right edge is covered for its full height by the action rail on most apps, so centre rather than range right.
• The caption takes the bottom. Leave it empty rather than fighting it.
• The clip is silent on purpose so a creator's track runs across the whole edit.

Drop a file on the Main background image box in the first step of the editor, or browse for one. It is re-encoded on the server at up to 3840 pixels on the long edge, without chroma subsampling, so type laid over it stays sharp. Metadata is stripped.

• PNG, JPEG, WebP or GIF, up to 8MB.
• It becomes the background on every format, not just the one on screen.
• To use it on one file only, turn on Edit this one on its own first, then upload.
• The Backdrop step has the same control, plus the painted album to pick from instead.

By default a change applies to all twenty formats at once, which is the point of the system. When one slot needs something different, switch that file into its own mode and the rest stop following it.

1. Pick the format, from the strip under the canvas or from the Review step.
2. Press Edit this one on its own, or double-click its chip.
3. A violet band appears naming the file. Everything you change now stays on it.
4. Clear sends every format back to the shared settings.

Two different things, for two different needs.

• Leaving and coming back on the same browser restores your last edit automatically.
• The Share button copies a link with the whole configuration encoded in it, so somebody else opens exactly what you see. No account needed on either end.
• Ctrl+Z and Ctrl+Shift+Z step through your changes; the toolbar has both.

The order moves from paid to rendering to ready. You do not need to keep the tab open: the payment is confirmed through a webhook rather than on the page you are returned to, so closing the tab after paying does not lose the order.

• Download links are signed and expire after about fifteen minutes. The orders page issues a fresh one whenever you need it, as many times as you need.
• The whole pack arrives as one ZIP, organised by platform.
• If the status stays on rendering for a long time, the order page is the right place to say so; the render can be re-queued from the admin side without a new payment.

Nothing in the paid pack carries a watermark. The previews on the site do, which is the only difference between what you see and what you download.

The price assumes one render per purchase, which is what keeps it where it is. Configure and compare as much as you like before checkout, which costs nothing, because that is where the freedom is meant to be.

If a file came out wrong, that is a different thing and it gets fixed: the order can be re-rendered without a second payment.