To generate a Streamlabs Desktop Diagnostic Report, open Settings > Get Support > Upload Diagnostic Report. When the upload completes, Streamlabs copies a diagnostic code to your clipboard; if you need it again, use the Copy button in the interface.
The code is what you share with Streamlabs support when they ask for the report. The report does not diagnose or fix a problem by itself, and generating one is separate from enabling additional crash reporting.
What the Diagnostic Report Is For
Streamlabs describes its Diagnostic Report as a built-in tool to help its support team and developers identify and resolve issues. You create it from inside Streamlabs Desktop, and the upload process gives you a code to pass on in your support conversation. It is a way to provide context for investigation, not a result that tells you what is wrong or changes your settings.
Streamlabs' report instructions describe information about the application's current state, including application details, settings, scenes and sources, and local computer and device details. The report can include platform usernames and the platform account currently connected, as well as past stream error logs and crash-log dates and times. That scope is broader than a crash record alone.
This matters when you decide whether the report is the right next step. If support asks for a Diagnostic Report, use the in-app upload and provide its code rather than trying to assemble a replacement from screenshots. If the question is about a particular error, also describe what you were doing when it occurred; the code does not replace a clear account of the problem.
The report is about Streamlabs Desktop and the computer where it is running. It is not a diagnostic report for YouTube's live control room or a separate streaming service. If your issue is instead that a YouTube broadcast appears offline after reconnecting, for example, that may call for checking the platform-side symptom as well; our guide to a YouTube radio stream showing offline after reconnecting covers that distinct situation.
Open Settings and Get Support
Start Streamlabs Desktop and wait until its main window is open. Find the gear icon for Settings, then open the Get Support section. The labels can be easier to follow if you keep the app open and move through the path one screen at a time: Settings, then Get Support, then the report upload control.
In Get Support, choose Upload Diagnostic Report. This is the ordinary report workflow. You do not need to enable additional crash reporting first, and you should not confuse this button with options that change what happens after a future crash.
If the app is not open, this exact path cannot be completed yet. Do not assume that a crash-specific procedure creates the same code; the separate crash guide covers additional crash information. First try to open Desktop normally, then return to the in-app route if it becomes available.
For a live channel operator, this is best done while the app is in the state support wants to investigate, if you can still open it. Avoid making unrelated changes just to reach the report button: settings or scenes altered before the report could change the context support sees. A short note with the time and symptom is useful to send alongside the code.
Upload the Diagnostic Report
Press Upload Diagnostic Report and allow the in-app process to finish. The report is uploaded as part of this action, and the resulting diagnostic code is copied automatically. Keep the interface open until the action has completed and you can see the code or its copy control.
The upload does not itself repair a scene, resolve an encoder error, or change a live broadcast. If you are currently on air, consider whether opening settings and carrying out troubleshooting actions could disrupt your production. The report is a support hand-off; it is not a reason to change a working stream during a broadcast unless you have decided that is necessary.
Once the code is available, paste it into the support conversation or ticket where Streamlabs asked for it. If you have not opened a support conversation yet, keep the code somewhere you can retrieve it while you create one. Do not invent a report URL or try to infer a destination from the code; follow the channel through which support is communicating with you.
The diagnostic code identifies the uploaded report for the support exchange. It is not the same thing as your YouTube stream key, and it should not be pasted into a public stream description or chat as if it were audience information. Share it in the intended support conversation. If you are unsure whether a message is genuinely from support, use the support channel you chose rather than forwarding diagnostic material to an unverified recipient.
Find the Copied Diagnostic Code
The automatic clipboard copy means there may be no separate download to find in your folders. After upload, click into the support reply box or a private note and paste the clipboard contents to check that a code was copied. If you need to avoid sending it immediately, paste it into a temporary private note first, then transfer it to the support thread when ready.
A clipboard only holds what was most recently copied. Copying a scene name, a link, or any other text after the upload can replace the diagnostic code. If a paste gives you something else, return to the report interface and use its Copy button again. Do not rely on a clipboard history unless you already know how your operating system manages it.
If you have already copied the code into a draft message, leaving Streamlabs Desktop will not remove that draft. Still, check the full pasted text before sending, especially if you have edited the message or copied other details in between. The purpose is to provide the code intact so support can use it to access the report.
It can help to write a brief note next to the code identifying the date and time you generated it, particularly if you create a fresh report after an earlier support exchange. Treat that note as your own context, not as a promise about how long Streamlabs keeps the report or how quickly someone will respond. The official instructions do not specify a response time or retention period.
Copy the Code Again
If the original clipboard copy has been overwritten, return to the report screen in Settings > Get Support and use Copy next to the diagnostic code. The Copy button is the intended way to copy it again; there is no need to upload another report simply because another clipboard action replaced the text.
Before copying, make sure the code shown belongs to the report you intend to share. Then press Copy, return to the support conversation, and paste it into your reply. You can verify that the paste looks complete before sending. Avoid adding spaces inside the code or retyping it by hand, since copying preserves the value as presented by the app.
If the interface has closed or you cannot locate the existing code, follow the available in-app route and see whether the report screen still presents a Copy control. If it does not, contact support in the channel you are using and explain that you cannot retrieve the code; do not invent a code or claim that a new upload is the same report. Keep your description factual so support can advise on the next step.
Share It With Support
Paste the diagnostic code in the ticket or conversation where Streamlabs support requested it. Put it in a clearly labelled line, for example, “Diagnostic code: [paste code]”, and include a concise description of the issue. A useful note says what you expected, what happened instead, and whether the issue is still occurring; it does not need to speculate about a cause.
If you can reproduce the problem, describe the steps without changing multiple settings at once. Include relevant context such as whether the symptom occurred while starting a stream, switching scenes, or reconnecting, but avoid putting passwords, stream keys, or unrelated account credentials into the message. The report code and a concise symptom description give support a clearer starting point than a long list of guesses.
Streamlabs states that the report includes information such as settings, scene and source configuration, connected platform usernames, and local system and device details. Its report article says that no identifying personal information is gathered other than usernames, and says information is stored and disposed of according to GDPR regulations and only Streamlabs employees can access report information. Those are Streamlabs' stated terms; consult its current report article if you want to review the latest wording before sharing. The article does not set out a particular retention duration or encryption method, so do not assume one.
Keep the code in the private support exchange rather than a public post. If you later discuss the problem in a creator group, describe the error without publishing the diagnostic code. This is a straightforward way to keep support material in the place it was requested and avoid exposing it to an audience that does not need it.
If You Cannot Generate a Report
If Streamlabs Desktop opens but Upload Diagnostic Report does not complete, note the exact message or behaviour and when it occurred. Try the normal in-app path again only if doing so is safe for your current stream and work; do not repeatedly alter scenes or output settings in an effort to force an upload. Send support the code if one was produced, together with the failure detail. If no code appeared, say that plainly.
If Desktop cannot open, you cannot navigate to Settings > Get Support to create the ordinary report. Streamlabs has a separate Desktop Crash Troubleshooting Guide for extra crash information. It describes enabling Enable reporting additional information on a crash from Settings > Get Support when the app opens, then restarting and sharing additional debug information after a subsequent crash. The guide also describes a fallback when the app cannot open. That is a different crash-investigation procedure, not a prerequisite for the standard Diagnostic Report.
Use the crash guide only when the issue is specifically a crash and the requested additional crash information is relevant. Its steps concern debug information associated with a subsequent crash; they do not provide the ordinary diagnostic code described here. If your immediate issue is a long-running YouTube channel, keep production recovery separate from the support report: a reporting action cannot restore a stream that has stopped. Our notes on keeping a StreamYard YouTube stream running 24/7 address continuity planning for that different workflow.
When a technical issue concerns the broadcast rather than the report upload, gather the precise symptom and keep your current configuration noted before making changes. For instance, a latency setting affects the delay and interaction trade-off in a YouTube live stream; it is not something to alter simply because a Streamlabs report is being requested. See the guide to choosing a YouTube Live latency setting for an FFmpeg stream for that separate decision.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Where do I find the Diagnostic Report in Streamlabs Desktop?
Open Settings, select Get Support, then choose Upload Diagnostic Report. The report is generated through the app; the code produced by the upload is what you share with support.
Is the diagnostic code copied automatically?
Yes. Streamlabs says the code is copied to your clipboard after the report upload. If another copy action has replaced it, return to the interface and press Copy to copy the code again.
Does the Diagnostic Report fix the issue?
No. It provides information for Streamlabs support and developers to investigate; it does not diagnose or fix the problem by itself. Include a short, accurate description of what happened with the code.
Is additional crash reporting required to upload a Diagnostic Report?
No. The ordinary report uses Settings > Get Support > Upload Diagnostic Report. Additional crash reporting is a separate workflow for gathering extra crash information, described in Streamlabs' crash troubleshooting guide.