What Your Browser Tells Websites: User-Agent, OS, and More

Contents
The moment you land on a website, your browser is already sending information to the server — no consent window required. What browser you're using, what operating system you're on, how big your screen is: all of it goes along with every request. Because this happens without any permission prompt or popup, most people never notice it's happening at all.
Summary ① The User-Agent string plus screen, time zone, and language info are included by default in every page request ② Sites mostly use this information for ordinary things like switching between mobile and desktop layouts, auto-translating, and diagnosing errors ③ Combining several of these values can make it possible to identify an individual — a practice commonly called "fingerprinting"
Why support asks, "What browser are you using?"
When you report a bug to a website or app, the question that almost always comes back is, "Which browser and operating system are you using?" It feels like pointless paperwork, but it's information that's genuinely needed to fix the problem. Chrome, Safari, and Firefox sometimes render the same code differently, and even the same browser can behave differently on Windows versus macOS.
From a developer's side, when a report comes in saying "the payment button won't click," knowing whether the problem only happens in one browser engine or happens everywhere makes a huge difference in how fast it gets debugged. Browser and OS details are the starting point for narrowing things down.
What the User-Agent string actually is
The most well-known piece of information a browser sends to a server is the User-Agent string. Packed into that string as text are the browser name and version, the rendering engine, and operating system details. A website reads the pattern in that string and concludes something like, "This user is visiting from Safari on iOS."
Where this gets used is mostly ordinary. If you're on a mobile device, show the mobile layout. If the browser is old, display a "please update your browser" notice. Read the user's language setting and auto-translate the UI. The reason this information travels without separate consent is that it was built into the basic communication protocol the web runs on from the start.
How to check what your browser is sending right now
To see this yourself, you have to open your browser's developer tools and type navigator.userAgent into the console. Values like screen resolution, time zone, and CPU core count each live under a different property name, so you have to look up and type each one separately. If you're not a developer, that process is a wall in itself — and checking values one at a time gets tedious fast.
Check your browser's User-Agent, OS, screen resolution, time zone, and more in real time, and copy any value.

What your browser actually exposes
The information a browser exposes doesn't stop at the User-Agent string. Here are the items you can typically check.
| Item | How it's exposed |
|---|---|
| Browser/OS/device type | User-Agent string pattern |
| Screen resolution and available area | screen object |
| Time zone | Intl.DateTimeFormat |
| Language and list of preferred languages | navigator.language(s) |
| CPU logical core count | navigator.hardwareConcurrency |
| Approximate device memory (GB) | navigator.deviceMemory (supported browsers only) |
| Touchscreen support | Touch event support detection |
Each value on its own is nothing special. Look at just one screen resolution or one time zone, and there are countless people with the same value.
The idea of "fingerprinting"
The problem shows up when you combine several of these values at once instead of looking at them one by one. Gather screen resolution, time zone, language, CPU core count, and installed font lists all together, and the number of possible combinations shoots up — which can produce a combination that re-identifies a particular visitor to some degree, even without cookies. This is called browser fingerprinting.
Fingerprinting is a widely known browser privacy concept, but exactly what percentage of users can be uniquely identified depends on the browser, whether extensions are installed, and the point in time, so there's no single number to pin it to. Still, the principle itself is clear: one value is anonymous, and a combination of several values can carry identifying power depending on the situation.
Does incognito mode or a VPN hide it?
There's a common misconception here. Incognito (private) mode only avoids saving your browsing history and cookies — it doesn't hide values like the User-Agent, screen resolution, or time zone. A VPN is the same story: it changes your IP address and connection region, but it has nothing to do with the screen, language, and hardware information your browser sends.
In other words, these two tools solve two different problems. Leaving no browsing history behind and hiding your browser environment information are separate jobs.
The short version
- The User-Agent string and screen, time zone, and language info are sent with every page request without any separate consent
- Sites mostly use this information for ordinary purposes like layout switching, auto-translation, and error diagnosis
- When support or a bug report asks "what browser/OS are you on?", that's a normal procedure that relies on exactly this information
- A single value rarely identifies you, but combining several values can create identifying power — that's the principle behind fingerprinting
- Incognito mode and VPNs handle browsing history and IP/region information respectively; neither one hides your browser environment information itself
Check your browser's User-Agent, OS, screen resolution, time zone, and more in real time, and copy any value.
Frequently asked questions
Why is the User-Agent string so complicated and weird-looking?
The User-Agent string still carries the fingerprints of the early browser compatibility wars, which is why the format got messy — including other browsers' names along the way. These days it's often kept as-is out of convention, so it's normal to see names in the string that seem to have nothing to do with the browser you're actually using.
If I use incognito mode, does this information stay hidden?
No. Incognito mode clears your browsing history, cookies, and login sessions when the session ends — it doesn't hide the User-Agent, screen resolution, or time zone values themselves. This information is exposed exactly the same way in incognito mode.
When I contact support, how do I check my browser information and include it?
Open the My Browser Info Checker page and it immediately shows the browser name, version, operating system, and screen resolution you're using right now. Copy those values and paste them straight into your message — no need to hunt down and type out each one.
Does a VPN also hide my browser fingerprint?
No. A VPN is a tool for changing your connection IP address and region information; it doesn't affect browser environment details like screen resolution, time zone, or hardware core count. In fact, if your VPN's apparent region and your system time zone don't line up, that mismatch can become an unusual combination all by itself.
This article was adapted from our Korean original. Read the Korean original