Quick summary
Apex Grand Prix is a full race weekend in a browser tab. Twenty cars line up on a five-kilometre permanent road course with sixteen named corners, three DRS zones and a pit lane that works; you qualify nothing and start anyway, and the field races you properly. Underneath the broadcast overlay — position tower, sector timing, delta, tyre temperatures, battery — is a real vehicle model: a fixed 240 Hz physics step running behind an accumulator, per-wheel load transfer, tyres that heat and wear, and driver aids you can switch off one at a time until the car is genuinely yours to lose.
Who this template is for
Apex Grand Prix is a racing simulation that happens to run in a browser tab. It is for people who want proof that the web can carry a real vehicle model and a full television presentation, not a car sliding along a ribbon of road.
- Studios and agencies who need a genuinely playable set piece in the portfolio — one that stands up to being driven, not just screenshotted
- Developers studying a real-time vehicle model — fixed-step physics, load transfer, a tyre curve with heat and wear — wired to a renderer rather than sitting in a notebook
- Brands who want a branded circuit or a liveried car that opens from a link, with nothing to install and nothing to license
What problem this template solves
Most “browser game” offerings are either heavy engine exports or toy demos that fall apart the moment you look under the hood. This build is neither.
- Engine exports ship megabytes of runtime before the first frame ever draws
- Toy demos skip the hard parts — real collision, game states, difficulty curves and persistence
- Builders who want to learn from a finished game almost never get to see the instructions that produced it
What you get with this template
You get a full race weekend: a five-kilometre road course with sixteen corners, twenty cars running the same physics, a working pit lane and DRS, and a broadcast overlay reading from the model rather than approximating it.
- A vehicle model at a fixed 240 Hz behind an accumulator, so the car handles identically at any frame rate — with ABS, traction, stability, auto gears and two driving aids you can switch off one at a time
- A procedurally generated circuit: centreline to road mesh to kerbs, run-off, barriers, grandstands, crowd and trackside furniture, all derived so the whole track can be changed in one place
- A broadcast layer — position tower, sector timing, delta, tyre temperatures, battery, DRS and minimap — asserted against the model by a QA suite that drives a full five-lap race
Page sections overview
| Section | Purpose |
|---|---|
| Zero Binary Assets | Draw every texture and synthesise every sound at boot, so the build ships as code |
| Fixed-Step Vehicle Model | Make the car behave the same on every machine, then let the render catch up |
| A Field That Actually Races | Give nineteen rivals the same physics you drive, and no rails to hide behind |
| Broadcast Presentation | Build the television layer from the model, so the numbers on screen are the real ones |
| A Gate That Has To Pass | Hold the build to thirty-five suites and eleven measured image metrics |
Design & branding system
The art direction is a daylight television broadcast: neutral grade, long lenses, and a car that stays readable against a bright circuit.
- Cascaded shadow maps with a blocker-search softening pass — contact shadows tight under the floor, distant ones soft, so the car sits on the track instead of floating
- A camera director with television, chase, cockpit, halo and bonnet modes, framed the way a race broadcast frames a car rather than the way a game camera follows one
- Ten invented constructors with their own liveries, colours and three-letter codes, on an invented circuit — nothing on this grid is licensed from anybody
Mobile & speed optimization
The game targets desktop first — keyboard and mouse are the primary controls — while staying light enough to load instantly anywhere.
- No engine runtime and no asset downloads, so the whole game arrives in a handful of requests
- A capped frame delta keeps the simulation stable even when the browser tab stutters or loses focus
- The page stays lean: no frameworks, no trackers, nothing between the visitor and the game loop
How this template helps you convert
A playable game holds attention longer than any showreel. The page around it is structured to turn that attention into a next step.
- Visitors play immediately — no signup, download or install stands between them and the first round
- The finished build is fully inspectable, which turns curious players into builders who want the prompt behind it
- The one-time prompt unlock offers a concrete, low-friction next step while the session is still hot
Other information about this template
Apex Grand Prix is a simulation first and a showpiece second. A few notes before you build on it.
- Keyboard is all it needs — WASD or the arrow keys drive it, and the driving aids are tuned so a first-time player can complete a lap
- Everything ships as static files — vanilla ES modules on an import map, no bundler, no build step, no server
- The circuit, the car, the tyre model, the camera director and the post chain are separate systems meeting through one shared context, so any of them can be replaced without touching the others
- It is fill-rate bound rather than CPU bound: the quality row moves the framebuffer, which is the lever that actually buys frames on a slower machine
How it works
Vanilla ES modules on an import map. No engine, no bundler, no build step — and no binary assets at all: every texture on the circuit is drawn procedurally at boot with Canvas2D and noise, and every sound is synthesised in WebAudio. The car, the sky, the tyre model, the camera director and the post chain are separate systems that only meet through one shared context object. The cinematic look is a real post stack — cascaded shadow maps with a PCSS softening pass, ambient occlusion, motion blur, depth of field, bloom and a graded display transform — and every screenshot on this page is reproducible from the build’s own QA harness, which gates thirty-five suites and eleven visual metrics before anything ships.
Screenshots
Captured from the live build — the title screen and real play, level by level.
