Skip to content
uncompressed.io

Answer

What is a proxy file
in video editing?

A proxy is a small, lightly compressed stand-in for a camera original, made so the timeline plays in real time on the machine you edit on. You cut against the proxy. You finish from the original. Here is how that works, and why nothing on the delivery side of this product makes one.

See the review room

Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month

By uncompressed.io · Updated September 2026

The short answer

A proxy is a small stand-in
so the timeline plays in real time.

A camera original is written to be the best possible picture, not the easiest possible playback. A proxy is the opposite trade. It is a second, smaller file generated from the original, cheap enough to decode that the edit runs at speed on the machine in front of you.

Apple documents the mechanics for Final Cut Pro, and its page is the clearest first-party description of the idea. Proxy media is a transcode to Apple ProRes 422 Proxy or H.264. It can be created at frame sizes from 12.5 percent to 100 percent of the original. Apple states that proxy files “increase editing performance and take up considerably less storage space than optimized files”.

The second half of that page matters more than the first. Apple states that when transcoding files, Final Cut Pro “always retains the original media for future use”. A proxy is an addition, never a substitution. That is the whole reason the workflow is safe: the small file carries the edit, and the original is still there to carry the finished picture.

Camera original
Optimized media
Proxy media
Whatit is
The file the camera wrote
A transcode made forediting performance
A small stand-infor the edit
Codec inFinal Cut Pro
Whatever the camera records
Apple ProRes 422
Apple ProRes 422 Proxyor H.264
Framesize
Native
Apple does not publishone on this page
12.5 to 100 percentof the original
Why itexists
It is the picture. Everythingelse is derived from it
Better performance during editing,faster render times, better colorquality for compositing
Increases editing performance,considerably less storagethan optimized files
Aftertranscoding
Always retainedfor future use
Kept alongsidethe original
Kept alongsidethe original

Quotations and figures from Apple Support, Create optimized and proxy files in Final Cut Pro for Mac, fetched 11 September 2026. Other editing applications run comparable workflows under their own names; we cite only the vendor page we verified today.

Why the edit needs one

A timeline
is not one decode.

Playing a single clip is a modest job. An edit is not that. At any given second the application may be decoding two or three streams at once, holding the frames on either side of a cut, applying a transform, a stabilizer, a grade and a title on top, and then drawing the result twenty-four or more times a second without dropping one. The decode is the floor, and everything creative stacks on top of it.

So the constraint is not whether the machine can open the file. It is whether the machine can open the file and still have room left for the work. A proxy buys that room by spending less of the budget on the picture, which is acceptable precisely because the proxy is never the deliverable. Judgments that depend on the actual pixels, the grade, the noise, the fine detail in a sky, are made after the switch back to the original.

1

Keep the originals

Copy the cards, verify them, and store them where the edit can reach them. Nothing in a proxy workflow modifies or deletes what the camera wrote.

2

Generate proxies

The application writes a second, lighter set of files and links them to the originals. In Final Cut Pro that is ProRes 422 Proxy or H.264, at 12.5 to 100 percent of the original frame size.

3

Cut against the proxies

The timeline plays, the trim is responsive, and the storage bill for the working set is small. Structure, rhythm and story get decided here.

4

Switch back for the finish

Because the original media is retained, the grade and the export are made from it. The proxy has done its job and can be discarded.

Where proxies stop

A proxy is an editing tool.
Nothing here makes one.

The word travels. On the editing side a proxy is a stand-in your application makes for your benefit. On the hosting side, a platform that generates playback renditions is doing the same thing to your finished film, on its own terms, and the file your client watches is no longer the file you approved.

That is the one thing this product does differently, and it is worth stating plainly. No proxy is generated here. No rendition ladder is generated here. The player streams the exact bytes you uploaded, with no transcode anywhere. When a client presses play, the picture they judge is the picture you exported, at the bitrate you chose.

The honest cost of that is compatibility. A platform that re-encodes can accept almost anything and hand the viewer something their device will certainly play. Refusing to re-encode moves that decision back to you, where the grade already lives. It is a better trade for a filmmaker and a worse one for someone who wants to upload a camera file and forget about it, so the rest of this page is about making the right upload.

0

renditions generated

The player streams the exact bytes uploaded, with no transcode anywhere.

3

codecs that stream

Browser playback is H.264, HEVC and AV1.

12.5%

smallest proxy frame size

Apple documents proxy frame sizes from 12.5 to 100 percent of the original.

5 GB

free hot storage

Starter is free, one film at a time, no credit card.

What actually plays

The viewer’s browser
decides the export.

If no stand-in is generated for you, the export you upload has to be one the viewer can decode. Below is what the browser vendors publish, quoted from MDN.

