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. It can be very useful for telling other players your map location and monitoring performance.

Legend
When displaying reduced debug info, only the starred items are included.

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 seconds per frame with lines marking 1/60s and 1/30s per frame. 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.

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


 * : Reload all chunks.
 * : Toggle visibility of hitboxes of entities. It also shows which direction entities are looking.
 * : Make a debug crash (press keys for at least 10 seconds and release).
 * : Clear chat history (including previously typed messages and commands) (As of 1.11, player can still use the up button to view previous commands/things they said in chat).
 * : Increases render distance by 1 (Minimum and Maximum are 2-32).
 * : Decreases render distance by 1 (Min and Max are 2-32).
 * : Toggle IDs of items, the durability of tools, the armor color and the scale of maps.
 * : Toggles the visible chunk borders around the player.
 * : Cycle between Creative and Spectator gamemodes.
 * : Toggle automatic pause when Minecraft loses focus on / off.
 * : Gives help and shows all + key combinations.
 * : Reloads server side modules, textures and sounds.
 * : Reload textures, models, sounds, and any other resource pack contents.
 * : 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 +)

When the  gamerule is set to , the effects of  (entity hitboxes) and  (chunk boundaries) will not be shown.

Trivia

 * Lc, Biome, and the lighting values do not display when you are in the void or above y = 255 (in the Overworld)
 * When triggered in the Nether, the "B" (biome) displays the biome of "Hell". In the End, until release 1.8 (snapshot 14w17a) it indicated the biome "Sky", likely because The End was originally going to be the Sky Dimension.
 * When used in a chunk that was created prior to Alpha 1.2 (when there were no biomes), the B field will read "Ocean".
 * Deeper into the profiler, some tasks will have numbers higher than 9 and can't be accessed. Pressing the two keys simultaneously will not open the task.