Share system diagnostics without exposing private info

When a computer problem needs support, you may be asked for system details, browser information, or test results. Sending everything your device can report is rarely necessary, and a screenshot can reveal more than you intend.

Use TooLab's System Info and Browser Info to inspect useful details in your browser. Then choose only the information that helps explain the problem.

Gather the diagnostics you need

1. Open System Info and review the processor, graphics, screen, battery, and network details. Write down only fields that relate to the issue. For example, a screen problem may call for screen details, while a battery issue may need battery information.
2. Open Browser Info if the issue happens on a website or in a browser-based app. Check the browser version, engine, permissions, privacy settings, codecs, and supported features. Include the version and any relevant permission or feature status, not the entire report by default.
3. Describe the problem in plain language. Include what you expected, what happened instead, the steps that reproduce it, and whether it happens every time. Note the date and approximate time if the problem comes and goes.
4. Connect each detail to the symptom. For a camera issue, say whether the camera works in another app. For a browser feature problem, include the browser and the feature support result. Leave out unrelated hardware details.

These checks run in your browser. You can inspect the information before deciding what to send, and copy the relevant details into your support message yourself.

What the results mean

System details help narrow down compatibility

Processor, graphics, screen, battery, and network information can help support staff spot a possible compatibility issue or understand the device setup. A result describes what the browser can report, though. It is not a complete inventory of your computer, and it does not prove that a component is healthy.

In particular, a browser can provide only a rounded hint about RAM size, not the exact installed amount. If memory capacity matters, check it in your operating system and label it as a system-reported value. For more on the limits of browser reports, see what a browser-based hardware check cannot detect.

Browser details explain web app behavior

The browser version and engine can help explain why a website behaves differently after an update or in another browser. Supported features can show whether a web app's required browser capability is available. A missing feature does not necessarily mean your computer is broken. The site may need a newer browser or a different browser engine.

A permission status points to access, not hardware condition

If a camera or microphone permission is blocked, a website may be unable to use that device even when the hardware works. Permission status is useful when the problem is limited to a browser. It does not prove that an app has permission or that the device itself is faulty.

A normal result does not rule out an intermittent fault

A device can pass a quick check and still fail occasionally, especially if the problem depends on heat, movement, a cable position, or another app. Tell support when the fault occurs and what you were doing. A single normal reading is a snapshot, not a guarantee.

Share the report safely

1. Send the smallest useful set. Start with the device type, operating system, browser and version, the exact symptom, and steps to reproduce it. Add a test result only when it helps explain the problem.
2. Remove identifying details. Before sending a screenshot or copied report, look for names, email addresses, account details, device identifiers, and network information. Blur or remove anything support does not need. A screenshot can include open tabs, notifications, or other private content outside the diagnostic tool.
3. Do not share secrets. Support should not need your password, one-time sign-in code, recovery key, or private browsing history to diagnose ordinary hardware or browser problems. Do not include those in a report.
4. Check the destination. Use the support channel you already trust, such as the organization's official support portal. Avoid posting a complete diagnostic report publicly. If support asks for a particular field, ask why it is needed if the purpose is unclear.
5. Keep a copy of what you sent. Save the text of your report and note any changes you made to hide private details. This makes it easier to follow up without collecting the information again.

If you are checking camera or microphone access on Windows 11, use Settings › Privacy & security › Camera or Settings › Privacy & security › Microphone. On macOS, use System Settings › Privacy & Security › Camera or System Settings › Privacy & Security › Microphone. You can report whether access is enabled without sending a screenshot of every privacy setting.

When a focused test is more useful

If support is investigating one specific device, run a check for that device rather than sending a broad collection of details. A keyboard, screen, camera, microphone, or connection test can show whether the symptom appears outside the app where you first noticed it. Include the result and the conditions of the test, such as which device was connected or which browser you used.

Do not treat a browser result as proof of a physical repair need. A test can reveal symptoms, but it cannot inspect every driver, internal connection, or hardware fault. Share the evidence and let support decide the next diagnostic step.