Browser and System Information
Review environment values this browser exposes to the current page. Separate the User-Agent string from low-entropy Client Hints, then inspect language, cookie settings, touch points, exposed logical processors, approximate memory and API presence. Collection starts only when you press Read information; it makes no network probes or camera, microphone or location permission requests.
Key features
- Explicitly read the current environment on request
- Separate User-Agent from low-entropy Client Hints
- Distinguish exposed APIs, missing APIs and unreadable values
- Preview the entire JSON before copying and clear it when finished
How to use
- Press Read information to capture values exposed by the current browser.
- Review the string, coarse device, Client Hints and API sections separately.
- Press Read again after changing a browser setting.
- Review the JSON before copying it, then Clear when finished.
Use cases
- Compare low-entropy Client Hints across browsers
- Prepare a local API-presence report for a support request
- See which coarse system values privacy settings reduce or hide
Frequently asked questions
How does this differ from the IP information page?
It does not look up IP addresses, locations or network providers. It separates low-entropy Client Hints and API presence from the User-Agent string, with a reviewable JSON report and no network probes.
Does API exposed mean the feature will work?
No. It means an object or function exists. Secure context requirements, browser policy, permissions and connected devices can still prevent a call from succeeding. This tool does not execute those capabilities.
Why does Client Hints contain an unusual brand?
Browsers may deliberately include GREASE brands or reduced versions. Values are shown as provided without guessing which brand is genuine. No high-entropy details are requested.
Are CPU and memory values exact specifications?
hardwareConcurrency is the number of logical processors exposed to the browser, not necessarily the physical core count. deviceMemory is a privacy-reduced and rounded estimate in GiB. Missing values remain unknown.
Does cookieEnabled mean all storage will work?
No. It is a browser-reported flag, not a test of a particular cookie or third-party storage policy. IndexedDB is checked only for API presence; no database is opened and no data is written.
Is the report sent to a server automatically?
This tool creates no server requests or analytics events from the values it reads. The JSON remains on this page until you copy it to the clipboard. Review the included browser and system details before sharing it.
Privacy
Values are read in the current page only after you press Read information. They are not sent to a server or analytics event or written to storage. The tool does not request permissions or high-entropy hints, enumerate devices or fonts, or collect WebGL identifiers.
Comments & questions