Skip to main content

What is My Browser

Detect your browser, OS, device, screen resolution, and capabilities. See cookies, WebGL, localStorage, geolocation support and more.

Detected live in your browser. No data leaves this page.

Browser & device
Capabilities
User-agent string

Share on Social Media:

What Is My Browser? Read the Exact Details Every Website Already Sees

Open this page and, before you have even scrolled, your browser has already told it everything: that you are running Chrome 124 on Windows 11, that your window is 1536 pixels wide, that your language is set to English, and that your user agent reads Mozilla/5.0 (Windows NT 10.0; Win64; x64).... The What Is My Browser tool simply catches that confession and prints it back in plain English. Every site you visit receives the same handful of signals; the difference is that most never show them to you. This one does, instantly, with copy buttons on the values you are most likely to need.

The result answers the literal question "what is my browser" with a single headline sentence, then unfolds the rest: browser name and version, operating system, device type, screen resolution, the live size of your browser window, your language, and whether cookies and JavaScript are switched on. No install, no account, no upload. The detection is read-only and finishes in the time it takes the page to paint.

How to Read Your Result

There is one rule that trips people up, so read it first: the tool reports on whichever browser is displaying this page right now. If you want to know about Firefox, open the tool in Firefox. If you tapped a link inside a chat app and landed here, you may be looking at that app's built-in viewer, not your real browser. Everything else is just reading the screen.

  1. Read the headline. One sentence, such as "You are using Safari 17 on macOS." That is your answer to what is my browser version in one glance.
  2. Scan the detail panel. Operating system, device type, screen resolution, browser window (viewport) size, language, cookies, and JavaScript status are listed in order.
  3. Grab the user agent. The raw text string sits in its own field with a copy button. Support teams and developers ask for this exact line constantly.
  4. Copy what you need straight into a support ticket or bug report instead of retyping it. One wrong character in a user agent sends a developer hunting for the wrong bug.
  5. Refresh to re-check. After you update your browser or rotate a tablet, reload the page; detection runs on load, so the new version or orientation only shows after a refresh.

What Each Value Means, and How to Act on It

The panel shows several numbers and labels that look related but answer different questions. Knowing the difference is what turns a curiosity into a fix.

Browser name and version

The name identifies the application: Chrome, Firefox, Safari, Edge, Opera, Brave, Vivaldi, Samsung Internet. The version is the release, like Chrome 124 or Firefox 125. Version is the part that quietly causes problems, because security patches and new web features ship with each release. A site that refuses to load a checkout form, or a video call that will not start your camera, is very often a browser two or three versions behind. The headline tells you immediately whether you are current.

User agent string

This is one line of text your browser sends to every server, packing the browser, version, rendering engine, and operating system into a single machine-readable string. A typical Chrome-on-Windows agent reads Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36. Decoded, that says: Windows 10/11 64-bit, the WebKit-derived Blink engine, Chrome 124, with the historical "Safari" token every Chromium browser still carries for compatibility. Servers read it to decide which version of a page to send you. When a developer asks for your browser user agent, copy this whole line verbatim.

Screen resolution versus browser window size

These two numbers are the most commonly confused. Screen resolution is the full pixel size of your physical display, for example 1920 by 1080. Your browser window (viewport) size is only the area available to draw the web page, which is always smaller because it excludes the tabs, address bar, scrollbars, and any space lost when the window is not maximised. A maximised 1920-wide screen often reports a viewport of roughly 1903 by 937. Responsive websites react to the viewport, never the resolution, which is why a designer cares about that smaller number most.

Language, cookies, and JavaScript

The language reflects your browser's preferred locale, which some sites use to choose a default translation before you pick one. The cookie and JavaScript flags matter for troubleshooting: a surprising number of "this site is not working" reports come down to a privacy extension having blocked one or both. If the panel shows JavaScript disabled, most modern sites simply cannot function, and that is your answer.

Three Worked Examples

The values mean more when you see them solve a real problem.

The "unsupported browser" banner

