One very basic operation is opening a new terminal. By default, the keybinding for this is $mod+Enter, that is Alt+Enter (Mod1+Enter) in the default configuration. By pressing $mod+Enter, a new terminal will be opened. It will fill the whole space available on your screen.

If you now open another terminal, i3 will place it next to the current one, splitting the screen size in half. Depending on your monitor, i3 will put the created window beside the existing window (on wide displays) or below the existing window (rotated displays).

To move the focus between the two terminals, you can use the direction keys which you may know from the editor vi. However, in i3, your homerow is used for these keys (in vi, the keys are shifted to the left by one for compatibility with most keyboard layouts). Therefore, $mod+j is left, $mod+k is down, $mod+l is up and $mod+; is right. So, to switch between the terminals, use $mod+k or $mod+l. Of course, you can also use the arrow keys.

At the moment, your workspace is split (it contains two terminals) in a specific direction (horizontal by default). Every window can be split horizontally or vertically again, just like the workspace. The terminology is "window" for a container that actually contains an X11 window (like a terminal or browser) and "split container" for containers that consist of one or more windows.

TODO: picture of the tree

To split a window vertically, press $mod+v before you create the new window. To split it horizontally, press $mod+h.

A split container can have one of the following layouts:

To switch modes, press $mod+e for splith/splitv (it toggles), $mod+s for stacking and $mod+w for tabbed.

To display a window in fullscreen mode or to go out of fullscreen mode again, press $mod+f.

There is also a global fullscreen mode in i3 in which the client will span all available outputs (the command is fullscreen toggle global).

Aside from opening applications from a terminal, you can also use the handy dmenu which is opened by pressing $mod+d by default. Just type the name (or a part of it) of the application which you want to open. The corresponding application has to be in your $PATH for this to work.

Additionally, if you have applications you open very frequently, you can create a keybinding for starting the application directly. See the section [configuring] for details.

If an application does not provide a mechanism for closing (most applications provide a menu, the escape key or a shortcut like Control+w to close), you can press $mod+Shift+q to kill a window. For applications which support the WM_DELETE protocol, this will correctly close the application (saving any modifications or doing other cleanup). If the application doesn’t support the WM_DELETE protocol your X server will kill the window and the behaviour depends on the application.

Workspaces are an easy way to group a set of windows. By default, you are on the first workspace, as the bar on the bottom left indicates. To switch to another workspace, press $mod+num where num is the number of the workspace you want to use. If the workspace does not exist yet, it will be created.

A common paradigm is to put the web browser on one workspace, communication applications (mutt, irssi, …) on another one, and the ones with which you work, on the third one. Of course, there is no need to follow this approach.

If you have multiple screens, a workspace will be created on each screen at startup. If you open a new workspace, it will be bound to the screen you created it on. When you switch to a workspace on another screen, i3 will set focus to that screen.

To move a window to another workspace, simply press $mod+Shift+num where num is (like when switching workspaces) the number of the target workspace. Similarly to switching workspaces, the target workspace will be created if it does not yet exist.

The easiest way to resize a container is by using the mouse: Grab the border and move it to the wanted size.

You can also use [binding_modes] to define a mode for resizing via the keyboard. To see an example for this, look at the default config provided by i3.

To restart i3 in place (and thus get into a clean state if there is a bug, or to upgrade to a newer version of i3) you can use $mod+Shift+r.

To cleanly exit i3 without killing your X server, you can use $mod+Shift+e. By default, a dialog will ask you to confirm if you really want to quit.

Floating mode is the opposite of tiling mode. The position and size of a window are not managed automatically by i3, but manually by you. Using this mode violates the tiling paradigm but can be useful for some corner cases like "Save as" dialog windows, or toolbar windows (GIMP or similar). Those windows usually set the appropriate hint and are opened in floating mode by default.

You can toggle floating mode for a window by pressing $mod+Shift+Space. By dragging the window’s titlebar with your mouse you can move the window around. By grabbing the borders and moving them you can resize the window. You can also do that by using the [floating_modifier]. Another way to resize floating windows using the mouse is to right-click on the titlebar and drag.

For resizing floating windows with your keyboard, see the resizing binding mode provided by the i3 default config.

Floating windows are always on top of tiling windows.

The building blocks of our tree are so called Containers. A Container can host a window (meaning an X11 window, one that you can actually see and use, like a browser). Alternatively, it could contain one or more Containers. A simple example is the workspace: When you start i3 with a single monitor, a single workspace and you open two terminal windows, you will end up with a tree like this:

