How to Install a QBCore Server on Localhost (Windows)

Set up a full QBCore server on your own PC for free, install and test your MLOs, then move the finished build to a live host in a few hours.

Most people who want to run a FiveM roleplay server make the same costly mistake. They rent a paid host on day one, and then they spend their first weeks learning where files go and how the config works, all while the monthly bill keeps running. Worse, every test happens live, so one wrong setting boots everyone off the server at once. Building a QBCore server on localhost first avoids all of that.

There is a calmer way. Localhost is your own computer acting as the server, which means you can install a full QBCore setup on your Windows PC for free. As a result, you build and test the whole city there first, and only then copy the finished files to a paid host. In our experience, that turns a stressful live launch into a calm one that takes a few hours. So this guide walks that exact path, step by step.

Key Takeaways

• A localhost QBCore server runs on your own PC for free. You only pay for hosting when you are ready to go public.
• You need three downloads: the FiveM server files, MariaDB (the database), and HeidiSQL (to view player data). txAdmin and the QBCore recipe handle the rest.
• The QBCore recipe creates the database and installs every script for you, so there is no manual SQL setup to worry about.
• Build and test your MLOs locally, then move the same files to a live host and launch in a few hours. Every RPBazzar MLO is unlocked and editable at the current 9.99 flat price.

Why Build a QBCore Server on Localhost First?

A localhost server is simply a FiveM server running on your own computer instead of a rented machine. In other words, you are the host, the build, and the only player until you eventually decide to open it up to others. For anyone still learning the basics, that makes it the safest possible place to start. So here is why so many experienced builders set up locally first, before they ever spend a cent on hosting.

• Practice before you pay. The rental clock starts the day you rent. As a result, there is no reason to burn paid hosting hours learning where server.cfg lives.
• It costs nothing. Localhost is free. Specifically, you only pay once the build is ready and players are coming.
• It is a safe sandbox. Crash it, break it, wipe it, reinstall. Importantly, nobody is watching, so there is no downtime to hurt your server's name.
• Testing is instant. There is no uploading files over FTP and waiting. In fact, you edit, restart, and test on the same machine in seconds.

Beyond the cost savings, building locally also makes you a sharper builder.

• You learn the real fundamentals. For example, the config, the resources folder, and how MLOs stream in, all with zero risk.
• You test every MLO before it goes live. In other words, you confirm a gang hideout or food court actually loads and works before any player sees it.
• You stage the whole build, then migrate. That is, you get the city finished locally, copy the files to a host, and flip it live.
• It doubles as a demo. Similarly, freelance builders can show a client the server running locally before paying for any deployment.

The table below shows the difference while you are still building.

	Localhost (your PC)	Paid host (while still learning)
Cost while building	Free	Monthly bill running
A mistake means	Reinstall, nobody sees it	Downtime players notice
Testing a change	Restart instantly	Upload, wait, restart
Who can join	Really just you; letting a friend in needs port forwarding and extra setup, and can still fail	Public before the build is ready, which is risky while you learn

What You'll Need Before You Start

This is a beginner-friendly setup that requires no coding background whatsoever, and the entire process runs comfortably on an ordinary Windows computer.

Your three downloads:

• FiveM server files (the Windows server build) from the Cfx.re artifacts page. Specifically, grab the latest recommended build.
• MariaDB from mariadb.org. In short, this runs the database in the background that stores all player data.
• HeidiSQL from heidisql.com. This, in turn, is the viewer you use to open that database and read player data later.

You also need:

• A free Cfx.re account (you log in with this during setup).
• Time: about 25 to 30 minutes for the whole install.
• Difficulty: Beginner.

Install MariaDB and HeidiSQL first, and once both applications are installed, you are ready to begin configuring the server itself.

Step 1: Create Your Server Folders

By the end of this step you will have a clean folder layout that keeps the server engine and your server data separate.

First, pick any drive with some free space. Then create a folder called FiveM-Server. Inside it, create two more folders:

1. server holds the engine, the FiveM server files you downloaded.
2. files holds your server data, the resources and config the QBCore recipe will install.

FiveM-Server/
├── server/   ← the FiveM server files go here
└── files/    ← your server data lands here

As a result, keeping these two apart makes the build easy to manage and easy to move to a host later.

Step 2: Extract the Server Files and Run It

By the end of this step the server will boot and open its setup page in your browser.

First, move the server files .zip you downloaded into the server folder, then extract all of it there. Then open the extracted files and run FXServer.exe.

A setup page opens automatically in your browser. txAdmin is the web control panel that runs and manages your server, and it is built into the server files, so you do not install it separately. For now, leave the FXServer window open in the background while you work through the setup.

Step 3: Log In With Your Cfx Account

By the end of this step you will be inside the txAdmin setup, signed in.

So on the page that opened, log in with your Cfx.re account and set your password. For a localhost test, any Cfx account works fine.

Tip from experience: If you have already bought paid or custom scripts, log in with the account that owns them. That keeps those paid scripts working without trouble. If you use a different account, you can change the Cfx key later, which we cover below.

Step 4: Name Your Server and Pick the QBCore Recipe

By the end of this step you will have chosen QBCore as your base and pointed txAdmin at your data folder. Now you make two choices that shape the whole build.

1. Server Name. Type a short name. This is only the label inside the txAdmin panel, so something like Localhost is fine. You can rename it later in settings.
2. Deployment Type. Choose Popular Recipes, which downloads the latest scripts. Then select QBCore and continue.
3. Data Location. Open your files folder, copy its full path, and paste it here. For example, you might enter E:\FiveM-Server\files. Then click Change Path, delete the old path, and replace it with yours.

This is the moment the two-folder layout pays off. As a result, the recipe deploys everything into files, kept neatly apart from the engine in server.

Step 5: Add Your Cfx Key and Run the Recipe

By the end of this step every QBCore script and the database will install on their own.

1. Click Go to Recipe Deployer.
2. On Step 1: Review Recipe, click Next.
3. Now paste your Cfx key. A Cfx key is a free server registration key that tells FiveM your server is allowed to run. Get it from the Cfx.re registration keys portal. For your first time, open the link, click Generate Key, then copy the key and paste it in.
4. Click Step 3: Run Recipe. The download of all the scripts begins.

The recipe also sets up the database for you, which is the part that scares most beginners off. Here is how it works. MariaDB runs quietly in the background as the engine that stores everything, and the QBCore recipe creates and fills the database during this same install. As a result, you never build a table or write a line of SQL by hand. HeidiSQL stays out of the way until you actually want it. For example, once players have characters, you open HeidiSQL, connect to that database, and read their money, jobs, and inventory in a plain table. So the two database tools you installed earlier are not extra homework. One runs the data, the other lets you look at it, and the recipe wires both up for you in this step.

Step 6: Save, Run, and Restart Once

By the end of this step your QBCore server is live on your machine.

When the download finishes, the last button says Save & Run. So press it, and your server starts. Then, once it is fully launched, restart it one more time so everything loads cleanly. After that, you are ready to connect.

Step 7: Connect and Play

By the end of this step you will be inside your own server.

With the server running, open the FiveM client. Then look for the extra direct-connect button. If you do not see it yet, do not worry, because it appears after FiveM restarts, so you can skip ahead. Now press F8 to open the console, type connect localhost, and press Enter. You are in your own QBCore city.

How to Reopen Your Server Later

The good news is you do not repeat the whole setup next time. Instead, to start the server again, go to your server folder (for example E:\FiveM-Server\server), find FXServer.exe, and run it.

Similarly, to open the txAdmin panel anytime, go to localhost:40120 in your browser. Then log in with the same Cfx username and password you set during the install.

When the Recipe Download Fails

Recipe downloads sometimes stop partway through, usually a network hiccup rather than anything you did. If that happens:

1. Start the deploy over from the beginning. In particular, delete everything inside the files folder first so you begin clean.
2. If it fails again, install Cloudflare's 1.1.1.1 (WARP), connect it, then retry. As a result, most connection problems that block the download clear up.

In our experience, a clean retry after emptying the files folder fixes this nearly every time.

Install Your First MLOs on Your Localhost Server

Now comes the fun part, and the reason localhost matters so much. An MLO is a custom interior or building you stream into your server, such as a house, a nightclub, or a gang hideout. This is exactly where you test those interiors with no risk and no live players watching. For each one, you drop the MLO into your stream folder, add it to your resources, restart, and walk through it in-game. Specifically, you watch for three things: that the interior streams in fully, that the doors and teleports work, and that no textures are missing. If any of those fail on localhost, you fix them now, while the only person affected is you. As a result, the version you push to the live host is one you have already confirmed works, so it will load clean there too.

For that reason, test each piece here first. For example, a police station, a gang base, a hospital, or a nightclub: load it, confirm the coords and doors work, then keep building. Below are the categories most owners start with, on both stores.

Start With a Gang Hideout

Browse the gang hideouts on RPBazzar (84 MLOs) or on Payhip. A hideout is the heart of a crew's roleplay, so it makes a great first interior to load and test on your localhost build.

First, spawn into it, check the entrances, and confirm the interior streams in fully before you move on. Because every RPBazzar MLO ships unlocked, you can also reskin the walls and logo for each crew once the base loads. As a result, three crews can share one base file and still each get their own look. So test it locally now, and that is one less surprise waiting for you on launch day.

Add a Food Court or Restaurant

Browse the food courts on RPBazzar (109 MLOs) or on Payhip. Food spots give players somewhere to gather, work, and run in-character businesses, so they earn their place early in a build.

Next, load one, check the props and signage render, and walk the space to feel the scale. Meanwhile, the localhost test means you catch any missing texture before a single player ever sees it. In fact, that one habit, testing every interior locally first, is what separates a clean launch from a buggy one.

Every Other Category Installs the Same Way

The same drop-into-stream, restart, and test loop covers the whole catalogue. So pick a category, load it on your localhost server, and confirm it works before you commit it to the live build. Here are the popular ones with both store links.

Category	Browse on RPBazzar	Browse on Payhip
House	86 MLOs	Payhip
Mechanic Shop	67 MLOs	Payhip
Nightclub	44 MLOs	Payhip
Mansion	42 MLOs	Payhip
Bank	27 MLOs	Payhip
Apartment	20 MLOs	Payhip
Drug Lab	18 MLOs	Payhip
Hospital	17 MLOs	Payhip
24-7 Store	15 MLOs	Payhip
Bar	10 MLOs	Payhip
Casino	9 MLOs	Payhip

Notably, the full library runs to more than 50 categories, and each one loads on your localhost server the same way.

From Localhost to Live in a Few Hours

Here is the payoff of building locally. Once your city is tested and you are happy with it, going public is fast, because the hard work is already done.

First, you copy your files server data, including your resources and your server.cfg, to your paid host. Then you install MariaDB on the host, import the same database, and point the config at it. After that, you set your Cfx key, open the right ports, and start the server. Because everything was already tested on localhost, you are not building live and guessing at the same time. Instead, you are launching a build you have already walked through end to end, interior by interior. As a result, most owners get from a finished local build to a live, joinable server in a few hours rather than days. In our experience, the few problems that do appear are small config tweaks, not broken MLOs, because the heavy testing already happened on your own PC.

That, in short, is the whole reason to start on localhost. You learn for free, you test for free, and you only pay once you are ready to open the doors.

You Do Not Need to Be a Developer

This is worth repeating, because it changes who can do the work. The setup looks technical, but txAdmin and the QBCore recipe do the heavy lifting. Specifically, they download the scripts, build the database, and wire it together. Your only job is to follow the steps, point the data location at the right folder, and paste a free key.

In other words, if you can install a program and copy a folder path, you can stand up a QBCore server on your own PC. From there, testing MLOs is just dragging a file in and walking around. So this is well within reach for a first-time owner.

About the Author

This guide comes from the team behind RPBazzar, an MLO marketplace run by people with three-plus years in the FiveM space, including running and launching servers. We set servers up on localhost before going live ourselves, and we tested this flow on Windows before writing it. Every step here was reviewed by our own server builders for accuracy. Tools change over time, so we keep this page updated. Questions are welcome through our contact page, and you can read more guides on our blog.

Frequently Asked Questions

Is a localhost FiveM server free?

Yes. Because a localhost server runs entirely on your own computer, there is no hosting cost whatsoever while you build and test. In fact, you only pay for a host once you actually decide to take the server public. Specifically, the server files, txAdmin, MariaDB, HeidiSQL, and a Cfx registration key are all completely free.

Do I need a Cfx key for a localhost server?

Yes. The recipe specifically requires a free Cfx key during setup. For example, you can generate one in roughly a minute at the Cfx.re registration keys portal, then paste it in. Importantly, if you log in using the account that already owns your paid scripts, those scripts continue working without any additional steps.

Can my friends join my localhost server?

Not easily, and that is fine. Since localhost works only on your own computer, letting friends in means sharing your IP, opening ports, and sometimes installing extra software, and even then the connection can still fail. For that reason, a localhost build is best treated as a solo space for testing and learning. If friends need to join at different times and you cannot leave your PC running constantly, a VPS (a rented always-on server) is the sensible next step. Localhost stays the best place to test, and once everything works, you move the finished build to a host.

Will my MLOs work on the live host after I test them locally?

Yes, and that is precisely the purpose of testing on localhost first. For example, if an MLO loads cleanly on your local server, it behaves identically on your live host, because you carry over exactly the same server files and configuration. As a result, you discover problems before any player ever sees them.

Do I have to set up the database by hand?

No. The QBCore recipe automatically creates and populates the database for you during installation while MariaDB operates quietly in the background. In other words, you never construct any tables yourself. HeidiSQL, meanwhile, exists only for the moments when you want to open the database and examine player data.

How long does it take to go from localhost to a live server?

Once your local build is thoroughly tested, most owners go live within a few hours. Specifically, you copy your server data to the host, connect it to the database, configure your Cfx key, and launch it. As a result, the genuinely slow part, building and testing everything, is already finished on localhost.

Build It Local, Then Make It Yours

Set up your QBCore server on localhost, test it for free, and only pay for hosting when your city is ready. In the end, the MLOs you load are what make it feel like your server, not a copy of everyone else's.

Browse everything on RPBazzar (804 MLOs) or on Payhip (770 products). Every MLO is unlocked and editable at the current 9.99 flat price, so you can test it on localhost tonight and have it ready for launch day.