Start with the controls shown by the game
Our catalog contains different game engines and input designs. A puzzle may rely on selecting pieces, while another title expects a keyboard, a drag gesture, or an on-screen control. A browser edition does not automatically mean that every game works equally well on both touchscreens and desktop input devices.
Read the opening instructions, settings, or help screen inside the title before trying familiar shortcuts. If there are no instructions and you cannot establish how to start, report that as a usability problem. We do not publish a universal set of controls that would override a game's own design.
If the keyboard appears to do nothing
Click or tap inside the game area before pressing a movement key. The address bar, the catalog's search field, or another page control may otherwise receive that input. If arrow keys scroll the surrounding page, check that the game actually expects keyboard input and give its play area focus again.
Use the game's own pause control where available before switching tabs or changing the window size. A title can pause, keep running, or lose input when focus changes; the surrounding toolbar cannot guarantee one behaviour for all games. Avoid using browser shortcuts as guessed game commands, particularly shortcuts that close or reload the tab.
If touch targets or the playfield are cut off
Check whether the game's opening screen requests portrait or landscape orientation. If you rotate the device, wait for the layout to settle before dragging or tapping again. Browser bars and on-screen keyboards can reduce the available space, especially on a small screen.
Opening the direct player from the toolbar can help separate a layout problem in the embedded area from a problem in the title itself. It will not convert a keyboard-only game into a touch game. If the direct version is still unusable, include the orientation and the part of the screen that is cut off in your report.
Fullscreen and audio usually need an intentional action
Use an explicit fullscreen control inside a game when one is available. The catalog's arrow-out-of-a-square button opens a new tab; it is not a fullscreen button. Fullscreen availability depends on both browser support and the game offering that action, so its absence does not necessarily indicate a broken page.
For sound, first press the game's start or audio control, then check its mute setting and your device volume. Browsers can restrict media playback that begins before a user interacts with a page. Do not enable unexpected notifications, microphone access, or unrelated permissions merely to unmute a game.
Choose a check that matches the symptom
If the game has never reached an interactive screen, follow the loading guide. If it runs but shows different progress, read the saves guide before resetting anything. If it runs but a specific button or gesture fails, describe that action precisely: what you selected, what you expected, and what actually happened.
The browser check on our support page can show basic graphics support, whether this page can save a small setting, and the space available to the page. Those observations are useful context for an issue report, but they do not replace a title-specific compatibility test.
References and next steps
Game behaviour can vary by title and browser. If this guide no longer matches what you see, send a correction or issue report. See our editorial approach for the scope of this guidance.