Support can often narrow a Firefox problem with the installed version, relevant extensions or graphics details. Those facts do not require handing over the browser’s whole profile folder. Begin with a short description of the failing action and ask which configuration section is useful.

Capture the relevant snapshot

Open Firefox Help, More Troubleshooting Information, or enter about:support in the address bar. Note the browser version, operating system and update channel. A release build, an Extended Support Release and a development build can have different behaviour even when the browser icon looks the same.

Match the additional section to the problem. For a rendering issue, the Graphics information may help. For an extension problem, the add-on names and versions may matter. Record the snapshot date so support can distinguish it from information collected before an update.

The page also contains action buttons, including troubleshooting and refresh options. Reading configuration information does not require running those actions. Preserve the current evidence before making a change that could alter the problem.

Review the shareable copy

Mozilla provides Copy text to clipboard for a readable report and Copy raw data to clipboard for structured JSON. Use the format requested by the recipient. Paste into a private local draft first rather than directly into a public forum.

Mozilla says the profile-directory line is omitted from the copied report for privacy. That omission is not a guarantee that every other field is suitable for public posting. Review organisation details, modified preferences, paths and other identifying information before sharing the requested sections.

Include the exact symptom, time and steps already tried beside the configuration excerpt. If you omit unrelated sections, say so rather than presenting the excerpt as a complete report. Do not rename unexplained values or replace them with guesses.

Keep the original snapshot privately until the case is resolved. After any proposed change, repeat the failing task and record its result separately; a configuration report describes the environment but does not itself establish the cause or a successful repair.

Sources: Mozilla Support.