Winlator controls: the complete input and controller setup guide

Published by WinlatorAPK, an independent guide site run by Android emulation enthusiasts. We are not affiliated with brunodev85 or the Winlator project. More about us.

Most "controls not working" complaints in Winlator come down to one thing: the input mode. Simulate Touch Screen turns your finger into a mouse, right for point-and-click games, strategy, and RPGs. Emulate Controller turns the touchscreen into a virtual Xbox-style gamepad, right for anything with controller support. Match the mode to the game and most inputs just work.

If Winlator isn't installed yet, the setup guide gets you there first.

The three input modes

Winlator's input system revolves around modes that change what your touchscreen does inside the container. Understand these and everything else falls into place:

You switch modes in Winlator's input settings. The golden rule: a game with gamepad support wants Emulate Controller; a point-and-click adventure wants Simulate Touch Screen. Match the mode to the game first, then fine-tune everything else. Skipping this step is how you get an hour of "why is my touch doing the wrong thing."

Touchscreen gestures and right-click

In Simulate Touch Screen mode, your finger is the mouse. The gestures you need:

This works well for slower-paced games: RPGs, turn-based strategy, point-and-click adventures, visual novels. It takes a few minutes to get used to, and then it feels natural. For anything fast or precise, move on to the virtual gamepad or a physical controller. Touch-as-mouse was never going to carry you through a shooter.

The on-screen keyboard

Windows games love keyboard input, and Winlator includes an on-screen keyboard you summon inside the container. Look for the keyboard toggle in Winlator's in-container toolbar or overlay. Tapping it brings up an Android keyboard that types into the Windows program.

It's fine for entering names, passwords, chat messages, and the occasional console command. It's miserable for real-time gaming. You can't hold W to move while a keyboard covers half the screen and your thumbs have nowhere to go. For games that need constant keyboard input, map the important keys onto the virtual gamepad (below) or connect a physical keyboard.

If the keyboard doesn't appear when you expect it, check that you're tapping the toggle rather than waiting for it to auto-appear. Winlator doesn't always summon it automatically the way Android apps do. The toggle is the reliable path.

Setting up the virtual gamepad

The virtual gamepad is Winlator's best answer to touch gaming: an on-screen controller overlay whose buttons you map to keyboard keys, mouse actions, or gamepad inputs. Here's the setup:

  1. Switch the input mode to Emulate Controller in Winlator's input settings. This tells Windows programs that an XInput gamepad is connected.
  2. Open the gamepad layout editor from the input controls screen. You'll see a default overlay: analog stick, face buttons, triggers, D-pad.
  3. Map each on-screen button. Tap a button in the editor and assign it: a keyboard key (W, Space, E), a mouse button, or a gamepad button. For a shooter, map the left side to WASD-style movement, the right side to mouse-look, and the buttons to click, reload, and jump.
  4. Position and resize everything. Drag buttons to where your thumbs naturally rest. Bigger buttons for actions you hit constantly, smaller ones for menus. This matters more than people expect. A well-placed layout plays dramatically better than the default.
  5. Save the profile. Winlator supports input profiles, so keep one layout for shooters, one for racing games, one for RPGs, and switch between them instead of rebuilding from scratch every time.

Spend ten minutes building a proper layout per genre instead of fighting the default in every game. The default is a starting point, not a finished product. Community members share profiles for popular games and handhelds, which can save you the initial setup, but you'll still want to adjust for your own thumbs.

Mapping philosophy: frequency over logic

Map by frequency, not by logic. The buttons your thumbs hit every second (move, look, primary action) get the biggest, most comfortable positions. Menu keys and once-per-hour actions get tucked into corners. For shooters, mouse-look on the right side with a generous area beats a cramped "accurate" layout every time. And don't map everything. A clean layout with eight well-placed buttons plays better than sixteen cramped ones.

XInput vs DInput: why some games ignore your controller

Windows games talk to controllers through two old APIs, and which one a game listens to decides whether your input registers:

If a game doesn't respond to the virtual gamepad or a physical controller in Emulate Controller mode, the game might be DInput-only. Older titles are the usual suspects. Workarounds the community uses: mapping the controller to keyboard keys instead (the game definitely listens to the keyboard), or checking whether the game has a setting to switch its input API. When a controller "doesn't work" in exactly one old game but works everywhere else, DInput is the first suspect.

USB and Bluetooth controllers, mice, and keyboards

Physical peripherals work, and for longer sessions they're worth it.

