qb-core · QB

A loading screen for QBCore Framework

QBCore servers usually ship with qb-loadingscreen or a themed variant. Ours replaces it with a hosted screen you edit in the browser — no HTML, no re-uploads, and it keeps working after a QBCore update because nothing in the framework is touched.

Open the builder Full install notes

Resource folder: [qb]/ or resources/[standalone]/
Framework dependency: None
Lines to add to server.cfg: 1

Installing on QBCore Framework

01Design the screen

Pick one of the templates, drag the widgets you want onto the canvas and set the server name, palette and rules.

02Export the resource

Download the generated resource folder. It holds an fxmanifest and a small data file, with no HTML to maintain on your side.

03Drop it into resources/

Any resource folder works. The resource is standalone, so load order and framework version do not matter.

04Add one line to server.cfg

Add the ensure line, remove the ensure line of the loading screen you were using before, and restart the server.

# server.cfg
# switch the old one off first:
# ensure qb-core

ensure ls_yourserver

Worth knowing on QBCore

Remove qb-loadingscreen first

FiveM only allows one resource with a loadscreen directive. Comment out or delete the ensure line for qb-loadingscreen in your server.cfg before adding ours, otherwise neither will show.

Drop it in any resource folder

The generated resource is standalone — it does not depend on qb-core, so it can live in [standalone], [qb] or the root of resources/. Load order does not matter.

Survives framework updates

Because the screen is hosted and the resource is just a pointer, updating QBCore never overwrites your design. Edits you make in the editor go live without touching the server.