A user keeps getting "Your browser is not supported" on a banking site. The tool reports Chrome 109 on Windows 10. Chrome is on 124, so this machine is fifteen releases behind, almost certainly stuck because Windows updates were paused. The fix is not the bank; it is updating Chrome (or, on Windows 10, confirming the OS still receives Chrome updates). The headline diagnosed it in one line.

The user agent that looks fake

A developer asks a tester for their agent and receives Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 from someone on Windows. That is a privacy extension spoofing the agent to look like Firefox on Linux. The tool is not wrong; it reports exactly what the browser claims, which is exactly what every website also receives. The takeaway: disable the spoofing extension before reporting a real bug, or the developer chases a Linux issue that does not exist.

The mismatched layout

Two colleagues open the same dashboard. One sees a cramped single-column view, the other sees the full grid. Comparing tools side by side: one reports a viewport of 768 pixels, the other 1440. The 768-pixel window triggered the tablet breakpoint even on a desktop, because that person had the window snapped to half the screen. Maximising it restored the full layout. Nothing was broken; the viewport explained everything.

When the Result Surprises You

Most confusion about what browser am I using comes from a few predictable causes. Each has a clean explanation.

  • The name is not the browser you thought you opened. You are almost certainly inside an in-app browser. Links tapped in social, messaging, and email apps frequently open in a built-in viewer rather than your default. Use the app's menu to choose "Open in browser," then re-run the tool.
  • The version looks rounded or short. Browser makers now report a simplified user agent to reduce fingerprinting, which can flatten the minor version. The major version shown is still accurate and is what compatibility checks rely on.
  • It says Safari even though you opened a different browser on iPhone. On iOS, third-party browsers have historically run on Apple's own web engine, so engine references to Safari can appear in the string. The application name in the headline still tells you which app you are actually in.
  • Resolution and window size do not match. They are not supposed to. Resolution is the whole display; the viewport is only the visible web area. Maximise the window to bring the two numbers as close as your toolbars allow.
  • Details did not change after an update. The page is stale. Reload it, or close and reopen the tab, because detection only runs when the page loads.

How Browser Detection Actually Works

Trusting the result is easier once you know where it comes from. When your browser requests any web page, it attaches a set of request headers, the most relevant being the user agent. On top of that, the browser exposes JavaScript properties the page can read directly: navigator.userAgent, navigator.language, navigator.cookieEnabled, screen.width and screen.height, and window.innerWidth and window.innerHeight for the viewport. This tool reads those standard, publicly available values, the same ones every site you visit can read, and translates them into friendly labels. Nothing is probed, scanned, or extracted.

There are two honest limits worth stating. First, some privacy browsers and extensions deliberately alter the user agent, so the tool shows what your browser claims rather than ground truth; that is still useful, because it is precisely what the rest of the web sees. Second, the ongoing simplification of user agent strings means very fine-grained version numbers may be rounded on certain browsers. Where modern browsers expose the newer Client Hints signals, those help keep the major version exact even when the legacy string is generic.

Why the same site can look different to two people

Because servers read your user agent and your page reads your viewport, two visitors at the same address can receive different layouts. A narrow viewport gets the mobile arrangement; a wide one gets the full version; an old user agent might even get a legacy fallback page. When a colleague sees a button you cannot find, comparing browser details usually reveals the cause in seconds, most often a version gap or a window snapped to half-width.

Where People Actually Use This

Knowing your browser sounds trivial until a problem hinges on it. These are the situations where the tool earns its place.

  • Filing a support ticket that gets solved on the first reply. The first question support asks is "which browser and version?" Paste the exact details and the user agent and the team can reproduce your issue immediately instead of trading three rounds of guesses.
  • Clearing a compatibility check before it matters. Proctored exams, conferencing tools, and trading platforms list supported browsers. Confirm you meet the bar before the session starts, not thirty seconds after it fails.
  • QA and responsive testing. Testers grab the reported engine, version, and viewport to log exactly which environment a defect appeared in, so a bug report carries the evidence with it.
  • Checking a borrowed or public machine. On a library PC or hotel kiosk, see what browser you are about to log in with before you trust it with a password.
  • Untangling mobile in-app browsers. When a link refuses to behave on a phone, the tool reveals whether you are in your real browser or an app's embedded viewer, which is the difference between a fixable setting and a dead end.
  • Understanding your own exposure. Your user agent, language, and screen size combine into a browser fingerprint that advertisers use to recognise your device across sites. Seeing those values plainly is the first step to deciding whether you want a tracker blocker or a more privacy-focused browser.

