Current snapshot
{{ summaryTitle }}
{{ summarySecondaryLine }}
{{ badge.value }}
Check goal:
{{ focusHelperText }}
{{ experienceHelperText }}
{{ probeStorageEnabled ? 'On: test storage writes and quota in this browser session.' : 'Off: skip storage writes and quota estimation.' }}
{{ probeStorageEnabled ? 'On' : 'Off' }}
{{ includeRendererHint ? 'On: include renderer/vendor when exposed.' : 'Off: keep graphics details coarse.' }}
{{ includeRendererHint ? 'On' : 'Off' }}
Section Item Detail Copy
{{ row.section }} {{ row.item }} {{ row.detail }}
Signal Value Copy
{{ row.key }} {{ row.value }}
Section Signal Detail Copy
Compatibility verdict {{ compatibilityVerdict.value }} {{ selectedExperienceLabel }}. {{ compatibilityVerdict.detail }}
Compatibility action Action note {{ note }}
Compatibility signal {{ row.value }} {{ row.label }} {{ row.hint }} {{ row.detail }}
Section Signal Detail Copy
Privacy verdict {{ privacyVerdict.value }} {{ rendererPolicyLabel }}. {{ privacyVerdict.detail }}
Privacy action Action note {{ note }}
Privacy signal {{ row.value }} {{ row.label }} {{ row.hint }} {{ row.detail }} 

                    

                


            


        

    

                

                

                    

                        

                            Tags: Devtools, Diagnostics, HTTP
                        

                        

                            
                            
                        

                    

                

            

        

    


                    
        

        

        

            

            
        

        


                    

                

                

                    

                                                                                

                                
                                    
                                        Application Programming Interface (API) Testing Tool
                                                                                    Test an HTTP API from your browser with method, headers, auth, body modes, cURL import, CORS clues, response traces, and saved presets.
                                                                            
                                    
                                
                            

                                                                                

                                
                                    
                                        What Is My Screen Resolution
                                                                                    Check your screen resolution, viewport, DPR, breakpoint fit, and capture size with density warnings when you enter display diagonal.
                                                                            
                                    
                                
                            

                                                                                

                                
                                    
                                        What Is My Internet Protocol (IP) Address?
                                                                                    Check your public IP address with IPv4/IPv6 visibility, ASN, reverse-DNS, location, and source agreement clues for support tickets.
                                                                            
                                    
                                
                            

                                                                                

                                
                                    
                                        cURL Command Generator
                                                                                    Build a cURL command from method, URL, headers, auth, body, and transfer flags, with shell-aware quoting, import parsing, and warnings.
                                                                            
                                    
                                
                            

                                            

                

            

        
                                                                                                                                                                                                                                                        
        

        

            
            

                Customize

                

                    

                        

                            
                            
                        


                        

                            
                            
                        


                        

                            
                            
                        

                    


                    

                        Advanced

                        

                            

                                
                                

                                    
                                    
                                

                            


                            

                                
                                

                                    
                                    
                                

                            


                            

                                
                                

                                    
                                    :
                                    
                                

                            


                            

                                
                                

                                    
                                    
                                

                            


                            

                                

                                    
                                    
                                

                            


                            

                                

                                    
                                    
                                

                            


                            

                                
                                
                            


                            

                                
                                
                            

                        

                    

                

            

            
        


        

            
            
            
        


        
        

    

    

        

  

    
A browser support report is useful only when it describes the session that actually produced the problem. The phrase "Chrome on macOS" can hide the details that decide whether a sign-in flow persists, a dashboard chart renders, a clipboard button works, or a responsive layout switches into a compact view. Browser name and version are only the start.


    
Modern websites read a mix of identity, capability, display, storage, graphics, preference, and privacy signals. Some of those values come from long-standing browser fields such as the user-agent string. Others come from feature checks, storage probes, display metrics, network hints, User-Agent Client Hints, and privacy preferences such as Global Privacy Control or Do Not Track. Two windows can show the same browser family and still behave differently because one is private, resized, signed into a different profile, blocked by an extension, missing a secure context, or using a graphics path that cannot open WebGL.


    

      

        
        
          

            Question
            Signals that help
            Common mistake
          

        
        
          

            Why does support need more than a browser name?
            Browser version, operating system, engine, viewport, time zone, language, and device hints.
            Assuming every profile with the same browser name exposes the same environment.
          

          

            Why does an app work in one window but fail in another?
            Secure context, cookies, local storage, session storage, IndexedDB, service worker support, and private-window behavior.
            Blaming the website before checking whether the browser allowed storage and modern APIs.
          

          

            Why are maps, charts, or media broken?
            WebGL, WebGL 2, WebGPU presence, device pixel ratio, color settings, Save-Data, and optional renderer detail.
            Treating a loaded page as proof that its graphics path is healthy.
          

          

            How much detail is safe to share?
            Fingerprint surface, high-entropy User-Agent Client Hints, time zone, language list, hardware hints, screen metrics, and renderer data.
            Posting a full diagnostic report publicly when a private support channel would be more appropriate.
          

        
      

    


    

      Browser session signals grouped by identity, capability, storage, and privacy
    


    
