FiveM artifacts: what they are and how to update them safely
Artifacts are the FXServer build that runs your server. Picking the wrong channel or updating the wrong way is one of the few mistakes that can take a roleplay community offline for a whole evening, so it is worth ten minutes of reading once.
What an artifact actually is
An artifact is a published build of FXServer: the executable and runtime that run your server, released by Cfx.re for Windows and Linux. It is not a resource, it does not go into your resources folder, and it is not something you edit.
Two consequences matter in practice. First, txAdmin is bundled inside the artifacts, so running the binary with no arguments is what opens the panel, and updating artifacts updates your txAdmin along with it. Second, because the artifact is the process that runs everything, you download it from the official Cfx.re listing and nowhere else. An artifact from a Discord attachment or a random mirror is not a risky script: it is arbitrary code with full control of your server and its database credentials.
Which build channel to run
The build Cfx.re marks as stable for general use. If you do not have a specific reason to be on something else, this is the answer.
The newest build. It gets you fixes and new natives first, and it also gets you the regressions first. Running it on a live roleplay server is how you find out about a bug at peak hours.
Sometimes a resource you cannot replace only works below a certain build. Pinning is legitimate, but write down which build and why, because that note is what stops the pin from becoming permanent by accident.
Updating without losing an evening
- 1
Check what you are running now
The build number is printed in the server console on boot and shown in txAdmin. Write it down before you change anything: without the old number a rollback is guesswork.
- 2
Read the change list for the builds you are skipping
Not just the one you are moving to. If you jump twenty builds, every breaking change in between applies to you at once, and that is where the surprises live.
- 3
Update a copy, not the server
Artifacts live in their own folder, separate from your server data. That separation is the whole point: unpack the new build alongside the old one and point the start command at it, so reverting is switching a path back.
- 4
Boot with your real resource list
An empty server always starts. What you need to know is whether your resources start, so test with the actual server.cfg and watch the console for errors on the way up.
- 5
Keep the previous build until you are sure
Give it a few days of real player load before deleting the old folder. Some incompatibilities only show up under concurrency, not on an empty test server.
Four mistakes worth naming
Overwriting the artifacts folder in place
You lose the ability to roll back in one move. Unpack each build into its own folder and switch which one you launch.
Mixing artifacts and server data in the same directory
It works right up until an update deletes something it should not. Keep the artifacts folder and the server data folder separate from day one.
Chasing the latest build on a live server
New builds fix things and break things. Unless you are waiting on a specific fix, being a few builds behind on the recommended channel is the boring, correct choice.
Updating on a Friday
If it goes wrong you will be debugging during your busiest hours with your smallest staff. Update early in the week, in your quiet window.
Frequently asked questions
What are FiveM artifacts?
Artifacts are the FXServer server build: the executable and runtime that actually run your server, published by Cfx.re per platform. They are not a resource and they do not go in your resources folder. txAdmin ships inside them, which is why running the artifact binary is what opens the txAdmin panel.
Where do I download FiveM server artifacts?
Always from the official Cfx.re runtime listing for your platform, Windows or Linux. Do not take artifacts from a Discord attachment or a mirror: the artifact is the process that runs your whole server, so a tampered build is total compromise, not a bad script.
Which artifact build should I use?
The recommended channel unless you have a concrete reason not to. Latest is for a test server. Pinning an older build is legitimate when a dependency forces it, as long as you record which build and why.
How often should I update artifacts?
There is no schedule that fits every server. Update when a fix you need lands, when a framework you use requires a newer build, or periodically so you never face a twenty-build jump at once. Never update straight onto production without booting the new build against your real resource list first.
Do artifacts include txAdmin?
Yes. txAdmin is bundled with the artifacts and is what starts when you run the binary with no arguments. That is also why updating artifacts updates your txAdmin version.
The panel that comes bundled with these builds has its own guide: txAdmin, what it is and how to set it up . And when the server is stable and the bottleneck becomes content, the FiveM scripts catalog covers QBCore, ESX, Qbox and standalone.