Premiere Pro Export Using Proxies: Why It Doesn't by Default

Sep 25, 2026

Premiere does not export from your proxies unless you explicitly ask it to. Enabling proxies speeds up editing; it changes nothing about what gets encoded when you hit export. That single fact explains two complaints that look like opposites — "I cut with proxies and the export still took all night" and "why is my export soft?"

Adobe's proxy page says it in one sentence: "By default, Premiere uses full resolution media while exporting, even if you have enabled proxies. If you want to export proxies, you need to explicitly specify it in the Export Settings dialog box while exporting your project."

So before you change anything, work out which of the two problems you actually have.

What the Use Proxies checkbox actually does

Proxies exist for playback. Adobe describes the export-time switch this way: "Proxies are used to increase performance while editing and exporting. When this option is enabled, Premiere exports using the proxy files already generated for your sequence instead of rendering new media. This option can improve export performance."

Two phrases in there carry all the weight.

"the proxy files already generated" — with the box ticked, your deliverable is built from the proxy media, not from the camera originals. Proxies are low-resolution copies; the Create Proxies dialog opens on "the default frame size of Half" with the "default ProRes QuickTime Proxy" preset. Export from those and the result reflects that media, which is exactly why some people find their final file looks worse than the timeline did.

"instead of rendering new media" — that is where the speed comes from. Premiere is not re-reading and re-decoding the full-resolution source, so the export gets easier on your machine.

And the default state, verbatim from Adobe: "The checkbox will default to unchecked." If nobody on your team turned it on, it is off.

The fix, depending on which problem you have

If the export is slow and you want the proxies used

Adobe's own instruction is two steps: In the Media File > General section, select Use Proxies. — then, optionally, Select Use Previews to further speed up the export process.

That is the whole change. It lives in the export settings, not in project settings, and it is not sticky in a way you should assume — check it in the dialog you are exporting from.

If the export came out looking wrong

Look at the same checkbox and clear it. A soft or low-detail export from a proxy-based project is the expected outcome of Use Proxies being on, because Premiere is encoding the proxy media rather than the full-resolution media. Clearing it puts you back on Adobe's documented default behaviour.

If what you actually want is a smaller finished file — not a faster render — proxies are the wrong lever entirely. Encode the full-resolution export once, then compress the result:

Try it right here

Runs in your browser. Your file is not uploaded anywhere.

Loading tool…

This runs inside your browser tab: the file is read from disk, re-encoded locally, and handed straight back. Nothing is uploaded, which matters for client work under NDA. It is also a cleaner way to control delivery size than fighting the export dialog, since Adobe itself warns that "Estimated File Size is a rough estimate based on a constant bit rate video without audio or metadata." If you would rather tune the encode inside Premiere instead, CBR vs VBR in Premiere Pro exports covers what those bitrate modes actually do.

When both boxes are ticked, previews win

This is the detail that catches people who turn on everything at once. Adobe is explicit about the priority: "When this option is selected, Premiere uses the rendered previews if a section of the timeline has both a rendered preview and proxy media."

So on a timeline where some ranges are rendered (green bars) and others are not, ticking both switches gives you a mixed-source export — previews where they exist, proxies elsewhere. Worth knowing before you go looking for why one stretch of the video looks different from the rest.

Preview files have their own quality caveat. Adobe's wording for Use Previews: "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." The preview codec you picked in sequence settings becomes part of your deliverable. If you want a clean slate, Adobe's route for clearing them is Sequence > Delete Render Files.

Sending the job to Media Encoder changes the rules

If you queue exports rather than render in Premiere, one line from Adobe's preview-files page matters: "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."

Read "for each encoding process" literally. It is a per-job setting in the queue, not a preference you set once. Tick it on job one and job two does not inherit it.

When Create Proxies is greyed out

If you are stuck a step earlier and cannot make proxies at all, Adobe gives a specific eligibility list rather than a vague one: "You can create proxies only for video clips without captions. Proxies are not supported for any other types of files or growing files. The media must also be online."

So the four documented blockers are captions on the clip, a non-video file type, a growing file, and offline media. Attaching proxies you made elsewhere has its own list: "You can attach proxies only for video-only, audio/video, and offline clips in the Project panel. Other file types (for example, audio-only, stills, or image sequences) are not supported."

Worth knowing where the files land, because "my proxies vanished" is usually a path problem rather than a Premiere problem: "By default, Premiere appends "_Proxy" to the name of your Proxy clips (for example, scene01_Proxy.mxf) and places Proxy clips (on disk) in a folder named Proxies that is placed right next to the full resolution clips." The encoding itself is not done by Premiere either — Adobe notes that a proxy job is created in Adobe Media Encoder for each project item that can be proxied, and an offline proxy is attached to each one. If Media Encoder is not running or the job failed there, the attachment is what you are left with.

You can also have Premiere make them on the way in. Adobe's ingest options include Create Proxies, described as the option to create and attach proxies to the media, and Copy and Create Proxies, which copies media and creates proxies for them as well.

Adobe also documents things the proxy workflow does not cover at all, including Dynamic Link for After Effects compositions or projects, editing audio in Adobe Audition, and the option to modify audio channels and interpret footage. If one of those is misbehaving on a proxy project, that is documented behaviour rather than a broken install.

How to tell it worked

Three checks, in order:

  1. Before you export, confirm the state of Use Proxies in the export dialog itself. It is the only place the decision is made.
  2. After the export, open the finished file and compare a detailed frame — text, foliage, fabric — against the same frame in the timeline at full resolution. A proxy-sourced export shows the difference there before it shows anywhere else.
  3. If speed was the goal and turning Use Proxies on changed nothing measurable, the bottleneck was probably never decode. Other export-side settings can dominate — see when Premiere's smart rendering doesn't kick in and the rest of the export troubleshooting guides.

FAQ

Does Premiere use proxies when exporting? Not by default. Adobe states that Premiere uses full resolution media while exporting even if you have enabled proxies, and that you must specify proxy export explicitly in the export settings dialog.

Where is the Use Proxies checkbox? Adobe's instruction is In the Media File > General section, select Use Proxies. The same General area holds Use Previews, described as optional and intended to speed the export up further.

Will exporting with proxies lower my quality? Premiere encodes from the proxy files instead of rendering new media, and proxies are low-resolution copies — the Create Proxies dialog defaults to a frame size of Half. Treat a proxy export as a preview or review copy, not a master.

What happens if I enable both Use Proxies and Use Previews? Adobe says Premiere uses the rendered previews where a section of the timeline has both a rendered preview and proxy media. Previews take priority; proxies cover the rest.

Does Adobe Media Encoder pick up my previews automatically? No. Adobe states that Media Encoder does not automatically use Premiere preview files, and that you must select Use Previews in Media Encoder for each encoding process.


Wording cited from Adobe's official Premiere Pro help pages on proxy workflows, preview files, and export settings. Adobe revises these pages; verify against the current documentation before relying on them. For browser-based encoding that never uploads your footage, see all Clapr tools.

Clapr team

Clapr team

Premiere Pro Export Using Proxies: Why It Doesn't by Default | Clapr Blog