Download the minimal loading-screen starter resource
The ZIP contains the same original fxmanifest.lua and loading.html shown below, plus a README, inside a magnate_loading_starter folder. It uses local HTML and no background media or external assets. Follow the resource-manifest tutorial for placement and coordinate with any existing loading-screen resource before enabling it on staging.
The progress handler was checked in a synthetic Node environment: an ordinary fraction updates the display, unrelated events and invalid/nonfinite values are ignored, and out-of-range numbers are clamped. Those checks validate the example’s JavaScript behavior; they do not establish FiveM connection success, spawn readiness or loading-screen shutdown.
No FiveM session or game runtime was used for this package. Start with the minimal example when investigating a theme, then retain the exact resource and server context with any later result. The README includes the reuse terms and this validation scope.
Begin with the loading page, not a large theme
This original example targets current FiveM/GTA V development. It has not been run in a FiveM session and does not claim GTA VI support. Create a development resource containing fxmanifest.lua and loading.html. The resource-manifest tutorial explains the folder placement if this is your first resource.
The Cfx loading-screen guide uses the loadscreen declaration for the special joining screen. Keep this initial resource small: one local HTML file lets you investigate installation and message behavior without also diagnosing external fonts, video playback or an asset bundle.
fx_version 'cerulean'
game 'gta5'
loadscreen 'loading.html'
files { 'loading.html' } Show the reported progress without inventing an ETA
Put the example below in loading.html. Its progress element has an associated label, and its status text starts with a waiting message. The event handler ignores unrelated messages and rejects values that are not finite numbers before updating the display.
The fraction is clamped between zero and one to keep unexpected values from producing an invalid visual state. The label says reported progress because a percentage alone does not establish how many seconds remain, whether a framework is ready or when a player will be able to move.
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>Server loading</title>
<body>
<h1>Joining the server</h1>
<label for="progress">Loading progress</label>
<progress id="progress" value="0" max="1"></progress>
<p id="status" role="status">Waiting for progress information.</p>
<script>
const bar = document.querySelector('#progress');
const status = document.querySelector('#status');
window.addEventListener('message', ({ data }) => {
if (!data || data.eventName !== 'loadProgress') return;
if (typeof data.loadFraction !== 'number' || !Number.isFinite(data.loadFraction)) return;
const fraction = Math.min(1, Math.max(0, data.loadFraction));
bar.value = fraction;
status.textContent = `Reported loading progress: ${Math.round(fraction * 100)}%`;
});
</script>
</body>
</html> Keep progress reporting separate from shutdown
Cfx documents a default loading-screen lifecycle and an optional manual-shutdown directive. This small example does not enable manual shutdown. Do not add that option merely because a downloaded theme includes it: decide which part of your application owns completion first.
If you later choose manual control, identify the readiness signal and the code path that closes the loading UI. Write those down before adding an animation. An attractive fade-out cannot fix a missing completion path, and reaching the end of a progress bar is not a substitute for application readiness.
Infinite loading screen: isolate the last completed stage
Record whether the custom page appeared, whether reported progress changed, whether game scripts started and whether the intended character or spawn interface became ready. A moving video or a 100% label does not identify which stage is blocked. Keep the timestamp and first relevant error beside each observation.
Cfx says the default screen lasts until SHUTDOWN_LOADING_SCREEN is called. With loadscreen_manual_shutdown enabled, it documents additional control through SEND_LOADING_SCREEN_MESSAGE and SHUTDOWN_LOADING_SCREEN_NUI once scripts start. Inspect which path your installed resource uses before adding another close call.
On staging, compare the minimal resource above with the customized theme while keeping the surrounding server configuration constant. If the minimal page completes but the theme remains, inspect the theme’s assets and completion handler. If both remain, follow the connection, framework and spawn errors rather than assuming the HTML theme is the cause.
Do not use a fixed timer as evidence of readiness. It may hide the screen before the player can proceed while leaving the underlying failure unresolved. Define which component owns completion, observe its readiness signal and verify the close path runs once under the intended conditions.
| Stage | Record |
|---|---|
| Page loads | Resource revision, local or remote page and first asset error |
| Progress arrives | Last observed event and fraction, without inferring an ETA |
| Scripts start | Relevant client and server startup errors |
| Application is ready | Actual framework or spawn readiness signal |
| Screen closes | Completion owner and default or manual shutdown path |
Render handover names as text
Cfx documents server handover data on window.nuiHandoverData and demonstrates rendering a player name as text instead of HTML. Follow that boundary when personalizing a welcome screen: a name is display content, not markup to execute.
Test a missing name, a long synthetic name and text containing angle brackets. Define a readable fallback and verify it without depending on background media. Do not publish connection details or private player data in a public troubleshooting screenshot.
Test the lightweight version before adding media
In your own development environment, verify a new connection, reconnection and a failed connection path. Observe the status text and game/client logs. Test a version without added media as a baseline, then add one asset at a time so you can isolate the change that caused a blank page or longer preparation.
For a video theme, assess the extra download and decode work separately from game loading. A looping background can continue after progress stops changing, which makes motion a poor health indicator. Keep visible text useful even when the background media fails to load.
| Observed problem | Inspect before changing the design |
|---|---|
| Default screen still appears | Resource startup and loadscreen path |
| Custom page is blank | Packaged files and HTML asset paths |
| Progress text never changes | Message event name and fraction value |
| Progress says 100% but joining continues | Readiness and shutdown logic separately |
| Theme works without video only | Media size, format and browser errors |
Questions, answered.
Is loadscreen the same as ui_page?
No. Cfx documents loadscreen for the special joining/loading frame. ui_page declares an ordinary resource UI page.
Does 100% loading progress mean the player has spawned?
Do not infer that from the percentage alone. Verify the application’s readiness and loading-screen shutdown behavior separately.
Sources & editorial notes
Source review: November 7, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.
- Cfx — Loading screens Official loading frame, progress messages and lifecycle documentation.
- Cfx — Resource manifest Official manifest metadata and file declarations.
Published by an independent editorial brand. Read our editorial standards.