Video production support diagnostics: what to send

Your editing problem may happen only with one project, one camera format, or one step in the workflow. A useful support request helps someone reproduce that situation without making them guess which computer, file type, or export settings you used.

Start with the System Info test for a quick hardware overview. Then add the video app version, the exact action that fails, and the relevant project and media settings. You can share those details without sending private footage or an entire project.

Collect diagnostics support can use

1. Open System Info and note the processor, graphics, screen, battery, and network details it shows. Record the operating system and browser too. The test gives a browser-visible overview, not a complete service record for every component.
2. Write down the video editor's name and version, and whether it is a desktop app or runs in a browser. Include the operating system version. On Windows 11, find it in Settings › System › About. On a Mac, check System Settings › General › About.
3. Describe the affected media and project settings. Useful details include the file container and codec, resolution, frame rate, project timeline settings, and whether you use proxies. A proxy is a lower-resolution copy used to make editing smoother. Share only the properties support needs, not confidential video.
4. Write the steps that lead to the issue in order. For example: import a particular type of clip, add it to a timeline, apply an effect, then play or export. Include the exact error text if one appears and whether the problem happens every time.
5. Separate the symptom from your guess about its cause. Say whether playback stutters, the export stops, the image looks wrong, or the app closes. If you have a screenshot, check it for client names, file paths, email addresses, and other private information before sharing.

Include the time of the problem and whether the computer was on battery or plugged in. If the issue started after an update or a hardware change, note that too. These details help support compare runs made under similar conditions.

What the symptom can tell support

Playback stutters, but the exported file is smooth

This points to a problem during preview rather than necessarily a problem with the final video. The editor may be struggling to decode the source clips or draw effects in real time. Tell support whether the stutter appears with one clip, only after adding effects, or throughout the whole timeline. Mention whether proxies are enabled.

The export is slow or stops partway through

Report the export format, resolution, frame rate, and the approximate point where it slows or fails. Say whether the same project exports if you choose a lower resolution or a short range of the timeline. A browser graphics test cannot confirm that a particular editor, codec, or export setting is working correctly, so treat system details as context, not proof of the cause.

Colors, framing, or playback speed look wrong

State whether the issue appears in the editor preview, the exported file, or both. Include the project and export frame rates, the monitor in use, and whether the problem changes on another screen. On Windows 11, the display details are under Settings › System › Display › Advanced display. On a Mac, check System Settings › Displays.

The app closes, freezes, or shows an error

Give support the exact error text, the action immediately before it, and whether the app recovers or needs to be reopened. If the issue happens only with one project, say so. Avoid sending the full project unless the support team requests it through a suitable private channel.

Make the report easy to reproduce

1. Use one clear example. Choose a short, non-sensitive clip or a project that demonstrates the problem. If support needs a sample file, ask what format and size are appropriate before sending it.
2. Change one condition at a time. If you test with proxies on and off, or with another export preset, note each result separately. That makes it easier to see which change matters.
3. Record the power and display setup. Note whether the laptop was charging and which monitors were connected. Windows 11 power options are under Settings › System › Power & battery. On a Mac, check System Settings › Battery.
4. Keep the original error wording. Copy it accurately or take a screenshot. If you include logs, use the app's support instructions, and review the files for usernames, project paths, or other details you do not want to disclose.

A short report can follow this pattern: “The editor freezes when I scrub a 4K, 30 fps clip with an effect applied. It happens every time after importing the clip. Playback is normal before the effect. The editor version is [version], and the operating system is [version].” Add your System Info details and any exact error message below it.

Keep private production material private

Do not attach raw footage, client names, credentials, or a complete project by default. A screenshot can reveal more than the visible preview, including window titles and file paths. Crop it to the relevant area or cover private details before sharing. If support needs a project or sample clip, ask how to provide it securely and whether a short, anonymized example will be enough.

System Info helps describe the computer, but it cannot diagnose every editing-app setting or prove that a video file is healthy. A precise description of what you did, what happened, and what you expected is often the most useful diagnostic evidence.