How to Change the Bridge Image in a FiveM Loading Screen

To remove a bridge image from a FiveM loading screen, first identify whether it belongs to your custom loading resource or to the client’s own connection interface. CSS in your resource can only change the page that resource controls.

Find the owner of the image

On a test server, inspect active resource manifests for the loadscreen directive. Resource names need not contain the word loading. Open the referenced HTML and its styles/scripts, then search for the visible image filename or background declaration.

If the bridge is an image or video inside that page, record the exact selector or asset reference. There is no documented universal .bridge-overlay class that removes every FiveM connection image.

Change an existing loading resource

1. Back up the entire resource and its configuration. Check the package’s license and customization instructions.
2. If the resource exposes a background setting, change that setting first. Otherwise edit the exact image, video or CSS declaration you identified.
3. Keep required local assets declared in fxmanifest.lua. Preserve progress and shutdown logic; removing the surrounding container can break those elements.
4. Start the changed resource on staging and perform a fresh connection. Verify that the image changed and that progress, readable text and transition into the game still work.

When the image belongs to the default screen

Use a supported custom loadscreen resource if you want to replace the default resource-loading presentation. Follow the Cfx.re loading-screen documentation and the complete starter tutorial below.

A custom loading page does not necessarily replace every earlier client connection screen. Do not modify FiveM client internals or delete unrelated UI elements to hide an image you do not control.

If the old image remains

Check that the edited resource is the active loadscreen, that its asset path changed as expected and that another stylesheet is not overriding it. Inspect NUI errors with the documented development tools.

Retest reconnects and a full server restart. Use targeted cache recovery only after identifying stale files; broad server-cache deletion is not a CSS debugging step.