If Premiere hangs partway through a render or an export, Adobe treats it as one troubleshooting case with a six-step checklist. The page that owns it opens with exactly this symptom: "Learn how to troubleshoot when Premiere hangs, freezes, or becomes unresponsive while rendering or exporting."
The problem with following that checklist today is step three. It tells you to switch the renderer to Mercury Playback Engine Software Only — an option Adobe removed from Premiere in version 25.2, documented on a second Adobe page updated a month after the troubleshooting page. Nearly every tutorial on frozen exports still teaches that step.
What counts as this problem
Adobe splits export trouble across separate pages that do not share solutions:
- Hangs, freezes, or goes unresponsive during render or export — the six-step page below.
- Only one project fails — a separate page that asks you to test a second project first.
- Exports finish, but slowly — a third page, which is about system requirements and graphics drivers. It is written for slow exports, not for exports that never finish.
One note if you arrived from an error dialog rather than a hang: Adobe's current Premiere Pro troubleshooting page does not contain the phrase "Error compiling movie" anywhere in its text. That string now appears on Adobe's Premiere Elements help page — a different product with a different UI, so its menu paths do not transfer. More on that split in what "Error compiling movie" means now.
Adobe's six steps, word for word
The page's own framing is modest: "Attempt to resolve export issues by following some standard troubleshooting steps mentioned here." The steps:
- "Try exporting your project to a different file format. Check the formats that Premiere supports for direct export."
- "Go to Preferences > Media and deselect Enable hardware accelerated decoding (requires restart) to export to H.264 or HEVC."
- "If you are not exporting to H.264, or if the issue persists, select File > Project Settings > General, and in the Video Rendering and Playback section, select Mercury Playback Engine Software Only."
- "If you’re using a custom export preset, change to a built-in preset. Go to the Export Settings dialog box, select the Preset dropdown menu, and choose a built-in preset that matches your desired output format."
- "Select Queue to open Media Encoder to export your project using Adobe Media Encoder. An added advantage to using Media Encoder is that you can work on other projects in Premiere."
- "If you’re using a third-party transition or plugin, remove that temporarily from the project and export again."
That is the whole official list. Clearing the media cache, renaming the project file, and exporting to a different drive are not on it. Adobe does document the media cache, but on pages about performance and disk management rather than as a remedy for a failed export.
Step three is the one to skip
Adobe's page on software rendering removal states it plainly: "In Premiere (version 25.2 and later), the option to choose software rendering (“Mercury Playback Engine Software Only”) from Project Settings > General has been removed." The stated reason: "Software rendering can cause poor performance and rendering in 8-bit, which can result in image quality issues."
Who is affected, verbatim: "Premiere – Windows", "Premiere - Macintosh Intel", "Adobe Media Encoder - All platforms". And for Apple silicon: "This change has no effect on Premiere on Apple silicon computers, as software rendering has never been an option on this platform."
Two clarifications that get lost in most write-ups:
- Only rendering lost its software option. "This change only affects rendering. Customers can still choose to use software encoding when exporting. For best performance, the use of hardware encoding is strongly recommended."
- A greyed-out Renderer menu is not a fault. "On a computer with a single type of GPU, that GPU will be selected in Project Settings > General > Renderer, and the menu will be greyed out, as there is no second GPU type to select. The playback engine shown is active and being used for rendering."
Adobe also asks for a report in one specific case: "If you have a project that rendered correctly using software rendering in version 25.1 or earlier that no longer renders correctly in later versions, please submit a bug report so we can fix the issue."
The order that costs the least time
The remaining five steps are still the official ones. Run them in this order:
- Switch to a built-in preset (step 4) — fastest thing to rule out.
- Queue it to Media Encoder instead of exporting in-app (step 5).
- Deselect hardware accelerated decoding in Preferences > Media, restart, retry (step 2). The checkbox is named two different ways across Adobe's own pages — "Enable hardware accelerated decoding (requires restart)" and "H264/HEVC hardware accelerated decoding (requires restart)" — so look for either wording.
- Export a different format (step 1).
- Temporarily remove third-party transitions and plugins (step 6).
If step 1 finally gets you a finished file but a very large one — ProRes or QuickTime rather than H.264 — you can shrink it afterwards without going back into Premiere at all:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
It runs inside your browser tab, so the file is never uploaded to a server. If you only need the container changed rather than the bitrate cut, MOV to MP4 handles that side.
Other causes, in order of likelihood
Only this one project fails. Adobe's project-specific page starts with "Try exporting a different project and see if it works." If the others are fine, then "your existing project could have a problem rendering third-party plugins, transitions, or LUTs" — the three suspects Adobe names. The documented move is a clean container: "try importing it into a new project. To do this, select File > Import, navigate to your original project file (.prproj), select Open, and then attempt to export again."
The destination folder doesn't exist. From Media Encoder's documentation: "When specifying a destination folder, ensure that the specified destination folder exists. If you specify a folder that does not exist, an error message informs you that the file cannot be encoded because the folder cannot be found."
Accents or double-byte characters in the output folder name — under narrow conditions only. Adobe's Media Encoder known issues describe "An issue affecting H.264 and HEVC or H.265 exports on Windows with Adobe Media Encoder 23.1" that "impacts H.264 and HEVC or H.265 exports to folders with names that use double-byte characters, such as Chinese, Japanese, Korean, or extended ASCII characters, like accents and umlauts." The listed workarounds: an ASCII-only destination folder, exporting to another format such as Apple ProRes, or, for H.264 exports only, disabling hardware-accelerated encoding. Note every qualifier — that entry is about one app version, one platform, two codecs, and the folder name.
Nothing on the list worked. Adobe's last-resort page: "If Premiere continues to hang or freeze during rendering and export, even after following the recommended troubleshooting steps, consider reverting to an earlier version of the application," through Other versions in the Creative Cloud desktop app.
How to tell it worked
Media Encoder writes two plain-text logs: AMEEncodingLog.txt for successfully encoded jobs, and AMEEncodingErrorLog.txt "for jobs that failed, or were stopped by the user." Open them from File > Show Log (Ctrl + L) and File > Show Errors. A job that finished lands in the first file and shows Done in the queue; Adobe defines the failure state as "Adobe Media Encoder encountered an error when attempting to encode the specified item." That log is the only official place to confirm which pass actually completed.
FAQ
Where is Mercury Playback Engine Software Only? I can't find it. On version 25.2 and later it is gone — Adobe removed the software rendering choice from Project Settings > General. On Apple silicon Macs, Adobe says software rendering "has never been an option on this platform." Tutorials pointing you there predate the change.
Is my Renderer dropdown greyed out because my GPU is unsupported? Not necessarily. Adobe's explanation is that a machine with a single GPU type has nothing else to switch to, so the menu is disabled while the engine shown is still active and rendering.
Will clearing the media cache fix a frozen export? It is not one of Adobe's six documented steps for this problem. Adobe covers the media cache on its own pages, framed around performance and disk space.
Should I export from Premiere or send it to Media Encoder? Adobe lists queuing to Media Encoder as an official troubleshooting step, and notes you can keep working in Premiere while it runs. When you send a job over, "The H.264 Match Source - Adaptive High Bitrate export preset is applied by default … However, if the sequence or clip has been previously opened in Export mode or Quick Export, the last-used export setting is applied instead."
Why does Media Encoder still process my queue one file at a time? By design. "Adobe Media Encoder encodes all sources in sequence, but encodes all outputs of a source in parallel." Multiple outputs from one source run together; different sources do not.
More Premiere export troubleshooting lives in the fix guides, and every browser-based converter and compressor is listed on Clapr tools. Adobe's pages cited here were captured on 16 September 2026 — check the current help pages before relying on version-specific details.
