DEV Community

Marcus Rowe
Marcus Rowe

Posted on • Originally published at techsifted.com

Descript Not Working? 9 Common Problems and How to Fix Them

Disclosure: No affiliate links here. The Descript link below is a plain direct link -- no commission to us.

Descript works great right up until it doesn't.

I've been using it long enough to have hit most of the common failure modes at least once -- usually at the worst possible time, like when an episode is due in two hours and the export just... sits there. Spinning. Going nowhere.

Most Descript issues have actual solutions. Some of them are obvious once you know what to look for, and some are weird platform-specific quirks that Descript's own support documentation doesn't fully explain. This is the guide I wish existed when I first ran into these problems.

Before Anything Else: The Quick Fixes

Almost one-third of Descript issues I've seen get resolved by one of three things:

  1. Force quit and restart the app. Not just close the window -- fully quit Descript and relaunch it. The desktop app can develop memory issues after extended sessions.
  2. Check your internet connection. Descript is heavily cloud-dependent. Transcription, Overdub, Studio Sound, and several other features won't work without a live connection.
  3. Check the Descript status page. status.descript.com shows real-time outages. If something was working yesterday and suddenly isn't, a server-side issue could be the cause. This takes 10 seconds to check and can save you 45 minutes of troubleshooting.

If none of those fix it, keep reading.


Problem 1: Transcription Is Stuck or Wrong

Symptoms: The progress bar stops mid-transcription, transcription says complete but the text looks garbled, or the transcript is full of words that sound vaguely like what you said but aren't.

Stuck transcription:

If it's been more than 15 minutes on a 30-minute file, something's gone wrong. First, check your internet connection -- transcription runs on Descript's servers, and a dropped connection mid-process will cause it to hang.

Try removing the clip from the project and re-importing it. In the transcript panel, right-click the speaker track and select Re-transcribe. This kicks off a fresh transcription pass.

If re-transcription keeps stalling, export your audio to MP3 first (outside of Descript), then re-import the MP3. Sometimes large or unusual file formats trip something up in the processing pipeline. The MP3 roundtrip usually clears it.

Garbled or inaccurate transcription:

Descript's transcription accuracy varies based on audio quality, accent, and background noise. If the transcript is mostly incomprehensible, the audio is probably the problem, not Descript.

Things that tank transcription accuracy:

  • Heavy background noise (HVAC, traffic, music)
  • Speaker with a strong regional accent or non-English phrasing patterns
  • Multiple people talking at the same time
  • Phone call quality audio (compressed, mono, with artifacts)

For audio quality issues: run your recording through a noise removal tool before importing into Descript, or use Descript's built-in Studio Sound feature to clean it up first, then re-transcribe. Studio Sound doesn't fix bad transcription after the fact, but cleaning the audio before another transcription pass can help.

Wrong speaker labels:

If Descript assigned dialogue to the wrong speaker, you can manually reassign it. Click on the speaker label in the transcript panel, and there'll be an option to change which speaker that section is attributed to. Tedious, but it works.


Problem 2: Overdub Not Generating

Symptoms: You type a correction into the transcript, hit enter, and nothing happens. Or Overdub starts generating, the progress indicator spins, and then just stops without producing audio.

Overdub has a few known failure modes:

You're not on a paid plan. Overdub requires Creator or Pro. If you downgraded or your payment failed, Overdub will appear to be available but won't actually generate audio. Check your subscription status under Account Settings.

Your voice model needs updating. Descript periodically requires you to re-record your Overdub voice sample when the underlying AI model updates. If Overdub was working and suddenly isn't, go to Account > Overdub and check if there's a prompt to re-record. It usually takes about 10-15 minutes.

The correction is too long. Overdub works best on short corrections -- a word, a phrase, maybe a short sentence. Trying to generate a full paragraph through Overdub is asking for problems. Long generations have higher failure rates. Break long corrections into shorter individual segments.

Server load. During peak usage times, Overdub generation can slow down dramatically or time out. Try again during off-peak hours (early morning, late night). Not a great answer, but sometimes it's just traffic.


Problem 3: Video Won't Export

Stuck exports are one of the most frustrating Descript problems because you've done all the work and can't get the output.

Export hangs at a percentage:

If the export progress bar freezes at some point and won't move, the first step is to cancel and try again. If it freezes at the same spot twice, there's likely a specific clip in your project causing the issue.

Work backward from where the export stalls -- if it always freezes at 60%, look for what's happening at that point in your timeline. Corrupted B-roll files, unsupported video codecs in imported clips, or effects applied to a specific segment can all cause export failures at predictable points.

Try exporting a section of the project that doesn't include the problematic area to verify the issue is location-specific. Then re-import the problem clip or remove the effect that's causing issues.

"Export failed" error with no details:

This one's annoying because Descript isn't telling you much. Things to try:

  • Change the export format or quality settings. Sometimes switching from "Best" to "Good" quality clears the issue
  • Export to a different folder -- your current export destination might have permission issues
  • Close other applications and try again with more available memory
  • Update Descript to the latest version if you're behind

Video looks corrupted or artifacts appear:

If the exported file looks wrong (blocky, incorrect colors, audio out of sync), the issue is usually with an imported clip that has an unusual encoding. Re-encode problematic source files with Handbrake (free) before re-importing, then re-export.


Problem 4: Audio Sync Issues

Symptom: The video plays fine in Descript, but in the exported file, audio is noticeably ahead of or behind the video.

