# ❓ Frequently Asked Questions

Start with the question that matches your task. These are independent community notes, not a replacement for checking the source used by your server.

## Getting started

### How do I install QBCore?

Follow the [Linux installation guide](/docs/installation/linux) or [Windows installation guide](/docs/installation/windows), then complete the [first-boot checklist](/docs/getting-started) before adding resources.

### What version of FiveM artifacts should I run?

Start with the recommended artifact from the [Cfx.re server download page](https://runtime.fivem.net/artifacts/fivem/), choosing the correct platform. The artifact is the **FXServer executable and its accompanying files**. Record the artifact build you install and test updates on a separate server before replacing the production binaries.

`sv_enforceGameBuild` selects the **GTA game build used by clients**. It does not install, update, or pin the FXServer artifact version. See the [Cfx.re command reference](https://docs.fivem.net/docs/server-manual/server-commands/#sv_enforcegamebuild-build) before changing it; the command is applied at startup.

### Can I use txAdmin with QBCore?

Yes. Use the [project-maintained QBCore recipe](https://github.com/qbcore-fivem/txAdminRecipe) in txAdmin. The [installation guides](/docs/installation) cover host preparation; [first-boot checks](/docs/getting-started) cover the resulting server.

## Server management

### How do I update core resources safely?

Back up the database and files, record the current resource commits, and test a compatible set of updates on staging. Review dependencies and SQL changes together; updating one resource does not prove the rest remain compatible. Follow the [update conflict workflow](/docs/troubleshooting/resource-update-conflicts) and keep a tested rollback.

### How do I handle lag spikes or frame drops?

First distinguish client frame drops from server-side stalls. Use the [Resmon guide](/docs/performance/resmon-basics) for client resource measurements and the [performance guides](/docs/performance) for further diagnosis. Record a reproducible workload before changing loops, queries, or configuration.

### What should I do before opening the server to the public?

Complete the [first-boot checklist](/docs/getting-started), review [security practices](/docs/security), test a backup restore, and verify [staff permissions](/docs/guides/how-to-become-admin). Publish rules and a player-support contact for your own server; this website's FAQ is not your server's rules page.

## Development

### How do I create custom UI with callbacks?

Follow the [NUI form tutorial](/docs/guides/nui-form-callback). Keep browser-to-client NUI callbacks distinct from server events, and validate any resulting server-side action.

### Where can I find API references?

Use the [API index](/docs/api), [client functions](/docs/api/client-functions), or [server functions](/docs/api/server-functions). Match examples to your installed resource commit and execution context.

### How do I keep server events secure?

Treat client input as untrusted. Validate permissions, input, state, and server-owned values before applying an action. Use the [safe server events guide](/docs/security/safe-server-events) as a starting point, not a security guarantee.

## Migration & upgrades

### Can I migrate from ESX without wiping data?

Possibly, but it depends on your schema, inventory, character system, and custom resources. The [ESX migration guide](/docs/migration/esx-to-qbcore) provides a planning workflow, not a universal lossless converter. Migrate a copy first and reconcile characters, inventory, and balances before switching production.

### How do I track framework updates?

Use the [update sources and checklist](/docs/overview/changelog), then compare upstream changes with the commits you actually run. Do not treat a recipe version or a roadmap announcement as a released version of every resource.

> 🙋</span>}>
> For server or framework help, use the [Support page](/support). To correct this website, use [Report a documentation error](/support#report-a-documentation-error).
