FiveM Image Sizes & Assets: The Definitive Guide

Bookmark this table. The Source column matters: “Cfx docs” means FiveM enforces or documents it, “Discord” means Discord publishes it, and “convention” means it is what works in practice across thousands of servers but nothing will reject a different size.

The server icon is the small square next to your server name in the FiveM server browser and on your cfx.re page. It is the only image FiveM is strict about. The Cfx documentation for load_server_icon states that the file must be a 96×96 PNG — a JPG, a 128×128 PNG or a renamed WebP will not show.

# The file sits next to server.cfg (the server's working directory)
load_server_icon myLogo.png

• Export at exactly 96×96. Resizing a large logo down to 96 in a browser tool usually blurs it — export from the design file at that size, or downscale with a sharp filter and check it at 100% zoom.
• Transparency works, but the list background differs between light and dark themes. A logo on a solid rounded square reads everywhere.
• Keep detail minimal. At 96 pixels a wordmark is unreadable; use the symbol from your logo, not the full lockup.
• The path is relative to where the server runs. If the icon does not appear, the server console prints an error when it cannot open the file.

We cover the icon on its own — including how to make one that stays readable at that size — in the FiveM server icon guide.

FiveM supports two optional banners set as server variables. banner_detail is shown on your server’s detail page in the server browser; banner_connecting is shown while a player is connecting. Both are URLs, so the image lives on a web host, not on the game server.

sets banner_detail "https://cdn.example.com/banner-detail.png"
sets banner_connecting "https://cdn.example.com/banner-connecting.png"

Cfx has never published an official banner size, and you will find wildly different “official” numbers online. The honest answer: the banner is drawn as a wide strip and scaled to the space available, so what matters is the shape. The long-standing community template on the Cfx forum uses 1865×108; many servers use 1920×200. Either works if you design for a wide, short strip and keep every important element in the middle third.

The full walkthrough, including safe areas and animated banners, is in the banner guide.

A loading screen is an HTML page rendered by FiveM’s built-in Chromium, so it follows web rules rather than game rules. There is no required resolution: the page fills the player’s window at whatever resolution they run. That is why the right approach is to design for 1920×1080 and build responsively, rather than exporting one giant image and hoping it fits.

Keep the text-safe area in the centre 1280×720 of your 1920×1080 design. A player on a 21:9 ultrawide sees extra width, a player on a 16:10 laptop loses a sliver of the sides, and a centred safe area survives both. Our guides on responsive loading screens, video backgrounds and fonts go deeper on each element.

Everything drawn by a script’s interface — inventory, HUD, phone, menus — is NUI: another HTML page in the same Chromium. Those images follow the same web rules, with one important convention for inventories.

• ox_inventory loads item images from nui://ox_inventory/web/images by default. The file name must match the item name exactly, in lowercase: an item called water needs water.png. The folder can be changed with the inventory:imagepath convar.
• The de-facto icon size is 100×100 with a transparent background and the item centred with a small margin. Larger sources (256×256) are fine but are downscaled anyway, so they only cost memory.
• qb-inventory and most QBCore inventories read from their own html/images folder with the same name-matching rule.
• HUD icons are best as inline SVG or an icon font, which stay sharp at every resolution and cost almost nothing.

Weapon icons follow the same rules; the weapon studio covers them in detail in its weapon inventory image guide.

Textures that are streamed into the game world — vehicle liveries, clothing, weapon skins, map tiles — are not web images. They live in .ytd texture dictionaries, compressed in GPU formats (DXT1, DXT5, BC7) with mipmaps, and the rules are the engine’s.

• Use power-of-two dimensions: 512, 1024, 2048, 4096. Non-power-of-two textures break mipmapping and waste memory.
• Pick the smallest size that looks right at the distance players see it. A pistol grip does not need 4096×4096.
• Compress: DXT1 for textures without alpha, DXT5 when you need alpha, BC7 when quality matters more than size.
• Generate mipmaps. Without them distant objects shimmer and the game reads full-resolution data it never needed.

The FiveM server checks every streamed asset when it starts. Any asset using more than 16 MiB of physical or virtual memory is printed as a warning, the colour gets more alarming at 32 and 64 MiB, and above 48 MiB the message adds: *“Oversized assets can and WILL lead to streaming issues (such as models not loading/rendering).”* Treat 16 MiB as your ceiling, not 48.

Minimap textures are the one case where you have no choice at all: the replacement must match the dimensions and layout of the original tiles. The minimap studio explains the full layout in its minimap technical specification.

For most FiveM communities Discord is the front door, so its images deserve the same care as the server’s.

Rich Presence is the “Playing on your server” card players see on each other’s profiles; FiveM can set it with a few natives. The whole setup is in the Discord Rich Presence guide, and the full Discord art set in Discord branding sizes.

• Open Graph image: 1200×630. This is the card shown when your website link is shared on Discord, X and Facebook. Without it your link posts as bare text.
• YouTube thumbnail: 1280×720 (16:9, minimum 640 wide). A face or a vehicle and three words beat a paragraph.
• Vertical video: 1080×1920 for TikTok, Reels and Shorts — the channel that brings most new players to roleplay servers today.
• Favicon: a 512×512 PNG master, exported down to 32×32 and 180×180 (Apple touch icon).

Anything referenced by URL — banners, loading screen assets hosted online, NUI images loaded from the web — is only as reliable as its host. The server icon is the exception, because it is read from disk.

1. 1Use HTTPS. The loading screen and NUI pages are served securely, and Chromium blocks http:// media on secure pages.
2. 2Use a direct file URL. The address must return the image itself — a share page from a cloud drive returns HTML.
3. 3Use a host that allows cross-origin requests if scripts read the file (for example to draw it on a canvas).
4. 4Avoid links that expire: Discord attachments and some image hosts sign their URLs.
5. 5Version your files (banner-v2.png) when you change them, so players do not keep a cached old copy.

Files placed inside a resource and declared in the manifest are served by the FiveM server itself and never expire, which is often the simplest option for loading screen assets. See how NUI asset paths work.

Design once, export many times. Keep a single master file per asset and export every size from it, so a colour change updates everything at once.

1. 1Create a master logo as a vector (SVG or a vector layer) with a symbol-only variant for small sizes.
2. 2Export the server icon at 96×96 PNG from the symbol variant.
3. 3Export the Discord icon at 1024×1024 and let Discord downscale it.
4. 4Build the loading screen background at 1920×1080 and export WebP at quality 80–85.
5. 5Export banners at 1865×108 or 1920×200 with the text centred.
6. 6Check every export at 100% zoom, on a dark and a light background.

Consistency across all of these is what makes a server look established. The server branding kit guide turns this list into a reusable set of colours, fonts and templates.