Tech · PRACTICAL GUIDE
Premiere Export Stuck at 100%? Check the File Before Delivery
An export can exist, play and even pass a decode while still failing your delivery requirements. Check the intended range, every required audio stream and the actual program before sending it.
Do not decide that a stalled Premiere export is complete solely because an output file exists. Once writing has stopped, compare that file with the intended export, run local technical checks where appropriate, and review the actual picture and sound.
This is a file-verification workflow, not a diagnosis of every 100% export hang or permission to cancel an active job. There is no single green light: duration, stream inventory, decoding, manual review and any required provenance serve different purposes.
First, protect the export and record what it should contain
A file in the destination folder is not a completion receipt. Do not use a motionless percentage, an unchanged file size or one zero-I/O reading as permission to force-quit the exporter. Save the project when the application permits it. This guide checks an existing file after the process writing it has stopped; it does not establish a safe cancellation point. If the writer’s state is uncertain, keep the output unverified and resolve the stalled job separately.
Before checking the file, record the intended sequence and export range, expected running time, frame rate, dimensions and required audio delivery. Adobe’s Export screen lets you preview and choose a range: the whole sequence and an In/Out selection are not interchangeable. Record whether delivery requires a stereo mix, several separate audio streams, captions or Content Credentials. A timeline with many audio tracks may legitimately export one mixed stream.
Once writing has stopped, keep the original and inspect a separately named copy. Do not overwrite the suspect output during a retry. File-size stability is only an observation, not proof that writing or finalization has finished.
Check the file’s duration and every expected stream
For the optional command-line checks, use a trusted FFmpeg installation that includes both ffmpeg and ffprobe. Run ffmpeg -version and ffprobe -version first. A command-not-found result is a setup problem, not a failed video. These examples were tested with FFmpeg 7.1.5 on Linux; they were not executed in Windows, macOS, Premiere or Media Encoder. Replace export.mp4 with the full quoted path to your stopped-export copy.
Run this metadata check: ffprobe -v error -show_entries format=duration:stream=index,codec_type,codec_name,duration,channels -of json "export.mp4"
Compare the format and stream durations with the intended export range, and compare the video/audio inventory with the delivery specification. Do not demand exact equality between rounded decimal durations: frame boundaries, audio padding and container reporting can differ. Investigate a meaningful discrepancy and inspect the actual endpoint. Missing duration information is unknown, not zero or a pass. The channels field describes channels within an audio stream; it is not the number of separate streams.
If sound is required and no audio stream is present, do not approve the file merely because the video plays. If multiple audio streams are required, count and identify all of them. This small metadata command does not check frame rate, dimensions, subtitles or the intended mix; inspect those separately in the player or editor. Successful probing does not decode the entire program.
Decode all video and audio, not just the default track
Run the following local read-and-decode check on the same copy. It decodes all mapped video and audio into FFmpeg’s null output rather than writing a replacement media file: ffmpeg -hide_banner -v error -xerror -abort_on empty_output+empty_output_stream -i "export.mp4" -map 0:v -map "0:a?" -f null -
The explicit mappings include all video streams and every available audio stream. The question mark permits a genuinely silent file; it does not waive a delivery requirement for audio. The xerror option stops on errors that FFmpeg reports, and abort_on rejects the specified empty-output conditions. Do not add -c copy: copying compressed packets is not this decoding test. The command does not validate subtitle/data streams or Content Credentials.
Let the command finish and check its exit status immediately: echo $? in a Bash-compatible shell, or $LASTEXITCODE in PowerShell. A zero exit status with no reported errors means this decoder found no error in the mapped material during this run. It cannot establish that the intended ending, dialogue, graphics or captions are present. A nonzero result means this check has not passed; the reason may be damaged media, an unsupported decoder, a permission problem or another environment issue. Preserve the message and investigate instead of automatically calling the file corrupt.
Why a “successful” check can still miss the problem
Our isolated test used a four-second synthetic H.264 video with two AAC audio streams, then created seven controlled files. The complete file, a playable short file and a video-only file all returned zero from the all-stream decode. The short file reported 1.52 seconds; the video-only file reported four seconds but had no audio. They are valid media, yet they fail a requirement for the original full-length, two-audio-stream deliverable.
A deliberately damaged second audio stream produced another useful distinction: metadata still reported four seconds and two audio streams. Decoding only the first audio stream returned zero; decoding all video and audio failed. A physically truncated file also retained four-second duration metadata but failed decoding. Empty and non-video files failed probing and decoding. All ten stated test assertions passed and the input hashes were unchanged.
These are command-behavior tests, not a reproduction of Premiere’s 100% stall. We did not test Premiere or Media Encoder, active-write safety, C2PA signing, real client footage or a Windows/macOS matrix. The results explain why expected specifications, technical decoding and editorial viewing must remain separate checks.
Make the delivery decision—and check credentials separately
Before delivery, play and listen through the intended exported program, not merely the opening or a few thumbnails. Compare the actual ending with the selected timeline endpoint; check each required audio stream or mix, dialogue continuity, sync, transitions, graphics, captions and unexpected black or frozen pictures. Technical decoding cannot tell whether a valid black frame or a silent passage belongs in your film. Checking the ending is already sound community advice; the stream checks above supplement it, not replace it.
If Content Credentials are required, follow Adobe’s separate instructions to inspect the exported asset. A playable file does not prove that its credentials were attached, and credentials do not prove that the audiovisual program is complete. Use an online inspection service only when you have permission to upload that footage. Do not strip or disable provenance just to make a stalled export appear acceptable.
Approve only after the independently recorded delivery requirements, technical checks and full manual review are satisfied. A missing stream, wrong endpoint, unresolved decode error or unverified required credential leaves the file unverified. Keep the project and existing output, record the exact failure, and make a retry to a new filename. This workflow helps decide whether a file can be handed over; it is not a universal fix for the stalled Premiere job.
