Quake II in browser

Game files

No game files requested at checked entry

Controls

Controls not confirmed

Account

No sign-in in checked entry

Mobile gameplay

Not tested

Full session

Not tested

HTTP link check

HTTP 200; 0 redirects (2026-10-15)

Basis: project instructions and limited desktop entry observation. Observations: Oct 15, 2026. Conditions organized: October 15, 2026.

A guest-name path loaded a first-person scene and Escape menu without sign-in or user-supplied files. Movement, aiming, saving, mobile play and a full match were not verified.

Project type: Browser port

The original entry identifies an unofficial Quake II browser project and credits FTE QuakeWorld. A scene and Escape menu were observed; this does not verify distribution rights or a full session.

Classification organized October 15, 2026 from the recorded source and check notes; not a new gameplay test.

This Quake II browser guide covers the particular project at q2.pieter.com, not every Quake-branded website or a downloadable edition. We followed the original entry through its player-name form and into its browser client. The page identifies an unofficial preservation effort and credits its operator and engine. Those credits identify the project we inspected; they do not establish publisher approval, the rights to distribute every asset, or reliable access on another device.

The guide was published on October 15, 2026, after a limited desktop observation. That is our check and publication date, not the first release date of this browser adaptation. A separate third-party reference helped locate the destination, but the facts below come from opening this entry ourselves. Neither a reference list nor the original game's age establishes when this particular web build appeared.

Guide published 2026-10-15. Source reviewed 2026-10-15. Author release-page publication: Not established. The checked entry did not provide a verified original browser-release date.

Game files

The checked route did not ask us to select a local installation, upload a disc image or provide an owned game folder. After Play, a loader displayed a total of 77.5 MB and named q2dm.pk3 during progress. That is an observed interface value, not a measured whole-session transfer or an assertion about the data's license. The distinction from WebXash is practical: we did not supply a game folder here, whereas WebXash explicitly asks for owned files. We do not host, extract or redistribute this project's data.

Controls

Escape opened a visible menu containing Multiplayer, Options, Video and Quit. This confirms one menu response after a scene appeared. It does not confirm walking, mouse look, firing, a particular movement layout or remapping. We did not use the original PC game's bindings as evidence for this browser adaptation. The directory therefore keeps gameplay controls unconfirmed rather than placing this entry in a confirmed keyboard or keyboard-and-mouse filter. Read the actual client's current settings before assuming a control scheme.

Account

We supplied an invented display name, TabGuideCheck, in the visible player-name field. That field did not request an email, password, payment or account registration, and the checked path reached a scene without those steps. An anonymous display name is not a persistent profile or proof that every server feature is anonymous. We did not inspect profile recovery, statistics ownership, private-server access or moderation settings. The account label applies only to the observed entry, not every future service linked by the operator.

Mobile gameplay

We used a desktop browser and did not test a phone, touch gestures, a mobile controller or rotation. A first-person scene on desktop is not evidence that the same path is usable on a touch screen. We also did not compare browsers or graphics hardware. The fact that this directory fits a small screen should not be mistaken for a compatibility badge for the external game. Use the original project's current guidance, and treat mobile performance and input as separate checks that remain open.

Full session

A first-person scene, weapon view and scoreboard appeared after loading, followed by the Escape menu response. We did not finish a match, verify a scoring event, test a map transition, confirm movement or establish a reproducible respawn path. Visible other-player information is a scene observation, not an independently audited player count. The screenshot on this guide deliberately shows the entry form rather than presenting an uncompleted match as a finished result. Sustained performance, repeated joins and later session recovery were not tested.

HTTP link check

An independent request to the root project URL returned HTTP 200 without a redirect on October 15, 2026. This request was separate from the browser path that loaded the client. A good root-page response cannot establish the condition of every asset, the game server, another route or a future connection. If a later attempt stops in the loader, distinguish that stage from the initial website request. Do not infer a universal outage or guaranteed availability from either one failed visit or this successful historical check.

Our observed order was player-name entry, Play, asset progress, a rendered scene, then an Escape menu. Each stage answers a different question. The entry form identifies the project; loading shows that the client requested data; the scene is stronger evidence than a static landing page; a single menu response remains narrower than verified gameplay. If your visit stops earlier, use that exact stage when reading the author's support information. Avoid treating another Quake project's instructions as interchangeable simply because the names or menus look familiar. No installer, launcher, account creation, notification permission or optional radio playback was needed for our recorded path.