The snapshot is temporary by nature. A browser update can change the user-agent string. A private window can change storage behavior. Resizing the window changes viewport and breakpoint clues. A network change can alter Save-Data or connection hints. Enabling optional renderer detail can help diagnose a GPU-specific chart failure, but it also makes the report more specific.


    
A browser diagnostic result is not an identity proof, a privacy guarantee, or a complete website test. It is a structured way to capture the browser-side conditions that often explain why one session fails while another succeeds.

  






  

    
How to Use This Tool:


    
Run the check in the same browser profile, privacy mode, network, and window size where the behavior matters. Changing those conditions before testing can remove the clue you are trying to capture.


    
    
      
  1. Choose a Check goal. Support opens with a handoff brief, Compatibility moves attention to API and feature clues, and Privacy emphasizes exposure and persistence signals.
    2. 
      
  2. Select a Compatibility target. Use General websites for ordinary browsing issues, Sign-in or workspace apps when login state or saved settings matter, and Media or graphics-heavy pages when charts, maps, canvases, or video are involved.
    3. 
      
  3. Keep Probe storage access on when cookies, local storage, session storage, IndexedDB, quota, or persistence could explain the issue. Turn it off if you only need identity, display, runtime, and privacy signals.
    4. 
      
  4. Leave Include renderer hint off for ordinary support notes. Turn it on only when graphics troubleshooting needs WebGL vendor or renderer detail.
    5. 
      
  5. Use Support Brief for a compact ticket summary. Use Browser Signal Ledger when a support engineer needs exact values such as viewport, device pixel ratio, language, time zone, storage status, and User-Agent detail.
    6. 
      
  6. Check Compatibility Signals and Capability Readiness when a site fails to load, sign in, save settings, copy text, or render graphics. Check Privacy Surface and Exposure Signal Mix before sharing a detailed report outside a trusted support channel.
    7. 
      
  7. If a snapshot error appears, refresh the page and retest in a simpler context. Embedded pages, strict privacy settings, extensions, or a blocked storage area can prevent one of the probes from completing.
    8. 
    


    
For a fair comparison, test the failing and working browser contexts with the same goal, target, storage-probe setting, renderer setting, and window size.

  






  

    
Interpreting Results:


    
Start with the summary badges, then confirm the cause in the matching table. Ready for current sites means the checked browser-side features are broadly present. Usable with caveats means at least one signal may explain fallback behavior. Compatibility gaps likely means a high-impact feature group is missing or blocked in the current session.


    
    
      
  • Storage ready, mixed, or restricted: Use this clue first for repeated sign-in prompts, lost settings, reload problems, and workspace apps that depend on IndexedDB or service workers.
    • 
      
  • Secure context: Treat an insecure context as a strong compatibility warning for clipboard writes, some storage reporting, and features that browsers restrict to trustworthy origins.
    • 
      
  • Graphics path: A WebGL or WebGL 2 result confirms that a graphics context opened, but it does not prove every chart, map, shader, or video path will work.
    • 
      
  • Privacy verdict: Lower, balanced, and high exposure describe share sensitivity. They do not measure anonymity or say whether a site follows a privacy preference.
    • 
      
  • Readiness and exposure charts: The 0 to 100 values compare signal groups inside this report. They are not browser market scores or standards-body ratings.
    • 
    


    
