How to Update FiveM Server Artifacts (and txAdmin, 2026)

To update a FiveM server, stop it, back up your server data folder (resources, server.cfg and txData), then replace only the artifact folder (the one with FXServer or FXServer.exe and citizen) with a new build from the Cfx.re artifacts page, and start again. Pick the recommended build unless a resource needs newer. txAdmin ships inside the artifact, so it updates at the same time. Your resources, database and txAdmin settings are not touched.

What an update changes and what it keeps

Recommended, latest or a build number?

The Cfx.re artifacts page and its version feed list a few channels. At the start of October 2026 the Linux feed showed recommended as build 35245 and latest as 36897, both with txAdmin 8.1.1. These numbers move every week or two.

The support windows come from Cfx.re's end of support and end of life policy. An artifact out of support shows players a grey End of Support warning but still lets them join. A red End of Life warning blocks joining until the owner updates, and artifacts older than three months drop out of the server browser.

What goes where

Only the first row is replaced. If your artifact and data share one folder, replace only citizen/, the FXServer executable and the files that came in the artifact download.

Step 1: Back up first

Stop the server from txAdmin, then copy resources, server.cfg and txData somewhere safe. Export the database too (HeidiSQL or mysqldump) if this is a roleplay server, since a resource update often follows an artifact update and can change tables.

Step 2: Download the new build

1. Open the artifacts page for your system: runtime.fivem.net/artifacts/fivem/build_server_windows/master/ for Windows or build_proot_linux/master/ for Linux.
2. Take the build marked recommended, unless a resource's page says it needs a newer one.
3. Windows builds come as server.7z, Linux builds as fx.tar.xz.

Step 3: Replace the artifact folder

Delete or rename the old artifact folder, then extract the new build in its place. Leave the server data folder and txData alone. On Linux:

cd ~/FXServer/server
mv alpine alpine-old
tar xf fx.tar.xz

Step 4: Start and check the version

Start the server the same way as before. The console prints the FXServer build number on start, and txAdmin shows its own version in its web panel. If txAdmin had an update banner before, it is gone now: txAdmin cannot update itself separately, it comes with the artifact.

Step 5: Change the game build, if you want new GTA content

New GTA DLC cars, clothes and map areas are unlocked with sv_enforceGameBuild in server.cfg:

sv_enforceGameBuild 3570

The FiveM server commands docs list the numbers, for example 3258 (Bottom Dollar Bounties), 3407 (Agents of Sabotage), 3570 (Money Fronts), 3751 (A Safehouse in the Hills) and 3889 (The Kortz Center Heist). It is read only at startup, so restart after changing it. Players' FiveM switches to that build when they join.

The gotcha: the game build needs the artifact first

Support for each GTA game build ships inside FXServer. An old artifact does not know a newer build exists, so setting sv_enforceGameBuild 3889 on an artifact from months ago leaves players stuck loading or rejected, and people blame their scripts. Always update the artifact first, start once, then raise the game build. Raising the build is also a one way door for some resources: maps and vehicles made for an older build can break or clash with new DLC content, so test on a copy before a busy evening.

The second trap is pinning. An exact build number feels safe, but it never moves, so a few months later players get the End of Life block. Pin only while testing, then go back to recommended.

Common problems

• Players see "End of Life" and cannot join: the artifact is out of support. Update it, then restart.
• Players stuck on loading after raising the game build: the artifact is too old for that build, or a resource does not support it. Update the artifact, or go back to the previous build number.
• txAdmin still says it is outdated: the old artifact folder is still the one being started. Check the path in your start script or shortcut.
• Scripts error after the update: a resource relies on old behaviour. Check its page for an update, especially frameworks like QBCore or ox_lib.
• Server will not start on Linux after extracting: the new files went into a subfolder. run.sh and alpine/ must sit where your start command expects them.

Updating on GamezServers

On a GamezServers FiveM server the artifact build is the FXServer build setting in Settings: recommended by default, latest, or an exact number. Press Update game and we back up the server, then reinstall that build. Your resources, server.cfg and txData stay, and txAdmin updates with it. If you typed an exact build number, Update game installs that same build again, so set it back to recommended to move forward. For building out the server afterwards, see how to add scripts to a FiveM server.

FAQ

How do I update txAdmin?

Update the FiveM artifact. txAdmin is bundled with FXServer, so a newer artifact brings a newer txAdmin.

Will updating artifacts delete my resources?

No. Artifacts only contain the server program. Your resources folder, server.cfg, txData and database are kept, as long as you replace only the artifact folder.

Should I use recommended or latest artifacts?

Recommended for almost every server. Latest has newer fixes but is supported for only two weeks after the next build, so you have to update much more often.

How often should I update FiveM artifacts?

Whenever a new recommended build comes out, or when players see an End of Support warning. Recommended builds stay supported for six weeks after the next one.