Feedback and Bug Reports

Feedback and bug reports

ShadePlay guide › Help

How to report a problem, send a hardware report or suggest an idea, and what to attach (and read first).

Where to report

Open the feedback page and pick a form:

• Bug report: something doesn't work as it should. Say what happened and what you expected, and add your ShadePlay version (Settings > About ShadePlay), your Windows version, your graphics card and its driver version, and whether you use the simple or the advanced settings.
• Hardware report: how ShadePlay works on your graphics card, especially AMD Radeon and Intel Arc. Attach the encoder test's report (Testing AMD and Intel graphics).
• Idea / feature request: something ShadePlay should do. It is kept simple on purpose, so new options usually go into the advanced settings.

Questions go in Discussions, linked from the same page.

You need a free GitHub account to open an issue.

From the tray menu

Send feedback / report a bug in the tray menu opens the same page in your browser. It attaches nothing and sends nothing: you write the report and choose what to attach. If no browser opens, the settings window opens with the address: The browser didn't open. Go to https://github.com/baddo-baddo/ShadePlay/issues/new/choose yourself.

What to attach

The more a report shows, the faster it can be fixed:

• The logs, for anything that went wrong: %APPDATA%\ShadePlay\logs (paste that into the File Explorer address bar), or the advanced tray menu's Open logs folder, or Open logs on the Status page. shadeplay.log is the tray app (including each update step), engine.log the recorder, and update.log the last 50 update events (failed checks and updates, automatic updates).
• The encoder test's report for a hardware report: shadeplay-encoder-test.json from your desktop.
• A clip's .json file, when a clip is wrong (a wrong name, a missing track, the wrong length). Clips have one only when Saving > Write a clip info file (.json) next to each clip is ticked or an after-save command is set; tick it, then save a new clip when the problem happens again.
• A screenshot of the tray menu or the settings window, if it helps.

Read it first

These files are about your PC, and an issue on GitHub is public:

• Logs and .json files contain file paths with your Windows user name, and names of clips, games, windows and devices. Open them in Notepad, read them, and replace what you don't want public.
• Don't attach crash dumps (the files in %APPDATA%\ShadePlay\dumps) to a public issue: they can contain pieces of what was in the program's memory. Just say in the report that there is one.
• Don't attach clips you haven't watched: they show your screen and contain your sound and other people's voices.
• Screenshots of the Status page show your settings file's path.

Security problems

Please don't report a security problem in a public issue. Report it privately, as the security policy describes.

Thank you

ShadePlay is maintained by one person and was built with Claude, an AI model made by Anthropic. Clear reports are the fastest way to a fix, and reports from hardware nobody has tested yet are especially welcome.

---

Next: Glossary

See also: Troubleshooting · Privacy · Testing AMD and Intel graphics