What the Tool Does Not See

It is fair to be wary of any page that reads device information, so here is the boundary, stated plainly. The tool shows only the standard signals your browser already broadcasts to every website. It does not read your files, your history, your saved passwords, or the contents of other tabs. It does not need an account and stores nothing about you to function. One thing it deliberately does not cover is your network: questions like what is my browser IP or your location come from your connection, not your browser software, and belong to a separate tool. What you see here is strictly the software side of your identity online.

Tips for an Accurate, Reportable Result

  • Open the tool in the exact browser you want to check. Copying the link into another app reports that app instead.
  • Maximise the window before reading the viewport if you want your browser size to approach your full screen resolution.
  • Update, then refresh. Reload after updating so the version number you report is the one actually running.
  • Use the copy buttons for the user agent. Never retype it; a single transposed character changes its meaning.
  • Disable user-agent-changing extensions temporarily when you need the true, unmodified value.
  • Check each device separately when a problem appears on only one of them, since the browser and version usually differ between a phone and a computer.

Related Tools

If the What Is My Browser tool helped, these other free utilities on Tools Hub pair naturally with it:

  • What Is My IP — see the public IP address your network connection is using, the companion to your browser details.
  • What Is My Screen Resolution — a dedicated, detailed read of your display and viewport dimensions.
  • User Agent Parser — paste any user agent string and break it into browser, engine, version, and OS.
  • Internet Speed Test — measure download and upload speed when a site feels slow, ruling out the connection before the browser.
  • Cookie and JavaScript Checker — confirm whether cookies and scripts are enabled, which many sites require to load at all.
  • Word Counter — a handy free text utility for everyday writing and editing.

Frequently Asked Questions

Is the What Is My Browser tool free?

Yes, it is completely free with no sign-up, no payment, and no watermark of any kind. Use it as many times as you want, on as many devices as you want, at no cost.

Do I need to install anything or create an account?

No. The tool runs entirely in your web browser. There is no software to download and no account to register. Open the page and your details appear automatically.

How accurate is the browser detection?

The tool reports exactly what your browser shares with every website, so it reflects what the wider internet sees. A value only looks generic when a privacy extension or the browser maker has deliberately simplified the user agent, in which case the tool honestly shows that same value.

What is a user agent string and why would I need it?

A user agent is the line of text your browser sends to identify itself, bundling the browser, version, engine, and operating system. Support teams and developers request it constantly to reproduce an issue. The tool displays it with a one-tap copy button so you never type it by hand.

Can I check what browser I am using on my phone?

Yes. Open the tool in the mobile browser you want to verify and read the headline. It works the same way in every browser and on every device, so the result reflects whichever app is showing the page right now.

Does the tool collect or store my personal data?

The tool only displays the standard, public details your browser already broadcasts to every site. It does not read your files, history, passwords, or other tabs, and it requires no personal information to work.

Why does a website tell me my browser is unsupported when it looks current?

Usually the site checks for a minimum version and your browser is a release or two behind, or an extension is altering your user agent. Use the tool to confirm what is my browser version, then update if needed or temporarily disable user-agent-changing extensions.

What is the difference between my browser and my default browser?

Your browser is whichever app is open right now; your default browser is the one your device uses to open links automatically. The tool reports the browser currently displaying the page, which helps you verify whether your default setting is behaving as expected.

Will the tool work on older systems and locked-down work machines?

Yes. It is a lightweight web page that reads standard browser values, so it runs on older operating systems and managed work computers without installing anything, which makes it a reliable way to confirm your setup on a restricted device.

🔗 Relevant Tools

Leave a comment

Comments go straight to our team — they are not published on the site.

ads

Please disable your ad blocker!

We understand that ads can be annoying, but please bear with us. We rely on advertisements to keep our website online. Could you please consider whitelisting our website? Thank you!