A useful confidence check is side-by-side reproduction. If one context works and another fails, compare Browser Signal Ledger, Compatibility Signals, and Privacy Surface before changing the website or support ticket.

  






  

    
Technical Details:


    
Browser diagnostics are built from observable client signals, not from a single master identifier. Some signals describe what the browser claims to be, such as user-agent data, engine, operating system, platform, and Client Hints. Other signals describe what the session can do, such as opening storage, using modern JavaScript APIs, creating a WebGL context, or writing to the clipboard.


    
Feature checks are often more reliable than browser-name checks because support changes over time and privacy settings can hide or alter details. A browser can parse as a current engine while storage is blocked, a graphics context is unavailable, or the page is not in a secure context. That is why a practical diagnostic report combines identity, runtime, storage, display, graphics, preference, and exposure signals.


    
Signal Map

    

      

        
        
          

            Signal family
            What it covers
            Why it affects interpretation
          

        
        
          

            Browser identity
            Browser name and version, engine, operating system, device profile, raw User-Agent, brands, and high-entropy User-Agent Client Hints when available.
            These values help reproduce browser-specific bugs and also add detail to the fingerprint surface.
          

          

            Display and input
            Viewport, screen size, device pixel ratio, color depth, color scheme, color gamut, reduced motion, reduced data, pointer, hover, and touch support.
            Responsive layout, image density, animation choices, and pointer behavior can change from these values alone.
          

          

            Runtime APIs
            Secure context, Fetch, AbortController, ResizeObserver, IntersectionObserver, module scripts, CSS Grid, WebAssembly, service workers, clipboard writes, and share support.
            Current app flows often assume these APIs exist, especially in authenticated or dashboard-style pages.
          

          

            Storage and persistence
            Cookies, local storage, session storage, IndexedDB, storage quota estimate, and persisted-storage status.
            Storage availability affects sign-in, saved preferences, cached data, and reload behavior.
          

          

            Graphics path
            WebGL, WebGL 2, WebGPU interface presence, and optional WebGL vendor or renderer detail.
            Charts, maps, canvas drawing, and media-heavy pages can fail or degrade when the graphics path is restricted.
          

          

            Privacy preferences and exposure
            Global Privacy Control, Do Not Track, Save-Data, connection hints, hardware hints, time zone, language list, and renderer disclosure.
            These values affect both site behavior and how carefully a diagnostic report should be shared.
          

        
      

    


    
Rule Core

    
The compatibility verdict comes from ordered rules across five checked groups. The most severe group sets the final verdict, so one limited result can move the whole browser snapshot to Compatibility gaps likely.

    

      

        
        
          

            Checked group
            Ready condition
            Caution condition
            Limited condition
          

        
        
          

            Core web runtime
            At least 6 of 7 runtime checks pass.
            4 or 5 runtime checks pass.
            Fewer than 4 runtime checks pass.
          

          

            Storage and session state
            All 4 storage/session checks pass.
            2 or 3 checks pass, the storage probe is off, or a workspace target lacks secure context.
            Fewer than 2 checks pass.
          

          

            Secure-context features
            Secure context is on and clipboard write support is available.
            Secure context is on but clipboard write support is limited.
            Secure context is off.
          

          

            Graphics path
            WebGL opens a context and Save-Data is not pushing a lighter path.
            WebGL is absent for general targets, or Save-Data suggests lighter media behavior.
            A graphics-heavy target cannot open WebGL.
          

          

            Layout and input profile
            The active viewport is at least 360 pixels wide.
            The active viewport is narrower than 360 pixels.
            No separate limited state is assigned for this group.
          

        
      

    


    
Chart scores are lookup values for the current report. They make the visual comparison readable, but they do not create a formal browser rating.

    

      

        
        
          

            Signal state
            Readiness score
            Exposure score
            Meaning
          

        
        
          

            Ready, available, or lower exposure
            100
            20
            The feature is present, or the privacy row exposes comparatively less detail.
          

          

            Caution or partial
            65
            45
            The browser is usable, but the signal may explain fallback behavior.
          

          

            Limited
            30
            50
            A meaningful capability is missing or constrained.
          

          

            Blocked
            15
            50
            A probe or feature is unavailable in this browser context.
          

          

            Moderate exposure
            45
            60
            Several identifying signal groups are visible together.
          

          

            High exposure
            45
            90
            The report includes enough detail that it should be shared carefully.
          

        
      

    


    