It is only natural to use so-called Split Containers in order to build a layout when using a tree as data structure. In i3, every Container has an orientation (horizontal, vertical or unspecified) and the orientation depends on the layout the container is in (vertical for splitv and stacking, horizontal for splith and tabbed). So, in our example with the workspace, the default layout of the workspace Container is splith (most monitors are widescreen nowadays). If you change the layout to splitv ($mod+v in the default config) and then open two terminals, i3 will configure your windows like this:

An interesting new feature of i3 since version 4 is the ability to split anything: Let’s assume you have two terminals on a workspace (with splith layout, that is horizontal orientation), focus is on the right terminal. Now you want to open another terminal window below the current one. If you would just open a new terminal window, it would show up to the right due to the splith layout. Instead, press $mod+v to split the container with the splitv layout (to open a Horizontal Split Container, use $mod+h). Now you can open a new terminal and it will open below the current one:

You probably guessed it already: There is no limit on how deep your hierarchy of splits can be.

Let’s stay with our example from above. We have a terminal on the left and two vertically split terminals on the right, focus is on the bottom right one. When you open a new terminal, it will open below the current one.

So, how can you open a new terminal window to the right of the current one? The solution is to use focus parent, which will focus the Parent Container of the current Container. In this case, you would focus the Vertical Split Container which is inside the horizontally oriented workspace. Thus, now new windows will be opened to the right of the Vertical Split Container:

In some cases, i3 needs to implicitly create a container to fulfill your command.

One example is the following scenario: You start i3 with a single monitor and a single workspace on which you open three terminal windows. All these terminal windows are directly attached to one node inside i3’s layout tree, the workspace node. By default, the workspace node’s orientation is horizontal.

Now you move one of these terminals down ($mod+Shift+k by default). The workspace node’s orientation will be changed to vertical. The terminal window you moved down is directly attached to the workspace and appears on the bottom of the screen. A new (horizontal) container was created to accommodate the other two terminal windows. You will notice this when switching to tabbed mode (for example). You would end up having one tab with a representation of the split container (e.g., "H[urxvt firefox]") and the other one being the terminal window you moved down.

It is possible and recommended to use comments in your configuration file to properly document your setup for later reference. Comments are started with a # and can only be used at the beginning of a line:

Examples:

i3 has support for both X core fonts and FreeType fonts (through Pango) to render window titles.

To generate an X core font description, you can use xfontsel(1). To see special characters (Unicode), you need to use a font which supports the ISO-10646 encoding.

A FreeType font description is composed by a font family, a style, a weight, a variant, a stretch and a size. FreeType fonts support right-to-left rendering and contain often more Unicode glyphs than X core fonts.

If i3 cannot open the configured font, it will output an error in the logfile and fall back to a working font.

Syntax:

Examples:

A keyboard binding makes i3 execute a command (see below) upon pressing a specific key. i3 allows you to bind either on keycodes or on keysyms (you can also mix your bindings, though i3 will not protect you from overlapping ones).

My recommendation is: If you often switch keyboard layouts but you want to keep your bindings in the same physical location on the keyboard, use keycodes. If you don’t switch layouts, and want a clean and simple config file, use keysyms.

Some tools (such as import or xdotool) might be unable to run upon a KeyPress event, because the keyboard/pointer is still grabbed. For these situations, the --release flag can be used, which will execute the command after the keys have been released.

Syntax:

Examples:

Available Modifiers:

A mouse binding makes i3 execute a command upon pressing a specific mouse button in the scope of the clicked container (see [command_criteria]). You can configure mouse bindings in a similar way to key bindings.

Syntax:

By default, the binding will only run when you click on the titlebar of the window. If the --release flag is given, it will run when the mouse button is released.

If the --whole-window flag is given, the binding will also run when any part of the window is clicked, with the exception of the border. To have a bind run when the border is clicked, specify the --border flag.

Examples:

You can have multiple sets of bindings by using different binding modes. When you switch to another binding mode, all bindings from the current mode are released and only the bindings defined in the new mode are valid for as long as you stay in that binding mode. The only predefined binding mode is default, which is the mode i3 starts out with and to which all bindings not defined in a specific binding mode belong.

