SFTP (SSH File Transfer Protocol) is an encrypted network protocol for transferring files over an SSH connection. It lets you securely exchange files between your PC and your game server. With SFTP, you can access and manage your server files—whether you want to upload or download files, or edit them directly.
ZapX game servers only support access via SFTP. Classic, unencrypted FTP is not supported.
To connect via SFTP, you need an SFTP client. There are many clients available, but two of the best-known and most established are FileZilla and WinSCP.
| SFTP client | Download |
|---|---|
| FileZilla | Official website |
| WinSCP | Official website |
With FiveM, you mainly use SFTP to work with your resources, the server.cfg and the txAdmin data. Connecting and credentials work exactly as described above. Even though people often talk about "FiveM FTP": with ZapX you always connect via SFTP.
After logging in, the FiveM files are in the fivem folder and, below it, in the folder of your variant, for example fivem/standard. There you'll find:
| Folder / file | Contents |
|---|---|
<Name>_<Code>.base (e.g. Qbox_E99E54.base) | The server folder txAdmin creates when you set it up with a recipe. It contains the server.cfg and the resources folder. |
default | The txAdmin profile with settings (config.json), data and logs |
admins.json | The txAdmin admin accounts |
server-data | Another server folder with its own server.cfg and resources folder |
artifacts | The FiveM server files (FXServer). You don't need to change anything here. |
ZapX has no separate txData folder. The txAdmin data sits directly in this variant folder.
To see which server folder is currently active, open txAdmin and go to Settings → FXServer, field Server Data Folder. Changes to a server.cfg in any other folder have no effect.
- Extract the downloaded resource on your PC. The
fxmanifest.luafile (__resource.luafor older resources) must sit directly in the resource folder. - Stop your server.
- Upload the folder via SFTP into the
resourcesfolder of your active server folder. - Add the resource to the
server.cfgwithstart <foldername>and start the server.
You'll find more details in the guide FiveM: Installing Resources.
- Stop the server before you change the
server.cfg, files in thedefaultfolder or theadmins.json. The server and txAdmin write to these files, so changes made while the server is running can be overwritten. - Download a copy of the file first so you can go back if something goes wrong.
- You can also make smaller changes to the
server.cfgdirectly in the txAdmin CFG Editor.
With FiveM, the folder that grows most is cache in the server folder (<Name>_<Code>.base/cache). You can delete it while the server is stopped, FiveM recreates it on the next start. You can also remove older log files in default/logs. Leave the artifacts folder and the other txAdmin files unchanged.
Check that the folder name matches the name in the start command exactly (it's case-sensitive) and that the fxmanifest.lua sits directly in the folder, not in a subfolder. You'll find more issues under FiveM: Common Problems.