High-entropy User-Agent Client Hints deserve special care. They can reveal details such as full browser version, architecture, bitness, form factor, model, or platform version when the browser and policy allow them. That extra detail may solve a support reproduction problem, but it also narrows the set of sessions that look alike.


    
Privacy preferences are not shields against every signal. Global Privacy Control and Do Not Track can communicate user preference to cooperative sites, while the browser can still expose screen, storage, graphics, hardware, language, and time-zone clues through ordinary web APIs.

  






  

    
Privacy Notes:


    
The snapshot is generated from the current browser session. The storage probe tests whether simple local storage, session storage, and IndexedDB operations work, then reports availability and quota-style information. It does not need account content, browsing history, or page passwords to create the report.


    
    
      
  • Review Support Brief before sending it, especially when it includes time zone, language, screen size, hardware hints, or User-Agent detail.
    • 
      
  • Keep Include renderer hint off unless GPU-specific troubleshooting needs the WebGL vendor or renderer value.
    • 
      
  • Treat a high exposure result as a sharing caution, not as proof that a website is tracking you.
    • 
      
  • Retest after changing privacy settings, extensions, network, or window size because those changes can alter the visible signals.
    • 
    

  






  

    
Worked Examples:


    
A workspace app asks for sign-in after every reload. With Check goal set to Compatibility, Compatibility target set to Sign-in or workspace apps, and Probe storage access on, the Storage and session state row may show Caution or Limited. If Browser Signal Ledger also shows blocked IndexedDB or unavailable storage quota, the support note should focus on the browser context before the app team investigates account state.


    
A dashboard loads tables but charts stay blank on one laptop. With the graphics target selected, Graphics path can show whether WebGL opened a context. If the result is Limited because a graphics-heavy target cannot open WebGL, the next check is the graphics driver, browser profile, hardware acceleration setting, or a stricter privacy mode. If renderer detail is requested, share it only with the support team handling the graphics issue.


    
A privacy comparison between a normal window and a private window should keep the same viewport size and target. If the normal window reports High exposure with 8 or more identifying signal groups while the private window reports Balanced exposure, compare the Fingerprint surface, User-Agent disclosure, and Graphics disclosure rows before drawing conclusions. A lower result may reflect hidden renderer detail or fewer high-entropy hints, not full anonymity.


    
A support ticket for a narrow mobile layout should include the Viewport, Screen resolution, and Device pixel ratio values. A 340 pixel viewport can trigger a compact layout even on a laptop, so the visible window size may matter more than the device category.

  






  

    
FAQ:


    

      Does this identify my exact device?
      
No. The report describes browser-visible signals from the current session. Some combinations can be specific enough to share carefully, but the result is not a device serial number or account identity check.

    


    

      Why is the browser name not enough for support?
      
Many failures depend on storage access, secure context, viewport, graphics support, privacy settings, and User-Agent Client Hints. Two sessions with the same browser name can expose different values.

    


    

      What does the storage probe do?
      
It checks whether local storage, session storage, and IndexedDB accept simple operations in this browser session, then reports availability and storage estimate details when the browser provides them.

    


    

      Why is renderer detail optional?
      
WebGL renderer detail can help diagnose GPU-specific chart, map, or canvas failures. It can also make the report more unique, so the default keeps that hint off.

    


    

      Does Global Privacy Control or Do Not Track hide all signals?
      
No. Those preferences can communicate a privacy request, but the browser may still expose feature, display, storage, graphics, language, and time-zone signals.

    


    

      What should I do if the snapshot fails?
      
Refresh the page, turn off the optional storage probe if storage is blocked, or retest in a simpler browser context. If the issue only happens in the strict context, include the snapshot error in the support ticket.

    

  






  

    
Glossary:

    

      
User-Agent Client Hints

      
Structured browser and platform details that can expose coarse or high-entropy information depending on browser support and policy.

      
Secure context

      
A browser context that meets security requirements for sensitive web APIs, usually HTTPS or a trustworthy local origin.

      
IndexedDB

      
A browser storage system commonly used for larger app data, saved workspace state, and cached records.

      
WebGL

      
A browser graphics API used by many charts, maps, canvases, and interactive media features.

      
Global Privacy Control

      
A browser preference signal that can communicate a request not to sell or share personal data where supported.

      
Fingerprint surface

      
The combined set of visible browser, device, display, storage, language, graphics, and preference signals that can make a session more distinguishable.

    

  






  

    
References: