What Is My Browser
Everything a helpdesk asks about your browser — in one report you can copy.
Request headers
See the headers your browser sends: press the button to send one request to MySmartCoPilot’s server, which returns the headers it received. Cookies, authorization and licence headers are never shown, and nothing is stored.
About the What Is My Browser
This page reads what your browser reports about itself and puts it in one support report: the browser and its exact version, the operating system, the device, screen and window sizes, your languages and time zone, and whether cookies, storage, JavaScript, WebAssembly, WebGL, WebGPU and service workers work here. It also shows the Do Not Track and Global Privacy Control signals your browser sends.
Press Copy report and paste it into a support ticket or chat: it answers the usual helpdesk questions in one go. Where the classic user-agent string hides details — “Windows NT 10.0” is sent by Windows 10 and Windows 11 alike — the report uses User-Agent Client Hints when your browser offers them. An optional button shows the exact request headers your browser sent to MySmartCoPilot’s server.
How to use it
- Open the page: the report fills in within a second, with a summary such as “Chrome 141 on Windows 11” at the top.
- Read the sections — Browser and system, Screen and window, Language and time, Features and support, Preferences and privacy signals. Anything blocked or missing is marked in red with a short explanation.
- Optional: press Show request headers to see the headers your browser sent with a request to MySmartCoPilot’s server, each explained in a sentence.
- Press Copy report (or Download .txt) and paste it wherever your support team asks for details. Download JSON gives developers the raw values.
- Changed a setting, the window size or the zoom? Press Refresh to read everything again.
Examples
Browser: Chrome 141.0.7390.55 Operating system: Windows 11 Screen size: 1536 × 864 (16:9) Screen in device pixels: 1920 × 1080 Device pixel ratio: 1.25
Windows scales the 1920 × 1080 display by 125 %, so websites lay pages out on 1536 × 864 CSS pixels. Chrome’s client hints give the full version and the Windows release; the user-agent string alone says only “Chrome/141.0.0.0” and “Windows NT 10.0”.
Browser: Safari 26.0 Operating system: iPadOS 26 Device: Tablet (iPad)
iPadOS Safari sends a Mac user agent by default. A Mac has no touch screen, so a “Mac” with several touch points is reported as an iPad, and Safari’s own version, which comes with iPadOS, gives the system’s.
Sec-Fetch-Site: same-origin
Fetch Metadata: the request came from a page on the same site.
Browsers add these Sec- headers themselves; a script cannot fake them, which is why servers can trust them to block cross-site attacks.
Common uses
- Answering “which browser and version are you using?” in a support ticket with one paste.
- Checking that cookies, local storage and JavaScript work when a site will not let you sign in.
- Finding the real screen size, viewport and device pixel ratio when a page looks blurry or cut off.
- Confirming that Global Privacy Control is on after enabling it, and seeing the Sec-GPC header it sends.
- Showing web developers which Client Hints and Fetch Metadata headers a browser really sends.
Why the version or the system can look wrong
Browsers send less in their user-agent string than they used to. Chromium-based browsers (Chrome, Edge, Opera, Brave…) send only the major version, as in “Chrome/141.0.0.0”; Windows 10 and Windows 11 both send “Windows NT 10.0”; current browsers report macOS 10.15 on every newer Mac; and Android phones on Chrome all say “Android 10; K”. The details are still available through User-Agent Client Hints, which this page reads when the browser offers them: a platform version of 13 or higher on Windows means Windows 11 (Microsoft’s table).
- Firefox and Safari do not offer client hints, so the report says “Windows 10 or 11” or “macOS” instead of guessing.
- iPhone and iPad: since iOS 26 and iPadOS 26, the user agent says version 18.6 on every newer system (WebKit). Safari comes with the system and has its version, so in Safari the report shows the real one; other browsers do not tell, and the report then says “18.6 or later”.
- iPad: Safari asks for desktop websites by default and then sends a Mac user agent; the touch screen gives it away.
- Extensions and settings can change the user agent. The report shows what your browser says, so a spoofed value is reported as it is.
Screen size, device pixels and zoom
Websites lay out pages in CSS pixels. The device pixel ratio says how many of the screen’s own pixels make one CSS pixel: 1 on a basic monitor, 2 or 3 on phones and high-resolution laptops, and 1.25 or 1.5 when Windows or macOS scales the display. Screen size × device pixel ratio is close to the display’s native resolution.
On desktops, browser zoom changes the device pixel ratio: at 125 % zoom a 1.0 screen reports 1.25, and the viewport (the part of the window that shows the page) gets smaller in CSS pixels. If a site looks too large or too small, check the zoom first (Ctrl or ⌘ and 0 resets it).
What the request headers show
Show request headers sends one small request from this page to MySmartCoPilot’s server, which sends back the headers your browser sent with it, values unchanged:
- Accept-Language lists your languages with weights (RFC 9110 §12.5.4); sites use it to choose a language.
- Sec-CH-UA, Sec-CH-UA-Mobile and Sec-CH-UA-Platform are the low-detail client hints Chromium browsers send to every HTTPS site; the detailed ones go only to sites that ask with an Accept-CH header.
- Sec-Fetch-Site, Sec-Fetch-Mode and Sec-Fetch-Dest are Fetch Metadata headers: for this button they say same-origin, cors and empty. Opening a page sends navigate and document instead, plus Sec-Fetch-User: ?1 when you started the navigation yourself.
- Accept-Encoding lists the compression formats your browser can unpack. Our hosting network replaces this header on the way and keeps the original, so the page shows the value your browser sent.
- DNT and Sec-GPC appear only when those signals are on.
Cookies, authorization headers and MySmartCoPilot’s own licence header are never shown, and neither are the headers our hosting network adds or overwrites on the way (your address and country, Connection), because they did not come from your browser. Header names travel in lower case over HTTP/2 and HTTP/3, and the server does not see the order in which they were sent, so the list is sorted for reading.
Do Not Track and Global Privacy Control
Do Not Track (DNT: 1) asks sites not to track you. Its W3C specification was never finished and ended as a Working Group Note, Safari removed it, and few sites honour it.
Global Privacy Control is its successor: browsers that support it send Sec-GPC: 1 with every request and expose navigator.globalPrivacyControl to scripts. Firefox, Brave and DuckDuckGo’s browser support it; other browsers need an extension. In California, businesses must honour opt-out preference signals such as GPC as a valid request to opt out of the sale or sharing of personal information (California Privacy Protection Agency).
Limitations
- It reports what the browser says about itself: a changed user agent, privacy protections or extensions can make values differ from the real device.
- Third-party cookie blocking cannot be tested from a single site, and browsers do not reveal which extensions are installed.
- Device memory is rounded to a power of two and capped by the browser, and the connection estimate (4G or faster, Mbit/s, round trip) exists only in Chromium browsers.
- The request headers are those of a script’s request from this page, not of a page load, and MySmartCoPilot’s server allows a limited number of these requests per hour for each visitor.
- Some values, such as the time zone and languages, are what the browser is set to, not where you are.
Privacy
The report is made in your browser and is not sent anywhere; Copy and Download stay on your device. Probing storage writes and removes one test value in this site’s local and session storage. Only when you press “Show request headers” does MySmartCoPilot’s server receive a request, and it answers with the headers of that request without storing or logging them — cookies, authorization and licence headers are never included.
Frequently asked questions
How do I check whether my browser is up to date?
This report shows the exact version. Browsers update themselves; to check now, open the browser’s About page: Chrome — Settings → About Chrome; Edge — Settings → About Microsoft Edge; Firefox — Help → About Firefox; Safari updates with macOS or iOS (Software Update). It shows whether a newer version is available and installs it.
Why does it say “Windows 10 or 11”?
Both send “Windows NT 10.0” in the user agent. Chrome, Edge and Opera also offer a client hint that tells them apart, and then the report shows Windows 10 or Windows 11; Firefox and Safari do not, so the report does not guess.
Cookies or storage show as “Blocked” — what does that mean?
The browser refuses to let this site keep data: a privacy setting, a “block all cookies” option, some private modes, or an extension. Many sites then cannot keep you signed in or remember a shopping basket. Allow cookies for the site in the browser’s settings (usually under Privacy or Site settings) and press Refresh.
What is the difference between screen resolution and viewport?
The screen size is the whole display in CSS pixels; the viewport is the part of the browser window that shows the page, so it shrinks with toolbars, sidebars and smaller windows. Responsive websites adapt to the viewport, not to the screen.
Is JavaScript enabled?
If you can see this report, yes: it is built by JavaScript. With JavaScript off, the page says so instead of showing the report.
Does this page send or store my information?
No. Everything is read in your browser and stays there. The request-headers button sends one request to MySmartCoPilot’s server, which only reads that request’s headers to send them back and stores nothing.