Sync issues almost always come from one of two places:

Variable frame rate video: Smartphones, particularly older iPhones and Androids, record in variable frame rate (VFR) by default. Most editing software including Descript prefers constant frame rate (CFR). Convert your video to CFR using Handbrake before importing -- it's a free conversion that fixes sync issues in probably 70% of cases.

To convert: open Handbrake, load your video, go to Video settings, and change Framerate from "Same as source" to a fixed value (30 or 60 fps depending on your original recording). Export and re-import into Descript.

Multiple audio tracks with different sample rates: If you imported audio recorded at 44.1kHz and the camera audio is at 48kHz, Descript can sometimes drift over long recordings. Check your audio recording settings -- use 48kHz across all sources if possible.


Problem 5: Screen Recording Won't Start or Crashes

On Mac:

Descript needs screen recording permission. Go to System Settings > Privacy & Security > Screen Recording and make sure Descript is checked. If it's already checked, try unchecking and rechecking it -- Mac's permission system can get stuck in an inconsistent state.

Also check microphone permissions in the same menu if you're trying to record audio alongside the screen capture.

On Windows:

Windows doesn't have the same granular permissions system, but Descript still needs to run in a context that allows screen capture. If you're running Descript from a restricted corporate environment or a managed device, screen recording may be blocked at the system level -- not something Descript can override.

For non-managed Windows machines: try running Descript as administrator once to see if permission is the issue. If that fixes it, right-click the Descript icon, go to Properties > Compatibility, and check "Run this program as an administrator."

Screen recording starts but stops unexpectedly:

This is usually a disk space issue. Screen recordings generate large temporary files. Check your drive space -- Descript needs several GB free to record and process. On a near-full drive, recordings will stop mid-session.


Problem 6: File Import Errors

"Unsupported format" errors:

Descript supports a wide range of formats but has limits. Files with unusual codecs (old .avi files with DivX, .wmv with Windows Media codec, .flv) often fail.

Fix: convert to MP4 (H.264 video, AAC audio) using Handbrake before importing. H.264/AAC is the most universally compatible combination and Descript handles it reliably.

Large files fail or stall on import:

Files over 4GB can sometimes cause issues on import, particularly on the free tier which may have size limits. Split your recording into segments before importing if you're working with very long files.

Corrupted file imports:

If a recording is partially corrupted (recording stopped unexpectedly, drive ran out of space mid-record), Descript may fail to import it or produce a transcript of only part of the content. Try opening the file in another player (VLC, QuickTime) first to verify it plays correctly. If it doesn't play cleanly in VLC, it's a corrupted source file -- Descript can't fix that.


Problem 7: Login and Subscription Issues

Can't log in:

The most common login failure is a cached session that's gone bad. Try logging out completely, clearing the app cache, and logging back in. On Mac, Descript's cache is in ~/Library/Application Support/Descript. On Windows, it's in %AppData%\Descript. Deleting the cache folder doesn't delete your projects -- those are stored in the cloud.

If you use SSO (Google or Apple sign-in) and your Google/Apple account has changed something recently (password reset, 2FA change), you may need to re-authenticate through that provider first.

Features missing after upgrade:

If you upgraded your subscription but Overdub or other Pro/Creator features still aren't showing up, log out and back in. Descript's local app state sometimes doesn't refresh the entitlements immediately after a subscription change.

Subscription shows active but features are locked:

This occasionally happens after a payment fails and then succeeds on retry. The system updated the subscription status but the app cached the locked state. Log out, wait five minutes, log back in.


Problem 8: App Performance Slowdowns

Descript can get sluggish, especially during long editing sessions or with large projects.

Memory leak after long sessions: The app accumulates memory over hours of use. Closing Descript and reopening it periodically during long editing sessions helps. I restart it roughly every 2-3 hours when working on long projects.

Large project files: Projects with lots of imported media, many edits, and extended timelines get slow. If performance is unacceptable, try splitting your project into smaller segments. Edit in sections, then combine the exports.

Too many effects: Descript's AI effects (Studio Sound, eye contact correction) are processed on export, but having many applied to a long video can slow down the editing preview. Disable effects during editing and re-enable for the final export.


Browser vs. Desktop App: Which One to Use

Descript has a web version that works in Chrome and Edge. The browser version is useful for quick reviews and light edits, but it has real limitations:

  • No screen recording in the browser version
  • Slower performance on large projects
  • Limited export options compared to desktop
  • Overdub may behave differently -- some users report more generation failures in browser than desktop

If you're doing real editing work, use the desktop app. The browser version is fine for reviewing transcripts or making small corrections when you're on a machine that doesn't have Descript installed.


Still Stuck?

If none of these fixes work, Descript's support is genuinely responsive. Use the in-app chat (bottom right corner of the desktop app) rather than email -- response times are faster. Include:

  • Your OS and Descript version (Help > About)
  • What you were doing when the issue occurred
  • Any error messages (exact text, not paraphrased)
  • Whether the issue is reproducible or intermittent

For context on the normal Descript workflow that usually works without any of these problems, the how to use Descript guide covers the basics from scratch.

If you specifically need the podcast workflow, Descript for podcasting goes deeper on audio-specific setup and common podcasting issues.


Most Descript problems aren't Descript problems -- they're source file issues, permission issues, or connection issues that happen to surface inside Descript. Work through the checklist here systematically and you'll fix most things in under 10 minutes. The ones that require real support are genuinely unusual.

Top comments (0)