Working with binding modes consists of two parts: defining a binding mode and switching to it. For these purposes, there are one config directive and one command, both of which are called mode. The directive is used to define the bindings belonging to a certain binding mode, while the command will switch to the specified mode.

It is recommended to use binding modes in combination with [variables] in order to make maintenance easier. Below is an example of how to use a binding mode.

Note that it is advisable to define bindings for switching back to the default mode.

Note that it is possible to use [pango_markup] for binding modes, but you need to enable it explicitly by passing the --pango_markup flag to the mode definition.

Syntax:

Example:

To move floating windows with your mouse, you can either grab their titlebar or configure the so called floating modifier which you can then press and click anywhere in the window itself to move it. The most common setup is to use the same key you use for managing windows (Mod1 for example). Then you can press Mod1, click into a window using your left mouse button, and drag it to the position you want.

When holding the floating modifier, you can resize a floating window by pressing the right mouse button on it and moving around while holding it. If you hold the shift button as well, the resize will be proportional (the aspect ratio will be preserved).

Syntax:

Example:

The maximum and minimum dimensions of floating windows can be specified. If either dimension of floating_maximum_size is specified as -1, that dimension will be unconstrained with respect to its maximum value. If either dimension of floating_maximum_size is undefined, or specified as 0, i3 will use a default value to constrain the maximum size. floating_minimum_size is treated in a manner analogous to floating_maximum_size.

Syntax:

Example:

New workspaces get a reasonable default orientation: Wide-screen monitors (anything wider than high) get horizontal orientation, rotated monitors (anything higher than wide) get vertical orientation.

With the default_orientation configuration directive, you can override that behavior.

Syntax:

Example:

This option determines in which mode new containers on workspace level will start.

Syntax:

Example:

This option determines which border style new windows will have. The default is normal. Note that new_float applies only to windows which are starting out as floating windows, e.g., dialog windows, but not windows that are floated later on.

Syntax:

Example:

The "normal" and "pixel" border styles support an optional border width in pixels:

Example:

You can hide container borders adjacent to the screen edges using hide_edge_borders. This is useful if you are using scrollbars, or do not want to waste even two pixels in displayspace. Default is none.

Syntax:

Example:

With the for_window command, you can let i3 execute any command when it encounters a specific window. This can be used to set windows to floating or to change their border style, for example.

Syntax:

Examples:

The valid criteria are the same as those for commands, see [command_criteria].

When a new window appears, it will be focused. The no_focus directive allows preventing this from happening and must be used in combination with [command_criteria].

Note that this does not apply to all cases, e.g., when feeding data into a running application causing it to request being focused. To configure the behavior in such cases, refer to [focus_on_window_activation].

no_focus will also be ignored for the first window on a workspace as there shouldn’t be a reason to not focus the window in this case. This allows for better usability in combination with workspace_layout.

Syntax:

Example:

As you learned in the section about keyboard bindings, you will have to configure lots of bindings containing modifier keys. If you want to save yourself some typing and be able to change the modifier you use later, variables can be handy.

Syntax:

Example:

Variables are directly replaced in the file when parsing. Variables expansion is not recursive so it is not possible to define a variable with a value containing another variable. There is no fancy handling and there are absolutely no plans to change this. If you need a more dynamic configuration you should create a little script which generates a configuration file and run it before starting i3 (for example in your ~/.xsession file).

To automatically make a specific window show up on a specific workspace, you can use an assignment. You can match windows by using any criteria, see [command_criteria]. It is recommended that you match on window classes (and instances, when appropriate) instead of window titles whenever possible because some applications first create their window, and then worry about setting the correct title. Firefox with Vimperator comes to mind. The window starts up being named Firefox, and only when Vimperator is loaded does the title change. As i3 will get the title as soon as the application maps the window (mapping means actually displaying it on the screen), you’d need to have to match on Firefox in this case.

Assignments are processed by i3 in the order in which they appear in the config file. The first one which matches the window wins and later assignments are not considered.

Syntax:

Examples:

Note that the arrow is not required, it just looks good :-). If you decide to use it, it has to be a UTF-8 encoded arrow, not -> or something like that.

To get the class and instance, you can use xprop. After clicking on the window, you will see the following output:

xprop:

The first part of the WM_CLASS is the instance ("irssi" in this example), the second part is the class ("URxvt" in this example).

