Loading screensbeginner6 min readupdated 25 Oct 2026

Your changes aren’t showing up in game

The short answer

FiveM caches the loading screen on each client. After an edit, wait about a minute for the edge cache to expire, then have players clear their FiveM cache folder — or run refresh and restart the resource on the server.

You edited the screen, saved, and players still see the old one. This is caching, and there are three layers of it.

Your changes aren’t showing up in game — illustrated with a FiveM-compatible minimap render

#Wait out the edge cache

Hosted screens are cached at the edge for about 60 seconds so they load fast worldwide. Immediately after saving, an existing cached copy may still be served. Give it a minute before assuming something is wrong.

#Clear the FiveM client cache

FiveM keeps its own copy on each player’s machine. Deleting the cache folder in the FiveM application data directory forces a fresh fetch on the next connect. This is the fix that works when nothing else does.

#Refresh and restart on the server

If you are using a local file rather than a hosted URL, the resource itself has to be reloaded before anyone sees a change.

lua
# server console
refresh
restart pityus_yourslug

#Confirm you edited the screen that is actually live

If you have several screens, check that the slug in your fxmanifest matches the one you edited. Editing a different screen and wondering why nothing changed is more common than it sounds.

Share this guideXRedditFacebook

Questions

How long until my edit is live?
Usually under a minute for new connections. Players already connected keep the version they loaded with.
Do I need to re-export the resource after every change?
No. With a hosted screen the resource is only a pointer, so you export it once and never again — that is the main reason to use one.

Ready to pick a map?

Twelve themes on three base map styles, $8 each, instant download.

Relevant to what you just read

The tool for this

A drag-and-drop loading screen, hosted for you From Free, built in the browser, exported as a drop-in resource.