Use Previews tells Premiere to export from the render files your sequence already has, instead of rendering that footage a second time. Adobe's Use preview files when rendering page describes preview files as "temporary render files created during editing to improve playback performance," and adds that "these files can also be used during export to avoid re-rendering the same content."
That is the entire idea, and it takes one checkbox. The part almost nobody mentions is that the checkbox does not travel with the job when you hand the export to Adobe Media Encoder — Adobe says so in plain words, and this guide covers both halves.
Before you start
- A rendered sequence. If nothing has been rendered, there are no preview files to reuse and the option has nothing to work with.
- An awareness of your preview codec. Adobe's export settings reference is explicit that this option "may impact quality depending on the preview format you've chosen." The Adjust sequence settings page lists preview codec among the settings you can modify on an existing sequence — "frame size, timebase, pixel aspect ratio, audio format, preview codec, and color management" — with the caution to "adjust carefully, as changing core parameters can affect playback or quality."
- A decision about where you export from. Premiere's own export mode and Media Encoder both offer the option, but they do not behave the same way. Step 3 is the difference.
Step 1: Render the sequence so preview files exist
Premiere's render bar tells you what state each section of the timeline is in. Adobe's Render sequence sections page defines the three colours:
| Bar | Official description |
|---|---|
| Red | "Unrendered section that likely won't play back smoothly." |
| Yellow | "Unrendered, but may still play back in real time." |
| Green | "Already rendered and ready for smooth playback." |
Green is what Use Previews consumes. Which render command you choose decides how much of the timeline turns green, and the two commands are not interchangeable:
- Render Effects In to Out — "Renders the sections of the video tracks lying within the In and Out points, containing a red render bar."
- Render In to Out — "Renders the sections of the video tracks lying within the In and Out points, containing either a red render bar or a yellow render bar."
So Render In to Out covers red and yellow; Render Effects In to Out covers red only. If your goal is to have as much of the export come from previews as possible, the broader command is the one you want, and you should set In and Out points around the whole sequence first.
One thing in your favour: previews are not thrown away every time you touch the timeline. Adobe states that "Premiere maintains existing preview files whenever possible," that "preview files move along with their associated segment of a sequence as you edit your project," and that "when a segment of a sequence is changed, Premiere automatically trims the corresponding preview file, saving the remaining unchanged segment." A small tweak in reel two does not cost you reel one.
Step 2: Turn on Use Previews in Premiere's export settings
Adobe gives the path in one line: "In the Export Settings dialog box, in the GENERAL section, select Use Previews."
You reach that dialog with File > Export > Media, or with the keyboard shortcut "Ctrl + M (Windows) or command + M (macOS)."
The export settings reference spells out exactly what the option does and what it trades away:
"Use Previews | When this option is enabled, Premiere exports using the preview files already generated for your Premiere sequence instead of rendering new media. This option can help speed-up export times but may impact quality depending on the preview format you've chosen."
Read both clauses. "Can help speed-up export times" is the upside; "may impact quality depending on the preview format" is the price, and the size of that price is set by your sequence's preview codec, not by the checkbox.
Step 3: In Media Encoder, tick it again — for every single job
This is the step that separates a fast export from a puzzling one, and Adobe states it directly:
"Media Encoder does not automatically use Premiere preview files for encoding. To make use of the Premiere preview files, you must select the Use Previews option in Adobe Media Encoder for each encoding process."
Three things follow from that sentence, and all three are worth internalising:
- The setting is not inherited. Enabling Use Previews in Premiere does not carry over when the job lands in the Media Encoder queue.
- It is per job, not per session. "For each encoding process" means a queue of eight outputs needs the box ticked eight times.
- A silent slow export is the symptom. Nothing fails. The encode simply re-renders content that was already sitting on disk as green bar.
If you are routing exports that way, the official handoff is "File > Export > Send to Adobe Media Encoder," and Adobe's reason for using it is scheduling rather than speed: Media Encoder "lets you queue multiple exports, use custom presets, and render files without interrupting your editing workflow," and is "recommended for longer exports or when you need to create multiple delivery versions."
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
Worth being clear about scope: Use Previews changes how long the export takes, not how big the finished file is. If the reason you are chasing export time is that the deliverable also has to fit a size limit, that is a separate job — the compressor above runs in your browser tab, so the file never leaves your machine, and you can also do it with the standalone video compressor.
Common mistakes
- Assuming Media Encoder inherits the setting. It does not, per the quote above. This is the single most common reason people conclude that Use Previews "does nothing."
- Confusing Use Previews with Use Proxies. They are different checkboxes with different sources. Adobe notes that "by default, Premiere uses full resolution media while exporting, even if you have enabled proxies," and that to export from proxies "you need to explicitly specify it in the Export Settings dialog box." In the proxy workflow, Use Previews is listed as an optional extra to "further speed up the export process."
- Not knowing which one wins. If a stretch of timeline has both, Adobe is unambiguous: "When this option is selected, Premiere uses the rendered previews if a section of the timeline has both a rendered preview and proxy media." Previews take priority.
- Deleting render files right before exporting. "To delete all the render files for a sequence, select Sequence > Delete Render Files" — useful for reclaiming disk space, and exactly the wrong move ten minutes before a deadline export.
- Leaving Maximum Render Quality on out of habit. Adobe's guidance is narrower than most people assume: "This option is only useful when exporting to a different frame size. If you're exporting at the same frame size as your source media, leave this setting deselected." It also warns that "export times can increase significantly, especially on systems without a supported GPU."
FAQ
Does Use Previews reduce export quality? It can. Adobe's wording is that it "may impact quality depending on the preview format you've chosen" — so the outcome depends on your sequence's preview codec rather than on the option itself. For a review copy the trade is usually worth it; for a master, render previews in a format you would be happy to deliver.
Why is my Media Encoder export still slow with Use Previews on in Premiere? Because Media Encoder "does not automatically use Premiere preview files for encoding." You have to select Use Previews inside Media Encoder, and Adobe specifies that this is required "for each encoding process."
Do I have to re-render the whole sequence after every edit? No. Adobe says Premiere "maintains existing preview files whenever possible," moves them along with their segment, and trims the affected preview when a segment changes, "saving the remaining unchanged segment."
Is this the same thing as smart rendering? No. Smart rendering is a separate mechanism that, per Adobe, "avoids recompression during export by copying matching source data directly to the output file" and "works only when source codec, frame size, frame rate, and bit rate match export settings exactly." See why Premiere Pro smart rendering stops working for the conditions it requires.
What if my export is slow for reasons unrelated to previews? Adobe's page on slow exports points at the machine rather than the timeline: "ensure your device meets our recommended technical requirements" and "check if any of the drivers installed need updates. We recommend using NVIDIA Studio Drivers." Anything more specific than that — bitrate recommendations, for instance — you should check the official documentation for, because Adobe's export pages describe the mechanisms without publishing target numbers.
Quotes taken from Adobe's Premiere and Media Encoder help pages on helpx.adobe.com, checked 17 September 2026. Adobe revises these pages regularly — verify against the official documentation before relying on a specific menu name. More walkthroughs in the how-to guides, and the rest of the browser-based toolkit is at Clapr tools.