H.264 / AVC
HEVC / H.265
AV1
Chrome
All versions
Devices with hardware support onWindows 8+, Linux and ChromeOS;all devices on macOS Big Sur 11+and Android 5.0+
Supported
Edge
All versions
Chromium: devices with hardwaresupport on Windows 10 1709+ whenthe HEVC video extensions from theMicrosoft Store is installed
Supported
Firefox
All versions, dependent on theoperating system codecs
Windows from Firefox 134,macOS from 136, Linux from 137,Android from 137 (hardware only)
Supported
Safari
All versions
All devices on macOSHigh Sierra or later
17, on M3 MacBooks and later,iPhone 15 Pro, and iPhone 16and later
Opera
All versions
Same support statusas Chrome
Supported

Browser support as published in MDN's Web video codec guide, fetched 11 September 2026. MDN states support at the codec level only. On phones, Android's own documentation lists HEVC decoding from Android 5.0 and AV1 decoding from Android 10, with an AV1 encoder and decoder mandatory from Android 14 (Android Developers, Supported media formats, fetched 11 September 2026).

On 10-bit 4:2:2

No vendor documents 10-bit 4:2:2 HEVC decode in a video element, in either direction, and the one primary decoder specification among the documents checked, Microsoft’s Media Foundation H.265 decoder, lists 4:2:0 chroma only. Our side is safe either way, because we never re-encode: a 10-bit 4:2:2 file is stored and served untouched. The browser side is not documented, so test your own export with your own client before you rely on it.

What to upload

Send the film,
not a stand-in of it.

Streams in a browser

H.264, HEVC and AV1. These are the three codecs a browser decodes, and the player serves your file at exactly the bitrate you exported. 8K plays when the viewer's hardware decodes it, which is a real caveat on older machines.

Hosted, but downloaded

ProRes and DNxHR are hosted here for client download, not streamed. A colorist or a finishing house pulls the file; a browser will not play it. If the same film also needs to be watched online, upload a browser-compatible export alongside it.

Camera RAW

The macOS app plays R3D, BRAW and N-RAW natively, under support agreements with RED, Blackmagic Design and Nikon. None of the three streams, and none plays in a browser. For every other RAW format the honest workflow is to finish to HEVC or ProRes first, then upload.

Two files, one film

A high-bitrate export for viewing and a mastering file for download can live side by side. Both count toward your storage, which is the only thing metered here: there are no bandwidth caps and no per-view charges.

The practical rule is short. Cut against a proxy because your machine needs one. Upload the finished export because your client needs to see the picture you signed off on. The two are unrelated jobs, and the second one is the one this product refuses to do behind your back.

If you want the arithmetic behind what a library of masters and exports costs to keep online, the storage guide works through a full year of projects, and the pricing page carries the plans and the per-terabyte block rates.

Questions

Frequently asked

What is a proxy file in video editing?

A proxy is a smaller, lighter copy of a camera original that an editing application creates so the timeline plays back smoothly. The edit runs against the proxy; the finished picture comes from the original, which is kept.

What codec is a proxy file?

In Final Cut Pro, Apple documents proxy media as a transcode to Apple ProRes 422 Proxy or H.264. Other applications use their own formats; we only cite the one vendor page we verified.

How small is a proxy file?

Apple documents proxy frame sizes from 12.5 percent to 100 percent of the original, and states that proxies take up considerably less storage than optimized files. A proxy at 12.5 percent is one eighth of the original width and height.

Does making a proxy replace my camera original?

No. Apple states that when transcoding files, Final Cut Pro always retains the original media for future use. The proxy is an additional file, not a replacement, which is why the final export can come from the original.

What is the difference between proxy media and optimized media?

Apple describes optimized media as a transcode to Apple ProRes 422 for better performance during editing, faster render times, and better color quality for compositing. Proxy media is a transcode to ProRes 422 Proxy or H.264 that increases editing performance and takes considerably less storage than optimized files.

Does uncompressed.io make a proxy of my film?

No. No proxy and no playback rendition is generated here. The player streams the exact bytes you uploaded, with no transcode anywhere, so the file your client watches is the file you exported.

My client says the video stutters. Do I need a proxy?

Not a proxy. Because nothing is re-encoded here, the file you upload is the file that plays, so the fix is on the export side: choose a codec the viewer's browser decodes, and a bitrate their connection can sustain. Browser playback is H.264, HEVC and AV1.

Let the client watch the master, not a stand-in

Upload a browser-compatible export and share it in the review room. The player streams the exact bytes you uploaded, with no transcode anywhere, so what your client sees is the file you approved.