Device Info tells you exactly what the user was on when the session happened — browser, OS, screen size, locale and timezone. It's the fastest way to rule environment in or out when you're debugging an issue.
Where to find it: open any session replay or cobrowsing recording, expand the right-hand panel, then go to Dev tools → Device Info. It works the same way for both recording types.
What each field means
Browser — Which browser the user was on (Chrome, Safari, Firefox, Edge, etc.).
OS — Operating system: Mac OS, Windows, iOS, Android, Linux.
Engine — The rendering engine behind the browser (Blink, WebKit, Gecko). Useful when a bug is engine-specific rather than browser-specific.
Screen — Full resolution of the user's display, in pixels.
Window — The actual size of the browser window, usually smaller than the screen. This is the number that matters for layout and responsive bugs.
Type — Device category: Desktop, Mobile or Tablet.
Locale — The user's language and region setting (e.g. en-US, da-DK). Affects date formats, number formats and which translations your app served.
Timezone — The user's timezone. Handy for reading timestamps the way the user saw them.
User Agent — The raw user agent string, including exact browser and OS version numbers. Copy this straight into a bug report.
Why it's useful
Reproduce bugs faster. Match the user's browser, window size and OS instead of guessing.
Spot environment-specific issues. If every affected session is Safari on iOS, you've found your pattern.
Explain "it looks broken" reports. A cramped window or an unexpected locale often explains a layout or formatting complaint on its own.
Hand off clean context to engineering. The User Agent line gives devs exact versions with no back-and-forth.
Notes
Device Info is captured automatically at the start of every session — nothing to configure.
Values reflect the state at capture time. If a user resizes their window mid-session, the Window value shows the size when recording started.