FiveM Image Sizes & Assets: The Definitive Guide

Getting FiveM image sizes wrong costs you visibility, performance, and polish. An oversized server icon that the browser can't display correctly, a stretched banner, or uncompressed vehicle textures eating into player VRAM — these are avoidable problems with a single reference document. This guide covers every major visual asset in FiveM with exact dimensions, accepted file formats, and the precise location in your server configuration where each one is set.

Whether you are building a server from scratch or refreshing the branding on an existing community, the table below is the single source of truth you need. All dimensions listed here are authoritative — do not use third-party guesses that circulate on forums.

Complete FiveM Asset Dimensions Reference Table

Server Icon: 96x96 PNG

The server icon is the smallest but most visible asset in FiveM. It is displayed beside your server's name in the multiplayer browser and must be named icon.png, placed directly in the root of your server directory — the same folder that contains your server.cfg. The file must be exactly 96x96 pixels. FiveM does not resize it; an off-size image will appear distorted or may not display at all.

Server Banner: 1900x520 PNG or JPG

Server banners are set via convars in server.cfg. Two separate banner convars exist: banner_detail for the banner shown in the server info panel, and banner_connecting for the banner shown during the connection handshake before your loading screen fires. Both accept a publicly accessible HTTPS URL pointing to an image file. The recommended dimensions are 1900x520 pixels.

# server.cfg — server banner convars
sets banner_detail "https://yourcdn.com/assets/banner_detail.png"
sets banner_connecting "https://yourcdn.com/assets/banner_connecting.png"

Host your banner images on a reliable CDN or static hosting service. If the URL is unreachable, FiveM will simply show a blank area rather than erroring — but players will see an unprofessional empty panel. Use PNG for sharp logos and text, or JPG for photographic backgrounds at smaller file sizes.

Loading Screen: 1920x1080 Background with NUI

A FiveM loading screen is a full NUI resource — an HTML page that FiveM renders in the CEF browser while the game world loads. The background image for a loading screen should be 1920x1080 pixels (Full HD, 16:9 aspect ratio) so it fills the screen without scaling artifacts on the most common monitor resolutions. The resource declares itself via the loadscreen directive in fxmanifest.lua.

Supported Loading Screen File Formats

• Background image: PNG (lossless, best for logos and UI overlays) or JPG (smaller file size for photographic backgrounds)
• Audio: MP3 or OGG — both work in FiveM's CEF environment
• Fonts: web fonts loaded via @font-face or a CDN link work in the NUI context
• Video: HTML5 video (MP4/H.264) can be used as a background via a <video> element

Discord Rich Presence Assets: 512x512

Discord Rich Presence lets players show their FiveM server name, player count, and a custom image in their Discord profile. You set it up by creating an application in the Discord Developer Portal, uploading art assets under Rich Presence > Art Assets, and then calling the native functions in a client-side Lua script. Discord recommends 512x512 pixels for art assets, with a hard maximum of 1024x1024. Assets must always be square.

-- client.lua — Discord Rich Presence setup
CreateThread(function()
    SetDiscordAppId('YOUR_APPLICATION_ID')
    SetDiscordRichPresenceAsset('your_asset_name')
    SetDiscordRichPresenceAssetText('Your Server Name')
    SetDiscordRichPresenceAssetSmall('small_icon_name')
    SetDiscordRichPresenceAssetSmallText('Playing FiveM')
end)

Vehicle Liveries and Textures: Power-of-Two Only

Vehicle textures in FiveM are stored in YTD (texture dictionary) files, which contain DDS-compressed images. GTA V and FiveM only support power-of-two texture dimensions: 1024x1024, 2048x2048, and 4096x4096 pixels. Using non-power-of-two sizes causes corruption, stretching, or crashes. Choose your resolution based on how prominent the vehicle is in your server.

DXT Compression: DXT1 vs DXT5

• DXT1: No alpha channel. Use for solid liveries and body textures with no transparency. Smallest file size and lowest VRAM usage.
• DXT5: Includes alpha channel. Use for decals, dirt overlays, or liveries that need transparency layers.
• Never export uncompressed (RGBA8) textures to a YTD — the file size and VRAM cost is massive and will cause stuttering for all nearby players.
• Generate mipmaps when exporting your DDS file. Missing mipmaps cause visible LOD pop-in at distance.

Texture Optimization Tips to Reduce Stutter

1. Always use power-of-two dimensions. Non-power-of-two textures are not supported and will cause issues.
2. Match texture resolution to screen visibility. A generic background prop does not need a 4096x4096 texture; 1024x1024 is sufficient.
3. Use DXT1 wherever possible. It delivers 8:1 compression over uncompressed RGBA with minimal visible quality loss on solid-color liveries.
4. Include all mipmap levels when exporting DDS. This allows the GPU to use lower-resolution versions at distance, reducing VRAM pressure.
5. Audit your YTD dictionary sizes. A single YTD over 64 MB is a red flag — split the dictionary or reduce individual texture resolutions.
6. Test streaming load on a populated server. Textures that look fine in solo testing may cause stuttering when 30+ players all stream vehicles simultaneously.

Quick Format Reference

Summary and Next Steps

Getting these dimensions right the first time saves hours of debugging and keeps your server looking professional in every touchpoint — from the browser list to a player's Discord status. Bookmark this page as your go-to reference whenever you are creating or updating server assets. If you need custom-designed assets that match the exact specs above, the team at CRM Development produces server branding packages, loading screens, and vehicle livery packs built to these standards from the ground up.