How to gather non-sensitive specs for a help forum

A help forum may ask for your computer specs before someone can troubleshoot a problem. You can provide useful details without posting a full system report or exposing information that identifies you or your device.

Use the System Info tool to check processor, graphics, screen, battery, and network details your browser can access. Then select only the facts that relate to the problem.

Gather the specs you need

1. Open System Info on the device you need help with. Review its processor, graphics, screen, battery, and network details. Write down only the items that could affect the issue.
2. Check your operating system and memory in its settings. In Windows 11, open Settings › System › About to find the Windows version, device specifications, and installed RAM. On a Mac, open System Settings › General › About. Avoid copying a serial number or other device identifier.
3. Check which browser you use and its version with Browser Info. Include this if the problem happens on a website or in a browser. It can help other people tell whether the issue may depend on a browser feature.
4. Make a short draft that includes the relevant details, what you were doing, and what happened. Keep the original report private, and copy only the selected facts into your forum post.

You do not need every value in every report. For a browser game that runs slowly, processor, graphics, browser, and operating system details may help. For a problem with a laptop display, screen resolution and whether an external screen is connected may be more useful.

What the specs mean

Processor and graphics

The processor handles general calculations, while the graphics processor draws images and video. These details can help when a game, video editor, or graphics-heavy website runs slowly. They do not prove that either part is faulty, and a browser-based report is not a full hardware diagnostic.

Screen details

Screen resolution describes the number of pixels in the display. It is useful for problems such as blurry pages, incorrect sizing, or a layout that does not fit. If you use more than one monitor, say which screen has the problem rather than posting a long list of every display detail.

Battery and network

Battery information can add context to a laptop power issue. Network details may matter if a site disconnects or loads slowly. Share the type of connection or the symptom when it helps, but do not post a public IP address, Wi-Fi password, or other connection identifiers. A system report cannot explain every cause of a slow internet connection.

Operating system, memory, and browser

The operating system version and browser version help others understand which software environment you are using. Memory, often called RAM, can matter when a computer slows down with many tabs or apps open. If you check RAM in a browser, treat its estimate as approximate: browsers get only a rounded hint about RAM size. Use your operating system settings for a reported installed-memory value, and say where you found it.

Check your draft before posting

1. Remove identifying numbers. Do not include serial numbers, product keys, account names, or other unique identifiers. A general device model is usually enough if the model is relevant.
2. Leave out network identifiers. Do not post passwords, a public IP address, or a screenshot that reveals your network name. If network behavior matters, describe whether you use Wi-Fi or a wired connection and what the connection does.
3. Crop or redact screenshots. A screenshot can reveal open tabs, email addresses, notifications, file names, or workplace information. If you need to attach one, crop it to the relevant area and cover private details before sharing.
4. Post only details that answer the question. A complete list of hardware rarely makes a forum answer better. Start with the operating system, browser if relevant, device type, and a few specs tied to the problem. Add more only if someone asks for a specific detail.
5. Check who can see the post. Assume a public forum post can be read and copied by people outside the discussion. If your issue involves a work or school device, follow your organization’s rules before sharing configuration details.

Why a shorter report is safer and clearer

A system report can contain details that have nothing to do with your question. Posting everything makes it harder for readers to spot the useful information, and screenshots may expose details you did not mean to share. A concise list also makes it easier to update your post if you discover that one of the facts was wrong.

For example, a useful post might say: “Windows 11 laptop, issue happens in my browser, 1920 by 1080 display, and the page freezes when I start a video.” Add the browser name and version if the problem is browser-specific. You usually do not need to include a serial number, exact network address, or a screenshot of the entire report.

Keep the full report on your device and share only the non-sensitive details needed to explain the problem.