See exactly what your players pressed, clicked, and steered while they played. Player input recording captures keyboard, mouse, and gamepad input during Windows playtests and shows it on top of the gameplay video, in sync with what's happening on screen.
Turn it on when you order
Player input recording is available for playtests where players play on Windows. Upload your Windows build or a browser build when setting up your playtest and then find Should we record player inputs? and check Enable Input Recording.
What we record
Keyboard: every key press and release, shown with the player's own keyboard layout. A French player's A key shows as A, not Q.
Mouse: the five standard mouse buttons and the scroll wheel.
Gamepads and joysticks: buttons, D-pad, shoulder buttons, stick positions, and stick clicks. Triggers show as pressed once they're pulled about halfway.
We don't record mouse movement or how hard a trigger is pulled.
Find player input in the video player
Open any video from a playtest with input recording enabled. Player input shows on top of the video by default. To change how it looks, click the keyboard icon next to the fullscreen button. This opens the Player input menu.
If a video has no keyboard icon, there's no input data for it. That can happen when the player didn't play on Windows or input recording wasn't turned on for the playtest.
Change how player input looks
In the Player input menu you can:
Turn it on or off with the switch at the top.
Pick a display: Overlay or Panel. More on both below.
Move the overlay to any of the four corners under Position.
Show or hide devices: check or uncheck Keyboard, Mouse, and Gamepad. Devices the player never used are grayed out.
Every video opens with input on and the overlay in the bottom-left corner. The player doesn't remember your choices between videos.
Overlay
The overlay shows small labels in a corner of the video, one row per device: one for the keyboard, one for the mouse, and one for each gamepad. Each gamepad row starts with the controller's name.
A held key or button is purple.
After it's released, it fades to gray over one second.
The newest input appears first in each row.
Rows disappear when the device isn't being used.
A short label appears when a controller connects or disconnects.
Panel
The panel adds a strip below the video with a drawing of each device in use: a keyboard, a mouse, and a gamepad. Pressed controls light up, and sticks move with the player's thumbs.
Gamepad buttons use the labels for that brand: A/B/X/Y for Xbox, ✕/○/□/△ for PlayStation, and Nintendo's layout for Nintendo controllers. Other gamepads show unlabeled buttons.
Controls that aren't on the drawing, like extra keys or back paddles, show in an Other controls list beside it.
The keyboard caption shows the player's Windows input language, for example Keyboard (US). This is the language setting, not always the physical keyboard.
A device stays in the panel while it's in use and for 60 seconds after.
Click the arrow in the panel header to collapse it and give the space back to the video. A dot in the header lights up while the player is pressing something.
Both the overlay and the panel stay visible in fullscreen.
Download the raw data
Want to run your own analysis? Open the video's download menu and choose Download device input data (JSON). You get a JSON file with every recorded input and its timing, matched to the video.




