Transcoding means converting video from one format to another. The software decodes the original (reading the source’s codec) and re-encodes it into the new format (writing the new codec). You end up with a new file that has the same content but different technical traits.
What can change during transcoding:
Common reasons to transcode:
Transcoding always loses a little quality, because re-encoding cannot keep every bit of the original. The loss is usually small with good codec choices, but it can be noticeable with poor ones. The best approach is to transcode from the highest-quality source down to only what you need. Transcoding already-compressed footage into even more compression makes the loss worse.
Common transcoding tools include FFmpeg (free, command-line, very powerful), Adobe Media Encoder, Apple Compressor, DaVinci Resolve (built in), and dedicated tools like Shutter Encoder.
Here are a few reasons transcoding is such a basic part of editing.
Smoother editing. Footage in delivery codecs like H.264 is hard to edit smoothly. Transcoding to editing codecs like ProRes or DNxHR makes it flow.
Meeting delivery requirements. Each platform wants a specific format. Transcoding gives each one exactly what it expects.
Many deliverables from one source. A single source can become several deliverables through transcoding, with different codecs, wrappers, and resolutions for each platform.
Archiving. Working files in editing codecs get transcoded into archival codecs for long-term storage. Archival codecs favor compatibility and staying playable for years.
Fixing compatibility. Not every codec works in every program. Transcoding to a widely supported format clears up these problems.
Saving storage. Transcoding to a more efficient codec shrinks the file. The same content takes up less space.
Streaming and bandwidth. Transcoding for the web tunes bandwidth use, with lower bit rates, efficient codecs, and resolution scaling all done in one step.
HDR and SDR delivery. Making both HDR and SDR versions of the same content takes transcoding. The HDR master produces the SDR version this way.
Keeping old formats alive. Older formats get harder to support over time. Transcoding to current standards keeps the content playable.
Cloud workflows. Cloud editing and review platforms often want specific formats. Transcoding to their requirements is what makes those workflows possible.
For client work, transcoding happens at a few stages: bringing footage in (source to editing format), making proxies (full resolution to proxy), and delivering (editing master to platform formats). Each stage is its own transcode with its own needs.
For broadcast and feature work, it gets more involved: master files, multiple language versions, multiple resolutions, and multiple delivery formats. Each transcode is its own specific deliverable.
Here is how transcoding usually goes.
Pick your source and destination formats. Know what you have (the source) and what you need (the destination). The destination depends on the goal: editing, delivery, or archiving.
Choose a tool. Adobe Media Encoder, Apple Compressor, the DaVinci Resolve deliver page, FFmpeg, or a dedicated tool. Pick based on your workflow and how complex the job is.
Set the options. Codec, container, resolution, bit rate, frame rate, color space. Each one shapes the result. Presets make common jobs quick.
Check the source first. Make sure the source file is good before you start. A bad source makes a bad transcode, and the conversion only amplifies problems.
Balance quality against file size. A higher bit rate means better quality but bigger files. A lower bit rate means smaller files but lower quality. The right balance depends on the goal.
Run the transcode. The conversion takes time, depending on the source size, the destination, and your computer. Modern hardware speeds many of these up a lot.
Check the result. Play the new file to confirm it works. Look at the video and audio, and make sure the length matches. A quick check catches problems early.
Batch process when you have many files. Most tools let you set things up once and run a whole batch. This is handy for projects with a lot of source media.
Match delivery specs exactly. Platforms like YouTube, Netflix, and broadcast have specific requirements. Match them closely, since small differences can get a file rejected.
Use hardware acceleration when you can. Many modern GPUs speed up H.264 and H.265 encoding a lot. Turning it on makes transcoding faster with no quality loss for most uses.
Keep the metadata you need. Things like timecode, color metadata, and captions should carry through. Check that the new file still has them.
For most client work, transcoding is just part of the pipeline. Bringing footage in, making proxies, and delivering all involve it. Knowing your tools speeds up the whole job.
Here are a few patterns that cause transcoding trouble.
Quality loss from a poor codec choice. Going from a high-quality source to a heavily compressed destination loses quality. Match the codec to the goal: heavy compression for streaming delivery, light compression for editing.
Too many passes. Transcoding the same content over and over (H.264 to ProRes to H.264 to MP4) stacks up quality loss. Each pass loses a little, and several together can show. Always start from the highest-quality source you have.
Wrong color space. Source and destination in different color spaces with no proper conversion. The colors come out wrong.
Frame rate artifacts. Changing the frame rate during transcoding can add judder or motion problems. Keep the frame rate the same unless you really need to change it.
Wrong delivery format. Transcoding to a format the platform will not accept, so the delivery gets rejected. Match the platform’s requirements closely.
Bit rate too low. Heavy compression that adds visible artifacts. The file looks bad. A higher bit rate, within reason, looks better.
Bit rate too high. Files that are bigger than they need to be, which means slow uploads and wasted bandwidth. Match the bit rate to the goal.
Lost metadata. A transcode that strips important metadata like timecode, captions, or audio channels. The file loses some of what made it useful.
Audio sync drift. Changing the frame rate can pull the audio out of sync if it is not handled right. Check the sync after any frame rate change.
Long transcodes that block other work. Conversions that tie up your computer. Run them overnight or in the background so you can keep editing.
A bad source that gets worse. Transcoding from already-degraded footage amplifies the damage. A transcode cannot add quality the source never had.
For client work, careful transcoding is part of doing the job well. Editors who understand it deliver clean files. Those who do not can end up with subtle quality issues.
Transcoding is one of those quiet technical steps that only gets noticed when it goes wrong, which is exactly why we take it seriously. At Clipmasters, your dedicated editor makes deliberate format choices at every stage, matching each platform’s specs so your video looks right wherever it lands. You never have to worry about codecs or settings. You just get clean files in the formats you need.
Both words mean changing video from one format to another. "Transcoding" is the more technical term in video work, and "converting" is more common in everyday use. They do the same thing: decode the source and re-encode it to a new format. The two terms are basically interchangeable.
A little loss is unavoidable when you re-encode, because lossy codecs cannot keep every detail. How much depends on your codec, your bit rate, and how many times you transcode. The best approach is to start from the highest-quality source, use sensible bit rates, and keep the number of passes down.
When the footage does not play smoothly while you edit. Delivery codecs like H.264 and H.265 are built for compression, not editing. Transcoding to editing codecs like ProRes or DNxHR makes things much smoother. The time you spend up front pays off in faster editing.
It depends on the goal. For editing: ProRes on Mac or DNxHR across platforms. For delivery: H.264 for the widest compatibility or H.265 for better compression. For archiving: ProRes 4444 or DNxHR HQX for top quality, or ProRes 422 or DNxHR HQ for a good balance of quality and size.
It depends on the length of the footage, how complex the source and destination codecs are, the resolution, and your computer. Modern hardware can often transcode faster than real time using GPU acceleration. Heavier jobs, like RAW to ProRes, can run slower than real time. Most software shows you a time estimate as it goes.
Skip to content
