At 11:48 p.m., the export bar stopped at 99%. The upload deadline was tomorrow morning; the laptop fan had become a tiny aircraft engine. “Cancel it and start over?” my colleague asked. I hovered over the button, then noticed the output file had grown by another few megabytes. That number at the end of the progress bar did not necessarily mean the job had one percent of its work left. An editor may still be writing the final frames, closing audio streams, or assembling the file index.

Read the activity, not just the percentage

Give the export a short observation window—perhaps five minutes—and compare the output file size and modified time. Also check whether the editor responds and whether the destination drive is still writing. If any of those signals move, the render may be slow rather than frozen. A final shot with stabilization, denoising, layered graphics, or a long effect can take much longer than a simple frame.

If the file and drive activity are unchanged and the application is unresponsive for a sustained period, a stall becomes more plausible. Before ending the process, preserve the project: save a copy under a new name if possible, or duplicate the project file and note where its media lives. Check free space on the destination drive and on the volume that holds temporary files or the editor cache. The export can need scratch space even when the finished video would fit.

What you noticePossible explanationSafer first move
Output file keeps growingFinal frames or file metadata are being writtenWait; do not open the active file
No file or disk change for a long timeA clip, effect, encoder, or drive may be stuckCopy the project and test a short range
Scratch or destination drive is nearly fullTemporary render space is exhaustedFree space safely, then retry a small export
The same timeline point fails repeatedlyA specific source clip or effect is involvedIsolate that section in a duplicate project

Turn the ending into a small diagnostic test

Work from a copy, not the only project. Set the export range to the last minute or two and try again. If that range stops at the same place, inspect nearby footage, captions, transitions, audio processing, and any unusually large still image. Disable one effect at a time in the copy. If a short render succeeds when a particular effect is off, you have a useful lead; re-enable other effects and confirm the result before changing the full timeline.

When an effect is the culprit, render that complicated section to an intermediate file or use the editor’s render-in-place feature, if available. Keep the original media and project intact, and record where the intermediate lives. Do not lower the final resolution or frame rate just to make the progress bar move: that can hide an unrelated storage or codec problem and create a delivery that no longer meets its requirements.

Check the export path and settings in a controlled order

  1. Check three places for free space. Look at the output volume, the system temporary-file volume, and the editor’s cache or scratch location. Remove only regenerable cache through the application’s controls or after confirming the exact cache folder. Do not delete project files, autosaves, or source media as a guess.
  2. Simplify the destination. Export a short test to a new local folder instead of a network share or a cloud-synced folder. For an external drive, check its cable, power, and sleep behavior. A disconnected volume can leave a render waiting on file access.
  3. Inspect the final timeline section. Look for offline media, a damaged source, an unusual variable-frame-rate recording, a very large still, or an effect stack that begins near the end. A new sequence containing only the suspect section can help separate timeline trouble from project-wide settings.
  4. Change one encoder setting at a time. If hardware encoding fails, compare a short software-encoded test. If the software version works, use that mode for the full render if time and quality permit. A different codec may improve compatibility, but it can also change file size, quality, and playback support.

If you had to force-quit, reopen the editor and save any recovered project under a new name before continuing. For a recurring failure, record the application version, operating system, export format, the timecode where it stops, and available disk space. Check the editor’s official support material for that version. Random codec packs and registry edits can make a narrow render problem harder to diagnose.

A render diagnostic diagram separating the output drive from the editor cache

Before restarting a large export, make a small diagnostic matrix instead of changing several settings at once. Write down the timeline range, output folder, encoder mode, and whether effects are enabled. Test the same short section with one variable changed. If a local destination works but a network folder fails, investigate the connection or permissions. If software encoding works while hardware encoding stops, the encoder path is a stronger lead. If both fail at exactly the same frame, inspect the source media and effects around that point. This simple comparison prevents a “fix” from becoming a new, unexplained export preset.

Pay attention to storage that is easy to overlook. A project may point to media on an external SSD while the editor stores previews on the system drive. The export can therefore fail because the system volume is full even when the video destination has plenty of room. Cloud-sync clients can also hold a file while uploading it, and network shares may pause when a laptop changes Wi-Fi or sleeps. Use a local folder for the test, leave the editor open, and avoid moving the source footage until the export completes.

The timeline itself can contain a hidden edge case. A still image with enormous dimensions, a clip with a variable frame rate, or an effect whose license is unavailable may only become visible when rendering reaches that section. Scrub through the last successful frame and the next few seconds in the editor. Confirm that the media plays, that no offline-media warning appears, and that the export range includes what you intended. If the same frame fails repeatedly, export the preceding and following portions separately in a copy; the split can reveal whether the boundary or the clip is at fault.

Think about the audience before choosing a workaround. A delivery for a client, an archive, and a social upload may need different codecs, but each has a specific playback requirement. Keep the original project and a high-quality master; make a smaller upload copy only after the master has completed and passed playback checks. Verify the beginning, the failed end section, audio, captions, and duration in a separate player. A file that exists is not necessarily a finished export.

If the editor offers an export log, preserve it along with the project copy. A support request is more useful when it includes the application and operating-system versions, encoder, output destination type, timecode, and whether a short software-encoded test succeeded. Remove private client footage and account details before sharing logs. Avoid sending the entire project to a public forum: project files may include paths, names, or linked assets that were not meant to be public. These details are usually enough to begin a useful diagnosis without exposing the whole edit. Keep a known-good copy unchanged until the replacement has passed playback checks.

If you work with client footage, keep the diagnostic copy private and remove identifying filenames before sharing it with support.

For a delivery deadline, leave time for the full render and playback check; a short diagnostic export cannot guarantee that the complete timeline will finish at the same speed.

Questions creators ask

Is waiting 30 minutes at 99% always safe?

There is no universal cutoff. A growing file or active disk suggests work is continuing; a frozen application with no file or drive activity for a long period suggests a stall. Protect the project and autosave before you decide to stop it.

Can I open the file while it is still exporting?

Avoid it. The container may not have its final index or metadata yet, so a player may report a broken file even while the editor is writing it. Wait for completion, then verify the finished copy in a separate player.

Will lowering the resolution fix the export?

Not necessarily. It may shorten a test, but it will not repair a failing drive, bad source clip, or encoder issue. Keep the required delivery specifications and use a lower-resolution test only to isolate performance.

At a glance
Watch file and disk activity before deciding whether 99% means “working” or “stuck.”
Protect a project copy, test the final section, and change storage, effects, or encoding one at a time.