Getting the screen onto your server
There is one directive involved and one line in your config. Everything below is about the two ways to point FiveM at a screen, and the four things that go wrong when it does not appear.
The resource folder
The export is a folder with a manifest in it. No markup, no stylesheet, nothing you have to maintain — the manifest names the screen and FiveM does the rest.
Pick one of the templates, drag the widgets you want onto the canvas and set the server name, palette and rules.
Download the generated resource folder. It holds an fxmanifest and a small data file, with no HTML to maintain on your side.
Any resource folder works. The resource is standalone, so load order and framework version do not matter.
Add the ensure line, remove the ensure line of the loading screen you were using before, and restart the server.
# server.cfg ensure ls_yourserver
Or set it straight in server.cfg
If you would rather not add a resource at all, FiveM reads the screen address from the config directly. This is the shorter route and it skips the folder entirely.
# server.cfg sets loadscreen "<your screen address>" sets loadscreen_manual_shutdown "true"
Leave loadscreen_manual_shutdown off unless something on your side is going to call the shutdown itself. With it on and nobody calling it, the screen stays up after the session has already started.
When nothing shows
Two resources with a loadscreen directive cancel each other out. Search your server.cfg for every ensure line that starts a loading screen and leave exactly one enabled.
The client caches the loading screen it last fetched. Clear the FiveM cache folder, or reconnect once after a full client restart rather than using the reconnect command.
That is loadscreen_manual_shutdown without the matching shutdown call. Either leave the setting off, or make sure the resource that owns the screen calls the shutdown when the session starts.
The widgets that call out to an endpoint need the address filled in. An empty endpoint is why a widget renders its placeholder rather than a number — it never invents one.
Questions
Does this replace my existing loading screen resource?
It does. FiveM honours one loadscreen directive at a time, so the old resource has to be disabled in server.cfg first. Leaving both enabled is what gives players a black screen instead of either design.
Do I have to re-upload anything after an edit?
No. The resource points at a hosted URL rather than carrying the markup, so an edit is live for the next player who connects. Nothing on your server changes and nothing restarts.
Does it depend on my framework?
No. A loading screen is a FiveM directive, not framework code. The exported resource imports nothing from QBCore, ESX, Qbox or vRP, so a framework update cannot break it.
What happens if the hosted screen cannot be reached?
FiveM falls back to its own default loading screen and the player still connects. A loading screen never blocks a join; it is a page shown while the client streams the world.
Can I keep the slug my server already points at?
Yes. The live screen URLs that servers already carry in their server.cfg are not being moved. The address a server.cfg holds today keeps resolving to the same screen.
Framework-specific notes
Still stuck? The 20 designs and the 50 widgets are all editable after the install, so nothing here has to be decided up front.