Free tool
FiveM server artifacts: which build is safe to run
Short answer: Cfx currently recommends build 35245. Of the servers we track, 2,060 are running a build with a documented issue. Before you update, check your target build against the issue table.
Updated: Aug 20, 2026
35245
Build recommended by Cfx
35265
Highest build in use
2,060
Servers on a build with a known issue
15,414
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 |
|---|---|---|---|---|
| 25770 | 13,410 | 68,226 | 6,972 / 6,438 | Behind the recommended build |
| 32561 | 3,019 | 30,678 | 2,659 / 360 | Behind the recommended build |
| 34833 | 2,914 | 18,987 | 1,539 / 1,375 | Behind the recommended build |
| 34629 | 1,538 | 10,376 | 861 / 677 | Behind the recommended build |
| 31689 | 1,394 | 14,705 | 803 / 591 | Documented issueGetVehiclePedIsIn server native returns 0 (citizenfx/fivem#4051) |
| 35245 | 1,168 | 4,330 | 689 / 479 | Up to date |
| 35265 | 1,136 | 2,367 | 395 / 741 | Up to date |
| 33864 | 997 | 996 | 0 / 997 | Documented issueFailed Windows build (works OK if using Linux!) |
| 35214 | 980 | 1,445 | 218 / 762 | Behind the recommended build |
| 30811 | 725 | 3,716 | 482 / 243 | Behind the recommended build |
| 35145 | 649 | 6,267 | 352 / 297 | Behind the recommended build |
| 31039 | 557 | 10,075 | 352 / 205 | Behind the recommended build |
| 31623 | 447 | 5,305 | 313 / 134 | Behind the recommended build |
| 33230 | 427 | 576 | 0 / 427 | Documented issueFailed Windows build (works OK if using Linux!) |
| 17000 | 391 | 247 | 232 / 159 | Behind the recommended build |
| 31405 | 310 | 1,034 | 179 / 131 | Behind the recommended build |
| 32698 | 304 | 827 | 0 / 304 | Documented issueFailed Windows build (works OK if using Linux!) |
| 30906 | 256 | 3,242 | 165 / 91 | Behind the recommended build |
| 30819 | 241 | 1,030 | 127 / 114 | Behind the recommended build |
| 29753 | 214 | 191 | 126 / 88 | Behind the recommended build |
| 28108 | 184 | 1,123 | 120 / 64 | Behind the recommended build |
| 30439 | 160 | 936 | 108 / 52 | Behind the recommended build |
| 35186 | 110 | 185 | 50 / 60 | Behind the recommended build |
| 30707 | 105 | 395 | 59 / 46 | Behind the recommended build |
| 33746 | 102 | 149 | 0 / 102 | Documented issueFailed Windows build (works OK if using Linux!) |
| 31550 | 99 | 340 | 58 / 41 | Behind the recommended build |
| 28009 | 95 | 223 | 40 / 55 | Behind the recommended build |
| 29586 | 90 | 99 | 57 / 33 | Behind the recommended build |
| 28626 | 79 | 74 | 51 / 28 | Documented issueIssues with packet loss/timeouts |
| 28954 | 76 | 40 | 46 / 30 | Behind the recommended build |
| 29199 | 75 | 393 | 49 / 26 | Behind the recommended build |
| 26389 | 75 | 39 | 32 / 43 | Documented issueIssues with building Yarn resources on some Linux servers |
| 25018 | 62 | 57 | 46 / 16 | Behind the recommended build |
| 25839 | 56 | 13 | 42 / 14 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 26803 | 54 | 56 | 38 / 16 | Documented issueIssues with building Yarn resources on some Linux servers |
| 31602 | 52 | 399 | 38 / 14 | Behind the recommended build |
| 29052 | 51 | 506 | 30 / 21 | Behind the recommended build |
| 25988 | 51 | 3 | 27 / 24 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 25963 | 49 | 309 | 37 / 12 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 29391 | 47 | 24 | 31 / 16 | Behind the recommended build |
| 23683 | 46 | 13 | 31 / 15 | Behind the recommended build |
| 22443 | 46 | 8 | 23 / 23 | Behind the recommended build |
| 31392 | 44 | 334 | 29 / 15 | Behind the recommended build |
| 27417 | 44 | 22 | 28 / 16 | Documented issueIssues with building Yarn resources on some Linux servers |
| 30863 | 39 | 252 | 19 / 20 | Behind the recommended build |
| 27722 | 39 | 26 | 18 / 21 | Documented issueYarn fails to exit cleanly on Windows |
| 24574 | 39 | 272 | 21 / 18 | Behind the recommended build |
| 7290 | 39 | 0 | 20 / 19 | Behind the recommended build |
| 30290 | 37 | 110 | 26 / 11 | Behind the recommended build |
| 23918 | 37 | 8 | 21 / 16 | Behind the recommended build |
| 28518 | 35 | 7 | 28 / 7 | Behind the recommended build |
| 24079 | 34 | 182 | 16 / 18 | Behind the recommended build |
| 24769 | 30 | 4 | 22 / 8 | Behind the recommended build |
| 26261 | 27 | 9 | 14 / 13 | Documented issueIssues with building Yarn resources on some Linux servers |
| 27092 | 26 | 48 | 16 / 10 | Documented issueIssues with building Yarn resources on some Linux servers |
| 28871 | 25 | 8 | 14 / 11 | Behind the recommended build |
| 27938 | 24 | 2 | 13 / 11 | Documented issueSIGSEV crashes (issue #3915) |
| 21703 | 24 | 7 | 11 / 13 | Behind the recommended build |
| 22934 | 22 | 6 | 14 / 8 | Behind the recommended build |
| 31536 | 21 | 90 | 15 / 6 | Behind the recommended build |
| 31374 | 21 | 51 | 15 / 6 | Behind the recommended build |
| 30408 | 20 | 423 | 9 / 11 | Behind the recommended build |
| 27818 | 20 | 1 | 8 / 12 | Documented issueSIGSEV crashes (issue #3915) |
| 28556 | 19 | 16 | 10 / 9 | Behind the recommended build |
| 22279 | 18 | 1 | 15 / 3 | Behind the recommended build |
| 18884 | 17 | 0 | 15 / 2 | Behind the recommended build |
| 29368 | 15 | 1 | 11 / 4 | Behind the recommended build |
| 27926 | 15 | 3 | 12 / 3 | Documented issueSIGSEV crashes (issue #3915) |
| 25355 | 15 | 490 | 10 / 5 | Behind the recommended build |
| 28814 | 13 | 278 | 8 / 5 | Behind the recommended build |
| 16085 | 13 | 4 | 5 / 8 | Behind the recommended build |
| 31367 | 10 | 165 | 7 / 3 | Behind the recommended build |
| 30373 | 10 | 22 | 8 / 2 | Behind the recommended build |
| 25528 | 10 | 0 | 5 / 5 | Behind the recommended build |
| 20896 | 10 | 3 | 9 / 1 | Behind the recommended build |
| 30790 | 9 | 3 | 7 / 2 | Behind the recommended build |
| 27547 | 9 | 0 | 4 / 5 | Documented issueIssues with building Yarn resources on some Linux servers |
| 27055 | 9 | 34 | 4 / 5 | Documented issueIssues with building Yarn resources on some Linux servers |
| 18443 | 9 | 0 | 5 / 4 | Behind the recommended build |
| 17346 | 9 | 15 | 5 / 4 | Behind the recommended build |
| 12508 | 9 | 2 | 6 / 3 | Behind the recommended build |
| 23368 | 8 | 8 | 7 / 1 | Behind the recommended build |
| 20664 | 8 | 1 | 7 / 1 | Behind the recommended build |
| 20313 | 8 | 0 | 4 / 4 | Behind the recommended build |
| 18683 | 8 | 1 | 7 / 1 | Behind the recommended build |
| 13227 | 8 | 4 | 2 / 6 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 12208 | 8 | 1 | 6 / 2 | Behind the recommended build |
| 29047 | 7 | 2 | 3 / 4 | Behind the recommended build |
| 27636 | 7 | 24 | 5 / 2 | Documented issueIssues with building Yarn resources on some Linux servers |
| 27366 | 7 | 32 | 6 / 1 | Documented issueIssues with building Yarn resources on some Linux servers |
| 25924 | 7 | 0 | 6 / 1 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 21547 | 7 | 2 | 7 / 0 | Documented issueMultiple (unconfirmed) reports of server-sided natives throwing errors or causing crashes; best to avoid |
| 21314 | 7 | 1 | 5 / 2 | Behind the recommended build |
| 15488 | 7 | 1 | 4 / 3 | Behind the recommended build |
| 14583 | 7 | 0 | 2 / 5 | Documented issueCrash when using the new onEntityBucketChange |
| 13890 | 7 | 3 | 5 / 2 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 12911 | 7 | 0 | 2 / 5 | Behind the recommended build |
| 28097 | 6 | 63 | 3 / 3 | Behind the recommended build |
| 25718 | 6 | 0 | 4 / 2 | Behind the recommended build |
| 19826 | 6 | 1 | 4 / 2 | Behind the recommended build |
| 17871 | 6 | 0 | 2 / 4 | Behind the recommended build |
| 15015 | 6 | 1 | 2 / 4 | Behind the recommended build |
| 10488 | 6 | 0 | 2 / 4 | Behind the recommended build |
| 5848 | 6 | 2 | 6 / 0 | Behind the recommended build |
| 29365 | 5 | 2 | 5 / 0 | Behind the recommended build |
| 21130 | 5 | 1 | 4 / 1 | Behind the recommended build |
| 20718 | 5 | 1 | 4 / 1 | Behind the recommended build |
| 19413 | 5 | 1 | 3 / 2 | Behind the recommended build |
| 19032 | 5 | 0 | 3 / 2 | Behind the recommended build |
| 18270 | 5 | 1 | 3 / 2 | Behind the recommended build |
| 16565 | 5 | 1 | 3 / 2 | Behind the recommended build |
| 16501 | 5 | 0 | 2 / 3 | Behind the recommended build |
| 14758 | 5 | 0 | 2 / 3 | Documented issueTimeouts due to latency units being in nanoseconds |
| 14318 | 5 | 0 | 3 / 2 | Behind the recommended build |
| 13079 | 5 | 0 | 5 / 0 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 11535 | 5 | 1 | 5 / 0 | Behind the recommended build |
| 10822 | 5 | 0 | 1 / 4 | Behind the recommended build |
| 5181 | 5 | 3 | 5 / 0 | Behind the recommended build |
| 22819 | 4 | 1 | 4 / 0 | Behind the recommended build |
| 20944 | 4 | 0 | 2 / 2 | Behind the recommended build |
| 16811 | 4 | 0 | 2 / 2 | Behind the recommended build |
| 14482 | 4 | 1 | 3 / 1 | Behind the recommended build |
| 12168 | 4 | 0 | 4 / 0 | Behind the recommended build |
| 12160 | 4 | 1 | 3 / 1 | Documented issueCannot use entity native calls in entityRemoved |
| 12031 | 4 | 0 | 3 / 1 | Behind the recommended build |
| 10778 | 4 | 1 | 4 / 0 | Behind the recommended build |
| 10191 | 4 | 0 | 4 / 0 | Documented issueGetVehicleNumberPlateText server native broken, will cause issues with scripts involving vehicles |
| 27715 | 3 | 1 | 2 / 1 | Documented issueIssues with building Yarn resources on some Linux servers |
| 27250 | 3 | 1 | 2 / 1 | Documented issueIssues with building Yarn resources on some Linux servers |
| 25987 | 3 | 0 | 0 / 3 | Documented issueNode.js sandboxing seems to be causing issues for people - best to avoid for now |
| 23984 | 3 | 0 | 2 / 1 | Behind the recommended build |
| 20035 | 3 | 1 | 3 / 0 | Behind the recommended build |
| 17715 | 3 | 0 | 1 / 2 | Behind the recommended build |
| 16636 | 3 | 2 | 2 / 1 | Behind the recommended build |
| 16237 | 3 | 1 | 3 / 0 | Behind the recommended build |
| 16057 | 3 | 0 | 2 / 1 | Behind the recommended build |
| 15859 | 3 | 1 | 3 / 0 | Behind the recommended build |
| 15729 | 3 | 0 | 2 / 1 | Behind the recommended build |
| 15414 | 3 | 0 | 1 / 2 | Behind the recommended build |
| 15315 | 3 | 0 | 1 / 2 | Behind the recommended build |
| 14862 | 3 | 0 | 3 / 0 | Documented issueTimeouts due to latency units being in nanoseconds |
| 12966 | 3 | 1 | 3 / 0 | Documented issueHigh FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) |
| 12913 | 3 | 1 | 2 / 1 | Documented issueCauses a crash when restarting Node.js 22 |
| 12180 | 3 | 0 | 3 / 0 | Documented issuevoip-server-mumble.dll server crash (citizenfx/fivem#3054) |
| 11895 | 3 | 1 | 2 / 1 | Behind the recommended build |
| 9956 | 3 | 0 | 2 / 1 | Behind the recommended build |
| 9655 | 3 | 1 | 2 / 1 | Behind the recommended build |
| 4394 | 3 | 0 | 1 / 2 | Behind the recommended build |
Builds with documented issues
The full list of builds with issues reported by the community. The data comes from FiveM Artifacts DB, an open project by JG Scripts, and we show it here next to the one thing we add: how many servers are still running each of them.
| 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 | 4 |
| 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 | 4 |
| 12180 | voip-server-mumble.dll server crash (citizenfx/fivem#3054) | 3 |
| 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 | 3 |
| 12913–14177 | High FXServer CPU usage on Linux artifacts; fixed by 14193 (citizenfx/fivem#3222) | 23 |
| 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 | 7 |
| 14583–14862 | Timeouts due to latency units being in nanoseconds | 8 |
| 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 | 7 |
| 25839–25988 | Node.js sandboxing seems to be causing issues for people - best to avoid for now | 166 |
| 25943 | Failed build | — |
| 26261–27715 | Issues with building Yarn resources on some Linux servers | 264 |
| 27722 | Yarn fails to exit cleanly on Windows | 39 |
| 27783–27938 | SIGSEV crashes (issue #3915) | 59 |
| 28626 | Issues with packet loss/timeouts | 79 |
| 31689 | GetVehiclePedIsIn server native returns 0 (citizenfx/fivem#4051) | 1,394 |
| 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 | — |
Issue data source: FiveM Artifacts DB by JG Scripts, fetched on Aug 20, 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.
- Replace the FXServer files with the new build. 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