Free tool
FiveM server artifacts: which build is safe to run
Updated: Oct 5, 2026
—
Build recommended by Cfx
36897
Highest build in use
823
Servers on a build with a known issue
1,147
Players on those servers
What the server park actually runs
Every public FiveM server announces its FXServer version to the cfx list. This is what they declare, counted server by server and cross-referenced with documented issues. It is the figure neither the official list nor the issue databases publish: how many servers actually run each build.
| Build | Servers | Players | Windows / Linux | Status |
|---|---|---|---|---|
| 35245 | 13,402 | 51,211 | 7,109 / 6,288 | No reference |
| 35945 | 5,062 | 26,837 | 2,449 / 2,613 | No reference |
| 25770 | 4,085 | 13,088 | 2,304 / 1,781 | No reference |
| 36897 | 2,698 | 12,075 | 675 / 2,023 | No reference |
| 35805 | 870 | 4,622 | 471 / 399 | No reference |
| 35265 | 745 | 5,063 | 463 / 282 | No reference |
| 32561 | 668 | 7,178 | 574 / 94 | No reference |
| 35574 | 402 | 1,922 | 233 / 169 | No reference |
| 31689 | 357 | 683 | 213 / 144 | Documented issueGetVehiclePedIsIn server native returns 0 (citizenfx/fivem#4051) |
| 34833 | 355 | 922 | 212 / 143 | No reference |
| 35419 | 280 | 1,152 | 159 / 121 | No reference |
| 17000 | 271 | 59 | 160 / 111 | No reference |
| 34629 | 208 | 422 | 111 / 97 | No reference |
| 36727 | 189 | 1,179 | 189 / 0 | No reference |
| 31039 | 184 | 57 | 107 / 77 | No reference |
| 33864 | 160 | 279 | 0 / 160 | Documented issueFailed Windows build (works OK if using Linux!) |
| 35713 | 151 | 247 | 85 / 66 | No reference |
| 30811 | 132 | 257 | 72 / 60 | No reference |
| 33230 | 123 | 158 | 0 / 123 | Documented issueFailed Windows build (works OK if using Linux!) |
| 31623 | 116 | 611 | 75 / 41 | No reference |
| 35636 | 109 | 527 | 67 / 42 | No reference |
| 32698 | 108 | 230 | 0 / 108 | Documented issueFailed Windows build (works OK if using Linux!) |
| 28108 | 100 | 629 | 65 / 35 | No reference |
| 35145 | 98 | 143 | 63 / 35 | No reference |
| 31405 | 84 | 58 | 43 / 41 | No reference |
| 29753 | 83 | 293 | 40 / 43 | No reference |
| 30439 | 68 | 220 | 46 / 22 | No reference |
| 30906 | 64 | 273 | 40 / 24 | No reference |
| 30819 | 58 | 155 | 29 / 29 | No reference |
| 29586 | 55 | 19 | 40 / 15 | No reference |
| 25018 | 51 | 8 | 42 / 9 | No reference |
| 25988 | 48 | 9 | 30 / 18 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 26389 | 46 | 11 | 24 / 22 | Documented issueIssues with building Yarn resources on some Linux servers |
| 28626 | 42 | 58 | 23 / 19 | Documented issueIssues with packet loss/timeouts |
| 23683 | 42 | 12 | 30 / 12 | No reference |
| 28009 | 41 | 179 | 17 / 24 | No reference |
| 26803 | 41 | 11 | 25 / 16 | Documented issueIssues with building Yarn resources on some Linux servers |
| 35214 | 38 | 49 | 17 / 21 | Documented issueLua io.readdir directory iteration errors |
| 30707 | 37 | 17 | 16 / 21 | No reference |
| 29199 | 37 | 7 | 26 / 11 | No reference |
| 28954 | 36 | 7 | 22 / 14 | No reference |
| 25963 | 36 | 199 | 27 / 9 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 27417 | 35 | 5 | 21 / 14 | Documented issueIssues with building Yarn resources on some Linux servers |
| 25839 | 33 | 11 | 26 / 7 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 27722 | 29 | 38 | 20 / 9 | Documented issueYarn fails to exit cleanly on Windows |
| 7290 | 29 | 0 | 10 / 19 | No reference |
| 31550 | 27 | 21 | 16 / 11 | No reference |
| 24079 | 26 | 223 | 14 / 12 | No reference |
| 35407 | 24 | 4 | 14 / 10 | No reference |
| 29052 | 24 | 9 | 15 / 9 | No reference |
| 28518 | 23 | 55 | 20 / 3 | No reference |
| 24574 | 23 | 105 | 14 / 9 | No reference |
| 24769 | 22 | 5 | 14 / 8 | No reference |
| 30290 | 20 | 21 | 16 / 4 | No reference |
| 23918 | 20 | 5 | 10 / 10 | No reference |
| 21703 | 20 | 3 | 7 / 13 | No reference |
| 35692 | 19 | 0 | 11 / 8 | No reference |
| 26261 | 19 | 3 | 11 / 8 | Documented issueIssues with building Yarn resources on some Linux servers |
| 22443 | 19 | 74 | 11 / 8 | No reference |
| 12911 | 19 | 0 | 1 / 18 | No reference |
| 29391 | 18 | 5 | 11 / 7 | No reference |
| 31392 | 16 | 71 | 6 / 10 | No reference |
| 33746 | 15 | 0 | 0 / 15 | Documented issueFailed Windows build (works OK if using Linux!) |
| 27938 | 15 | 1 | 6 / 9 | Documented issueSIGSEV crashes (issue #3915) |
| 22279 | 15 | 4 | 10 / 5 | No reference |
| 35186 | 14 | 0 | 7 / 7 | Documented issueLua io.readdir directory iteration errors |
| 27092 | 14 | 64 | 9 / 5 | Documented issueIssues with building Yarn resources on some Linux servers |
| 18443 | 13 | 2 | 7 / 6 | No reference |
| 30863 | 12 | 58 | 7 / 5 | No reference |
| 25355 | 12 | 273 | 7 / 5 | No reference |
| 22934 | 11 | 0 | 6 / 5 | No reference |
| 28871 | 10 | 1 | 5 / 5 | No reference |
| 28556 | 10 | 16 | 4 / 6 | No reference |
| 27818 | 10 | 0 | 3 / 7 | Documented issueSIGSEV crashes (issue #3915) |
| 31602 | 9 | 3 | 5 / 4 | No reference |
| 30408 | 9 | 172 | 6 / 3 | No reference |
| 18884 | 9 | 4 | 8 / 1 | No reference |
| 27926 | 8 | 1 | 5 / 3 | Documented issueSIGSEV crashes (issue #3915) |
| 17346 | 8 | 2 | 3 / 5 | No reference |
| 25528 | 7 | 0 | 3 / 4 | No reference |
| 23368 | 7 | 1 | 6 / 1 | No reference |
| 19032 | 7 | 11 | 6 / 1 | No reference |
| 31536 | 6 | 0 | 3 / 3 | No reference |
| 31374 | 6 | 0 | 4 / 2 | No reference |
| 28814 | 6 | 2 | 3 / 3 | No reference |
| 20896 | 6 | 3 | 5 / 1 | No reference |
| 19413 | 6 | 1 | 3 / 3 | No reference |
| 18683 | 6 | 0 | 6 / 0 | No reference |
| 15414 | 6 | 2 | 4 / 2 | No reference |
| 11535 | 6 | 1 | 5 / 1 | No reference |
| 30790 | 5 | 0 | 5 / 0 | No reference |
| 29368 | 5 | 0 | 3 / 2 | No reference |
| 28097 | 5 | 7 | 2 / 3 | No reference |
| 25718 | 5 | 3 | 3 / 2 | No reference |
| 20664 | 5 | 0 | 4 / 1 | No reference |
| 17871 | 5 | 1 | 3 / 2 | No reference |
| 16085 | 5 | 0 | 1 / 4 | No reference |
| 14583 | 5 | 0 | 1 / 4 | Documented issueCrash when using the new onEntityBucketChange |
| 13890 | 5 | 0 | 4 / 1 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 12208 | 5 | 0 | 3 / 2 | No reference |
| 30373 | 4 | 1 | 2 / 2 | No reference |
| 29047 | 4 | 1 | 2 / 2 | No reference |
| 27366 | 4 | 0 | 4 / 0 | Documented issueIssues with building Yarn resources on some Linux servers |
| 27250 | 4 | 1 | 4 / 0 | Documented issueIssues with building Yarn resources on some Linux servers |
| 23984 | 4 | 0 | 2 / 2 | No reference |
| 20150 | 4 | 1 | 1 / 3 | No reference |
| 18270 | 4 | 1 | 3 / 1 | No reference |
| 17212 | 4 | 0 | 1 / 3 | No reference |
| 16501 | 4 | 1 | 3 / 1 | No reference |
| 15488 | 4 | 0 | 3 / 1 | No reference |
| 13631 | 4 | 0 | 1 / 3 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 13227 | 4 | 0 | 1 / 3 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 12508 | 4 | 2 | 3 / 1 | No reference |
| 10488 | 4 | 0 | 2 / 2 | No reference |
| 29365 | 3 | 5 | 3 / 0 | No reference |
| 25755 | 3 | 0 | 3 / 0 | No reference |
| 21547 | 3 | 3 | 3 / 0 | Documented issueMultiple (unconfirmed) reports of server-sided natives throwing errors or causing crashes; best to avoid |
| 19826 | 3 | 0 | 1 / 2 | No reference |
| 16565 | 3 | 1 | 1 / 2 | No reference |
| 15859 | 3 | 0 | 3 / 0 | No reference |
| 15744 | 3 | 0 | 3 / 0 | No reference |
| 14758 | 3 | 0 | 1 / 2 | Documented issueTimeouts due to latency units being in nanoseconds |
| 14318 | 3 | 0 | 0 / 3 | No reference |
| 13079 | 3 | 0 | 3 / 0 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 12651 | 3 | 20 | 3 / 0 | Documented issueFailed Linux build, ignore |
| 12031 | 3 | 2 | 2 / 1 | No reference |
| 10191 | 3 | 0 | 3 / 0 | Documented issueGetVehicleNumberPlateText server native broken, will cause issues with scripts involving vehicles |
| 5848 | 3 | 1 | 2 / 1 | No reference |
| 5181 | 3 | 2 | 3 / 0 | No reference |
Download FiveM server artifacts
Artifacts are downloaded from the official Cfx site. Open the index for your platform and enter the folder starting with the build number you want: every folder is named "build-hash", so the bare number is not a valid URL.
Builds with documented issues
The full list of builds with issues reported by the community, shown next to the one thing we add: how many servers are still running each of them. Source credited below.
| Build or range | Reported issue | In use |
|---|---|---|
| 8509 | State bags not replicated to clients | — |
| 10072 | Crashing when players join | — |
| 10191 | GetVehicleNumberPlateText server native broken, will cause issues with scripts involving vehicles | 3 |
| 10268–10309 | sv_experimentalNetGameEventHandler enabled by default; can cause server crashing and reports of issues downgrading after upgrading | — |
| 10930 | Failed build, ignore | — |
| 12078–12083 | Some clients will fail to connect with 'ReadBulk of header failed' error | — |
| 12092–12135 | SetPlayerModel may cause SIGSEGV crashes on some clients due to changes in player handling. 12031 and below works fine. | — |
| 12151 | Crashing if using newest title update (TU) | — |
| 12160–12165 | Cannot use entity native calls in entityRemoved | — |
| 12180 | voip-server-mumble.dll server crash (citizenfx/fivem#3054) | — |
| 12255 | Unconfirmed, but several reports of server-side issues that don't persist when downgrading; best to avoid | — |
| 12509 | Failed build, ignore | — |
| 12651 | Failed Linux build, ignore | — |
| 12767 | os.date() appends null terminator; can break Lua scripts | — |
| 12913–12932 | Causes a crash when restarting Node.js 22 | — |
| 12913–14177 | High FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) | 16 |
| 12933–13045 | Still crashes (sometimes) when restarting resources due to Node.js 22 | — |
| 13079 | Failed Linux build (works OK if using Windows!) | — |
| 13380–13458 | Server crashing due to integer encoding (PR#3235) | — |
| 13759–13890 | Mumble (voice) external connections blocked by default | — |
| 14583–14716 | Crash when using the new onEntityBucketChange | 5 |
| 14583–14862 | Timeouts due to latency units being in nanoseconds | 3 |
| 16276 | Multiple reports of issues loading JS within resources | — |
| 17462 | Failed build, ignore | — |
| 21547 | Multiple (unconfirmed) reports of server-sided natives throwing errors or causing crashes; best to avoid | 3 |
| 25839–25988 | Node.js sandboxing seems to be causing issues for people - best to avoid for now | 117 |
| 25943 | Failed build | — |
| 26261–27715 | Issues with building Yarn resources on some Linux servers | 163 |
| 27722 | Yarn fails to exit cleanly on Windows | 29 |
| 27783–27938 | SIGSEV crashes (issue #3915) | 33 |
| 28626 | Issues with packet loss/timeouts | 42 |
| 31689 | GetVehiclePedIsIn server native returns 0 (citizenfx/fivem#4051) | 357 |
| 31725 | Failed build | — |
| 32698 | Failed Windows build (works OK if using Linux!) | — |
| 33230 | Failed Windows build (works OK if using Linux!) | — |
| 33746 | Failed Windows build (works OK if using Linux!) | — |
| 33864 | Failed Windows build (works OK if using Linux!) | — |
| 34303 | Failed build, ignore | — |
| 34410 | Failed build | — |
| 35186–35214 | Lua io.readdir directory iteration errors | 52 |
Issue data source: FiveM Artifacts DB by JG Scripts, fetched on Oct 5, 2026
How to update your server artifacts
The process is the same on any host or VPS, and the order matters more than the speed.
- Check in the table above that the build you are jumping to has no reported issue.
- Stop the server. Updating a running server leaves half-written files behind.
- Back up the server folder, or at least server.cfg and your resources. Going back has to stay possible.
- Download the build from the official index linked above and replace the FXServer files with it. Leave txData and your resources alone.
- Start it and watch the console for the first few minutes: artifact failures show up on load, not later.
And one rule that saves grief: do not update on the day a build ships. Issues take a few days to surface, and the table above is precisely the record of the ones that surfaced late.
Where these numbers come from
We read the public cfx server list every 30 minutes and store the FXServer version each server declares. The recommended build comes from the official Cfx artifacts page. Issue data comes from FiveM Artifacts DB by JG Scripts, released into the public domain. We count FiveM servers only (not RedM) and drop builds with fewer than three servers, which are noise. Two caveats: the version is self-declared by the server, and "no reported issue" does not mean "no bugs", only that nobody has reported them yet.
The monitoring your server deserves
Set up FiveMonitor in 5 minutes and see for yourself why we are the lightest option on the market.
Start for free