How the editor works
Everything runs in this tab. There is no install, no import step and no project file to configure. This page walks through the screen once, from opening it to sending someone a link.
Open the editor
/new gives you an empty project with a main.gd already attached to the scene root, running Godot 4.7 stable. It starts playing by itself, so what you see on the right is your project already running.
If you would rather read something that already works, the 133 examples open in this same editor. An example is copied into your browser when you open it, so editing one touches only your copy and reloading the page writes the original files back.
Write the code
The panel on the left is the code editor. Typing is all you need to do: the script is checked and saved on its own a moment after you stop, with no save button anywhere.
If the script does not compile, the error lands on the offending line, in red, with the message from the engine. Completion for the Godot API comes as you type.
Add scripts and shaders
The + above the list creates a file. Pick Script or Shader, type a name without the extension, and it shows up under Scripts or Shaders. The trash icon next to it deletes the selected file, and main.gd cannot be deleted.
Only main.gd is attached to a node. Everything else you reach from code: Get.script('player') and Get.shader('water'), both without the extension.
Read the screen
The bar floating under the viewport is where the project itself is controlled.
+ and deletes it with the trash. The default scene stays.print() calls, and the red one counts errors. Clicking either opens the output panel.Move the camera
Hold the middle mouse button to orbit the editor camera, and hold shift with it to pan. The scroll wheel zooms. This moves the editor view, not the camera inside your game, so it never changes what a player would see.
The Code button in the top bar hides the code panel when you want the viewport wider.
Take the project with you
scenes, scripts and shaders, which is a Godot project you can open on the desktop.Your project lives in this browser, not on a server, so it survives a refresh but goes away if you clear the site data. The ZIP is the copy that does not depend on that.
What the browser cannot do
Godot on the web renders through WebGL 2, which is the Compatibility renderer. Screen space reflections, VoxelGI, SDFGI, volumetric fog, decals, depth of field and compute shaders are not available there, no matter what the project settings say.
One that surprises people: GPUParticles does not draw. Use CPUParticles2D and CPUParticles3D, which is what every example in the catalog does.
There is also no asset import, so images, audio and models have to be generated in code, with FastNoiseLite, Image, GradientTexture2D or AudioStreamGenerator.