# Step through code

When the debugger is stopped at a breakpoint, you can step through it using four buttons in the {ref}`toolbar <debugger-ui-tour-toolbar>`:

```{image} breakpoint_toolbar.png
```

In order, the buttons are:

- Play: run to the next breakpoint
- Step over: advance to the next line in the same function.
- Step in: advance to the next line in the function, unless on a function call, in which case enter the function being called
- Step out: run to the end of the current function, in which case, the debugger will skip the return value from a function, returning execution to the caller

## Split console

When paused, you can press the Esc key to open and close the split console to gain more insight into errors and variables:

```{image} split_console.png
:class: border
```

## Paused overlay

When the page is paused, an overlay appears on the viewport of the tab you are debugging.

```{image} debugger-overlay.png
:class: border
```

This lets you know what kind of breakpoint the code is paused on (breakpoint, event breakpoint, etc.), and also provides a step button and a play button. The thinking here is that if you've got your DevTools open in a separate window, as many people do, it can be easier to have the buttons available right there to move the code forward while you are looking at the result.

Starting Firefox 142, this overlay can be disabled from the Debugger settings.

```{image} debugger-overlay-setting.png
:class: border
```

## Inline variable preview

The {ref}`source pane  <debugger-ui-tour-source-pane>` gives you an instant preview of the variables on each line of code you've stepped through. See {ref}`Set a breakpoint > Inline variable preview <debugger-how-to-set-a-breakpoint-variable-preview>` for more information.
