Skip to Content
Server OpsArtifacts

FiveM Server Artifacts

FiveM server artifacts are the versioned FXServer binaries distributed by Cfx.re. For a production server, download the build marked LATEST RECOMMENDED on the official artifact listing.

Server artifacts are not your resources, database, or server.cfg. Keep the binary directory separate from server data so an update or rollback does not overwrite application data.

Which artifact should you use?

ChannelUse it forProduction recommendation
Latest recommendedNormal server operation and supported updatesYes
Latest optionalTesting a newer optional release or a required fixTest first
Newest unlabelled buildReproducing a specific upstream issueNo

Cfx.re can mark old builds as end-of-support or end-of-life. Unsupported builds older than three months may no longer be joinable from the server browser. See the official artifact support timeline  for the current policy.

Do not automate against guessed JSON endpoints. The artifact listings are the verified source for the current recommended download links.

Before updating

Record the current artifact directory and verify that you can restore it. A server update should not require changing server.cfg, resources, or the database.

# Example Linux layout
/opt/fivem/
├── artifacts/
│   ├── 25770/
│   └── current -> /opt/fivem/artifacts/25770
└── server-data/
    ├── resources/
    └── server.cfg

Pre-update checklist:

  • Record the current build number.
  • Copy the exact recommended download URL from the official listing.
  • Confirm the previous artifact directory still exists.
  • Back up server.cfg, resources, and the database using your normal backup process.
  • Stop FXServer before replacing the active binary path.
  • Test the update during a maintenance window.

Update FiveM artifacts on Linux

The official Linux archive is normally named fx.tar.xz. FiveM for GTAV Enhanced may use a different archive name; follow the label on the download page.

1. Download into a new version directory

Copy the recommended Linux artifact URL, then set a version label for your local directory:

ARTIFACT_URL="paste-the-recommended-linux-download-url"
ARTIFACT_VERSION="replace-with-build-number"
ARTIFACT_ROOT="/opt/fivem/artifacts"
 
sudo mkdir -p "$ARTIFACT_ROOT/$ARTIFACT_VERSION"
curl --fail --location "$ARTIFACT_URL" \
  --output "/tmp/fivem-$ARTIFACT_VERSION.tar.xz"
sudo tar -xf "/tmp/fivem-$ARTIFACT_VERSION.tar.xz" \
  -C "$ARTIFACT_ROOT/$ARTIFACT_VERSION"

curl --fail prevents an HTTP error page from being treated as a valid archive. Do not remove the currently active directory yet.

2. Verify the extracted server

test -x "$ARTIFACT_ROOT/$ARTIFACT_VERSION/run.sh"
test -x "$ARTIFACT_ROOT/$ARTIFACT_VERSION/alpine/opt/cfx-server/FXServer"

The exact contents can change between artifact families. If either check does not match the downloaded archive, inspect the extracted directory before changing the active symlink.

3. Switch the active version

sudo ln -sfn \
  "$ARTIFACT_ROOT/$ARTIFACT_VERSION" \
  "$ARTIFACT_ROOT/current"

Start FXServer through your existing service or txAdmin configuration. The startup command must still execute the server.cfg stored in your separate server-data directory.

4. Validate the update

# Replace the service name if yours differs
sudo systemctl status fivem
sudo journalctl -u fivem --since "10 minutes ago"
 
# The default FiveM endpoint uses TCP and UDP 30120
nc -zv 127.0.0.1 30120

Also verify:

  1. FXServer starts without a fatal artifact or license error.
  2. Required resources reach the started state.
  3. The database connection succeeds.
  4. A test client can connect and spawn.
  5. Critical framework, inventory, voice, and persistence flows still work.

Update FiveM artifacts on Windows

  1. Stop FXServer or stop the server from txAdmin.
  2. Download LATEST RECOMMENDED from the Windows artifact listing .
  3. Extract the archive into a new versioned directory such as C:\FXServer\artifacts\25770.
  4. Keep C:\FXServer\server-data and its resources directory separate.
  5. Point the startup command or service at the new FXServer.exe.
  6. Start the server and complete the validation checklist above.

For FiveM for GTAV Enhanced, the Windows binary and archive names can differ. Use the current names shown in the official txAdmin setup guide .

Roll back an artifact update

If the new build prevents startup or breaks a critical verified flow:

  1. Stop FXServer.
  2. Point the active path or service back to the previous artifact directory.
  3. Start the server with the unchanged server-data directory.
  4. Verify startup, resource state, database access, and client connection.
  5. Preserve the failed build and logs until the cause is understood.

Linux symlink rollback:

PREVIOUS_VERSION="replace-with-previous-build"
sudo ln -sfn \
  "/opt/fivem/artifacts/$PREVIOUS_VERSION" \
  "/opt/fivem/artifacts/current"
sudo systemctl restart fivem

Restoring the database or resources is normally unnecessary when only the artifact binaries changed. Restore application data only if it was changed during the same maintenance window.

Common artifact problems

The download is HTML instead of an archive

The URL is stale, incomplete, or points to an error page. Copy the recommended link again and download with curl --fail --location.

FXServer reports no resources

The process was probably started from the wrong server-data directory or without the correct +exec server.cfg argument. The artifact directory and server-data directory serve different purposes.

Players see an end-of-support or end-of-life warning

Move to a currently supported artifact. Do not hide the warning with unrelated configuration changes.

Resources fail after the update

Read the first resource error in the FXServer log, then test the same resource on the previous artifact. If the rollback resolves the failure, keep the previous supported build active while you update or report the incompatible resource.

HostingNetworking