
FiveM server artifacts are the FXServer builds your server runs on, and the questions are always the same: which build do you download, and how do you update without breaking anything? For a long time the answer was one line: run Recommended. Two dates changed that this autumn. Since 15 October 2026 players can no longer connect to servers below build 35245, and a long run of Latest builds loses support between 2 and 13 November 2026. This guide has the current builds, their support dates and the update steps for a txAdmin server on Windows and Linux.
Quick answer: FiveM server artifacts are the FXServer packages that run your server, with txAdmin built in. On 31 October 2026 the Recommended build is 35245 (out since 20 August) and Latest is 38055 (30 October). Run Recommended unless a resource or fix you need requires something newer. Servers below 35245 stopped accepting connections on 15 October, and every build from 37555 to 38069 except 38055 loses support between 2 and 13 November. To update, stop the server in txAdmin, close FXServer, replace the build files while txData, your resources and server.cfg stay where they are, then start FXServer again.
What FiveM Server Artifacts Are
Cfx.re's download page calls an artifact "a package that includes the files needed to run/update your RedM or FiveM server". On Windows that's server.7z with FXServer.exe inside. On Linux it's fx.tar.xz, which unpacks into a run.sh script and an alpine folder.
Your resources, your server.cfg and txAdmin's txData folder (its logs, configs and data) are not part of the artifact, which is why an update only swaps the build files. txAdmin is part of it, though: it has been "a component of FXServer" since early 2020, according to its developers, so each artifact brings its own txAdmin version.
Don't mix up the artifact build with the game build. 35245 is an FXServer version; the game build is the GTA V title update you set with sv_enforceGameBuild, such as 3889 for The Kortz Center Heist, and it "can only be specified at startup". Since 35245 the FiveM client always runs the latest stable GTA V executable and loads only the title update content your server requests, Cfx.re announced. sv_replaceExeToSwitchBuilds is fully deprecated, and support for The Kortz Center Heist update needs server version 35245 or higher.
FXServer Artifacts on 31 October 2026
The old artifact lists on runtime.fivem.net now redirect to the Server Download page. Pick Platform "FiveM / RedM", your Operating System and Update Branch "Recommended" or "Latest". On the Latest branch, an "Older Builds" list holds the previous builds.
| Branch | Build | Date | txAdmin inside | Windows file | Linux file |
|---|---|---|---|---|---|
| Recommended | 35245 | 20 August 2026 | 8.1.1 | server.7z | fx.tar.xz |
| Latest | 38055 | 30 October 2026 | 8.1.2 | server.7z | fx.tar.xz |
These numbers come from Cfx.re's version API for Windows and Linux, the same data txAdmin checks every 15 minutes. Its recommended and latest fields name the two builds above. Two older fields, critical and optional, both still point to 7290, a build from January 2024 that the old artifacts page showed as "LATEST OPTIONAL". txAdmin compares your build with all three numbers, so in practice it only warns below 35245.
Running FiveM for GTAV Enhanced? Choose that platform on the same page. Its Cfx Server files, cfx-server_win_x64.zip and cfx-server_linux_x64.tar.xz, were at build 170 on 31 October and have their own numbering. Our Enhanced early access guide covers that platform; the rest of this post is about FXServer.
Recommended vs Latest
Recommended is a single build that Cfx.re promotes as the baseline, and it changes rarely. 35245 replaced 25770 on 20 August 2026, the day Cfx.re announced support for The Kortz Center Heist update. A Recommended build stays supported until six weeks after the next one, and the version API shows exactly that: 25770's support ended on 1 October 2026.
Latest is the newest build on the Latest branch and moves fast: 38055 is from 30 October. A Latest build is supported until two weeks after the next release in line, so running Latest means updating at least every two weeks to stay supported.
For a live community, run Recommended. Use Latest on a test server, or when a resource or fix you need requires a newer build, and then keep up with it. Some resources name a minimum server build in their documentation, so check before you drop back to an older one. On Linux, note that Cfx.re's setup guide calls the Linux FXServer "a courtesy port" and says issues are more likely to get fixed on the Windows version.
End of Support and End of Life Dates
Cfx.re's support policy works in two stages. Outdated artifacts "will not stop functioning", but Cfx.re won't support them, and "unsupported server artifacts older than three months will not be joinable from the server browser." Players see the stage when they join: a gray end-of-support (EOS) warning means the server is still joinable, a red end-of-life (EOL) warning with a failed connection means the owner has to update. The 15 October cutoff for builds below 35245 comes on top of this.
The version API lists both dates for every build. On 31 October 2026 it gave this picture (dates in UTC):
| Your build | Status on 31 October 2026 | Next date |
|---|---|---|
| Below 35245 | No connections since 15 October 2026 | Update now |
| 35245 (Recommended) | Supported, no end date set | Six weeks after the next Recommended build |
| 35265 to 36897 | Support ended 3 September to 14 October | End of life 20 November to 30 December 2026 |
| 37045 to 37474 | Support ended 16 to 30 October | End of life 2 to 16 January 2027 |
| 37555 to 38069, except 38055 | Supported | Support ends 2 to 13 November, end of life 19 to 30 January 2027 |
| 38055 (Latest) | Supported, no end date set while it is Latest | API lists end of life on 30 January 2027 |
To check your own build on a Linux machine, set BUILD to your number and run:
BUILD=37555
curl -s https://changelogs-live.fivem.net/api/changelog/versions/linux/server \
| python3 -c "import json,sys; d=json.load(sys.stdin); b='$BUILD'; print('recommended', d['recommended'], '| latest', d['latest']); print('end of support', d['support_policy'].get(b, 'not listed')); print('end of life', d['support_policy_eol'].get(b, 'not listed'))"
On 31 October that printed end of support 2026-11-02T12:55:13Z and end of life 2027-01-19T12:55:13Z for 37555. A date of 9999-12-31 means no end date is set yet. On Windows, open the Windows API link in a browser (in Firefox, switch to Raw Data) and search for your build number in quotes followed by a colon, such as "37555":. The first match sits under support_policy, the second under support_policy_eol.
Check Which Build Your Server Runs
The bottom of the txAdmin sidebar shows both versions, for example tx: v8.1.1 | fx: b35245. The fx number is your artifact build. Our txAdmin guide covers the rest of the panel.
Don't wait for txAdmin's warning bar. Its update check has an FXServer notice, "This version of FXServer is outdated." with "Please update FXServer to artifact 35245.", but it only fires below Recommended and says nothing about end-of-support dates on Latest builds. The bar also shows one notice at a time, and a txAdmin update goes first. Every build below 35245 predates txAdmin 8.1.2 (23 October 2026), so on exactly the servers that need the FXServer warning, a txAdmin notice can sit in front of it. Compare the fx number with the table above yourself.
How to Update FiveM Artifacts With txAdmin on Windows
txAdmin has no button that installs a new artifact, so the swap happens in the file system. These steps follow Cfx.re's txAdmin setup guide, which puts FXServer in C:\FXServer\server; use your own path if it differs. For a first install rather than an update, follow how to make a FiveM server.
- Note the
fxbuild in the txAdmin sidebar, so you know what you can roll back to. - On the Server Download page, pick FiveM / RedM, Windows and Recommended (or Latest), and download
server.7z. - Back up your server data folder (txAdmin shows the path under Settings, FXServer, "Server Data Folder"), the
txDatafolder and, if your framework stores data in MySQL or MariaDB, the database. - Warn players with Send Announcement in the sidebar, stop the server there, then close the FXServer console window. txAdmin runs inside FXServer and closes with it.
- Rename
C:\FXServer\servertoC:\FXServer\server-35245. That folder is your rollback. - Create a new, empty
C:\FXServer\serverand extractserver.7zinto it with 7-Zip or WinRAR. - Start
FXServer.exefrom the new folder and open txAdmin at http://localhost:40120. By default txAdmin keepstxDatain the folder above the artifact, hereC:\FXServer\txData, so your settings and admins are still there (unlessTXHOST_DATA_PATHpoints somewhere else). - Check that the sidebar shows the new
fxbuild and start the server. If Autostart is on (Settings, FXServer, advanced options), it starts by itself. - Join the server and watch the Live Console for errors on the first start.
An empty folder keeps leftovers of the old build away from the new one, and the renamed folder is a quick way back: close FXServer, swap the two folder names and start again.
Updating FXServer on Linux
On Linux the default txData location is the folder that holds run.sh, so it sits inside your server folder. Don't delete or replace that folder. Move only alpine and run.sh. Stop the server in txAdmin, stop FXServer (Ctrl+C in its terminal, or stop the screen, tmux or systemd session it runs in), copy the download address from the Server Download page (right-click Download, copy the link) and run, with Cfx.re's ~/FXServer/server layout:
cd ~/FXServer/server
mkdir -p ~/FXServer/rollback-35245
mv alpine run.sh ~/FXServer/rollback-35245/
wget -O fx.tar.xz "PASTE-THE-DOWNLOAD-ADDRESS"
tar xf fx.tar.xz && rm fx.tar.xz
bash ~/FXServer/server/run.sh
Keep the -O fx.tar.xz. If the archive from your first install is still in the folder, plain wget saves the new one as fx.tar.xz.1, and tar would unpack the old build again. tar needs xz, which is the xz-utils package on Debian and Ubuntu. Starting run.sh without +exec server.cfg brings txAdmin up, as the txAdmin README describes. To roll back, stop FXServer, move the new alpine and run.sh out of the way and move the old pair back.
On a Rented FiveM Server
On a hosted server the provider's panel decides where FXServer lives and which build is installed, and you may not see the artifact folder at all. Look for a version or build setting in the panel, and find out what a reinstall keeps before you run one. On a Space-Node FiveM server, txAdmin comes pre-installed and you reach your files through the control panel or SFTP. Ask our support (live chat, Discord or email, 08:00 to 20:00 UTC) how the build is set on your server before you swap files by hand.
If the Server Breaks After an Update
Read the first real error in the Live Console, not the flood after it. If the new build is the cause, go back to the previous folder and confirm the server runs again. Older Latest builds stay downloadable under "Older Builds", but don't pick one below 35245, because players can't connect to those anymore. To find a resource that broke, start with only your framework and its dependencies and add the rest back in groups, as our artifact update and version mismatch guide explains. For crashes that have nothing to do with an update, see why your FiveM server keeps crashing.
FAQ
Where do I download FiveM server artifacts now? On Cfx.re's Server Download page at docs.fivem.net/docs/server-download. The old runtime.fivem.net artifact lists redirect there. Choose FiveM / RedM, your operating system and the Recommended or Latest branch.
Should I use the Recommended or the Latest artifact? Recommended (35245 on 31 October 2026) for a live server. Latest (38055) gets fixes first, but each Latest build loses support two weeks after the next one.
What do the end-of-support and end-of-life warnings mean when players join? The server runs an outdated artifact. A gray end-of-support warning still lets players in; a red end-of-life warning with a failed connection means the build is unsupported and older than three months. Only the owner can fix it, by updating the artifact.
Does txAdmin update the artifacts for me? No. txAdmin ships inside the artifact and only tells you an update exists, and only when your build is below Recommended. You swap the files yourself, or your host does.
Why does txAdmin say a patch update is available on the Recommended build? Recommended 35245 ships txAdmin 8.1.1, and the API's newest txAdmin is 8.1.2 from 23 October 2026, which lists one fix: "core/webserver: reject compressed request bodies". txAdmin comes inside the artifact, so the notice disappears once you run a build with 8.1.2, such as Latest 38055. Postpone hides it for 48 hours.
Can I go back to an older artifact? Yes. Keep the previous build folder, or download the build again from "Older Builds" on the Latest branch. Stay at 35245 or above: players have been unable to connect to anything older since 15 October 2026.
Sources
All opened on 31 October 2026:
- Cfx.re docs: Server Download, End of Support/End of Life Warning Message, Setting up a server with txAdmin, Vanilla server setup, sv_enforceGameBuild, FiveM for GTAV Enhanced onboarding
- Cfx.re version API: Windows, Linux
- Cfx.re forum: Support for GTA Online: The Kortz Center Heist Update is Available Now (20 August 2026)
- Cfx.re artifacts page for Windows, archived 18 August 2026 (Recommended 25770, Optional 7290)
- txAdmin on GitHub: README, environment variables and txData path, v8.1.2 release, update check, warning bar, sidebar, FXServer settings