English
What Is My User Agent
Detect your user agent, browser, OS, device type, and browser capabilities instantly. Free tool with copy and tap-to-copy on mobile.
Your User Agent
Parsed User Agent Details
| Property | Value | Copy |
|---|---|---|
| User Agent String | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com) | |
| Browser | Mozilla | |
| Rendering Engine | WebKit | |
| Operating System | Unknown | |
| Device | WebKit | |
| Device Type | Bot / Crawler | |
| Architecture | Unknown | |
| Languages | Unknown | |
| Is Mobile | No | |
| Is Tablet | No | |
| Is Desktop | No | |
| Is Bot/Crawler | Yes (ClaudeBot) |
Browser Capabilities
| Capability | Value |
|---|---|
| Cookies Enabled | -- |
| Do Not Track | -- |
| Online Status | -- |
| Touch Support | -- |
| CPU Cores | -- |
| Device Memory | -- |
| Connection Type | -- |
| Screen Resolution | -- |
| Color Depth | -- |
| Platform | -- |
| Timezone | -- |
| Browser Language | -- |
Common Browsers & Platforms
What is What Is My User Agent?
What Is My User Agent is an online tool that detects and displays your browser's user agent string and parses it into readable information such as browser name and version, operating system, rendering engine, device type, and architecture. The user agent is a string that your browser sends to web servers with every request, identifying the browser, operating system, and device. The tool runs automatically on page load—no button click or form submission is required. As soon as you open the page, it reads your user agent from the server and displays it in a hero section, followed by quick info cards for browser, operating system, device type, and rendering engine. A detailed table lists all parsed properties including user agent string, browser, engine, OS, device, device type, architecture, languages, and flags for mobile, tablet, desktop, and bot detection. A separate Browser Capabilities section shows client-side capabilities such as cookies enabled, Do Not Track, online status, touch support, CPU cores, device memory, connection type, screen resolution, color depth, platform, timezone, and browser language. A Common Browsers and Platforms reference section highlights your current browser and platform with a YOU badge. Each row has a copy button so you can copy values to the clipboard. On mobile, tapping a row copies the value and shows a confirmation toast. No registration is required.
Every HTTP request includes a User-Agent header. A typical user agent string might look like: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. This string is difficult to read directly. Parsing it reveals that the browser is Google Chrome 120, the operating system is Windows 10 (64-bit), and the rendering engine is Blink (Chromium's fork of WebKit). Web servers use the user agent to serve different content, detect bots, or tailor the experience. Developers use it to debug browser-specific issues, test responsive designs, and understand how their site is being accessed. Knowing your user agent helps when troubleshooting website compatibility, reporting bugs, or configuring software that expects specific browser headers.
The tool uses server-side parsing with the Jenssegers Agent library to extract browser, OS, device, and related flags. The rendering engine (Blink, WebKit, Gecko, Trident, etc.) is detected via regex patterns. Architecture (32-bit, 64-bit, ARM, ARM64) is inferred from the user agent string. The Browser Capabilities section uses JavaScript to read navigator and screen properties: cookies enabled, Do Not Track, online status, touch support, hardware concurrency (CPU cores), device memory (when available), connection type (from the Network Information API), screen resolution, color depth, platform, timezone, and browser language. These values are not in the user agent string but are useful for understanding your browser environment. The tool is free and works on desktop, tablet, and mobile devices.
Modern browsers are moving toward reducing the amount of information in the user agent string for privacy reasons. Some browsers now send a simplified or unified user agent. The tool displays whatever string the server receives. Even with reduced user agents, the parsing logic can often still identify the browser and OS from the remaining tokens. The Browser Capabilities section complements the user agent by providing additional client-side information that is not sent in HTTP headers.
Who Benefits from This Tool
Web developers and QA testers benefit from What Is My User Agent when debugging browser-specific issues, testing responsive designs, and documenting test environments. When a bug occurs only in certain browsers, knowing the exact user agent helps reproduce the issue. The parsed browser, OS, and device type help developers understand the user's environment. The Browser Capabilities section shows client-side features that affect how your site behaves—for example, touch support, device memory, and connection type. These values are useful when implementing progressive enhancement or adaptive loading.
Support staff and help desk agents use the tool when assisting users with website compatibility or software configuration. If a user reports that a site does not work correctly, they may be asked to provide their user agent. The tool makes it easy to find and copy it. The copy button and tap-to-copy on mobile ensure users can quickly share the value. The parsed details make it easier for support to understand the user's browser and OS without interpreting the raw string.
End users benefit when troubleshooting their own issues, configuring software that asks for browser information, or verifying that their browser is correctly identified. Privacy-conscious users may want to check what their browser sends to websites. The tool is free and requires no installation or registration.
Content creators and marketers use the tool when analyzing traffic sources or understanding the devices their audience uses. Knowing the mix of browsers and platforms helps prioritize which environments to test. The Common Browsers and Platforms reference provides a quick overview of the most popular options.
Key Features
Instant Auto-Detection
The tool detects your user agent as soon as the page loads. No button click or form submission is required. The hero section displays the full user agent string in a readable font, with badges for browser, engine, OS, and device type. Quick info cards show browser, operating system, device type, and rendering engine at a glance.
Parsed User Agent Details
A detailed table lists all parsed properties: user agent string, browser, rendering engine, operating system, device, device type, architecture, languages, and flags for mobile, tablet, desktop, and bot. Each row has a copy button. The table is responsive and scrolls horizontally on small screens.
Browser Capabilities
A second table shows client-side capabilities: cookies enabled, Do Not Track, online status, touch support, CPU cores, device memory, connection type, screen resolution, color depth, platform, timezone, and browser language. These values are read from the browser's JavaScript APIs and update in real time.
Common Browsers and Platforms Reference
A reference section lists common browsers (Google Chrome, Firefox, Safari, Edge, Opera, Samsung Browser) and platforms (Windows, macOS, Linux, Android, iOS, Chrome OS). If your browser or platform matches, the tool highlights it with a YOU badge and a border. This helps you quickly identify your setup.
Copy to Clipboard
Each row in the Parsed User Agent Details table has a copy button. Clicking it copies the value to the clipboard and shows a SweetAlert2 toast. On mobile, where the copy button column may be hidden, tapping anywhere on the row copies the value and shows the same toast.
How to Use
- Open the What Is My User Agent tool page. The tool automatically detects your user agent on load.
- View the hero section to see your full user agent string and the badges for browser, engine, OS, and device type. Use the Copy button in the header to copy the full user agent.
- Scroll down to see the quick info cards for browser, operating system, device type, and rendering engine.
- View the Parsed User Agent Details table for all parsed properties. Use the copy button next to any value to copy it to the clipboard. On mobile, tap the row to copy.
- Scroll to the Browser Capabilities table to see client-side capabilities such as cookies, DNT, touch support, CPU cores, device memory, connection type, screen resolution, and more.
- Check the Common Browsers and Platforms section to see if your browser and platform are highlighted with the YOU badge.
Common Use Cases
- Finding your user agent for support requests or bug reports
- Verifying browser and OS detection for website compatibility
- Documenting the test environment for QA reports
- Understanding what information your browser sends to websites
- Checking device type (mobile, tablet, desktop) and architecture
- Copying user agent for software configuration or API testing
- Identifying rendering engine and browser version
- Checking browser capabilities such as touch support and device memory
- Comparing your setup with common browsers and platforms
- Debugging browser-specific issues in web development
Tips and Best Practices
Use the copy button when sharing your user agent with support or developers. The full string is often needed for accurate reproduction. The parsed details are useful for quick reference. On mobile, tap the row to copy—the copy button may be hidden to save space. The Browser Capabilities section shows values that are not in the user agent, such as device memory and connection type; these can affect how websites load or behave.
User agent strings can be spoofed by browsers or extensions. Privacy-focused browsers may send a simplified or generic user agent. The tool shows what the server receives. For the most accurate client-side capabilities, use the Browser Capabilities section, which reads directly from the browser.
The Common Browsers and Platforms section helps you quickly identify your setup. If you use Google Chrome on Windows, both Chrome and Windows will show the YOU badge. If you use Safari on a Mac, Safari and macOS will be highlighted. This visual feedback makes it easy to confirm that the tool correctly identified your environment. The reference includes the most popular browsers and operating systems, so most users will see at least one match.
Responsive design ensures the tool works well on all screen sizes. On mobile, the copy button column in the details table may be hidden to save space. Tapping anywhere on a row copies the value instead. This tap-to-copy behavior is especially useful on touch devices where small buttons are hard to tap. The SweetAlert2 toast provides immediate feedback so you know the copy succeeded. The layout adapts: cards stack on narrow screens and display in a grid on wider screens.
Limitations and Notes
The tool relies on the server receiving the user agent from the request. If you are behind a proxy or load balancer that modifies headers, the displayed value may differ. The parsing logic is based on common patterns; some browsers or bots may not be fully recognized. The Browser Capabilities section uses JavaScript APIs that are not supported in all browsers; unsupported values may show as Not available.
Device memory and connection type are available only in some browsers. The Network Information API is experimental. Privacy: the tool does not store your user agent persistently. The server may log requests for analytics. No personally identifiable information beyond the user agent is collected.
The tool is built with Laravel and Livewire. The server-side parsing happens in PHP using the Jenssegers Agent library. The client-side Browser Capabilities section uses Alpine.js to read navigator and screen properties. SweetAlert2 provides the copy confirmation toasts. The design follows the Tabler UI framework for consistent styling and dark mode support.
FAQs
What is a user agent string?
A user agent string is a text sent by your browser with every HTTP request. It identifies the browser, operating system, and device. Web servers use it to serve appropriate content or detect bots. The format varies by browser and is not standardized.
Why does my user agent show as different from my actual browser?
Some browsers or extensions may modify the user agent for privacy or compatibility. VPNs and proxies can also change headers. The tool displays what the server receives.
What is the rendering engine?
The rendering engine is the software that renders web pages. Common engines are Blink (Chrome, Edge), Gecko (Firefox), WebKit (Safari), and Trident (legacy IE). The engine affects how HTML and CSS are displayed.
Can I copy the user agent on mobile?
Yes. On mobile, the copy button column may be hidden. Tap anywhere on the row to copy the value. A confirmation toast will appear.
What is device type?
Device type indicates whether the browser is on a desktop, tablet, mobile, or bot. It is inferred from the user agent string. Mobile typically means a phone; tablet means a tablet device; desktop means a computer.
What is device memory?
Device memory is the approximate amount of RAM in gigabytes, reported by the browser. It is available only in some browsers (e.g., Chrome) and is used for adaptive loading or performance optimization.
What is Do Not Track?
Do Not Track (DNT) is a browser setting that requests websites not to track the user. The tool shows whether DNT is enabled. Compliance is voluntary; not all websites honor it.
Why does my browser show as Unknown?
If the parsing logic does not recognize your browser pattern, it may show as Unknown. This can happen with rare browsers, custom builds, or heavily modified user agents.
Is my user agent stored?
The tool does not store your user agent in a database. The server may log requests for analytics. No persistent storage of user agent data is performed.
What is the difference between user agent and browser capabilities?
The user agent is a string sent with every request. Browser capabilities are read from JavaScript APIs (navigator, screen) and are not part of the user agent. Capabilities include cookies, touch support, CPU cores, and device memory.
What browsers are supported?
The tool works in all modern browsers: Chrome, Firefox, Safari, Edge, Opera, and others. The parsing logic recognizes the most common browsers and operating systems. Rare or custom browsers may show as Unknown. The Browser Capabilities section uses standard JavaScript APIs supported in all major browsers.
Why do I see Bot/Crawler?
If the tool detects that the request comes from a bot or crawler (e.g., Googlebot, Bingbot), it will show Is Bot/Crawler as Yes and may display the bot name. This is useful for webmasters testing how their site appears to search engines. Normal users typically see No.
What is the architecture (32-bit, 64-bit, ARM)?
Architecture indicates the processor type. 64-bit is common on modern desktops and laptops. ARM and ARM64 are common on mobile devices and some newer laptops (e.g., Apple Silicon). The tool infers this from the user agent string.
Can I use this tool offline?
The tool requires an internet connection to load the page. Once loaded, the Browser Capabilities section runs entirely in JavaScript. The parsed user agent details come from the server, so you need to be online for the full experience.
What is touch support?
Touch support indicates whether your device has a touchscreen. The tool reads this from the navigator.maxTouchPoints property and the ontouchstart event. Mobile phones and tablets typically have touch support; desktops may or may not. The value helps developers decide whether to enable touch-based interactions.
How accurate is the browser detection?
The parsing logic recognizes the most common browsers and operating systems. Accuracy is high for Chrome, Firefox, Safari, Edge, Opera, and major OSes like Windows, macOS, Linux, Android, and iOS. Rare browsers, custom builds, or heavily modified user agents may not be fully recognized. The tool shows Unknown when it cannot identify a component.
What is the connection type?
Connection type (e.g., 4G, WiFi) is read from the Network Information API when available. It indicates the type of network connection your device is using. This API is supported in Chrome and some other browsers. It can help developers optimize content delivery based on connection speed.
Why are languages shown?
The languages field shows the preferred languages your browser sends in the Accept-Language header. It is parsed from the user agent or from the request. It helps websites serve content in your preferred language.
Search
Advertisement
