GoScript
Back to Blog
GoScript Journal

Render Settings: Stop Guessing at Export Time

·7 min read·GoScript Team /Design

Render settings are where a clean edit meets an audience, and they are also where a lot of editors default to whatever preset they clicked last time. That habit works until a platform recompresses your file and the result looks soft, or until a big export eats an afternoon it did not need to.

The three dials that matter are codec, bitrate, and resolution. Understand what each one does and export stops being a gamble.

The codec decides more than bitrate

The codec is the language the file is written in, and it sets the ceiling on quality. A high bitrate inside a weak codec still looks poor, while an efficient modern codec can hold up at a lower number. Choose the codec the destination expects before you fuss over the number next to it.

For uploading to a platform, a common delivery codec with a generous bitrate is the safe bet, because the platform will transcode it anyway. For archiving a master, pick one built for quality and for staying readable years from now, not one tuned for small size.

The number next to the codec is a target, not a guarantee. Two files at the same bitrate can look very different depending on how much motion sits in the frame, so treat the recommendation as a starting point and check the result rather than trusting it blindly.

Match resolution to the destination

Exporting 4K when the platform or the viewer only ever shows 1080p mostly wastes time and disk. Export at the resolution the video will actually be watched, unless you have a reason to deliver higher for future use or for a client who asked.

If your timeline is a mix of resolutions, decide the export frame from the highest-quality source you intend to keep, then let the editor scale the rest. Upscaling soft footage will not add detail, but it will keep the project consistent.

The right export is the one that survives the platform's own compression without falling apart. Size is a side effect, not the goal.

Settings by destination

  • For platform uploads, use a standard delivery codec and a bitrate near the top of the recommended range.
  • For email or quick review, a smaller file with a lighter bitrate is fine, since notes matter more than polish.
  • For archive, keep a high-quality master and store the project file beside it.
  • For a client broadcast, follow their spec sheet exactly, down to the audio levels.

Test before the final render

Render a short sample of the busiest part of the timeline, the segment with the most motion and the most overlays. A calm talking-head shot will pass almost any setting, so testing on an easy section tells you nothing. The hard part is where compression artifacts appear first.

Watch the sample on the device and platform you expect the audience to use. A file that looks sharp on a large calibrated monitor can still show banding on a phone, and that is exactly the difference an export preset should be chosen to avoid.

Keep the last few exports you were happy with and their settings in a note. When a client likes a prior delivery, you can match it in a minute instead of guessing at the numbers again, and consistency across a series is worth more than any single clever setting.

Key takeaways

  • Pick the codec before tuning bitrate, since codec sets the ceiling.
  • Export at the resolution the video will really be watched.
  • Use a high-quality master for archive, separate from delivery.
  • Test the busiest few seconds, not an easy shot.
  • Check the sample on the device your audience uses.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel