Where BlueStacks stores data on Windows and how to move it
Android emulators generate a surprising amount of data, and BlueStacks is no exception. If you play mobile games on a Windows machine, your emulator files (the saved games, downloaded apps, cached images, and system snapshots) quietly accumulate over time and can quickly eat into a small SSD. Knowing the exact location of those files lets you reclaim disk space, keep a tidy system, or migrate your setup to a new drive or a freshly built PC.
This guide walks through the default storage folders used by BlueStacks, explains what each directory actually contains, and shows how Australian users in Sydney, Melbourne, Brisbane and beyond can safely relocate that data to another drive without breaking their installed games and apps. Along the way we answer a few common questions, including what to do when BlueStacks refuses to launch after a folder move or a system update.
| Path | Type of data | Typical size | Can be moved? |
|---|---|---|---|
| C:\ProgramData\BlueStacks_nxt | Shared engine data, logs, guest properties | 2–10 GB | Yes, with symlink |
| C:\Users<name>\AppData\Local\BlueStacks_nxt | User settings, configuration files | 500 MB–2 GB | Yes, with symlink |
| C:\Users<name>\Documents\BlueStacks_nxt | Instance system image (.qcow2), internal storage | 20–100 GB+ | Yes, with symlink |
| D:\Games\BlueStacks (example) | Custom relocation target | Varies | Acts as new home |
Where BlueStacks keeps files on a Windows PC
The modern BlueStacks build, sometimes called BlueStacks 5 or the nxt engine, splits its data across three main Windows directories. Two sit inside the user profile and one is hidden inside ProgramData, which is a protected system folder that Windows normally hides from File Explorer. Each location has a distinct purpose, and moving one without the others will leave the emulator confused.
The first location, C:\ProgramData\BlueStacks_nxt, holds the shared engine components, log files, and a small amount of cached data shared between every instance of the emulator. The second location, found inside your personal AppData folder, contains user-specific configuration files, including the screen resolution, your account login token, and any per-instance settings you have tweaked. The third location, by default placed under Documents, is the heavy lifter: this is where each Android instance stores its virtual SD card, its system image, and every app you have installed through the Google Play Store.
Inside the data folder: what each subfolder holds
When you open the default Documents\BlueStacks_nxt directory, you will see a folder for every Android instance you have created. Each instance folder is essentially a self-contained virtual device, with its own internal storage, its own camera roll, and its own list of installed apps. The largest single file inside is usually the .qcow2 disk image, which expands as you install more games and download more in-game assets.
Below the instance folders sits a shared data folder used for cached APK installers and a few smaller utility directories. The ProgramData\BlueStacks_nxt folder mirrors this layout but stores the engine-side shared libraries and licensing tokens. The AppData location only carries lightweight configuration files, which is why it is rarely the cause of a full disk but can still matter when you are migrating to a new Windows profile after moving from Brisbane to Perth, for example.
How to locate the BlueStacks storage path
The easiest way to confirm the current storage paths is to open BlueStacks itself, click the gear icon for Settings, then head to the Storage tab. The path displayed there is the active one, and it will reflect any previous manual moves you may have performed. If you have never opened that screen before, the path will point to the default Documents folder, which on most Australian Windows installations still resolves to a relatively small C: drive on laptops shipped by JB Hi-Fi or Harvey Norman.
You can also locate the folders manually by typing %programdata% into the Run dialog for the shared data, and %localappdata% for the per-user configuration. The instance folder lives one level deeper, under Documents, so typing %userprofile%\Documents\BlueStacks_nxt in File Explorer will jump straight there. Knowing these three paths is the foundation of any successful relocation.
Getting ready to move your emulator files
Before you shift a single gigabyte, close BlueStacks completely and confirm the engine services are stopped. Open Services from the Start menu, find anything starting with BlueStacks, and stop those services. This prevents the emulator from holding open file handles on the virtual disk image, which would otherwise cause silent copy errors or corrupted instances.
Next, decide where you want the data to live. Many users in capital cities like Sydney and Adelaide keep a fast NVMe SSD for the operating system and a larger SATA SSD or HDD for game libraries; moving BlueStacks to the secondary drive frees up precious boot drive space and avoids those dreaded low-disk warnings when you are halfway through downloading a 6 GB APK on a slow NBN connection. Make sure the target drive is formatted as NTFS, because exFAT and FAT32 can occasionally cause issues with very large disk image files.
Finally, take a full backup. Copy the entire BlueStacks_nxt tree from all three locations to an external drive or a network share. With an NBN FTTC or FTTP upload link in regional Western Australia, uploading to a cloud backup service can take hours, so a local external SSD is usually the more practical Australian-friendly option.
Step-by-step guide to relocating BlueStacks data
Once your backup is safe, create the new folder structure on the target drive, for example D:\Emulator\BlueStacks_nxt. Mirror the layout of the original Documents folder by creating an instance subfolder. Now use the built-in mklink command to create symbolic links from the original path to the new one.
Open Command Prompt as Administrator and run something like mklink /D "C:\Users\YourName\Documents\BlueStacks_nxt" "D:\Emulator\BlueStacks_nxt". Repeat the process for the AppData and ProgramData folders if you also want to move those, although most users only need to relocate the large instance data. After the links are in place, start BlueStacks, open the Settings panel again, and verify that the Storage tab now shows the new path. Launch a previously installed game to make sure save data and progress survived the move.
Troubleshooting relocation problems
If BlueStacks throws an error after the move, the most common cause is a leftover lock file or a permission mismatch on the new folder. Right-click the new directory, choose Properties, and confirm that your Windows user account has Full Control. Running the emulator as Administrator once can also clear stubborn permission prompts, particularly on shared family PCs.
Sometimes the engine refuses to start at all and gets stuck in a crash loop, even though the files appear to be in the right place. This often follows a major BlueStacks update rather than a manual move, and the underlying cause is usually a stale configuration file that survived the relocation. A walkthrough on fixing the crash loop covers the registry tweaks and cache clears that resolve this exact scenario, and the same steps apply if the trigger was a folder move rather than an update.
Backing up and restoring BlueStacks instances
Treat each instance folder as a self-contained backup unit. If you only play one or two mobile games on your PC, you can simply copy the relevant instance folder to an external drive before a major system change. Restoring is then as simple as dropping that folder back into the new BlueStacks_nxt directory and re-creating the symbolic link.
For users who run multiple instances, BlueStacks ships with a built-in backup feature accessible from the sidebar. Export each instance to a single .bak file, copy those files to your backup medium, and you can rebuild your entire emulator setup on a new Windows machine in minutes. This is especially handy if you are upgrading from an ageing gaming laptop purchased years ago in Melbourne's CBD to a new rig and want to carry your progress across without re-downloading gigabytes of game data over your home connection.
Your boot SSD is ready for a fresh start. Pick the heaviest BlueStacks folder, follow the relocation steps above, and turn that cluttered C: drive into the lean machine it was always meant to be.