Play Web Dashers

Web Dashers controls: keys, tap and jump timing

Web Dashers has exactly one control, and the whole game is built on how well you time it. This page is the long version of the quickstart on the home page: every input the game accepts, what the jump actually does, why some deaths are your timing and some are the browser, and an order that gets you through the main levels.

Web Dashers controls at a glance

Input What it does Notes
Space, W or Up arrow Jump Hold it longer and the jump goes higher; release early and you land sooner
Left click Jump Works anywhere on the game picture, not just on the cube
Tap Jump Fullscreen first on a phone, so the browser bar does not steal the tap
In-game menu buttons Pause, restart, editor Use the game's own menu, not the browser back button

Keyboard controls in detail

Your cube runs on its own at a fixed speed. You never steer it, you cannot slow it down, and there is no second button to learn. Every decision you make is when to leave the ground.

Two things trip people up in the first minute. The first is focus: a browser game lives inside a frame, and until you click once inside that frame your keystrokes go to the page instead of the game. If space does nothing, click the game picture and try again. The second is key repeat: holding the jump key is supposed to extend the jump, not produce a stream of jumps, so you do not need to lift and re-press to keep hopping.

Laptop keyboards with shallow travel are fine. What matters is that the key is registered at the moment you press it, which is why playing on a keyboard that is also running a video call or a heavy page can feel unresponsive.

Mouse and trackpad controls

The mouse is the same control as the keyboard: a click anywhere in the game picture jumps. That makes one-handed play possible, and it is the easier option if your keyboard has a sticky space bar.

A trackpad works too, but tapping a trackpad adds a fraction of a second that you will feel on the tightest jumps. If you are stuck on one section, switch to a real key before deciding the level is impossible.

Touch controls on phone and tablet

On a phone the game is tap to jump, and it plays better than the keyboard-first design would suggest — it was built for keys, but the input is a single tap, so nothing is lost in translation.

Three things make mobile bearable. Tap the fullscreen button next to the game first, because a browser bar eats a big slice of a small screen. Keep your thumb on the game area rather than the edge of the screen. And expect the tightest jumps to be harder than on a keyboard: holding a thumb perfectly still for a high jump is a real skill, and a paired Bluetooth keyboard is the straight answer on hard levels.

What the jump actually does

The jump has a fixed height, and holding the key extends it only while the cube is still rising. On a low platform the difference is invisible; on a tall obstacle it is the difference between clearing it and not. Landing on a flat surface resets the jump immediately, so a fast chain of taps is a fast chain of hops.

The failure everyone hits first is panic tapping. You land, you tap twice out of nerves, and the second tap sends you into the next spike. If a section keeps killing you, count the beat out loud — the obstacles are placed on the music, and the track is a timing sheet you can hear.

What ends a run, and what does not

Touching a spike, a saw, a wall or the top of the screen ends the attempt. A death in a main level restarts the level from the beginning unless you are in practice mode. Falling into a gap counts as a death; standing still does not, because you cannot stand still.

Practice mode and checkpoints

Practice mode drops checkpoints so you can repeat one hard stretch instead of the whole stage. It is an early version in Web Dashers, but it is the difference between learning a section and quitting on it. The habit that works: run the same fifteen seconds six times in practice, then run the level from the start once. Do not leave practice and immediately expect the full run to feel the same — the beginning will now be boring, which is exactly when people lose focus and die there.

An order that works for learning the controls

  1. Clear the first main level without rushing. You are learning the relationship between the music and the jumps, not the layout.
  2. Play with the sound on. Muted play is possible, but the beat is the timing guide and you are making it harder for yourself.
  3. Break the hard part into pieces. Practice mode, same stretch, six attempts, then the full run.
  4. Change one thing at a time. If you keep dying at the same jump, vary when you press, not how hard.
  5. Only then open the level editor. Building a short level teaches you what is actually fair to expect from a player.

When the controls stop responding

If the cube moves but jumps do nothing, it is focus — click the game picture. If nothing moves at all, the game did not load; the loading fixes page covers the four usual causes. If the jump fires late, an extension or an ad-blocker that filters scripts on the page is the next thing to check, followed by the browser itself.

Web Dashers controls questions

Can I use a controller?

No official controller support is documented by the project. Keyboard, mouse and touch are the supported inputs.

Why does holding the key jump higher sometimes and not other times?

Because the jump only extends while the cube is still rising and the ground is far enough below. On a low platform it looks identical; on a high jump the difference is obvious.

Does the game run better in fullscreen?

Yes on phones, where browser bars take a big slice of a small screen. On desktop it is mostly a comfort thing.

Is there a way to slow the game down?

No. There is no slow-motion setting in Web Dashers, and practice mode is the built-in way to make a hard section learnable.

What is the difference between a tap and a hold?

A tap gives you the base jump. A hold gives you the same jump with more height, as long as you keep the key down while the cube is rising.