Skip to content

Install & update

The fastest path is the Config Builder or Build with AI: design your screen, export it and you get a ready-to-run 4zam_loading resource with your settings and files inside.

Build yours in the browser


Download

Use the zip you exported from the builder, or the stock version:

  1. Open the latest release.
  2. Download 4zam_loading.zip.
  3. Extract it into your server's resources so the folder is resources/4zam_loading.

The folder name matters: it must match the ensure line below.

Add to server.cfg

ensure 4zam_loading

Then restart your server. The loading screen shows the next time a player connects.

Only one loading screen

FiveM shows one loading screen. If another resource also declares a loadscreen (an older loading screen, or one bundled with a framework), stop or remove it so it does not take over.

Configuration

All settings live in one file:

resources/4zam_loading/html/config.json
  • Easiest: import that file into the Config Builder, change what you want and export again.
  • By hand: every option is in the Config reference. Put your own images, videos and music in html/assets/ and point to them as ./assets/your-file.webm, or use full URLs.

After editing, restart the resource (restart 4zam_loading) or the server.


Updating to a new version

What carries over: your config.json settings (theme color, rules, team, social headers and everything else) and your own images, audio and videos in html/assets/.

To update:

  1. Back up html/config.json and any files you added under html/assets/.
  2. Replace the resource: delete the old 4zam_loading folder and extract the new release in its place.
  3. Put your files back: copy your config.json over the new one and your files back into html/assets/.
  4. Restart the server.

Or skip the copying: import your old config.json into the Config Builder and export a fresh resource, which always uses the latest version.

Check the Changelog for what changed. New options are optional, so an older config.json keeps working.

Before you update

  • Do not overwrite your config.json unless the release notes explicitly say to.
  • If you changed the loading screen's own styles or code, back them up first: an update replaces them.

Coming from gucci_loading?

The resource was renamed to 4zam_loading in v1.2.0. Rename your folder to 4zam_loading and change your server.cfg line to ensure 4zam_loading.