What each browser detail means
Your browser is the app you use to open websites, and its name, version and operating system are the first things a developer asks for when you report a problem: for example, “Chrome 131 on Windows 10 or 11, window 1440 by 789 pixels” tells them exactly where to look.
When a client says “the site looks broken”, the first useful reply is “which browser and which device?”. This page answers that question for whoever opens it, with no install and no sign-in. Send the link to your client, ask them to press the copy button, and paste what they send into your bug report.
- Browser and version
- The app itself (Chrome, Safari, Firefox, Edge, Samsung Internet and others) and its main version number. Old versions miss newer CSS and JavaScript features, so a version that is a year or more behind is often the whole answer.
- Engine
- The part of the browser that actually draws the page. Blink is used by Chrome, Edge, Opera and Samsung Internet; WebKit by Safari; Gecko by Firefox. Two browsers on the same engine usually show the same layout bug, so the engine tells a developer which one to test first.
- Operating system
- Windows, macOS, iOS, iPadOS, Android, ChromeOS or Linux. Fonts, scroll bars, form controls and date pickers look different on each, even in the same browser.
- Device type
- Phone, tablet or desktop. It decides which layout the site shows and whether hover menus and tooltips can work at all.
- Window (viewport)
- The part of the browser window that shows the page, in CSS pixels. This is the size a layout responds to, and it is usually smaller than the screen because of toolbars, tabs and a window that is not full size.
- Pixel ratio
- How many real screen dots the device uses for one CSS pixel. A ratio of 2 or 3 is normal on phones and modern laptops; it is why a small image can look blurry on one screen and sharp on another.
- User agent
- A line of text every browser sends to every website, naming itself and the system it runs on. It is full of old compatibility words, which is why this page reads it for you instead of asking a client to make sense of it.
Browser strings, read for you
Each row is a sample user agent string in the exact format real browsers send, run through the same reader this page uses on your own browser. Notice how a Mac and an iPad in desktop mode send the same string, and only the touch screen tells them apart.
| Example | Browser | Engine | Operating system | Device type |
|---|---|---|---|---|
| Example: Windows laptop | Chrome 131 | Blink | Windows 10 or 11 | Desktop |
| Example: Windows laptop, Edge | Edge 131 | Blink | Windows 10 or 11 | Desktop |
| Example: Mac, Safari | Safari 18.1 | WebKit | macOS | Desktop |
| Example: iPhone, Chrome | Chrome 131 | WebKit | iOS 18.1 | Phone |
| Example: Android phone | Samsung Internet 26 | Blink | Android 10 | Phone |
| Example: iPad in desktop mode | Safari 18.1 | WebKit | iPadOS | Tablet |
| Example: Linux desktop, Firefox | Firefox 132 | Gecko | Linux | Desktop |
What browser detection cannot tell you
Browser versions on a Mac and on Windows 11 are partly hidden
To make people harder to track, browsers on a Mac report macOS 10.15 whatever the real version is, and Windows 11 still reports itself as Windows 10. Some browsers share the real version on request, and this page uses it when they do; otherwise it says the version is hidden rather than guessing.
Every browser on an iPhone is really Safari underneath
Chrome, Firefox and Edge on iPhone and iPad all use the WebKit engine that Safari uses. A client who says “it is broken in Chrome on my phone” has often found a Safari bug, so test in Safari on iOS first.
In-app browsers are not the browser your client thinks they use
A preview link tapped inside a social, chat or mail app often opens in that app’s built-in browser, which can block pop-ups, downloads and logins. When this page spots one, it says so. Ask the client to open the link in their normal browser and check again.
Browser details can be changed or faked
Privacy extensions, developer tools and some company networks change what a browser reports. Treat the result as a strong clue, not proof, and confirm with a screenshot when a bug only appears on one machine.
Questions about checking your browser
How do I find out which browser I am using?
Open this page. The browser name, version, operating system and device type appear at the top as soon as it loads, read from your own browser. Nothing is sent to us or anyone else.
What should I send my web designer with a browser bug report?
Press “Copy for bug report” and paste the result into your email or ticket, along with the page address, what you did, what you expected and what happened instead. A screenshot of the problem makes it even faster to fix.
Why does the browser checker say Windows 10 when I have Windows 11?
Windows 11 sends the same version number as Windows 10 in the user agent. Some browsers share the real version when a page asks, and this page then shows 11. If yours does not, the page says “10 or 11” rather than guessing.
Why does my iPad show up as a Mac in the browser checker?
Safari on iPad asks for desktop websites by default, and it sends the same text a Mac does. This page checks for a touch screen to tell them apart, so it can still say iPadOS.
Is it safe to share my browser details with a developer?
Yes. The details are the same ones every website you visit already receives. They do not include your name, passwords, location or browsing history. Read the copied text before you send it if you want to be sure.
Does the browser version matter for a website bug?
Often it does. A browser that has not updated in a long time may not support newer layout features, so parts of a page can overlap or vanish. Updating the browser and reloading is a quick first test.
Can a client check their browser on a phone?
Yes. Open the same link on the phone, tap the copy button, and paste the text into a message or email. The page works the same way on phones, tablets and desktops.