ctrl+shift+p filters: :st2 :st3 :win :osx :linux

Xdebug Client

by martomo ST2/ST3

Xdebug debugger client for Sublime Text 2 and 3

Labels php, xdebug



  • Total 98K
  • Win 51K
  • OS X 25K
  • Linux 22K
Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2 Mar 1 Feb 28 Feb 27 Feb 26 Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4
Windows 55 46 54 31 32 52 66 60 64 48 28 34 81 113 101 46 54 27 30 29 52 44 45 51 29 28 32 36 51 42 47 23 25 37 46 42 35 32 32 22 48 45 47 54 54 25
OS X 16 21 14 11 10 15 9 21 22 15 1 16 19 14 18 10 13 14 6 12 15 21 22 19 4 5 15 15 11 14 17 4 8 12 14 20 16 15 5 6 17 20 21 28 14 9
Linux 15 11 18 10 12 11 12 22 18 20 8 8 12 7 22 12 16 19 9 13 7 17 14 21 12 7 15 18 20 22 20 5 9 19 18 18 18 12 7 9 21 20 18 21 21 6




Xdebug debugger client integration for Sublime Text.


Based on the Xdebug protocol functionality in SublimeXdebug package by Kindari.

Build Status Package Control MIT License



  • Remote debugging by configuring path mapping
  • Navigate on breakpoint hit to relevant file on specific line, when found on local drive
  • Customizable debugging layout for displaying stack history and context variables with syntax
  • Overview of breakpoints in all files and disable/enable breakpoints with simple click
  • Evaluate code within the current execution context, by setting watch expressions
  • Inspect (nested) context variables
  • Works on both Sublime Text 2 and 3


Here is a complete list of commands you can find Command Palette under the Xdebug namespace or in the menu under Tools / Xdebug:

Start/Stop debugging session

  • Start Debugging - Ctrl+Shift+F9 or ⌘+Shift+F9
  • Start Debugging (Launch Browser)
  • Restart Session
  • Stop Debugging - Ctrl+Shift+F10 or ⌘+Shift+F10
  • Stop Debugging (Launch Browser)
  • Stop Debugging (Close Windows)

Launch Browser menu option will only show if you have an url configured within settings.


  • Add/Remove Breakpoint - Ctrl+F8 or ⌘+F8
  • Set Conditional Breakpoint - Shift+F8
  • Clear Breakpoints
  • Clear All Breakpoints

Watch expressions

  • Set Watch Expression
  • Edit Watch Expression
  • Remove Watch Expression
  • Clear Watch Expressions

Session commands

  • Evaluate
  • Execute
  • Status

Continuation commands

  • Run - Ctrl+Shift+F5 or ⌘+Shift+F5
  • Run To Line
  • Step Over - Ctrl+Shift+F6 or ⌘+Shift+F6
  • Step Into - Ctrl+Shift+F7 or ⌘+Shift+F7
  • Step Out - Ctrl+Shift+F8 or ⌘+Shift+F8
  • Stop
  • Detach


  • Restore Layout / Close Windows - Ctrl+Shift+F11 or ⌘+Shift+F11
  • Settings - Default
  • Settings - User


Package Control

Execute “Package Control: Install Package” in the Command Palette to retrieve a list of available packages. Search in the list and install package Xdebug Client.


Clone the repository by executing the following command in your Packages directory:

git clone https://github.com/martomo/SublimeTextXdebug.git "Xdebug Client"


Get the latest source from GitHub and extract the source into your Packages directory.

Note: You can locate your Packages directory in the menu under Preferences / Browse Packages...


In order to be able to debug your PHP scripts, you will need have Xdebug extension installed on your server. See here for installation instructions

Below is a configuration template for php.ini/xdebug.ini, be warned if you are on a Live environment, remote_connect_back allows every debug request from any source to be accepted.

