How I check what the browser says about my device
· 2 min read
A browser can reveal useful debugging context such as screen size, user agent hints, language, and platform, but not a complete identity.
The Device Information tool helps with the mechanical part, but I still check the result before using it somewhere real.
The simple idea
A browser can reveal useful debugging context such as screen size, user agent hints, language, and platform, but not a complete identity.
I use the tool to make the transformation visible: input on one side, output on the other, and a quick sanity check before I copy anything.
Step 1: Open the device information tool in the browser you are testing
Open the device information tool in the browser you are testing.
Step 2: Check screen and viewport values
Check screen and viewport values.
Step 3: Review language and locale settings
Review language and locale settings.
Step 4: Look at platform and user-agent hints
Look at platform and user-agent hints.
Step 5: Use the data to reproduce layout or compatibility issues
Use the data to reproduce layout or compatibility issues.
Step 6: Remember browsers may reduce or spoof some details for privacy
Remember browsers may reduce or spoof some details for privacy.
Step 7: Do not fingerprint users without consent
Do not fingerprint users without consent.
My checklist
Before I trust the result, I check:
- Open the device information tool in the browser you are testing.
- Check screen and viewport values.
- Review language and locale settings.
- Look at platform and user-agent hints.
- Use the data to reproduce layout or compatibility issues.
- Remember browsers may reduce or spoof some details for privacy.
- Do not fingerprint users without consent.
Small utilities are useful because they remove repetitive work. They are safest when the output is still reviewed.
Comments
Comments are welcome — please read the comment policy first. Powered by giscus and GitHub Discussions.