User Agent Parser Online
Kisi bhi User-Agent string ko browser, engine, OS, device type, aur CPU mein break karein aapke browser mein. String aapke device par rehti hai.
User Agent Parser poori tarah aapke browser mein chalta hai. Jo User-Agent strings aap paste karte hain — aur aapke khud ke browser ki User-Agent — kabhi aapke device se bahar nahi jaate aur ArrayKit ko upload nahi hote.
URL Parser kholein
User Agent Parser ke baare mein
User Agent Parser ek raw User-Agent string ko readable fields mein badal deta hai taaki aap exactly dekh sakein ki ek client kya hone ka daawa karta hai. Koi bhi User-Agent header paste karein, ya apna khud ka load karne ke liye "Use my browser's" par click karein, aur yeh string ko browser name aur version, rendering engine, operating system aur version, device type (desktop, mobile, tablet, ya bot), aur jab string ek advertise kare to CPU architecture mein break kar deta hai. Yeh Windows, macOS, Linux, Android, aur iOS ya iPadOS par Chrome, Firefox, Safari, Edge, Opera, aur Samsung Internet ko recognise karta hai, aur Googlebot jaise crawlers ko flag karta hai. Yeh tab kaam aata hai jab aap server logs padh rahe hon, device-specific rendering debug kar rahe hon, analytics rules likh rahe hon, ya feature detection test kar rahe hon. Poori string aapke device par parse hoti hai.
Features
- Chrome, Firefox, Safari, Edge, Opera, aur Samsung Internet se browser name aur version extract karta hai
- Rendering engine (Blink, WebKit, Gecko, Trident, ya Presto) identify karta hai
- Windows, macOS, Linux, Android, aur iOS ya iPadOS par operating system aur version report karta hai
- Device ko desktop, mobile, tablet, ya bot ke roop mein classify karta hai
- Googlebot, Bingbot, aur doosre spiders jaise crawlers detect karta hai
- Jab string ise advertise kare to CPU architecture (x64, arm64, arm, ya x86) surface karta hai
- Ek-click "Use my browser's" button aapka khud ka navigator.userAgent load karta hai
- Poore parsed result ko formatted JSON ke roop mein copy karta hai
User Agent Parser kaise use karein
- Ek User-Agent string paste karein, ya apna khud ka load karne ke liye "Use my browser's" par click karein
- Table mein browser, engine, OS, device, aur CPU fields padhein
- Yeh dekhne ke liye device badge check karein ki yeh desktop, mobile, tablet, ya ek bot hai
- Kisi bhi single field ko copy karein, ya poore result ko JSON ke roop mein copy karein
Example
Input
Mozilla/5.0 (iPhone; CPU iPhone OS 17_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.3 Mobile/15E148 Safari/604.1
Output
Browser: Safari 17.3
Engine: WebKit
OS: iOS 17.3
Device: mobile
Ek iPhone Safari string iOS par Safari mein resolve hoti hai, ek mobile device ke roop mein classified.
Common errors aur troubleshooting
- Edge ya Opera Chrome ke roop mein report hota hai. — Chromium browsers compatibility ke liye Chrome token rakhte hain. Yeh parser pehle Edg aur OPR tokens check karta hai, isliye poori string paste karein — ek truncated UA jo un tokens ko drop kare Chrome ke roop mein padhega.
- Ek iPad tablet ke bajaye ek desktop ke roop mein dikhta hai. — Modern iPadOS Safari default se ek Macintosh User-Agent bhejta hai. Site ka mobile request mode enable karein ya ek iPad string paane ke liye iPad ka Request Mobile Website option use karein.
- Browser ya version field Unknown kehta hai. — String ek in-app WebView, ek niche browser, ya bina kisi recognisable token ke ek spoofed header se ho sakti hai. OS aur device fields jaha possible ho phir bhi bhare jaate hain.
- Ek real visitor ek bot ke roop mein flag hota hai. — Kuch libraries aur preview fetchers bot-like tokens (crawler, spider, HttpClient) include karte hain. Raw string ke against confirm karein; parser sirf woh report karta hai jo User-Agent advertise karta hai.
Aksar pooche jaane wale sawaal
- User Agent Parser ek User-Agent string se kya nikaalta hai?
- Yeh browser name aur version, rendering engine, operating system aur version, device type (desktop, mobile, tablet, ya bot), aur jab string ek include kare to CPU architecture report karta hai.
- Yeh Edge aur Opera ko Chrome se kaise alag batata hai?
- Edge aur Opera Chromium par bane hain, isliye unki User-Agent mein abhi bhi ek Chrome token hota hai. Parser generic Chrome token se pehle Edg aur OPR tokens check karta hai, isliye woh unhe sahi Edge ya Opera label karta hai.
- Device type ek User-Agent se kaise decide hota hai?
- Yeh string mein signals dhoondhta hai: iPad ya tablet tokens ka matlab tablet, ek Mobile token ya iPhone ka matlab mobile, ek known crawler token ka matlab bot, aur baaki sab kuch desktop par fall back karta hai.
- Kya yeh Googlebot jaise bots detect kar sakta hai?
- Haan. Yeh Googlebot, Bingbot, aur DuckDuckBot jaise named crawlers, plus generic bot, crawler, aur spider tokens match karta hai, aur ek milne par device type ko bot mark karta hai.
- Kya User Agent Parser mere browser ki real User-Agent padhta hai?
- Sirf tab jab aap "Use my browser's" par click karte hain, jo aapke navigator.userAgent ko box mein copy karta hai taaki aap use inspect kar sakein. Kuch kahin nahi bheja jaata — value locally parse hoti hai.
- Jo User-Agent string main paste karta hoon woh kahan process hoti hai?
- Poori tarah aapke browser mein. String kabhi aapke device se bahar nahi jaati aur ArrayKit ko upload nahi hoti, isliye aap private logs se UAs safely paste kar sakte hain.
Related tools
Saare ArrayKit tools