An export panel offers a list of presets and one slider labeled bitrate. Most people pick the preset that names a screen size and accept whatever number comes with it. That works until a client says the file is too soft, or the upload sits in processing, or a hard drive refuses the copy. The fix is not a better preset. It is deciding what the file has to survive before you touch the slider.
Name the destination before you name a codec
Three destinations cover almost every job. A platform upload goes to a service that will re-encode it, so the file only has to be clean enough that the second encode has room to work. A client master goes to a person who may cut it again, so it has to hold detail during another round of compression. An internal review copy only has to be watchable and small enough to send over a chat app.
Write the destination on the first line of your export notes. Every number below follows from it. A single preset cannot be right for all three, and reaching for the largest file every time wastes hours of transfer on work nobody will watch twice.
Copy the frame rate the camera used
Platform guidance is unusually direct on this point. Content should be encoded and uploaded in the same frame rate it was recorded, with 24, 25, 30, 48, 50 and 60 frames per second listed as common values. Interlaced material should be deinterlaced first, so 1080i60 becomes 1080p30 rather than a progressive file that still carries field artifacts.
Changing frame rate in the export does not add information. Going from 24 to 30 duplicates frames, which makes slow pans and credits stutter in a way that is easy to see on a large screen. Going from 60 to 24 throws away more than half the frames, which turns handheld footage into a sequence of jumps. If a client asks for a different rate, do the conversion deliberately with a retiming tool and check the result at a fast cut. Do not let an export preset make that decision for you.
Mixed sources are the other trap. A timeline that mixes 23.976 and 25 fps clips will drift against its own audio over a long cut. Fix the clips at import, not at export.
Bitrate is a budget, not a score
The published upload recommendations are a useful floor because they come from the platform that will compress the file again:
| Resolution | Standard rate (24, 25, 30) | High rate (48, 50, 60) | | 2160p | 35 to 45 Mbps | 53 to 68 Mbps | | 1440p | 16 Mbps | 24 Mbps | | 1080p | 8 Mbps | 12 Mbps | | 720p | 5 Mbps | 7.5 Mbps |
HDR uploads sit higher, with 2160p listed at 44 to 56 Mbps for standard rates. Those figures assume variable bitrate and no hard cap. They are guidance for an upload that the service will transcode, not a target for a master that a client will edit.
Turn the number into a file size before you commit, because that is what the recipient actually feels. At 45 Mbps, ten minutes of 4K runs about 3.3 GB, and an hour runs close to 19.8 GB. The same ten minutes at 1080p and 8 Mbps is about 600 MB. A review copy at 12 Mbps for thirty minutes lands near 2.6 GB, which is still too large for most chat apps. Knowing that in advance is the difference between one export and three.
Hardware encoders are fast and tempting when a deadline is close. They also spend bitrate less efficiently than software encoders at the same nominal setting, so a file that looked fine in a quick check can fall apart in gradients, smoke and dark scenes. If you use one, raise the bitrate by roughly a third and compare a dark scene against the software result before you make it a habit.
Constant or variable, and how often to key
For anything headed to a platform, variable bitrate is the recommendation. It spends data on motion and saves it on static shots, which is exactly where a constant rate wastes space. The same guidance asks for a closed GOP with a length of half the frame rate, which works out to a keyframe every two seconds at 24, 30 or 60 fps. A two second interval also makes scrubbing feel responsive in a player, since seeking rarely has to decode more than a couple of seconds.
For a master that will be edited again, a shorter interval helps more. Some houses key every frame for the highest quality intermediate, which is what a mezzanine format like ProRes is for. H.264 and HEVC are delivery codecs, and pushing their bitrate very high does not turn them into an editing format.
When HEVC earns its keep
Apple's own description of HEVC states that it produces files up to 40 percent smaller than H.264 at the same visual quality, and that it carries support for larger frame sizes and HDR10 metadata. That is a real gain when you are sending a 4K review link over a home connection or archiving a season of finished cuts.
The catch is playback. Older machines, some Windows editing tools and a few browser players handle HEVC poorly or not at all. A safe rule is to keep H.264 for anything that leaves your control without a conversation, and to use HEVC when you know the recipient's setup or when the size difference decides whether the file moves at all. If you are unsure, export both and label them clearly in the filename.
Audio travels with the picture
Picture settings get all the attention, but a delivery is rejected over sound more often than over bitrate. The platform guidance asks for AAC-LC at 48 kHz, with 384 kbps for stereo, 512 kbps for 5.1 and 128 kbps per channel for immersive formats. Mono content is listed at 128 kbps.
Check peaks after export rather than trusting the timeline meter. A limiter that was active during playback is not always applied on the way out, and a clip that peaks above full scale will distort after the platform's own processing. Play the first thirty seconds and the loudest moment of the file on ordinary laptop speakers before you send anything.
Test the file, not the settings
Open the exported file in a plain player, not your editor. The editor can read formats that a client's machine cannot. Watch the first and last frame, scrub to the fastest cut, and check that the duration matches the timeline to the frame. Copy the file to a different drive and play it from there, because a file that only plays from the drive it was written to has a problem you want to find before the client does.
Then check the numbers in a media inspector: container, codec, resolution, frame rate, overall bitrate and audio sample rate. If the inspector shows a frame rate you did not intend, the export preset overrode your project setting, and that is worth fixing now.
A short decision sheet
- Write the destination and the recipient's playback setup at the top of the notes.
- Keep the frame rate the footage was shot at, and deinterlace anything interlaced.
- Choose bitrate from the resolution and frame rate, using published platform figures as the floor for uploads.
- Use variable bitrate with a two second keyframe interval for platform delivery.
- Prefer H.264 unless HEVC's smaller files solve a specific problem for a specific recipient.
- Verify audio codec, sample rate and peaks on the exported file.
- Record the exact settings next to the project so a re-export six months later matches the first one.
An export is a promise about how the file will behave on someone else's machine. Naming the destination first turns the bitrate slider from a guess into a decision with a number behind it, and the next person who opens the folder gets a file that plays the way you intended.