Controllers: connect over Bluetooth or USB (a USB-C OTG adapter works for wired controllers). Put Winlator in Emulate Controller mode so the game sees an XInput device. Most standard controllers (Xbox, PlayStation, generic Bluetooth pads) are picked up. If a controller pairs with Android fine but does nothing in the game, check the input mode first, then check whether the game is DInput-only (above).

Mice: a USB or Bluetooth mouse works for games that want real mouse input: strategy games, shooters, anything with precise aiming. This is the single biggest upgrade for FPS mouse-look on Winlator. Touch-based mouse-look is a compromise; a real mouse is not.

Keyboards: USB or Bluetooth keyboards work for games with heavy keyboard input. MMOs, strategy games, anything with hotkeys. Pair it, and the game receives keystrokes like a PC.

On a handheld built for gaming, like the ones in the device buying guide, the built-in physical controls can replace the virtual gamepad entirely. That's one of the reasons handhelds punch above their weight for Winlator: no overlay needed, no screen space lost.

One practical note: Android handles the Bluetooth pairing, not Winlator. Pair the device in Android's settings first, confirm it works in an Android app, then open Winlator. Debugging pairing inside the container is backwards.

Mouse not working? Fix checklist

When the mouse does nothing or behaves strangely, work through these:

  1. Check the input mode. In Simulate Touch Screen mode your finger is the mouse. In Emulate Controller mode the game expects a gamepad. A "dead mouse" is often just the wrong mode for what you're trying to do.
  2. For physical mice: confirm Android sees the mouse (test the cursor in an Android app). If Android doesn't see it, Winlator won't either.
  3. For FPS mouse-look: some games need the mouse captured by the game window. Click inside the game window first. If the cursor escapes to the container desktop, the game isn't capturing it.
  4. Check the game's own settings. Some games have a "controller enabled" option that hijacks input, or need mouse-look explicitly enabled. An input that works in menus but not in gameplay is usually a game setting.
  5. Restart the container. Input devices are enumerated when the container starts. A controller connected after launch sometimes isn't picked up until the container restarts.

If none of that helps and the input problem comes with crashes or error dialogs, it's probably not an input problem at all. The troubleshooting guide covers the deeper failures that disguise themselves as dead controls.

Per-game control profiles

Save a profile per game, not per genre, once you have a layout you like. Winlator's profile system exists for exactly this: your shooter layout for one game has different key bindings than your shooter layout for another. Name profiles after the game. Future you, opening Winlator after a month away, will be grateful.

Community-shared profiles are a good starting point, especially for popular handhelds where players pass layouts around. Treat them as starting points. Nobody else has your thumbs.

Frequently Asked Questions

How do I right-click in Winlator?

In Simulate Touch Screen input mode, right-click is a gesture: long-press or two-finger tap. Your finger acts as the mouse in this mode, so single tap is left click and the long press or two-finger tap is right click. If gestures aren't registering as clicks, check that you're in Simulate Touch Screen mode and not Emulate Controller mode.

Why is my controller not working in Winlator?

The most common cause is the wrong input mode: switch to Emulate Controller so the game sees an XInput device. Next suspects: the controller isn't paired in Android's settings, so pair it there first. Or the container was started before the controller connected, in which case restart the container. The third suspect is a game that only listens to the older DInput API: map the controller to keyboard keys instead. Test the controller in an Android app first to confirm the pairing itself is fine.

Why is my mouse not working in Winlator?

Check the input mode first: in Emulate Controller mode the game expects a gamepad, not a mouse. For a physical mouse, confirm Android recognizes it outside Winlator. For in-game mouse-look, click inside the game window so the game captures the cursor, and check the game's settings for controller or mouse-look options that might be overriding it.

Can I use a keyboard and mouse with Winlator?

Yes. USB (via OTG adapter) and Bluetooth keyboards and mice pair through Android's settings and work inside containers. A real mouse is the biggest upgrade available for shooters and strategy games. Pair and test in Android first, then open Winlator.

What is the difference between Simulate Touch Screen and Emulate Controller?

Simulate Touch Screen turns your finger into a mouse: taps are clicks, for point-and-click games, strategy, and RPGs. Emulate Controller turns the touchscreen into a virtual Xbox-style gamepad that Windows programs see as an XInput controller, for games with gamepad support. Match the mode to the game. Most input confusion is just the wrong mode.

Do I need to remap controls for every game?

You should save one input profile per game once you have a layout you like. Games have different key bindings, so a shared genre layout only gets you partway. Building the layout takes about ten minutes per game, and community-shared profiles for popular titles can give you a head start.

Last updated: 2026-10-09