Debug screen



The debug screen is triggered when the key is pressed. It shows the chunk cache, the memory usage, various parameters, the player's map coordinates and a graph that measures the game's current frame rate.

Legend
When the  gamerule is set to , only the starred items are included, in order from top to bottom. The left side is more about the actual game and the right side is more about the player's system information.

Profiler graph
Pie charts in the lower right of the debug screen display real-time profiling information. More detailed information about one section can be displayed by using the keys 1-9. Press 0 to go back to the previous section.

Frame time graph
Bar chart in the lower left of the debug screen displays real time measurement of milliseconds per frame with lines marking 16.7 and 33.3 milliseconds per frame, corresponding to 60 and 30 FPS respectively. The graph is color coded from green to yellow to red, with green being faster frame time, red being slower frame time, and yellow in between. In singleplayer and self-hosted LAN worlds (i.e. when running an integrated server), another graph, at the bottom right, shows milliseconds per tick (MSPT) with a line marking 50 MSPT, which is the maximum amount of time a game tick can take while maintaining 20 ticks per second (the intended rate). The color-coding is similar to the FPS graph.

More debug-keys
Text appears in chat for most debug keys listed here. Note that when using a specific key combination like, , etc., the debug screen does not open.


 * : Reload all chunks.
 * : Toggle visibility of hitboxes of visible entities. It also shows which direction entities are looking, as well as the entities eye level.
 * : Copies the player's coordinates and rotation in the form of a command.
 * Holding for 10 seconds instead forces a debug crash. This generates error code -1, which is misinterpreted by launchers as "video driver error"
 * forces a Java crash instead of a regular Minecraft crash. However, with some keyboards, it triggers only with right control (or rarely, vice versa), thus using left control produces a regular crash.
 * : Clear chat history. Does not include recently typed messages and commands from and.
 * : Increases render distance by 1 (must be between 2 and 32).
 * : Decreases render distance by 1 (must be between 2 and 32).
 * : Toggles visibility of the chunk borders around the player.
 * : Toggles visibility of IDs of items, durability of tools, and armor hexcodes for color. It also shows the scale of maps and details of a firework rocket in a crossbow.
 * : Copies server-sided block or entity data to the clipboard.
 * : Copies client-sided block or entity data to the clipboard.
 * : Cycle between Spectator mode and the previous gamemode. Switches to Creative mode if there is no previous gamemode. Requires cheats to be enabled.
 * : Toggle automatic pause when Minecraft loses focus on / off.
 * : Gives help and shows all + key combinations.
 * : Reload textures, models, sounds, and any other resource pack contents.
 * : Opens gamemode switcher menu. While holding down, a player can cycle between the game modes by pressing and enter the selected gamemode after releasing
 * : Toggle pause without pause menu (if pausing is possible). Singleplayer-only.
 * : Opens the debug screen with the profiler graph.
 * : Opens the debug screen with the Frame time graph.
 * (note that both graphs can be opened with )
 * : Brings up command shortcut menu (Realms Only)
 * : Generates Performance Metrics

When the  gamerule is set to , the effects of  (entity hitboxes),  (chunk boundaries),  (copying coordinates), and  (copying block/entity data) are not shown. Holding down to initiate a crash still works as expected, as well as

Trivia

 * Biome, and the lighting values do not display when the player is outside of the build limits.
 * Deeper into the profiler, some tasks have numbers higher than 9 and can't be accessed. Pressing the two keys simultaneously does not open the task.