zend_extension = /absolute/path/to/your/xdebug-extension.so
;zend_extension = "C:\Program Files (x86)\PHP\ext\php_xdebug.dll"
xdebug.remote_enable = 1
xdebug.remote_host = ""
xdebug.remote_port = 9000
xdebug.remote_handler = "dbgp"
xdebug.remote_mode = req
xdebug.remote_connect_back = 1

For details about all available settings for configuring Xdebug, see here.


The following settings can be configured in Xdebug.sublime-settings or in *.sublime-project files:

For remote debugging to resolve the file locations it is required to configure the path mapping with the server path as key and local path as value.

Determine which URL to launch in the default web browser when starting/stopping a session.

An IDE key is used to identify with debugger engine when Sublime Text will start or stop a debugging session.

This package does not filter sessions by IDE key, it will accept any IDE key, also ones that do not match this configured IDE key. It is merely used when launching the default web browser with the configured URL.

Host address of network interface which Sublime Text should listen to connect with debugger engine.

When specifying host address of network interface, be sure to specify an IPv4 address as Sublime Text will listen for connections through an IPv4 socket.

Which port number Sublime Text should listen to connect with debugger engine.

Maximum amount of array children and object's properties to return.

Maximum amount of variable data to initially retrieve.

Maximum amount of nested levels to retrieve of array elements and object properties.

Break at first line on session start, when debugger engine has connected.

Break on exceptions, suspend execution when the exception name matches an entry in this list value.

Always close debug windows and restore layout on session stop.

Show information about super globals in context view.

Display property by fullname in context view.

Do not show possible password values in context view.

Render evaluated result as parsed output instead of raw XML.

Always launch browser on session start/stop.

This will only work if you have the 'url' setting configured.

When launching browser on session stop do not execute script.

Do not use the debugging window layout.

Window layout that is being used when debugging.

Group and index positions for debug views.

Custom gutter icons for indicating current line or enabled/disabled breakpoints.

Do not use same icon for above values, because Sublime Text is unable to use the same icon for different scopes, in case there are duplicate icons detected it will fall back to the corresponding icon in the package.

Path to Python installation on your system.
Which is being used to load missing modules.

Show detailed log information about communication between debugger engine and Sublime Text.

