User Agent Detection Analysis Tool

Detect and analyze current and custom User Agent information, identifying details such as operating system, browser, and device type.

Bug report

Browser execution mode: Your data is processed in your browser and is not uploaded to the server.

Speed and Stability: Processing speed depends on your device and browser. For large batch work, the desktop version may be more stable.

Loading tool, please wait...

If the online tool fails to load or run, try the desktop tool.https://tools.yikeaigc.com/

Tool Usage

Return to old version

Current source Current browser

Browser Waiting to analyze

System Waiting to analyze

Device Waiting to analyze

Set analysis method

Set the source and parsing options before input and processing.

Set up before processing

Source Switch anytime

Current browser Read available User Agent and UA-CH info from the current page. Custom string Paste any User Agent for log or compatibility troubleshooting. Common templates Choose from desktop, mobile, WebView, crawler, and other templates. Batch analysis Paste multiple UAs by line and export results as a data file.

Parsing options Saved locally

Analyze as you type Auto-refresh results when custom or batch content changes. Prefer UA-CH enrichment When supported, add architecture, bitness, platform version, and more. Show product tokens Show product/version tokens in the UA to help troubleshoot spoofing or compatibility logic.

Current User Agent Checking UA-CH

Reading...

Enter content to analyze

Use current UA, paste custom content, load a template, or add batch lines.

Sample data supported

Confirm the source and options in Step 1, then click Analyze. In batch mode, enter one UA per line. “Name | UA string” is also supported.

Current browser input No manual input needed

Reading...

Custom User Agent

0 chars

Template category

User Agent template

Select a template

Batch User Agents

0 lines to analyze

Pending 1

Detected template 0

Last analyzed Not run

View results

Results include browser, system, device, engine, architecture, WebView, crawler, and compatibility notes.

Data export available

Items analyzed 0

Mobile/tablet 0

Crawler/bot 0

Avg. confidence 0%

Results list Waiting to analyze

Please run analysis first. Results will appear here.

Details Not selected

Click a result on the left to view the full analysis.

Instructions

Software Usage Instructions

Set the analysis method: First choose Current Browser, Custom String, Common Templates, or Batch Analysis, and enable real-time analysis, UA-CH supplementation, and product token display as needed.
Enter the User Agent: Current Browser mode reads it automatically; Custom mode lets you paste a single UA; Template mode lets you choose examples such as desktop, mobile, WebView, and crawler; Batch mode supports one UA per line.
Use the batch format: For batch analysis, you can paste multiple lines of UAs directly, or use the “Name | UA string” format to distinguish sources in the results.
Start analysis: After clicking “Start Analysis,” the tool identifies the browser, version, system, device, engine, architecture, WebView, crawler characteristics, and compatibility tips.
View results: On the results page, click any item on the left to view the full UA, UA-CH information, product tokens, recognition confidence, and related tips.
Save and export: You can save commonly used settings, or copy or export analysis results as JSON, CSV, or TXT files for test records, log organization, and data analysis.

FAQ

A: A User Agent is an identifying string sent by a client when accessing a website. It usually contains information such as the software name, version, operating system, device type, and compatibility fragments.

A: UA-CH is structured client hint information that can supplement fields such as platform, architecture, bitness, model, and version in supported environments, helping support traditional UA detection.

A: Many Windows 11 environments still display Windows NT 10.0 in the traditional UA, so the UA string alone cannot reliably distinguish them. UA-CH or other environment information is needed.

A: WebView means the page may be running in an in-app web view, such as WeChat, Android WebView, or another app’s built-in browsing environment. Some capabilities may differ from a standalone browsing environment.

A: Batch analysis is suitable for processing access logs, test samples, crawler identification records, and multi-device compatibility troubleshooting. Put one UA on each line, and you can also add a name to make them easier to distinguish.

A: Many UAs contain compatibility fragments, spoofing markers, or legacy fields, such as like Gecko, Chrome/Safari compatibility markers, etc. The tips help determine whether these fields may affect parsing.