Updated 2026-10-11 · 2 min read
QB Studio: local development for FiveM and QBCore
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.
What you need
- Windows and the QB Studio
.exeinstaller from the GitHub Releases page. - An existing local Cfx.re
FXServer.exeorcfx-server.exeartifact andtxAdmininstallation. - A
txDataroot containing a server-data folder withserver.cfgandresources/. - A valid server license key; Git for Windows 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
- Install the Windows application from Releases. GitHub's automatic source ZIP is not the Windows installer.
- Locate the
txDatadirectory and the correct server-data folder beneath it. Do not confuse that folder with the txAdmin control-profile folder. - Configure a non-empty local RCON password; keep it out of version control by using a
secrets.cfgexcluded from Git. - In QB Studio Settings, select
txData, the server-data workspace and the server artifact executable, then Save & Connect. - Start the test server from QB Studio and inspect the console before opening the game client.
The official README 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, debugging and safe server events.
Sources
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
VS Code Setup
Visual Studio Code is the recommended IDE for QBCore development. This guide will help you set up an optimal development environment with the right…
Debugging
Reliable debugging keeps your server stable and your players happy. This guide focuses on practical techniques for isolating pr oblems in Lua scripts…
