How WebArcade works
A practical reference for accounts, progress, multiplayer, privacy, browser support, fair play, and recovery when something goes wrong.
Accounts and sign-in
You can browse the catalogue and play local games without an account. Signing in adds profile synchronization, achievements, social tools, support tickets, and eligible leaderboard saving. Login accepts either the account email or the reserved username. Firebase Authentication verifies credentials; WebArcade's backend then checks account status and MFA before creating a secure session.
If MFA is enabled, password acceptance is not the end of login. Enter the one-time code sent to the account email. Never share passwords, codes, reset links, or session cookies with support.
XP and levels
XP is calculated from bounded best scores across 2048, Flappy, Solitaire, Pong, Snake, Tetris, Ludo, and Minesweeper, plus completed games and recorded wins. Level thresholds use the square of the level multiplied by 100. Visible levels run from 1 to 100.
Titles progress from New Player through Rising Challenger, Ranked Competitor, Arcade Veteran, Elite Player, and Arcade Legend. The backend calculates signed-in progression. Guest previews use the same formula locally but are not an account record.
Leaderboards and fair play
Eligible best scores are bounded, stored by the backend, and displayed with public profile settings. The games themselves run in the browser, so local-game scores are client-authoritative and should not be described as independently verified. WebArcade may hide or remove obviously manipulated entries.
Do not automate input, alter requests, impersonate another player, exploit room state, or interfere with availability. Report suspicious behavior through Support instead of testing it against the live service.
Multiplayer
UNO uses private six-digit room codes and backend transactions. Opponents receive card counts, not hidden hands or the deck. Pong uses Firebase Realtime Database for authenticated signaling and then a browser peer connection, with the host running match physics.
Room codes are temporary. After a release or a long disconnect, create a new room rather than reusing an old code. Corporate, school, VPN, and filtered mobile networks may block peer connectivity even when the website loads.
Browser and device compatibility
Use a current Chrome, Edge, Firefox, or Safari release with JavaScript, local storage, and first-party cookies enabled. Desktop keyboard and pointer controls are supported where the game uses them; touch games provide buttons, tap, long-press, or swipe alternatives.
Browser zoom is supported. Portrait is usually best for boards on phones, while Pong and some wide layouts benefit from landscape. Reduced-motion, increased-contrast, and reduced-transparency preferences are respected by shared interface components.
Privacy and deletion
Profile settings control public profile and stats visibility where available. Use account settings to clear game data, clear activity history, deactivate, or permanently delete an account. Sensitive actions can require a recent sign-in. Manual help is available from the public Support page.
Read the Privacy Policy for provider, retention, advertising-preparation, and deletion details.
Offline, slow, or failed requests
- Wait for the current progress indicator to finish; repeated clicks can create conflicting requests.
- Confirm the device is online and its clock is correct.
- Reload once. Local games may continue offline, but profile and multiplayer actions require the backend.
- Sign out and back in if the session-expired state appears.
- Use the displayed request ID when Support asks for diagnostic context.
Release notes
August 20, 2026: gameplay persistence moved to an authenticated backend transaction with duplicate-result receipts; runtime configuration was pinned to Node 22; game guides, environment checks, indexes, operational runbooks, and policy-safe advertising placement were prepared.
Earlier work added server-authoritative UNO rooms, complete XP/level calculations, consolidated social/catalog requests, bounded provider timeouts, improved mobile layouts, and shared loading and recovery states.
Still need help?
Browse the game-specific guides for exact controls and rules. For account access, bugs, privacy requests, or a problem that persists after retrying, open the public Support page. Include what you were doing, the page, browser, approximate time, and any request ID. Do not include credentials or one-time codes.