How to Start a FiveM Server in 2026

Five things, in this order: a Cfx.re license key (free from the Cfx.re Portal at portal.cfx.re, which replaced the old Keymaster in late 2025; required even for a local test server), somewhere to run (local for testing, VPS for real players), txAdmin as your control panel (ships bundled inside the FXServer artifact since 2020 and launches automatically on first boot), a framework decision (ESX, QBCore, or Qbox), and a database (MariaDB + oxmysql is the 2026 standard).

What you do not need before launch: a custom MLO pack, 40 paid scripts, or a full custom UI. Every week spent on content before the core loop works is a week your launch slips.

Run locally while you learn, it costs nothing and restarts are instant. Move to a VPS when friends start joining: you want 4+ dedicated cores (FiveM's main thread is single-core sensitive, so clock speed beats core count), 8–16GB RAM, and NVMe storage. Managed game hosting trades control for convenience; it is fine for a first server but you will outgrow the file-manager workflow once you debug seriously.

Location matters: put the box near your players. 40ms vs 120ms is the difference between clean driving and rubber-banding complaints on day one.

txAdmin is the panel that runs your server process: start/stop, live console, player list, bans, scheduled restarts, and recipe deployments. Three settings to get right immediately:

• Scheduled restarts twice a day. FiveM servers accumulate memory; restarts are hygiene, not failure.
• Server profile + backups before you touch anything.
• The recipe deployer can bootstrap an ESX or QBCore base in one click, use it for your first build instead of hand-assembling resources.

Your framework decides your script market, your hiring pool, and 80% of your future debugging. QBCore has the biggest beginner ecosystem, ESX the longest history and deepest catalog, Qbox the most modern engineering on a QBCore-compatible API. Decide before buying scripts, cross-framework migrations are weekend-eating work.

We keep a full decision guide with migration notes in the framework comparison.

Use MariaDB (not MySQL 5.7, not SQLite) and connect through oxmysql. Two rules save you from the classic day-30 meltdown: index every column you look up players by (identifier, citizenid, license), and never run queries inside a per-frame loop.

Resource discipline from day one: keep your resources/ folder organized by bracket ([core], [jobs], [vehicles]), start resources explicitly in server.cfg in dependency order, and keep the count under ~80 at launch. Every resource is tick budget and another thing that can break.

The five we see in nearly every audit: buying scripts before picking a framework, copying a 200-resource 'starter pack' and never reading what is in it, skipping ensure order so dependencies race on boot, leaving default passwords on the database while port 3306 is open to the world, and launching with streamed asset packs so heavy that new players time out on join. When you are within two weeks of opening, run the free 14-day launch checklist to catch these before players do.