Choose Step Over, Into or Out in the VS Code debugger

F10 steps over, F11 steps into and Shift-F11 steps out during a supported debugging session. The active debug configuration controls what is running.

Scope
Visual Studio Code · Current vendor documentation checked 3 November 2026; no running-app compatibility test is claimed.
Keyboard and customization
Documented Mac defaults; punctuation and function keys depend on keyboard layout and hardware.. User bindings, app versions, focused controls and installed extensions can change a command. Inspect the active app menu or its shortcut editor when a listed combination differs.
Review basis
Documentation reviewed 2026-11-03 by Codex — primary-documentation and editorial review; no hands-on runtime test. These bindings were not tested in a running app for this guide.

Confirm the paused program and frame

Stepping commands are meaningful inside an active debugging session, usually while execution is paused. Inspect the selected thread, stack frame and current line before advancing. A key label alone does not tell you which process is being debugged or whether the selected context is the one you intend to investigate.

Choose how much detail to follow

Step Over is useful when you want the next step in the current routine without following every called function. Step Into follows a call where the debugger can do so, while Step Out continues toward the caller. Debug adapters and language support can affect the exact movement and the available source information.

Use a safe program for learning

Practise stepping in a small local example that has no external side effects. Running or continuing a real program can write data or contact services. Inspect the configuration and breakpoints before starting, and do not treat stepping as a purely visual document-navigation command.

Documented commands for this workflow

Scroll the table sideways to see every column.

ActionKeysWhen to use it
Step overF10Advances within the active debugging workflow. ↗
Step intoF11Follows a call where the debug adapter supports it. ↗
Step outShift-F11Continues toward the calling context. ↗
Start or continue debuggingF5Can execute program code; verify the debug target first. ↗

Sources and corrections

Found a mismatch? Email pashaseenainc@gmail.com with your app version, macOS version, keyboard layout and the command. Please leave personal document names out.

Keep going

Right there when you need it.

Keep a compact shortcut reference in your Mac’s menu bar.

Explore the native Mac app