<!-- fivemad.com, Markdown source of https://fivemad.com/docs/getting-started -->
> Source: https://fivemad.com/docs/getting-started
> Section: Getting started
> Tags: fivem, fxserver, txadmin, cfx.re, beginner, overview
> Last updated: 2026-09-22
> Site map for assistants: https://fivemad.com/llms.txt

# Getting started with FiveM servers and development

What FiveM, FXServer, txAdmin and Cfx.re are, how the pieces fit together, and the order to read these docs in to run a server or write scripts.

These docs take you from "I want a FiveM server" to running one, managing it with txAdmin, installing resources and frameworks, and writing your own scripts. Everything here is checked against the official Cfx.re documentation and the source repositories on GitHub. When something depends on a version, the page says so.

If you only want to get a server online today, jump to [Setting up a server on Windows](/docs/server-setup/windows) or [on Linux](/docs/server-setup/linux). If you want to write code, start with [Your first resource](/docs/development/first-resource). Come back to this page when a word stops making sense.

## The pieces and who makes them

FiveM is a modification framework for Grand Theft Auto V that lets people run their own multiplayer servers with custom code, maps, vehicles and game modes. A few names show up everywhere:

| Name | What it is |
| --- | --- |
| **Cfx.re** | The team and platform behind FiveM (GTA V) and RedM (Red Dead Redemption 2). Cfx.re is owned by Rockstar Games. The forum is [forum.cfx.re](https://forum.cfx.re), the docs are [docs.fivem.net](https://docs.fivem.net/docs/). |
| **FiveM client** | What players install. It launches their own copy of GTA V and connects to servers. |
| **FXServer** | The server program you run. Also called the "Cfx platform server". On Windows it is `FXServer.exe`, on Linux you start it through `run.sh`. |
| **Server artifacts** | The FXServer builds you download. Each build has a number, for example `2xxxx`. See [Updating artifacts safely](/docs/server-setup/updating-artifacts) and our [Artifacts page](/artifacts). |
| **txAdmin** | The web panel and in-game admin menu that ships inside FXServer. It deploys servers from recipes, restarts them, bans players and more. |
| **Cfx.re Portal** | [portal.cfx.re](https://portal.cfx.re), where you create the free server license key that every server needs. |
| **Resources** | Folders of scripts and assets that FXServer loads. Everything a server does beyond vanilla GTA is a resource. |
| **Frameworks** | Big sets of resources that add players, jobs, money and inventories, for example QBCore, Qbox and ESX Legacy. See [Frameworks](/docs/frameworks). |

> [!NOTE]
> In July 2026 Cfx.re opened early access for **FiveM for GTA V Enhanced**, which runs on the newer Enhanced edition of the game with a separate server build called **Cfx Server**. The classic FiveM, now called **Legacy**, keeps running and is still what almost every server and resource targets. These docs cover Legacy FXServer unless a page says otherwise. See [FiveM Legacy and Enhanced](/docs/server-setup#fivem-legacy-and-fivem-for-gta-v-enhanced) for what changes.

## How it fits together

When you start a server, this is what happens:

1. You run FXServer. With no arguments it starts **txAdmin**, which opens a web panel on port `40120`.
2. txAdmin (or you, by hand) starts FXServer with a `server.cfg`. That file sets the server name, the license key, player slots, endpoints and which resources to start.
3. FXServer reads the `resources` folder, loads every resource you `ensure`, and runs their **server scripts**.
4. A player connects on port `30120`. Their client downloads the **client scripts**, NUI pages and streamed assets (models, textures, maps) of your resources, then joins.
5. Client scripts and server scripts talk to each other with **events**, and to the game through **natives**.

```text title="A typical server folder after a txAdmin deploy"
FXServer/
├─ server/            the artifact: FXServer.exe (Windows) or run.sh + alpine/ (Linux)
└─ txData/
   ├─ admins.json     txAdmin accounts
   └─ MyServer.base/  your server data folder (any name you pick in the deployer)
      ├─ server.cfg
      └─ resources/
         ├─ [cfx-default]/   mapmanager, spawnmanager, chat...
         └─ [local]/         your own resources
```

## A learning path through these docs

Follow the sections in this order. Each page links to the next one.

### 1. Understand what you need

- [Glossary](/docs/getting-started/glossary): every term you will meet, in one place.
- [Requirements](/docs/getting-started/requirements): hardware, Windows or Linux, and the legal basics (license, Rockstar content, monetisation).

### 2. Get a server online

- [Server setup overview](/docs/server-setup), then [Windows](/docs/server-setup/windows) or [Linux](/docs/server-setup/linux).
- [server.cfg explained](/docs/server-setup/server-cfg) line by line. You can also build one with the [server.cfg Generator](/tools/server-cfg-generator).
- [Ports and networking](/docs/server-setup/ports-and-networking) and [Database setup](/docs/server-setup/database) if you plan to run a framework.
- [Common errors and fixes](/docs/server-setup/common-errors) and [Security basics](/docs/server-setup/security).

### 3. Run it day to day with txAdmin

- [txAdmin overview](/docs/txadmin), [first setup and the deployer](/docs/txadmin/first-setup), [recipes](/docs/txadmin/recipes), [everyday admin](/docs/txadmin/everyday-admin) and the [Discord bot](/docs/txadmin/discord-bot).

### 4. Add content

- [Installing resources](/docs/resources), [recommended open source resources](/docs/resources/recommended), [maps, MLOs and clothing](/docs/resources/maps-mlos-clothing) and [vehicle packs](/docs/resources/vehicle-packs).
- Pick a framework, or none: [Frameworks compared](/docs/frameworks).

### 5. Write your own scripts

- [Development overview](/docs/development) (tools and setup), then [Your first resource](/docs/development/first-resource).
- [Client, server and events](/docs/development/client-server-events), [natives](/docs/development/natives), [state bags and OneSync](/docs/development/state-bags-onesync), [NUI](/docs/development/nui).
- [Threads and performance](/docs/development/threads-performance), [exports and dependencies](/docs/development/exports-dependencies), [debugging](/docs/development/debugging).
- [Streaming custom assets](/docs/development/streaming-assets) and [publishing a resource](/docs/development/publishing).

### 6. Watch instead of read

The [video tutorial archive](/docs/videos) groups hand-picked YouTube tutorials into courses: running your first server, txAdmin, frameworks, Lua scripting, NUI, streaming assets, CodeWalker and Blender with Sollumz.

## Where to get help

- **Official docs**: [docs.fivem.net](https://docs.fivem.net/docs/) for server setup, the scripting manual and the [natives reference](https://docs.fivem.net/natives/).
- **Forum**: [forum.cfx.re](https://forum.cfx.re) has Server Discussion, Development and Releases categories. Search before you post, most errors have been seen before.
- **Framework communities**: QBCore, Qbox, ESX and Overextended each run their own Discord and docs, linked from the [frameworks pages](/docs/frameworks).
- **txAdmin**: the [txAdmin Discord](https://discord.gg/txAdmin) and the docs folder in the [txAdmin repository](https://github.com/citizenfx/txAdmin/tree/master/docs).

> [!TIP]
> When you ask for help, paste the exact error from the server console or the F8 client console, your artifact build number and your `server.cfg` (with the license key and database password removed). That answers half the questions people will ask you.