Winlator Setup Guide: From Install to Your First Game

The whole setup in one paragraph: install the Winlator APK from the official GitHub releases, create one container per game, copy your game files into the folder that maps to the container's D: drive, then open the container and double-tap the game's EXE. Done right, your first game runs within about half an hour.

The rest of this guide walks through each of those steps screen by screen — the APK install, your first container, where game files go, mounting ISOs, opening EXE files, and launching your first program. (If you don't have the APK yet, the download guide covers getting the real file.) Take it in order: every step builds on the last, and skipping ahead is how people end up debugging three problems at once.

Step 1 — Install the APK

1. Download the APK from the official GitHub releases page (brunodev85/winlator). Never from a mirror.
2. Open the downloaded file. Android will ask you to allow your browser to install unknown apps — grant it. This is a one-time, per-app permission and it's completely normal for sideloading.
3. Confirm the install. Play Protect may show its generic "unknown app" caution; that's Android being careful with all sideloaded apps, not a judgment on Winlator.
4. Open Winlator from your app drawer. The first launch takes a little while as it extracts its runtime files. Give it a minute.

Step 2 — Understand containers before you touch anything

Winlator organizes everything into containers. A container is a self-contained Windows-like environment: its own virtual C: drive, its own registry, its own settings for resolution, graphics driver, DX wrapper, CPU cores, and Wine configuration. Think of each container as a separate little PC.

The golden rule: one game, one container. It's tempting to install five games into one container to save time. Don't. Different games want different settings, and when something breaks you want to delete one container and start over without touching your other working games.

On the main screen you'll see your container list (empty at first) and a button to create a new one. That's where we're headed.

Step 3 — Create your first container

1. Tap the + (create container) button.
2. Give it a name you'll recognize later — the game's name is the obvious choice.
3. Now the settings. For your very first container, keep it simple: use the defaults as a starting point and adjust only what's suggested for your hardware:

• Resolution: start with your phone's native resolution or 1280×720. Higher resolutions cost performance; you can raise it later once the game runs.
• Graphics driver: if your phone has a Snapdragon chip (Adreno GPU), try the Turnip driver option first — community experience favors it for most games. Other GPUs use their respective driver options.
• DX wrapper: DXVK is the usual starting point for DirectX 9–11 games. VKD3D is for DirectX 12 titles. WineD3D is the older fallback.
• CPU cores: set it to most of your phone's cores, but leave at least one or two free for Android itself. On an 8-core phone, 6 is a common starting value.

1. Save the container.

Don't overthink these on day one. The point of the first container is to prove the pipeline works; fine-tuning comes after you've seen a game actually launch. The settings-and-performance content in the guides section goes deep on tuning later.

What starter settings should you use for your phone tier?

You don't need perfect settings on day one — you need sane starting points. Pick your tier, set these, and only tune after you've seen a game actually launch. These are starting defaults, not benchmarked results:

Two rules for everything after this: change one setting at a time when troubleshooting, and judge performance only after the first few minutes — shader compilation makes the early minutes stuttery on any phone.

Step 4 — Launch the container and look around

Tap your new container to launch it. You'll see a Windows-style desktop: a taskbar, a desktop, a file explorer. Take a minute to get oriented. This isn't a video of Windows — it's a working environment. You can open the file explorer, browse drives, and run programs.

Notice the drives. C: is the container's internal system drive. D: is the shared drive — the bridge between Winlator and your phone's storage, and it's where your game files go. Remember this: D: drive = your games live here.

Step 5 — Put your game files in the right place (D: drive)

On your phone's actual storage, Winlator exposes a folder (inside the Winlator data directory, usually reachable through your file manager) that maps to the container's D: drive. The practical workflow:

1. On your phone, open your file manager and find the Winlator shared folder for your container (often under the app's storage as the D: drive mapping — check the container's drive settings if you're unsure which folder it points to).
2. Copy your game folder there — the full game directory, exactly as it would sit on a PC (with its EXE, data folders, DLLs, everything).
3. Inside Winlator's file explorer, open the D: drive. Your game folder should be sitting there.

Where do game files come from? Your own library: games you own on disc that you've copied over, DRM-free installers you've bought (GOG installers work well — run the installer EXE inside the container and install to the D: drive), or game folders copied from your PC. Winlator ships with no games and can't fetch them for you.

A note on ISOs

Many older PC games come as ISO disc images. Winlator can work with these:

1. Copy the ISO file to the D: drive folder on your phone.
2. Inside the container, you need the ISO mounted as a virtual disc drive. If your Winlator version includes ISO mounting in the container settings or drive options, enable it there and point it at the ISO.
3. Alternatively, extract the ISO on your PC first (any archive tool opens ISOs) and copy the extracted game folder to D: — this sidesteps mounting entirely and works just as well.
4. Once mounted or extracted, run the installer or the game's EXE from the virtual drive.

For games with multiple discs, mount or extract each disc in turn during installation, exactly as you would on a real PC.

Step 6 — Open EXE files and launch programs

Inside the container, opening a program works the way it does on Windows:

1. Open the file explorer and go to the D: drive.
2. Find your game's folder and the game's .exe file (the launcher or main executable — check the game's documentation if there are several).
3. Double-tap (or double-click, depending on your input mode) the EXE.

The first launch of anything is the moment of truth. A few things to know:

• First launches are slow. Wine may show configuration dialogs, install bundled components (like DirectX redistributables or Visual C++ runtimes that ship with the game), or just take a while. Let it finish.
• Wine Mono / Wine Gecko prompts: some programs trigger prompts to install Wine Mono or Wine Gecko. Allow these — they're normal Wine components, not malware.
• "Run as administrator": if a program complains about permissions, look for a run-as-administrator style option in the container's settings or the program's context menu rather than fighting it.

If the game reaches its menu, congratulations — the hard part is over. If it crashes or shows a black screen, don't panic: note exactly what happened (which screen, any error text) and work through the troubleshooting content. Nine times out of ten it's a graphics driver or DX wrapper mismatch, fixed by trying the other options in the container settings.

Step 7 — Set up your controls

Before you judge whether a game "works," get the input right:

• Touchscreen mode works for point-and-click games, menus, and strategy titles out of the box.
• Virtual gamepad: Winlator includes an on-screen gamepad overlay you can enable and customize — map buttons to keyboard keys for games that expect a keyboard.
• Mouse: for shooters and games needing precise aiming, enable mouse/pointer capture mode if your container offers it, and consider pairing a Bluetooth mouse — it transforms first-person games.
• Controllers: XInput-compatible controllers (including most Bluetooth gamepads) can be mapped for games with controller support.

Spend five minutes mapping controls for each new game. In our experience, a game that feels unplayable with default touch controls often feels fine with a mapped gamepad or mouse.

Step 8 — Install a second game (repeat the pattern)

Now that the first game works, the pattern for every future game is the same:

1. Create a new container named after the game (one per game, as in Step 2).
2. Choose settings suited to that game (2D indie title? lighter settings. Demanding 3D game? the full driver + DXVK treatment).
3. Copy the game to the D: drive, mount the ISO if needed.
4. Install/run the EXE inside the container.
5. Map controls, tune resolution until performance feels right.

In our view, this container-per-game discipline is what separates people who enjoy Winlator from people who fight it. Settings that make one game sing can make another crash; isolation keeps every game independent.

What mistakes do first-timers make?

• Putting games on C: instead of D:. — see Step 4: C: is the container's system area, D: is persistent shared storage.
• One container for everything. — see the golden rule in Step 2.
• Maxing resolution first. Start at 720p-ish, confirm the game runs, then raise resolution. Resolution is the cheapest performance lever you have.
• Changing five settings at once. When troubleshooting, change one thing, test, then change the next. Otherwise you'll never learn what fixed it.
• Judging performance in the first 60 seconds. Shader compilation and first-time setup cause stutter that disappears on later runs. Give a game a few minutes before deciding it's too slow.
• Downloading games from "free Winlator game" sites. Apart from the piracy issue, repacked game downloads are a classic malware vector. Use game files you own.

What files can Winlator actually run?

The short list: Windows .exe installers and programs, .msi installers, disc images (ISO) once mounted or extracted, and portable game folders copied straight from a PC. It doesn't run Android APKs (that's what your phone already does), it doesn't run Linux binaries, and it doesn't run console ROMs — those need their own emulators. If a file is a Windows program, Winlator is at least worth trying; if it's anything else, you're in the wrong app.

Frequently asked questions

How do I use Winlator on Android for the first time?

Install the APK from GitHub, create a container, put your game files on the D: drive, and launch the game's EXE inside the container. This guide covers each step in order.

Where do I put games in Winlator?

On the D: drive — the shared folder between your phone's storage and the container. Never on C:, which belongs to the container's system.

How do I mount an ISO in Winlator?

Copy the ISO to the D: drive folder, then mount it through the container's drive options — or extract the ISO on your PC first and copy the extracted files over, which avoids mounting entirely.

How do I open EXE files in Winlator?

Launch the container, open its file explorer, browse to the D: drive, and double-tap the EXE — exactly like opening a program on Windows.

Why does my game show a black screen on first launch?

Most commonly a graphics driver or DX wrapper mismatch. Try the other driver options and DX wrappers in the container settings, one at a time. The troubleshooting guides cover this in depth.

Do I need one container per game?

Strongly recommended. Per-game containers keep settings isolated so one game's configuration can never break another's.

Can I copy a game folder directly from my PC?

Yes — that's one of the most reliable methods. Copy the installed game folder to the D: drive and run its EXE inside the container. DRM-free games (like GOG releases) work best this way.

Can I back up my Winlator containers?

Partially. A container is just a folder inside Winlator's app data, so the files can be copied — but Android restricts access to other apps' private folders, so you'll need a file manager with full storage access. The practical backup that matters most is your saves: copy save folders to the D: drive (which lands in your Downloads, outside the container) and from there to cloud storage. If you ever reinstall Winlator, containers start from zero.

How do I completely remove a game?

The clean way is deleting its container — that removes the game, its settings, and its virtual Windows environment in one move. If you want to keep the container, uninstall the game from inside it (use the game's uninstaller or just delete its folder). Either way, there's no recycle bin: it's just gone.

Why does Winlator ask to install Wine Mono or Gecko?

These are normal Wine components that some Windows programs need — .NET-style runtime pieces and a browser engine that Wine implements itself. The prompt is expected, not a sign of malware. Allow the install and let it finish; blocking it is a common cause of programs that silently fail to start.

Can I use Winlator without an internet connection?

Yes. Once the app is installed and your game files are on the device, everything runs locally — no connection needed to play. You only need internet for the one-time APK download, for getting game files in the first place, and for account-based steps like the first Steam login if you run Steam inside a container.

Last updated: 2026-10-05