Overview of debugging tools

This guide will give you an overview of the available debugging tools in the engine.

Godot comes with a powerful debugger and profilers to track down bugs, inspect your game at runtime, monitor essential metrics, and measure performances. It also offers options to visualize collision boxes and navigation polygons in the running game.

Finally, you have options to debug the game running on a remote device and to reload changes to your scenes or your code while the game is running.

Panel del Depurador

Many of Godot's debugging tools are part of the Debugger panel, which you can find information about in Panel del depurador.

Menú de opciones de depuración

There are a few common debug options you can toggle on or off when running your game in the editor, which can help you in debugging your game.

You can find these options in the Debug editor menu.


Here are the descriptions of the options:

Exportar con Depuración Remota

Al exportar y publicar, el ejecutable resultante intentará conectarse a la IP de tu computadora para ser depurado.

Exportación Mini con Recursos en Red

This option speeds up testing for games with a large footprint on remote devices.

When Small Deploy with Network FS is on, instead of exporting the full game, deploying the game builds a minimal executable. The editor then provides files from the project over the network.

Also, on Android, the game is deployed using the USB cable to speed up deployment.

Ver Formas de Colisión

This option makes collision shapes and raycast nodes visible in the running game.

Navegación Visible

Navigation meshes and polygons will be visible on the running game.

Sincronizar cambios de escena

With this option, any change you make to a scene in the editor at runtime appears instantly. When used remotely on a device, this is more efficient with the network filesystem.

Sincronizar Cambios en Scripts

Any script that is saved will be reloaded on the running game. When used remotely on a device, this is more efficient with the network filesystem.

Script editor debug tools and options

The script editor has its own set of debug tools for use with breakpoints and two options. The breakpoint tools can also be found in the Debugger tab of the debugger.


The Break button causes a break in the script like a breakpoint would. Continue makes the game continue after pausing at a breakpoint. Step Over goes to the next line of code, and Step Into goes into a function if possible. Otherwise, it does the same thing as Step Over.

The Keep Debugger Open option keeps the debugger open after a scene has been closed. And the Debug with External Editor option lets you debug your game with an external editor.


Breakpoints won't break on code if it's running in a thread. This is a current limitation of the GDScript debugger.

Configuración de depuración en el proyecto

In the project settings, there is a Debug category with three subcategories which control different things.


These are some general settings such as printing the current FPS to the Output panel, the maximum amount of functions when profiling and others.


These settings allow you to toggle specific GDScript warnings, such as for unused variables. You can also turn off warnings completely.


Shapes are where you can adjust the color of shapes that only appear for debugging purposes, such as collision and navigation shapes.

Remoto en el panel de escenas

Al ejecutar el juego, en el editor aparecerán dos opciones en la parte superior del panel Escenas, Remoto y Local. Mientras uses Remoto puedes inspeccionar o cambiar los parámetros de los nodos del juego en ejecución.



Some editor settings related to debugging can be found inside the Editor Settings, under the Network > Debug and Debugger sections.