FiveM Artifacts and Server Builds: The Complete Guide

Every FiveM server runs on a versioned binary called an artifact — the compiled FXServer build that Cfx.re releases for Windows and Linux. Knowing how to download, update, and pin the right artifact is essential to keeping your server stable, secure, and compatible with the latest GTA content.

This guide explains the artifact system end-to-end: what the files actually are, the difference between Recommended and Latest builds, how to update safely on both Windows and Linux, and how sv_enforceGameBuild ties your server to a specific GTA DLC version.

What Are FiveM Server Artifacts?

An artifact is a specific versioned release of FXServer — the core server runtime that every FiveM server is built on. It includes the executable, CitizenFX components, scripting runtimes (Lua, JS, C#), and txAdmin (the web-based server management panel) bundled together. Artifacts are not your resources or your server data; they are the engine your server runs on.

Artifacts are hosted at runtime.fivem.net/artifacts/fivem/. There are two directories: build_server_windows for Windows Server and server for Linux. Each build is identified by a build number (e.g., 7290, 7350) and the page marks certain builds as Recommended in green.

Recommended vs Latest Builds

The artifact page distinguishes between two tiers of builds.

• Recommended (green label) — builds that have been in circulation long enough that major regressions would have been caught and reported. This is what you should run on a live production server.
• Latest — the most recently published build. May include new features, native support, or security patches, but has had less community testing. Use on staging servers first.
• Older builds — still available for download. Useful if a specific build is known to break something critical and you need to roll back.

Downloading Artifacts: Windows

For Windows servers (including Windows Server 2019, 2022, and consumer Windows 10/11), navigate to the build_server_windows listing. Download the .zip archive for your chosen build, then extract it into your server directory, replacing the old files.

1. Open runtime.fivem.net/artifacts/fivem/build_server_windows/master/ in a browser.
2. Click the green Recommended build (or a specific build number).
3. Download the .zip file to your server machine.
4. Stop FXServer (or use txAdmin to stop the server).
5. Extract the .zip, overwriting all existing files in the server binary directory.
6. Start FXServer again and verify the build number in the console startup output.

Downloading Artifacts: Linux

Linux artifacts are under the server directory. The recommended approach is to use wget or curl to download the archive directly to your server, then extract with tar. This can be scripted for automation.

cd /opt/fivem
wget -O fx.tar.xz https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/7290-XXXXXXXX/fx.tar.xz
tar -xf fx.tar.xz
rm fx.tar.xz

Replace the build number and hash in the URL with the actual Recommended build URL from the artifact page. After extraction, restart your server service (systemd, screen, tmux, or however you manage it).

Pinning a Build for Stability

Pinning means deliberately staying on a specific artifact version rather than always updating to the latest Recommended build. This is a valid strategy when your server is stable and you do not need any features from newer builds. To pin a build, simply do not update — keep the artifact files you have. Document which build number you are on so you know the baseline when issues arise.

However, do not pin indefinitely. Older builds may lack security patches, and very old builds may stop being recognized by the FiveM client. A reasonable approach is to update every 4–8 weeks to a well-tested Recommended build, or sooner if a security advisory is published.

txAdmin Is Bundled with Artifacts

Since artifact builds from a certain point onward, txAdmin is included in the artifact package. You do not install txAdmin separately — when you update your artifact, you also update your txAdmin version. txAdmin provides a web dashboard for managing your server, viewing console output, scheduling restarts, and managing players and bans. It runs on port 40120 by default and is accessible via your browser.

sv_enforceGameBuild: Tying Your Server to a GTA DLC Version

GTA V has received many updates since launch, and each major update ships with new assets — MLO interiors, vehicles, weapons, clothing. By default, FXServer loads a conservative baseline of GTA content. To use assets from newer DLC on your server, you must set sv_enforceGameBuild in server.cfg to the appropriate build number. All connecting clients must have that GTA version installed (this is now universal since GTA V updates automatically on Steam and Epic).

set sv_enforceGameBuild 2699

Safe Artifact Update Routine

Updating your FXServer artifact on a live server requires care. Follow this routine to minimize risk.

1. Check the Cfx.re forum and artifact page for any known issues with the new Recommended build.
2. Take a full backup of your server data directory (server.cfg, resources, database dump).
3. Test the new artifact on a staging or local copy of your server first. Start it, connect, and verify your core scripts work.
4. Schedule the update during low-traffic hours (late night for your region).
5. Announce the maintenance to your community in Discord with a time window.
6. Stop the live server via txAdmin or your process manager.
7. Overwrite the artifact files with the new build.
8. Start the server and monitor the console for errors during startup.
9. Connect a test account and verify core gameplay (spawning, inventory, jobs, vehicles).
10. If critical errors appear, restore from backup and roll back to the previous artifact.

Identifying Your Current Build

When FXServer starts, it prints the artifact build number in the first few lines of console output. In txAdmin, the build number is also visible in the dashboard footer. Always note your current build number before updating so you have a rollback target if needed.

Artifacts and Script Compatibility

In rare cases, a new FXServer artifact changes the behavior of scripting natives or deprecates old APIs. If your server runs a lot of custom scripts or older framework resources, test thoroughly after any artifact update. Framework maintainers (ESX-Framework, qbx_core, etc.) typically document which minimum artifact version their latest releases require.

Conclusion

Staying on the right FiveM artifact keeps your server secure, stable, and compatible with the latest GTA content. The process — download the Recommended build, test on staging, update during maintenance, verify — becomes routine once you have done it a few times. CRM Development server packs are tested and shipped against specific Recommended artifacts, with documented update procedures included, so your team knows exactly what to do when a new build drops.