Troubleshooting editor performance and playback issues

Under certain conditions, Descript projects can get slow, or laggy. This article will help you troubleshoot those issues and offers some tips on structuring your project to avoid performance issues in the first place.

General troubleshooting tips

Reduce the size and complexity of your projects
This is the largest cause of performance issues. Projects get slow when they have a combination of:
  1. Several GB of files
  2. Lots of edits in a composition or sequence
  3. Lots of compositions
  4. Long compositions and/or sequences

There’s no hard and fast rule here — it is also highly dependent on the age of your computer and the availability of its system resources — but if you’re noticing performance declines as your projects get bigger or more complex, this might be the issue. Try breaking out your compositions and files across multiple projects, or dividing a single complex/long composition or sequence into several and see if that helps.

Click here to learn how to copy a composition to a different project.

Close your other apps
Try closing other applications, especially apps that use a lot of your computing bandwidth, like your web browser.
Make sure you have enough free hard drive space
Descript gets slow if you have less than 20GB of available hard drive space. Click to learn about managing storage on Mac or to learn about managing storage on Windows.
Make sure your computer is powerful enough
Make sure your computer meets our recommended system requirements.
Try disabling effects
Effects (e.g. audio effects like the limiter, compressor, parametric EQ, or flanger) can cause CPU use spiking that results in glitchy playback. Try disabling them while editing to see if it resolves your issue. If it does, you can always edit with effects disabled and turn them on when you're ready to export.
Disable Grammarly
Grammarly has been known to cause issues with Descript and it will use a lot of resources trying to read your script while you make edits. We recommend you disable Descript from within the Grammarly app or just keep it closed.
Disable McAfee
We have found that running McAfee antivirus can cause performance issues with Descript. To avoid these issues, consider disabling McAfee while using Descript.
Enable optimized media files
By default, when you add audio or video files to Descript, we create new “proxy” versions that are optimized for playback performance (we also keep the originals and use them for export).

If you’ve disabled optimized assets, then it’s possible that the unoptimized files are causing your performance issues, and you should manually create optimized files for any high-resolution and bitrate files.

Diagnosing problems with your GPU (graphics card) in Windows
Make sure your GPU drivers are up-to-date. If your GPU drivers are up-to-date but it has been more than two years since the last update, then you’ll probably still have issues and we don’t recommend recording video with Descript and that specific GPU.
Use the fastest GPU on your machine
Currently, Descript only supports using one GPU at a time. Your machine might be defaulting to the slower one. This usually happens when an Intel chip with onboard graphics is being used versus the discreet (not on a CPU) GPU. Generally, this occurs on laptops that use the on-board GPU in low power mode.


Setting the default GPU on macOS
  1. Open Activity Monitor and navigate to Window > GPU History
  2. Start exporting a composition.
  3. Observe in the Activity Monitor which GPU is being used.

Apple Silicon chips have integrated GPUs, so they should always default to the correct and fastest GPU

Once you have determined which GPU is in use, and if it is not the discrete GPU in the machine (usually an AMD), you can manually override this by turning off Automatic Graphics Switching.


Setting the default GPU on Windows
  1. Open Task Manager (ctrl-alt-delete) and open the Performance tab.
  2. Start exporting a composition.
  3. Observe in the Task Manager which GPU is being utilized.
  4. If the GPU being used is not the one you want, you can switch it via the Graphics Card’s Settings.
Switching to the dedicated NVIDIA GPU
  1. Open the NVIDIA control panel. One way to do this is by right-clicking on an empty space on the desktop and selecting the NVIDIA control panel.
  2. Navigate to 3D settings > Manage 3D settings.
  3. Open the Program settings tab and select your app from the dropdown menu.
  4. Select the Preferred graphics processor for this program from the second dropdown menu. Your NVIDIA GPU should appear as a "High-performance NVIDIA processor"
  5. Save your changes.
Switching to the dedicated AMD GPU
  1. Open the AMD Radeon settings. One way to do this is by right-clicking on an empty space on the desktop and selecting AMD Radeon settings.
  2. Navigate to System > Switchable graphics.

  3. Locate your app using the search bar.

  4. Select the app and choose High Performance from the drop-down menu. The change will take effect the next time you load the app. 

Other potential issues and solutions

Video not showing up in canvas
If you see a blank screen in the canvas:
    • Your script layer may not be present. Click in the white space outside the canvas, look at the layer list in the Property Panel, then select the script layer and confirm opacity is toggled on.
    • It could be because no visual layers are present. Once you add a video or visual, it will appear on the canvas.

If you don’t see the canvas at all, switch to a video composition which you can do from the File menu.

Low-quality video previews in canvas
The canvas uses proxy files, but your exported content should be full quality. Try exporting or publishing to check quality. If export quality is still low, check your composition's resolution to confirm they are at a high enough resolution
Choppy video playback in the editor or exported file
Choppy playback could be caused by a low composition frame rate setting. To resolve this, increase your composition's frame rate setting in the Aspect ratio and video settings menu.
Error during playback
Occasionally files with an unsupported or invalid format will cause a playback error. If you run into this error, your best bet will be to re-encode the original file using a third-party application like VLC or Quicktime.

After that, you can use the Replace File feature to swap the source file in your existing project or re-import the file into a new project.

Troubleshooting non-reproducible performance issues
If you contact support with a performance issue, the support agent will open the project and try to reproduce the issue on their own computer. If it’s reproducible, great! We’ll escalate it to engineering and keep you in the loop about when it’s fixed or help you find a workaround while we work to fix the root of the issue.

If it’s not reproducible, then it probably means there’s something about the state of your computer or project that’s contributing to the issue. Here are a few more things you can try.

Reloading your project

You can do this by click Shift + Command + R (Mac) or Shift + Control + R (Windows)

Restart your computer

This actually works more than you would think. So if you haven’t already, try restarting.

Fully delete and reinstall Descript

Follow these instructions to remove all Descript data from your computer, and then reinstall.

None of that worked? Contact support

Most performance issues are resolved by addressing one of the above issues (in particular the first one about big projects), but if they don’t fix your problem, contact support and we’ll take a look!

Was this page helpful?
0 out of 0 found this helpful