What browser am I using?

All of this is read from your own browser with JavaScript. Nothing is sent to us or stored.

When a website or app misbehaves, the first question from support is usually "Which browser and version are you using?" Many bugs only happen in one browser, an outdated version, a particular screen size, or with cookies blocked.

Instead of hunting through menus, click Copy info (for tech support) and paste the whole list into the chat, ticket or email. It gives the support team everything they typically need in one go, and saves a round of back-and-forth questions.

For web developers, the same list is a quick way to check a tester's setup when a layout bug cannot be reproduced.

Running the latest version matters for security: browsers fix actively exploited vulnerabilities several times a year. Most update themselves automatically, but you may need to restart the browser to finish an update.

• Chrome: Menu (⋮) → Help → About Google Chrome.
• Edge: Menu (…) → Help and feedback → About Microsoft Edge.
• Firefox: Menu (☰) → Help → About Firefox.
• Safari (Mac): updates come with macOS through System Settings → General → Software Update.
• Safari (iPhone and iPad): Settings → General → Software Update.
• Android: update Chrome or Samsung Internet from the Google Play Store or Galaxy Store.

Opening the About page usually triggers a check and shows whether a restart is needed.

• Windows 10 or 11: browsers report "Windows NT 10.0" for both versions. Chromium-based browsers (Chrome, Edge, Opera) can tell them apart through a newer API, so the page shows the exact version there; in Firefox it shows "Windows 10 or 11."
• macOS version: Safari and Firefox freeze the macOS version in the user agent for privacy, so the page may show just "macOS."
• Reduced user agent: Chrome now sends a simplified user agent with less detail by default. The page asks the browser's User-Agent Client Hints API for the full version when available.
• iPhone browsers: Chrome, Firefox and Edge on iOS use Apple's WebKit engine, so in some respects they behave like Safari.

Screen resolution is the size of your display; window size is the part of it your browser gives to the web page, minus toolbars and the taskbar. Responsive websites react to the window size, which is why a page can look different on the same screen when the window is narrower.

Both are measured in CSS pixels. On high-density screens, one CSS pixel is drawn with several physical pixels: a phone with a pixel ratio of 3 and a 390 px wide viewport actually has 1,170 physical pixels across. That is why images for the web are often exported at 2× size.