The same screen on whatever you run
A loading screen is a FiveM directive rather than framework code, so the exported resource imports nothing from your framework and a framework update cannot overwrite it. What does differ between frameworks is which resource you have to switch off first, and where the folder usually lives. One page each.
PICK YOURS
One page per framework
Which resource to switch off, where the folder usually lives, and the one cfg line that differs.
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.
[qb]/ or resources/[standalone]/
ESX LegacyESX servers typically run esx_loadingscreen or a bundled HTML screen that has to be edited by hand. Ours is a drag-and-drop replacement hosted for you — change the server name, rules or background whenever you like and every player sees it on their next connect.
[esx]/ or resources/[standalone]/
Qbox ProjectQbox is a modern QBCore fork with a cleaner resource layout, and it pairs well with a hosted loading screen: one line in server.cfg, nothing bundled into your repo, and no HTML to maintain alongside your ox-based stack.
[standalone]/ or resources/[qbx]/
vRP FrameworkvRP servers are often older builds where the loading screen is a hand-written HTML folder nobody wants to touch. Swapping it for a hosted screen means you get a modern design without editing a single line of markup.
resources/ (any folder)