# QB Studio: local development for FiveM and QBCore

[QB Studio](https://github.com/qbcore-framework/qb-studio) is a **Windows desktop coding workspace** from the QBCore Framework organization. It combines a Monaco editor, local server controls, a resource tree, console, optional AI coding assistant and a local-client preview. Unlike `qb-core`, **it is not an FXServer resource** and must not be placed under your `resources/` directory.

This page is based on the [repository's install and configuration guide](https://github.com/qbcore-framework/qb-studio/blob/4d21c0cc46425539cbeec8cdb95b0eac689c5a66/README.md).

## What you need

- Windows and the QB Studio `.exe` installer from the [GitHub Releases](https://github.com/qbcore-framework/qb-studio/releases) page.
- An existing local Cfx.re `FXServer.exe` or `cfx-server.exe` artifact and `txAdmin` installation.
- A `txData` root containing a server-data folder with `server.cfg` and `resources/`.
- A valid server license key; [Git for Windows](https://git-scm.com/download/win) for GitHub imports.

The repo README includes separate launcher paths for FiveM Legacy, FiveM Enhanced and RedM. Linux/macOS installation should **not** be inferred from the Windows documentation.

## Connect a local test workspace

1. Install the Windows application from **Releases**. GitHub's automatic source ZIP is not the Windows installer.
2. Locate the `txData` directory and the correct server-data folder beneath it. Do not confuse that folder with the txAdmin *control-profile* folder.
3. Configure a non-empty local RCON password; keep it out of version control by using a `secrets.cfg` excluded from Git.
4. In QB Studio Settings, select `txData`, the server-data workspace and the server artifact executable, then **Save & Connect**.
5. Start the test server from QB Studio and inspect the console before opening the game client.

The [official README](https://github.com/qbcore-framework/qb-studio/blob/4d21c0cc46425539cbeec8cdb95b0eac689c5a66/README.md) describes port/profile resolution, separate Legacy/Enhanced paths, source integrity and update/rollback behavior in detail.

## Security and AI editing boundaries

QB Studio's documented control traffic is intended for loopback. A stock FXServer bind address may **still expose the server on other interfaces** depending on firewall/router settings. Keep development ports off the public Internet and never forward RCON.

The AI agent is scoped to approved coding actions and file changes; review proposed diffs before allowing writes. Do not confuse the local console/agent with remote server administration or arbitrary Lua execution.

## When to choose QB Studio

| Need | Recommendation |
| --- | --- |
| Windows local QBCore scripting with integrated console | QB Studio can reduce context switching |
| Cross-platform editing on macOS/Linux | Use your existing editor plus Cfx.re tools; QB Studio's README documents Windows |
| Production server administration | Use txAdmin and deployment tooling, not a development IDE |
| Validate a QBCore resource | Pair the editor with a disposable FXServer, SQL backup and multi-client tests |

Related: [VS Code setup](/docs/development/vscode-setup), [debugging](/docs/development/debugging) and [safe server events](/docs/security/safe-server-events).

## Sources

[Repository](https://github.com/qbcore-framework/qb-studio/tree/4d21c0cc46425539cbeec8cdb95b0eac689c5a66) · [Installation and capabilities](https://github.com/qbcore-framework/qb-studio/blob/4d21c0cc46425539cbeec8cdb95b0eac689c5a66/README.md) · [Releases](https://github.com/qbcore-framework/qb-studio/releases)
