Your Browser
{{ summaryTitle }}
{{ result.browser.name }} {{ result.browser.version }} {{ result.os.name }} {{ result.os.version }} {{ result.engine.name }}
  • {{ key }}
    {{ value }} 

                


            


        

    

                

                

                    

                        

                            Categories:
                                                            
                                    Development
                                
                                ,                                                             
                                    HTTP
                                
                                ,                                                             
                                    Validator
                                
                                                                                    

                        

                            Export to PDF
                            Fullscreen
                        

                    

                

            

        

    


    
    

        

        

            


                

                    

                    
                


                

                

                
            

        

    


    
    

        

  
  
A user-agent string condenses your browser’s name, version, operating system, and device class into one HTTP header shipped with every web request. Front-end engineers rely on these identifiers to negotiate feature support, deploy polyfills, and compile aggregate usage statistics that steer compatibility budgets across an ever-shifting landscape of devices and engines.

  
This tool parses that header with a fast, regex-driven library, then enriches the result with live screen resolution, language, and platform data from the browser runtime. The reactive engine instantly renders the combined profile as a tidy list, syntax-highlighted JSON, and copy-ready CSV, requiring no manual input or refresh whatsoever.

  
During cross-browser debugging you might paste the profile into a ticket to reproduce a rendering glitch, or confirm that enterprise clients still rely on legacy engines before retiring a costly shim. Do not rely on user-agent data alone to enforce authentication or security rules because spoofing and masking remain trivial tactics.






  
Technical Details:


  
  
User-agent detection maps a free-form header string to structured fields including browser family, major version, operating system, device vendor, and rendering engine. The parser applies thousands of ordered regular-expression rules curated from vendor changelogs and community fingerprints. When merged with live navigator properties, the technique yields a comprehensive execution context that guides progressive enhancement, A/B experiments, performance budgets, and analytics segmentation. It avoids network calls and respects privacy by running entirely in the client.


  
  
    
    
  1. Read the User-Agent header exposed by the runtime.
    2. 
    
  2. Apply a priority-ordered rule set to extract browser, engine, OS, and device tokens.
    3. 
    
  3. Query the runtime for navigator.language, navigator.platform, and screen dimensions.
    4. 
    
  4. Merge all attributes into a single immutable object for display, copy, or download.
    5. 
  


  
  

    

      
        
ParameterMeaning

      
      
        
BrowserFamily and full version extracted from the header.

        
EngineRendering engine that actually executes HTML, CSS, and JS.

        
Operating SystemDesktop or mobile OS name plus version.

        
Device TypePhone, tablet, console, smart-TV, or desktop.

        
ResolutionCurrent screen width × height in CSS pixels.

        
LanguagePrimary locale reported by the runtime.

        
User-AgentRaw header string displayed for copy or audit.

      
    

  

  
The values above help decide whether to serve modern bundles, polyfilled fallbacks, or strict legacy builds.


  
  
    
    
  • User-Agent – mandatory input captured automatically.
    • 
    
  • Navigator extras – language, platform, and vendor hints.
    • 
    
  • Screen metrics – width and height at evaluation time.
    • 
  


  
  

  
  
    
    
  • Relies on accurate vendor tokens; obfuscated headers degrade fidelity.
    • 
    
  • Assumes navigator.userAgent is accessible and not overridden.
    • 
    
  • Ignores feature detection; it classifies environment only.
    • 
    
  • Version mapping mirrors community data; minor releases may lag.
    • 
  


  
  
    
    
  • Custom Chromium builds may report unknown engine versions.
    • 
    
  • Proxy services that rewrite headers can mask original devices.
    • 
    
  • Embedded web-views often omit vendor suffixes, confusing detection.
    • 
    
  • Window resize after load will not recalculate resolution automatically.
    • 
  


  
  
Classification methods reflect RFC 7231 header semantics, W3C HTML 5.2 processing model notes, and published vendor compatibility matrices.


  
  
All parsing occurs locally; no data leaves the browser, aligning with GDPR and CCPA privacy principles.






  
Step-by-Step Guide:

  
Follow these steps to capture and share an exact browser profile.

  
    
    
  1. Open the page; the profile loads instantly.
    2. 
    
  2. Review the Info tab for human-readable fields.
    3. 
    
  3. Switch to JSON for the full object when debugging APIs.
    4. 
    
  4. Click Copy CSV or Download JSON to attach data to tickets.
    5. 
  






  
FAQ:


  

    Is my data stored?
    
No. Everything is parsed and rendered within your browser; nothing is transmitted to any server.

  


  

    Why does the browser name look wrong?
    
Some privacy tools randomise or truncate the header, which prevents accurate identification. Disable the masker and reload to verify.

  


  

    Does private browsing change results?
    
Incognito modes modify storage but rarely alter the header itself. You should see the same profile unless an extension intervenes.

  


  

    Can I simulate a mobile device?
    
Yes. Use your developer tools to override the user-agent string, then refresh this page to view the simulated profile.

  


  

    How do I share findings?
    
Copy the CSV or JSON output and paste it into issue trackers, chat threads, or email; the structure remains intact.

  






  
Glossary:

  

    
User-Agent
HTTP header identifying client software.

    
Rendering Engine
Core component that turns HTML and CSS into pixels.

    
Navigator
Browser API exposing runtime metadata.

    
Polyfill
Script that replicates modern features in old browsers.

    
Viewport
Logical window where the document is displayed.