Play Web Dashers

Web Dashers level editor: build your own level

The level editor is the newest and least finished corner of Web Dashers. This page covers what the editor can do today, how to open it, a build order that produces levels people actually finish, and the limits you will hit along the way. If you want one answer: it is worth your time for short levels, and it is not a replacement for the editor in the desktop Geometry Dash.

What the Web Dashers level editor can do right now

You get a grid, a selection of blocks and hazards, and a play button that runs what you just built. That is the whole core loop, and it works: place objects, run the level, fix what is unfair, repeat until the ending is reachable.

What you do not get yet is the deep side of the desktop editor. Deco tooling is missing, trigger systems are missing, and the object library is small. The project is still adding to it, so treat anything you build as something to keep short and to re-test after each game update. A level that plays cleanly today can break when the object set or the physics change.

The editor is also keyboard-and-mouse first. It loads on a phone with the rest of the game, but placing objects with a finger on a small screen is fiddly, and a long level is painful to repair that way.

How to open the level editor in Web Dashers

Start the game from the home page, let it load, then open the game's own menu and pick the editor entry. Everything happens inside the same frame: there is no separate editor page on this site and nothing to install.

Two practical notes from the way browser games behave:

If the editor entry does nothing at all, that is a loading problem rather than an editor problem. The loading fixes page walks through the four usual causes.

Placing your first objects

Start with the floor, then the path, then the hazards. Building it the other way around is how you end up with a level nobody can finish.

Blocks and the ground

Lay a continuous floor under the whole level before anything else. Gaps in the floor are the most common reason a test run dies in the first three seconds, and an accidental gap is hard to see once objects are stacked on top of it.

Spikes, saws and walls

Hazards go on the floor, and the height of the hazard decides the jump. A single spike on flat ground is a plain tap. Two spikes together want a jump you hold slightly longer. Three in a row, or a spike with a wall behind it, wants a rhythm rather than a reflex.

Place one hazard, test it, place the next. Testing after every two or three objects instead of building twenty and then pressing play is the single most useful habit in this editor.

Spacing obstacles to the beat of the track

Web Dashers is a rhythm platformer, so the distance between two obstacles matters more than the height of either one. If the player has to clear two jumps in the gap where the music gives them one beat, that section is unplayable however well it is built.

The practical rule: leave one empty stretch of floor after every hard pattern. That stretch is the recovery window, and it is what makes the next spike readable instead of cruel.

A build order that produces a level people finish

  1. Design eight seconds, not eighty. One idea, one obstacle pattern, one ending. A short level that is fun beats a long level that is almost finished.
  2. Build the first jump, then test immediately. Play it as someone who has never seen the layout, not as the person who placed every block. If you have to remember the layout to survive it, it is too tight.
  3. Leave a beat of empty space. One calm stretch after each hard pattern.
  4. Test with the sound off, then on. If the timing only works with the music, every player on a muted school laptop dies at the first spike.
  5. Raise the difficulty at the end, not the start. Players who die in the first two seconds never see the good part.
  6. Stop while it is still fun. Ten extra obstacles past the point where the idea is complete turn a good level into a chore.

Three level ideas you can build in one sitting

The eight second warm-up. Flat floor, four single spikes, generous gaps, then a short run to the finish. Build this one first: it teaches you how the editor grid maps to jump distance, which is the thing you cannot feel until you have tested it.

The rhythm staircase. Three jumps that each need a slightly longer hold, climbing onto three platforms, then a drop back to the floor with one spike in the landing zone. It looks impressive and it only uses blocks and spikes.

The fake-out corridor. A wide empty stretch that makes the player expect nothing, then one spike placed where the beat is obvious. Build the empty part first and test it. If the player cannot feel the beat in that stretch, the payoff does not land and the level reads as random.

Testing a level properly

Testing is not a single question of whether it plays. Run four separate checks:

That last check matters because the game keeps its data in your browser. Clearing the cache takes saved levels with it, and we hold no copy on this side.

Sharing a level and playing other people's levels

Once a level plays cleanly, save it. Web Dashers has an in-game search for levels that other players have published, and the same in-game system is where your level lives after it is uploaded. There is no upload form on this site and we do not host level files.

Online levels need a working connection to the game's own servers. The game reaches them through the project's proxy domains, and school and office filters sometimes block that whole pattern. The symptom is a main level that loads fine and an online search that comes back empty. That is a network block, not a broken level.

Because the editor is an early build, exact upload steps change between versions. If a button you expect is missing, the project's own GitHub page lists what the current version supports, and that is the only authoritative source.

Limits of the Web Dashers level editor

Common mistakes worth avoiding

Web Dashers level editor questions

Can I play a level I built without publishing it?

Yes. Testing is part of the editor loop: you build, you test, you build again, all inside the game.

Can I play other people's levels in the editor?

You can play them in the game through the in-game search. Treating someone else's level as a reference is the fastest way to learn what spacing works, but the editor does not give you their project file.

Will my level be lost if I clear my browser data?

Possibly. The game keeps level data in your browser and this site has no access to it. Note the layout down for anything you care about.

Do I need an account to use the level editor?

No. There is no sign-up on this site. Levels are saved and shared through the game itself.

Is the editor finished, or is it still being built?

Still being built. It is an early version with a basic tool set: blocks, hazards and a play test. Deco tools, triggers and a big object library are missing, and the project keeps adding to it.

Why is my saved level missing from the editor menu?

Usually one of two reasons: the browser cleared its storage, or a game update changed the save format. Try a reload first, then check the project's GitHub page for the current version notes.