Overview

To the right of a session’s screen is a row of tabs. Each one looks at the device or the app from another side. Tabs stay open in the background while you look at another one, so DevTools keeps its state and the terminal its shell.

Not every tab is there in every session: a tab appears only when the session can use it.

Tab	What it is for	When it appears
DevTools	Chrome DevTools for the app’s WebViews: Elements, Console, Network, Sources	always (WebView DevTools)
Pixel perfect	lay a design mockup over the screen and find where the app differs	unless the server turned it off (pixelPerfect.enabled)
WebSockets	the WebViews’ sockets and event streams, frame by frame	when the app has a WebView DevTools can reach
Cache	how the WebViews’ requests use the HTTP cache and a CDN	same as WebSockets
Images	images that are too big, in old formats or loaded but never shown	same as WebSockets
SVG	SVG path data that could be smaller	same as WebSockets
Network	slow, lossy or offline network conditions for the whole device	in emulator sessions with VPN locations
DNS	every name the device looks up, and rewrites of names to other addresses	in sessions with a VPN
Routes	where the connections go: servers, countries, networks, the VPN exit and slow paths	in sessions with a VPN
Logcat	the device’s log, with the app’s lines and crashes	when the session has ADB
Files	the app’s private data and the shared storage	when the session has ADB
Terminal	a shell on the device	when the session has ADB and the device a shell

Logcat, Files and Terminal talk to the device over ADB straight from your browser (see ADB tools). The connection opens when you first open one of them; if it drops, the tab offers Reconnect.

In recordings

A recording keeps what most of these tabs show: its player has Logcat, the WebViews’ Network, Console and WebSockets, Cache, Images, SVG, DNS, Routes and Pixel perfect, each as it was at the moment you are at. Files and Terminal aren’t recorded.