Urban Terror in browser

Game files

No own-file request before asset download

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.

An invented display name and Play started a loader without account registration or own-file upload. The loader displayed 1424.9 MB total; we stopped before completion. No scene, gameplay controls, cache persistence or match was verified.

Project type: Browser port

The original entry explicitly identifies Urban Terror and ioUrbanTerror compiled to WebAssembly, not Unreal Tournament. An asset loader was observed; gameplay was not reached.

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

This Urban Terror browser guide covers ut.pieter.com, whose original page explicitly identifies Urban Terror and credits FrozenSand and ioUrbanTerror compiled to WebAssembly. The abbreviated UT destination had been ambiguous in a secondary discovery list. Opening the source resolves that identity: this entry is not Unreal Tournament. We use the original project's name rather than treating two different games as interchangeable because of a shared abbreviation.

The source describes an unofficial, non-commercial preservation project and recommends desktop Chrome. Our October 15, 2026 check went beyond the landing page into the asset loader but stopped before its large download completed. That is a download-entry observation, not a scene or gameplay check. The date belongs to our visit and guide publication; we did not establish the adaptation's first release date, publisher endorsement or an independently audited license for the resources distributed by the external host.

Guide published 2026-10-15. Source reviewed 2026-10-15. Author release-page publication: Not established. The checked landing page did not establish this browser adaptation's original publication date.

Game files

The landing page warned that game data would download on first load and be cached afterward. After an invented display name and Play, the client showed Initializing and Preparing downloads, then Downloading game data and the filename zUrT43_001.pk3. One observed progress state read 57.6 MB / 1424.9 MB. We stopped before completion rather than claiming the whole package was downloaded. The displayed total is a loader value, not our measured transfer, a fixed future size or a guarantee about later network activity. No own-file upload appeared before that point; this directory supplies none of the external assets.

Controls

The display-name field accepted text and the Play button opened the loader. We did not reach a playable scene, capture the mouse or test movement, aiming, firing, jumping, team selection, remapping or controller input. Familiar first-person controls from the desktop game or another pieter.com project are not evidence for this browser client. The gameplay input filter remains unknown. Reading the source's desktop recommendation is useful preparation, but it is not a control test or proof that a particular browser and keyboard combination will operate the game successfully.

Account

We used the invented display name TabGuideCheck without entering personal information, a password or payment details. No account-registration step appeared before the asset loader. This supports the limited statement that the checked entry did not request an account, not that all multiplayer features or later server access are anonymous. We did not finish joining, reserve a name, inspect profile persistence, contact players or enable notifications. A name shown in an entry form should not be treated as a permanent account, and a server's later requirements remain outside this observation.

Mobile gameplay

Not tested. The source recommends a desktop browser and specifically Chrome; we did not compare browsers or complete a Chrome gameplay session. We also did not open the external client on a phone, use touch controls, pair a gamepad or test screen rotation. The size shown by the asset loader is worth reading before starting on any connection, especially a metered one. Neither a phone displaying the landing page nor a directory page fitting a narrow screen establishes that the game's transfer, graphics, storage and first-person input work there.

Full session

No playable scene or server session was reached during the check. We closed our test client while its asset download was still incomplete. We did not choose a team, spawn, move, score, complete a round, change maps or reconnect. The landing page also displayed player and map information, but those changing labels were not independently verified as active participants or a server we joined. The guide's public image uses the upper entry form and download warning, not another player's record or a scene falsely presented as our completed match.

HTTP link check

An independent request to ut.pieter.com's root returned HTTP 200 with zero redirects on October 15, 2026. Play later opened a /play route containing the invented display name; that user action is distinct from the root transport result. We do not publish a personalized play link or imply that the root response verifies all asset packages, the game server or uninterrupted availability. If your visit stops at initialization or an archive download, identify that exact state when consulting the original project. Our partial download is not evidence of either a universal outage or guaranteed gameplay.

This check is useful mainly for its setup boundary: the apparently simple name-and-Play entry can lead to a loader displaying roughly 1.4 GB, rather than a small instantly playable page. We did not establish a fixed download time, validate the displayed estimate or test whether interrupted data resumes. The source's cache statement was not verified by a second completed load, and this guide does not recommend clearing browser storage as a general repair. We stopped our test download without changing security settings or enabling permissions. The original page links FrozenSand and the official Urban Terror site and describes itself as unaffiliated with FrozenSand or id Software. Keep that disclosure separate from the question of whether this particular web client reaches a scene on your device.