Below are examples how to configure your Xdebug.sublime-settings and *.sublime-project files.


    "path_mapping": {
        "/absolute/path/to/file/on/server" : "/absolute/path/to/file/on/computer",
        "/var/www/htdocs/example/" : "C:/git/websites/example/"
    "url": "http://your.web.server/index.php",
    "super_globals": true,
    "close_on_stop": true


            "path": "..."
        "xdebug": {
            "path_mapping": {
                "/absolute/path/to/file/on/server" : "/absolute/path/to/file/on/computer",
                "/var/www/htdocs/example/" : "C:/git/websites/example/"
            "url": "http://your.web.server/index.php",
            "super_globals": true,
            "close_on_stop": true


Can I have both SublimeTextXdebug and SublimeXdebug installed?

No. Having installed both packages can cause conflicts, because they might both listen to the same port for a debugger engine response and have similar keymapping.

However (project) settings from SublimeXdebug are compatible with SublimeTextXdebug.

How can I start a debugging session?

SublimeTextXdebug can start or stop a debugging session by launching the default web browser with the configured URL and parameter XDEBUG_SESSION_START or XDEBUG_SESSION_STOP which uses the configured IDE key as value. By default the IDE key is sublime.xdebug.

When you do not configure the URL, the plugin will still listen for debugging connections from Xdebug, but you will need to trigger Xdebug for a remote session.

If you want to run a start a debugging session from command line, before you run your script, you will need to set the environment variable XDEBUG_CONFIG with the IDE key.


set XDEBUG_CONFIG="idekey=sublime.xdebug"
php myscript.php


export XDEBUG_CONFIG="idekey=sublime.xdebug"
php myscript.php

Make sure before defining the environment variable you have switched to the proper user environment.
As example you would set the environment variable as guest and execute the script as root (sudo), then root will not have the environment variable XDEBUGCONFIG that was defined by __guest_.

How do I set a breakpoint and/or watch expression?

With SublimeTextXdebug you can easily add/remove breakpoints, which are send on session start.
Or set/edit/remove watch expressions, that are evaluated in the current execution context.

Setting a conditional breakpoints or watch expressions is quite easy, it is like an if statement in PHP.

As example you only want to stop on breakpoint when value of $number is equal to 13, then your Breakpoint condition would be $number==13.
Another example would be when you would like to know the value of $item['image'] on each break, then your Watch expression would be $item['image'].

Another way is to set the breakpoint in your PHP code with the following function xdebug_break().

How to configure or disable breaking on exceptions?

By default the execution of a debugging session is suspended on each of the following exception names: * “Fatal error” - EERROR, E_CORE_ERROR, E_COMPILE_ERROR, E_USER_ERROR * _“Catchable fatal error”__ - ERECOVERABLE_ERROR (since PHP 5.2.0) * _“Warning”__ - EWARNING, E_CORE_WARNING, E_COMPILE_WARNING, E_USER_WARNING * _“Parse error”__ - EPARSE * _“Notice”__ - ENOTICE, E_USER_NOTICE * _“Strict standards”__ - ESTRICT * _“Deprecated”__ - EDEPRECATED, E_USER_DEPRECATED (since PHP 5.3.0) * _“Xdebug”__ * “Unknown error”

In order to specify which exception names to suspend the execution of a debugging session, configure the break_on_exception setting with a list of the specific exception names by choice from the list shown above.

It is also possible to specify custom exceptions instead of all exceptions (“Fatal error”). For example if you would configure “MissingArgumentException” instead of “Fatal error”, it would not break on “InvalidParameterException”.

To disable breaking on exceptions either configure an empty list break_on_exception: [] or set as break_on_exception: false.

How can I customize/disable the debugging layout?

Re-adjust the layout in Sublime Text to your liking and then in console (Ctrl+`) you type window.get_layout() and set that value as your debug_layout.

Further customizing can be done by assigning the Xdebug views to a group/index with the breakpoint_group, breakpoint_index, context_group, context_index, stack_group, stack_index, watch_group, watch_index settings.

Or you can disable the debugging layout by setting disable_layout: true, which will open all Xdebug views in current active group/window on session start and does not change your layout.

How to solve ImportError?

Older versions of Sublime Text do not come with Python bundled and rely on your Python system installation.
Some systems do not include specific modules which are required by this package, such as pyexpat.

Configure the python_path setting to the path of your Python installation on your system which is either newer or has all required modules. For example: "python_path" : "/usr/lib/python2.7".

What to do when you experience any issues?

First check following possible solutions that could resolve any issues:

  • Use absolute paths in your path_mapping setting, Xdebug does not return symbolic links.
  • Breakpoint is on an empty line, Xdebug does not stop on empty lines.
  • Set port and xdebug.remote_port to different port (9001), default port 9000 might already be used by an other application.
  • Add an exception for Sublime Text (plugin_host.exe) to your firewall, response from Xdebug could be blocked by firewall.
  • Lower the max_data/max_depth/max_children settings to increase response speed or prevent crashing, Xdebug could return to much data to process.
  • Change permissions for Sublime Text and it's packages on your filesystem, Sublime Text or package might not have valid rights.

Do you still experience any issues, then create an issue including the following data:

  • What operating system(s) and version of Sublime Text are you using?
  • How did you install SublimeTextXdebug, Package Control, git clone or download?
  • Are you trying to debug the script remotely or locally, through browser or command line?
  • Which version of Xdebug extension do you have?
  • Can you post your project/settings file and Xdebug configuration from the *.ini located on your server.
  • Does the console window (Ctrl+`) show any more information regarding the error?


SublimeTextXdebug is released under the MIT License.