FiveM server artifacts: how to update safely

Server artifacts are the FXServer program files. Updating them means swapping that one folder for a newer build from the Cfx.re Server Download page, while txData, server-data and your database stay put. On 19 October 2026 the Recommended build is 35245. Cfx.re asked servers to update to 35245 or later before 15 October 2026, when its compatibility window for older FXServer versions ended.

The steps are the same for ESX, QBCore and Qbox servers, because the artifact holds no framework code.

Before you start

• Access to stop the server. The txAdmin panel, the console window, or SSH on Linux.
• An extractor. On Windows, 7-Zip or WinRAR for server.7z. On Linux, the xz-utils package for fx.tar.xz.
• Where your txData is. txAdmin keeps its settings, admins and, by default, your deployed server-data in txData. Its default place differs by system:

On Linux, deleting the artifact folder deletes txData with it. The Linux steps move it across.

• The game edition. Cfx.re lists Asset Escrow as “Not implemented yet” on GTA V Enhanced. If your server runs escrowed scripts, such as paid scripts from the Cfx.re Portal, choose the FiveM / RedM platform on the download page, not FiveM for GTAV Enhanced.

Updating the artifact does not change server.cfg, your resources or your MySQL database, and your license key stays the same.

Find your current build

• txAdmin: the sidebar shows the build as fx: b35245.
• Any server: open http://<your-server-ip>:30120/info.json in a browser. The server value reads like FXServer-master SERVER v1.0.0.35245 win32; the last number is the build.

Pick Recommended or Latest

The download page has two update branches. Cfx.re supports each build for a time after the next one in line comes out:

Run Recommended on a live server. Take Latest only when a fix you are waiting for is in it, and try it on a test server first.

Update on Windows

1. In txAdmin, stop the server, then close the FXServer window. The server is offline from here.
2. In C:\FXServer, rename the server folder to server-old. This is your rollback copy; leave it untouched.
3. Copy C:\FXServer\txData to another drive. It is your backup if anything else goes wrong.
4. On the Server Download page, choose FiveM / RedM, Windows and Recommended, and select Download. You get server.7z.
5. Create an empty C:\FXServer\server folder and extract server.7z into it with 7-Zip. FXServer.exe must sit directly in C:\FXServer\server, not in a subfolder.
6. Start FXServer.exe, or the start_<build>_<profile>.bat that txAdmin writes to C:\FXServer for a named profile. The batch file calls FXServer.exe by its full path, so it works while the folder name stays server, even though its file name keeps the old build number. txAdmin opens with your existing profile because txData did not move.

Update on Linux

These commands assume the Cfx.re layout, ~/FXServer/server for the artifact, and the Recommended build 35245. For a later build, copy its Linux link from the download page.

1. In txAdmin, stop the server, then stop the FXServer process.

2. Keep the old build as your rollback copy, then make an empty folder:

   cd ~/FXServer
   mv server server-old
   mkdir server
   cd server
   

3. Download and extract the Recommended build:

   wget https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/35245-6efb47dff473c0e2a12fb50b08d74c0eb24a50d5/fx.tar.xz
   tar xf fx.tar.xz
   

   run.sh and the alpine folder appear in ~/FXServer/server.

4. If txData sat in the old folder, move it into the new one. The path stays ~/FXServer/server/txData, so txAdmin finds every profile where it left it:

   mv ~/FXServer/server-old/txData ~/FXServer/server/
   

5. Start the server. With txAdmin, run bash run.sh in ~/FXServer/server. Without txAdmin, start it from your server-data folder:

   cd ~/FXServer/server-data
   bash ~/FXServer/server/run.sh +exec server.cfg
   

If your host’s control panel has a version picker, the branches and build numbers mean the same there.

Roll back

1. Stop the server.
2. Rename server to server-broken and server-old to server. On Linux, move txData back into the restored server folder first.
3. Start the server. It runs the old build with the same data.

Keep your rollback copy at build 35245 or later, as Cfx.re asked. Report a broken build on the Cfx.re forum, as Cfx.re’s end-of-support page asks.

Set the game build with sv_enforceGameBuild

From build 35245, the FiveM client always runs the latest stable GTA V executable and loads only the Title Update content the server asks for with sv_enforceGameBuild. The older sv_replaceExeToSwitchBuilds is deprecated. The setting is read only at startup, so it goes in server.cfg, and changing it needs a full restart.

This is where updating touches scripts that use newer GTA V models, such as our All-in-One Drug System V2. Its docs explain Failed to load model x as a model from a newer game build than the server’s, and name build 3258 as the build we use. To run it on 3258, add to server.cfg:

sv_enforceGameBuild 3258

Our scripts set fx_version 'cerulean' in fxmanifest.lua, and almost all add lua54 'yes', which Cfx.re’s escrow FAQ still lists for escrowed resources. Cfx.re lists cerulean as the current manifest version, and Lua 5.4 is the only Lua since June 2025, so a new artifact changes neither line.

None of our manifests checked on 19 October 2026 sets a minimum server build (/server:) or game build (/gameBuild:), so the artifact our scripts need is the one Cfx.re lets players join. Installing or replacing scripts after the update is in how to install FiveM scripts.

Server artifact version is outdated: what the warnings mean

Players cannot join an unsupported build older than three months from the server browser.

Check it works

1. The txAdmin sidebar, or info.json, shows the build you installed.
2. The server console shows each resource starting, with no red errors from your framework, oxmysql or our scripts.
3. Join from your own game and walk past the scripts your players use most.
4. If textures, cars or maps look like the old version, clear the FiveM cache on the client and server.

Keep server-old until the server has run a few days without trouble, then delete it.

If it fails

• It looks like you ran FXServer inside WinRAR without extracting it first.: FXServer started from WinRAR’s temporary folder. Extract server.7z into C:\FXServer\server and start it from there.
• Due to environmental restrictions, your paths CANNOT contain non-ASCII characters.: a folder name in the artifact or txData path has a letter such as ä or ñ. Move the artifact to a plain path; txAdmin itself suggests C:/fivemserver/<build>/.
• txAdmin shows first-time setup instead of your server: it found no txData at its default path. On Linux, move txData from server-old into server. If you set TXHOST_DATA_PATH, check it still points to your txData.
• A warning that sv_endpointPrivacy or sv_exposePlayerIdentifiersInHttpEndpoint has been removed: build 35245 and later drop these settings. Delete the line from server.cfg. Tools that read player identifiers from /players.json need the sv_playersToken the warning names.
• Failed to load model x from the All-in-One Drug System V2: the server’s game build is older than the model. Set sv_enforceGameBuild 3258 and restart, as in the game build section.
• The server will not start on the new build and you have no time to look: roll back to server-old, then read the console of the failed start. If you are still building the server from scratch, how to make a FiveM server covers the first setup.