Should you have any problems with assignments, make sure to check the i3 logfile first (see http://i3wm.org/docs/debugging.html). It includes more details about the matching process and the window’s actual class, instance and title when starting up.

Note that if you want to start an application just once on a specific workspace, but you don’t want to assign all instances of it permanently, you can make use of i3’s startup-notification support (see [exec]) in your config file in the following way:

Start iceweasel on workspace 3 (once):

By using the exec keyword outside a keybinding, you can configure which commands will be performed by i3 on initial startup. exec commands will not run when restarting i3, if you need a command to run also when restarting i3 you should use the exec_always keyword. These commands will be run in order.

See [command_chaining] for details on the special meaning of ; (semicolon) and , (comma): they chain commands together in i3, so you need to use quoted strings (as shown in [exec_quoting]) if they appear in your command.

Syntax:

Examples:

The flag --no-startup-id is explained in [exec].

If you assign clients to workspaces, it might be handy to put the workspaces on specific screens. Also, the assignment of workspaces to screens will determine which workspace i3 uses for a new screen when adding screens or when starting (e.g., by default it will use 1 for the first screen, 2 for the second screen and so on).

Syntax:

The output is the name of the RandR output you attach your screen to. On a laptop, you might have VGA1 and LVDS1 as output names. You can see the available outputs by running xrandr --current.

If you use named workspaces, they must be quoted:

Examples:

You can change all colors which i3 uses to draw the window decorations.

Syntax:

Where colorclass can be one of:

Colors are in HTML hex format (#rrggbb), see the following example:

Examples (default colors):

Note that for the window decorations, the color around the child window is the "child_border", and "border" color is only the two thin lines around the titlebar.

The indicator color is used for indicating where a new window will be opened. For horizontal split containers, the right border will be painted in indicator color, for vertical split containers, the bottom border. This only applies to single windows within a split container, which are otherwise indistinguishable from single windows outside of a split container.

i3 uses Unix sockets to provide an IPC interface. This allows third-party programs to get information from i3, such as the current workspaces (to display a workspace bar), and to control i3.

The IPC socket is enabled by default and will be created in /tmp/i3-%u.XXXXXX/ipc-socket.%p where %u is your UNIX username, %p is the PID of i3 and XXXXXX is a string of random characters from the portable filename character set (see mkdtemp(3)).

You can override the default path through the environment-variable I3SOCK or by specifying the ipc-socket directive. This is discouraged, though, since i3 does the right thing by default. If you decide to change it, it is strongly recommended to set this to a location in your home directory so that no other user can create that directory.

Examples:

You can then use the i3-msg application to perform any command listed in the next section.

By default, window focus follows your mouse movements. However, if you have a setup where your mouse usually is in your way (like a touchpad on your laptop which you do not want to disable completely), you might want to disable focus follows mouse and control focus only by using your keyboard. The mouse will still be useful inside the currently active window (for example to click on links in your browser window).

Syntax:

Example:

By default, when switching focus to a window on a different output (e.g. focusing a window on workspace 3 on output VGA-1, coming from workspace 2 on LVDS-1), the mouse cursor is warped to the center of that window.

With the mouse_warping option, you can control when the mouse cursor should be warped. none disables warping entirely, whereas output is the default behavior described above.

Syntax:

Example:

When you are in fullscreen mode, some applications still open popup windows (take Xpdf for example). This is because these applications may not be aware that they are in fullscreen mode (they do not check the corresponding hint). There are three things which are possible to do in this situation:

Syntax:

Example:

When being in a tabbed or stacked container, the first container will be focused when you use focus down on the last container — the focus wraps. If however there is another stacked/tabbed container in that direction, focus will be set on that container. This is the default behavior so you can navigate to all your windows without having to use focus parent.

If you want the focus to always wrap and you are aware of using focus parent to switch to different containers, you can use the force_focus_wrapping configuration directive. After enabling it, the focus will always wrap.

Syntax:

Example:

As explained in-depth in http://i3wm.org/docs/multi-monitor.html, some X11 video drivers (especially the nVidia binary driver) only provide support for Xinerama instead of RandR. In such a situation, i3 must be told to use the inferior Xinerama API explicitly and therefore don’t provide support for reconfiguring your screens on the fly (they are read only once on startup and that’s it).

For people who cannot modify their ~/.xsession to add the --force-xinerama commandline parameter, a configuration option is provided:

Syntax:

Example:

Also note that your output names are not descriptive (like HDMI1) when using Xinerama, instead they are counted up, starting at 0: xinerama-0, xinerama-1, …

This configuration directive enables automatic workspace back_and_forth (see [back_and_forth]) when switching to the workspace that is currently focused.

For instance: Assume you are on workspace "1: www" and switch to "2: IM" using mod+2 because somebody sent you a message. You don’t need to remember where you came from now, you can just press $mod+2 again to switch back to "1: www".

Syntax:

Example:

If an application on another workspace sets an urgency hint, switching to this workspace may lead to immediate focus of the application, which also means the window decoration color would be immediately reset to client.focused. This may make it unnecessarily hard to tell which window originally raised the event.

In order to prevent this, you can tell i3 to delay resetting the urgency state by a certain time using the force_display_urgency_hint directive. Setting the value to 0 disables this feature.

The default is 500ms.

Syntax:

Example:

If a window is activated, e.g., via google-chrome www.google.com, it may request to take focus. Since this may not preferable, different reactions can be configured.

Note that this may not affect windows that are being opened. To prevent new windows from being focused, see [no_focus].

Syntax:

The different modes will act as follows:

If activated, marks on windows are drawn in their window decoration. However, any mark starting with an underscore in its name (_) will not be drawn even if this option is activated.

The default for this option is yes.

Syntax:

Example:

Config files support line continuation, meaning when you end a line in a backslash character (\), the line-break will be ignored by the parser. This feature can be used to create more readable configuration files.

Examples:

By default i3 will just pass i3bar and let your shell handle the execution, searching your $PATH for a correct version. If you have a different i3bar somewhere or the binary is not in your $PATH you can tell i3 what to execute.

The specified command will be passed to sh -c, so you can use globbing and have to have correct quoting etc.

Syntax:

Example:

i3bar can run a program and display every line of its stdout output on the right hand side of the bar. This is useful to display system information like your current IP address, battery status or date/time.

The specified command will be passed to sh -c, so you can use globbing and have to have correct quoting etc. Note that for signal handling, depending on your shell (users of dash(1) are known to be affected), you have to use the shell’s exec command so that signals are passed to your program, not to the shell.

Syntax:

Example:

You can either have i3bar be visible permanently at one edge of the screen (dock mode) or make it show up when you press your modifier key (hide mode). It is also possible to force i3bar to always stay hidden (invisible mode). The modifier key can be configured using the modifier option.

The mode option can be changed during runtime through the bar mode command. On reload the mode will be reverted to its configured value.

The hide mode maximizes screen space that can be used for actual windows. Also, i3bar sends the SIGSTOP and SIGCONT signals to the statusline process to save battery power.

Invisible mode allows to permanently maximize screen space, as the bar is never shown. Thus, you can configure i3bar to not disturb you by popping up because of an urgency hint or because the modifier key is pressed.

In order to control whether i3bar is hidden or shown in hide mode, there exists the hidden_state option, which has no effect in dock mode or invisible mode. It indicates the current hidden_state of the bar: (1) The bar acts like in normal hide mode, it is hidden and is only unhidden in case of urgency hints or by pressing the modifier key (hide state), or (2) it is drawn on top of the currently visible workspace (show state).

Like the mode, the hidden_state can also be controlled through i3, this can be done by using the bar hidden_state command.

The default mode is dock mode; in hide mode, the default modifier is Mod4 (usually the windows key). The default value for the hidden_state is hide.

Syntax:

Example:

Available modifiers are Mod1-Mod5, Shift, Control (see xmodmap(1)). You can also use "none" if you don’t want any modifier to trigger this behavior.

Specifies a command to run when a button was pressed on i3bar to override the default behavior. This is useful, e.g., for disabling the scroll wheel action or running scripts that implement custom behavior for these buttons.

A button is always named button<n>, where 1 to 5 are default buttons as follows and higher numbers can be special buttons on devices offering more buttons:

Please note that the old wheel_up_cmd and wheel_down_cmd commands are deprecated and will be removed in a future release. We strongly recommend using the more general bindsym with button4 and button5 instead.

Syntax:

Example:

Specifies the bar ID for the configured bar instance. If this option is missing, the ID is set to bar-x, where x corresponds to the position of the embedding bar block in the config file (bar-0, bar-1, …).

Syntax:

Example:

This option determines in which edge of the screen i3bar should show up.

The default is bottom.

Syntax:

Example:

You can restrict i3bar to one or more outputs (monitors). The default is to handle all outputs. Restricting the outputs is useful for using different options for different outputs by using multiple bar blocks.

To make a particular i3bar instance handle multiple outputs, specify the output directive multiple times.

Syntax:

Example:

i3bar by default provides a system tray area where programs such as NetworkManager, VLC, Pidgin, etc. can place little icons.

You can configure on which output (monitor) the icons should be displayed or you can turn off the functionality entirely.

You can use mutliple tray_output directives in your config to specify a list of outputs on which you want the tray to appear. The first available output in that list as defined by the order of the directives will be used for the tray output.

Syntax:

Example:

Note that you might not have a primary output configured yet. To do so, run:

Note that when you use multiple bar configuration blocks, either specify tray_output primary in all of them or explicitly specify tray_output none in bars which should not display the tray, otherwise the different instances might race each other in trying to display tray icons.

The tray is shown on the right-hand side of the bar. By default, a padding of 2 pixels is used for the upper, lower and right-hand side of the tray area and between the individual icons.

Syntax:

Example:

Specifies the font to be used in the bar. See [fonts].

Syntax:

Example:

Specifies a custom symbol to be used for the separator as opposed to the vertical, one pixel thick separator.

Syntax:

Example:

Specifies whether workspace buttons should be shown or not. This is useful if you want to display a statusline-only bar containing additional information.

The default is to show workspace buttons.

Syntax:

Example:

Specifies whether workspace numbers should be displayed within the workspace buttons. This is useful if you want to have a named workspace that stays in order on the bar according to its number without displaying the number prefix.

When strip_workspace_numbers is set to yes, any workspace that has a name of the form "[n]:[NAME]" will display only the name. You could use this, for instance, to display Roman numerals rather than digits by naming your workspaces to "1:I", "2:II", "3:III", "4:IV", …

The default is to display the full name within the workspace button.

Syntax:

Example:

Specifies whether the current binding mode indicator should be shown or not. This is useful if you want to hide the workspace buttons but still be able to see the current binding mode indicator. See [binding_modes] to learn what modes are and how to use them.

The default is to show the mode indicator.

Syntax:

Example:

As with i3, colors are in HTML hex format (#rrggbb). The following colors can be configured at the moment:

Syntax:

Example (default colors):

What good is a window manager if you can’t actually start any applications? The exec command starts an application by passing the command you specify to a shell. This implies that you can use globbing (wildcards) and programs will be searched in your $PATH.

See [command_chaining] for details on the special meaning of ; (semicolon) and , (comma): they chain commands together in i3, so you need to use quoted strings (as shown in [exec_quoting]) if they appear in your command.

Syntax:

Example:

The --no-startup-id parameter disables startup-notification support for this particular exec command. With startup-notification, i3 can make sure that a window appears on the workspace on which you used the exec command. Also, it will change the X11 cursor to watch (a clock) while the application is launching. So, if an application is not startup-notification aware (most GTK and Qt using applications seem to be, though), you will end up with a watch cursor for 60 seconds.

If the command to be executed contains a ; (semicolon) and/or a , (comma), the entire command must be quoted. For example, to have a keybinding for the shell command notify-send Hello, i3, you would add an entry to your configuration file like this:

Example:

If however a command with a comma and/or semicolon itself requires quotes, you must escape the internal quotation marks with double backslashes, like this:

Example:

The split command makes the current window a split container. Split containers can contain multiple windows. Depending on the layout of the split container, new windows get placed to the right of the current one (splith) or new windows get placed below the current one (splitv).

If you apply this command to a split container with the same orientation, nothing will happen. If you use a different orientation, the split container’s orientation will be changed (if it does not have more than one window). The toggle option will toggle the orientation of the split container if it contains a single window. Otherwise it makes the current window a split container with opposite orientation compared to the parent container. Use layout toggle split to change the layout of any split container from splitv to splith or vice-versa.

Syntax:

Example:

Use layout toggle split, layout stacking, layout tabbed, layout splitv or layout splith to change the current container layout to splith/splitv, stacking, tabbed layout, splitv or splith, respectively.

To make the current window (!) fullscreen, use fullscreen enable (or fullscreen enable global for the global mode), to leave either fullscreen mode use fullscreen disable, and to toggle between these two states use fullscreen toggle (or fullscreen toggle global).

Likewise, to make the current window floating (or tiling again) use floating enable respectively floating disable (or floating toggle):

Syntax:

Examples:

To change focus, you can use the focus command. The following options are available:

Syntax:

Examples:

Use the move command to move a container.

Syntax:

Examples:

If you want a window to stick to the glass, i.e., have it stay on screen even if you switch to another workspace, you can use the sticky command. For example, this can be useful for notepads, a media player or a video chat window.

Note that while any window can be made sticky through this command, it will only take effect if the window is floating.

Syntax:

Examples:

To change to a specific workspace, use the workspace command, followed by the number or name of the workspace. Pass the optional flag --no-auto-back-and-forth to disable [back_and_forth] for this specific call only.

To move containers to specific workspaces, use move container to workspace.

You can also switch to the next and previous workspace with the commands workspace next and workspace prev, which is handy, for example, if you have workspace 1, 3, 4 and 9 and you want to cycle through them with a single key combination. To restrict those to the current output, use workspace next_on_output and workspace prev_on_output. Similarly, you can use move container to workspace next, move container to workspace prev to move a container to the next/previous workspace and move container to workspace current (the last one makes sense only when used with criteria).

workspace next cycles through either numbered or named workspaces. But when it reaches the last numbered/named workspace, it looks for named workspaces after exhausting numbered ones and looks for numbered ones after exhausting named ones.

See [move_to_outputs] for how to move a container/workspace to a different RandR output.

Workspace names are parsed as Pango markup by i3bar.

To switch back to the previously focused workspace, use workspace back_and_forth; likewise, you can move containers to the previously focused workspace using move container to workspace back_and_forth.

Syntax:

Examples:

See [move_to_outputs] for how to move a container/workspace to a different RandR output.

To move a container to another RandR output (addressed by names like LVDS1 or VGA1) or to a RandR output identified by a specific direction (like left, right, up or down), there are two commands:

Syntax:

Examples:

To move a container to another container with a specific mark (see [vim_like_marks]), you can use the following command.

The window will be moved right after the marked container in the tree, i.e., it ends up in the same position as if you had opened a new window when the marked container was focused. If the mark is on a split container, the window will appear as a new child after the currently focused child within that container.

Syntax:

Example:

If you want to resize containers/windows using your keyboard, you can use the resize command:

Syntax:

Direction can either be one of up, down, left or right. Or you can be less specific and use width or height, in which case i3 will take/give space from all the other containers. The optional pixel argument specifies by how many pixels a floating container should be grown or shrunk (the default is 10 pixels). The ppt argument means percentage points and specifies by how many percentage points a tiling container should be grown or shrunk (the default is 10 percentage points). Note that resize set will only work for floating containers.

It is recommended to define bindings for resizing in a dedicated binding mode. See [binding_modes] and the example in the i3 default config for more context.

Example:

Often when in a multi-monitor environment, you want to quickly jump to a specific window. For example, while working on workspace 3 you may want to jump to your mail client to email your boss that you’ve achieved some important goal. Instead of figuring out how to navigate to your mail client, it would be more convenient to have a shortcut. You can use the focus command with criteria for that.

Syntax:

Examples:

This feature is like the jump feature: It allows you to directly jump to a specific window (this means switching to the appropriate workspace and setting focus to the windows). However, you can directly mark a specific window with an arbitrary label and use it afterwards. You can unmark the label in the same way, using the unmark command. If you don’t specify a label, unmark removes all marks. You do not need to ensure that your windows have unique classes or titles, and you do not need to change your configuration file.

As the command needs to include the label with which you want to mark the window, you cannot simply bind it to a key. i3-input is a tool created for this purpose: It lets you input a command and sends the command to i3. It can also prefix this command and display a custom prompt for the input dialog.

The additional --toggle option will remove the mark if the window already has this mark or add it otherwise. Note that you may need to use this in combination with --add (see below) as any other marks will otherwise be removed.

By default, a window can only have one mark. You can use the --add flag to put more than one mark on a window.

Refer to [show_marks] if you don’t want marks to be shown in the window decoration.

Syntax:

Example (in a terminal):

By default, i3 will simply print the X11 window title. Using title_format, this can be customized by setting the format to the desired output. This directive supports Pango markup and the following placeholders which will be replaced:

Using the [for_window] directive, you can set the title format for any window based on [command_criteria].

Syntax:

Examples:

To change the border of the current client, you can use border normal to use the normal border (including window title), border pixel 1 to use a 1-pixel border (no window title) and border none to make the client borderless.

There is also border toggle which will toggle the different border styles.

Note that "pixel" refers to logical pixel. On HiDPI displays, a logical pixel may be represented by multiple physical pixels, so pixel 1 might not necessarily translate into a single pixel row wide border.

Syntax:

Examples:

As described in http://i3wm.org/docs/debugging.html, i3 can log to a shared memory buffer, which you can dump using i3-dump-log. The shmlog command allows you to enable or disable the shared memory logging at runtime.

Note that when using shmlog <size_in_bytes>, the current log will be discarded and a new one will be started.

Syntax:

Examples:

The debuglog command allows you to enable or disable debug logging at runtime. Debug logging is much more verbose than non-debug logging. This command does not activate shared memory logging (shmlog), and as such is most likely useful in combination with the above-described [shmlog] command.

Syntax:

Examples:

You can make i3 reload its configuration file with reload. You can also restart i3 inplace with the restart command to get it out of some weird state (if that should ever happen) or to perform an upgrade without having to restart your X session. To exit i3 properly, you can use the exit command, however you don’t need to (simply killing your X session is fine as well).

Examples:

There are two commands to use any existing window as scratchpad window. move scratchpad will move a window to the scratchpad workspace. This will make it invisible until you show it again. There is no way to open that workspace. Instead, when using scratchpad show, the window will be shown again, as a floating window, centered on your current workspace (using scratchpad show on a visible scratchpad window will make it hidden again, so you can have a keybinding to toggle). Note that this is just a normal floating window, so if you want to "remove it from scratchpad", you can simple make it tiling again (floating toggle).

As the name indicates, this is useful for having a window with your favorite editor always at hand. However, you can also use this for other permanently running applications which you don’t want to see all the time: Your music player, alsamixer, maybe even your mail client…?

Syntax:

Examples:

There is a no operation command nop which allows you to override default behavior. This can be useful for, e.g., disabling a focus change on clicks with the middle mouse button.

The optional comment argument is ignored, but will be printed to the log file for debugging purposes.

Syntax:

Example:

There are two options in the configuration of each i3bar instance that can be changed during runtime by invoking a command through i3. The commands bar hidden_state and bar mode allow setting the current hidden_state respectively mode option of each bar. It is also possible to toggle between hide state and show state as well as between dock mode and hide mode. Each i3bar instance can be controlled individually by specifying a bar_id, if none is given, the command is executed for all bar instances.

Syntax:

Examples:

To help you get going if you have never used multiple monitors before, here is a short overview of the xrandr options which will probably be of interest to you. It is always useful to get an overview of the current screen configuration. Just run "xrandr" and you will get an output like the following:

Several things are important here: You can see that LVDS1 is connected (of course, it is the internal flat panel) but VGA1 is not. If you have a monitor connected to one of the ports but xrandr still says "disconnected", you should check your cable, monitor or graphics driver.

The maximum resolution you can see at the end of the first line is the maximum combined resolution of your monitors. By default, it is usually too low and has to be increased by editing /etc/X11/xorg.conf.

So, say you connected VGA1 and want to use it as an additional screen:

This command makes xrandr try to find the native resolution of the device connected to VGA1 and configures it to the left of your internal flat panel. When running "xrandr" again, the output looks like this:

Please note that i3 uses exactly the same API as xrandr does, so it will see only what you can see in xrandr.

See also [presentations] for more examples of multi-monitor setups.

There are several things to configure in i3 which may be interesting if you have more than one monitor:

A very common thing amongst users of exotic window managers is a status line at some corner of the screen. It is an often superior replacement to the widget approach you have in the task bar of a traditional desktop environment.

If you don’t already have your favorite way of generating such a status line (self-written scripts, conky, …), then i3status is the recommended tool for this task. It was written in C with the goal of using as few syscalls as possible to reduce the time your CPU is woken up from sleep states. Because i3status only spits out text, you need to combine it with some other tool, like i3bar. See [status_command] for how to display i3status in i3bar.

Regardless of which application you use to display the status line, you want to make sure that it registers as a dock window using EWMH hints. i3 will position the window either at the top or at the bottom of the screen, depending on which hint the application sets. With i3bar, you can configure its position, see [i3bar_position].

When giving a presentation, you typically want the audience to see what you see on your screen and then go through a series of slides (if the presentation is simple). For more complex presentations, you might want to have some notes which only you can see on your screen, while the audience can only see the slides.