How to Burn In Timecode in Premiere Pro and When to Skip It

Burned in timecode on a Premiere Pro review export comes down to one small piece of math, right, which is that a ninety second ad at 25 frames per second is 2,250 frames. When a client writes back asking you to fix the bit around twenty two seconds, they have handed you a window of roughly fifty frames and asked you to guess which one they meant. That guessing is the whole reason editors burn in timecode in Premiere Pro before a cut goes out, so the client can read a number off the picture and type it back to you, and to be very honest it works, and I am not here to tell you it is broken.

The catch here is what it costs on the other side of the round. In my agency we used to export a review version with the numbers burned in and then a clean master once the notes were closed, so a three round job quietly turned into six exports instead of three. Add the render minutes and that one afternoon when the wrong file goes to the client with a grey number in the corner, which I have done myself, and I'm pretty sure plenty of editors reading this have done it too, right.

So this post starts with the honest tutorial, the Premiere Pro timecode effect, the export overlay and a two preset routine that keeps the numbers off your master. Then comes the part almost nobody writes about, which is that burn in only exists because clients quote times by eye, right, and that problem has a different answer now.

Why editors burn in timecode for client review

Think about what the client is actually holding while they watch your cut. You have a timeline, a playhead and a program monitor that shows the exact frame, and they have a browser tab with a progress bar maybe four hundred pixels wide, right, so every pixel of that bar covers five or six frames. So they do the human thing and describe it, the bit after he says growth, the shot with the blue chair, somewhere around twenty two seconds, and then you sit there scrubbing and guessing and so on.

Burning a number into the picture fixes that vocabulary problem in the cheapest way available, because the client is suddenly reading the same clock you are reading and the note comes back as 00:00:22:14 instead of a description of a chair. That is why the habit has survived everywhere from dailies on a feature set down to a founder watching an ad on his phone, and if you want the background on those four pairs of digits, I wrote a plain explainer on how SMPTE timecode works.

In my agency, voice notes over WhatsApp basically double the round, because every vague description turns into a reply asking which moment they meant, so numbers on screen were a really really big step up, does that make sense, right.

How to burn in timecode in Premiere Pro step by step

There are two honest ways to do this in Adobe Premiere Pro, and I use both, depending on whether the overlay needs to live inside the sequence or only inside one particular export.

The Timecode effect on an adjustment layer

The sequence method uses the built in Timecode effect. Create an adjustment layer from the New Item button in the Project panel, drop it on the highest video track and stretch it across the full length of the sequence. Then find Timecode in the Effects panel under Video Effects and then Video, and drag it onto that adjustment layer rather than onto a clip, because on a clip it only shows up while that one clip is playing. Open Effect Controls and go through it properly, right, because the defaults can quietly show you a number that does not match your timeline.

• Position moves the box, Size scales the digits, and Opacity controls the black plate behind them.
• Format stays on SMPTE for client work, since the feet and frames options are for film people.
• Timecode Source is the one people get wrong: Clip counts from the first frame of whatever the effect sits on, Media reads the timecode embedded in a source file, and Generate counts from a start number you type in.
• Time Display has to match the sequence frame rate, so 25 for a 25 fps job, otherwise the frame digits drift away from your program monitor.
• Offset shifts the count by a number of frames, handy when a slate or bars sit in front of the programme.

The rule I follow is pretty simple, right. If the sequence starts at 00:00:00:00 and the adjustment layer starts on its very first frame, Clip already matches the timeline. If the sequence starts at 01:00:00:00 the way a lot of broadcast work does, switch to Generate and type that hour in, which you can confirm from Start Time in the Timeline panel menu.

The Timecode Overlay in the export settings

The export method lives in the export settings, where the Effects section (a tab if you work in Media Encoder) has a Timecode Overlay checkbox with its own position, size and opacity controls and a choice of where the numbers come from. I like this one better for exactly this job, right, because the overlay only exists in that render, so the sequence stays clean and you never have to remember to switch a track off before the master goes out.

A worked example with two export presets

On that same ninety second ad, with three review rounds planned, I set the export once as an H.264 review file with Timecode Overlay ticked and the box parked bottom centre at a size you can still read on a phone, and save that as a preset called Review TC. Then I make a second preset for the master, ProRes or whatever the delivery spec asks for, with every overlay switched off, and call it Master Clean. Every round after that is the same couple of clicks, right, and on the final round both presets go to the Media Encoder queue together, so the clean file and the review file can never be confused because they were never the same render.

If you go the adjustment layer route anyway, keep that layer on its own labelled track so nobody wonders in six weeks why a cutdown has numbers on it. Markers are a related habit and useful for your own memory, though they stop where the client starts, and I got into that in Premiere Pro markers against a review tool.

The problems burned in timecode creates

A timecode overlay in Premiere Pro solves a communication problem by creating a file management problem, right, and the file management problems are the ones that bite, because nobody notices them until the wrong file is sitting in the client's inbox.

Even with presets you are exporting twice every round, which means two renders, two uploads and two file names that nobody can mix up, and on a long form piece that adds up to real hours across a month. If you have ever tried to work out what to charge when revisions eat your hours, those doubled renders sit right in the middle of that number and nobody is paying you for them.

The overlay also covers a piece of your frame, so on a vertical cut where the safe area is already tight you end up hiding exactly the corner the client wanted to talk about. And the number still has to travel from the screen into an email, so a human reads eight digits off a moving picture and types them into a message. I have received 00:01:42:13 when the client meant 00:01:24:13 more times than I can count, right, so at the end of the day you have built a bridge out of somebody's short term memory.

If you work in other tools the trap has the same shape, and I walked through it for Blackmagic in Resolve burn in timecode and when comments win and for Apple's editor in burning timecode for Final Cut Pro client review.

Frame accurate comments that carry their own timecode

What made me stop burning numbers into most of my review exports was realising that if the player the client watches in already knows the frame, nobody has to read a number off the screen or type one back, right, because the comment carries its own timecode.

That is basically what we built PlayPause around. You upload the cut and send one link, and the client opens it in a browser with no account and no install, so when they pause and type, the comment sticks to that exact frame. They can drag a range when the note covers a whole section, draw straight on the frame when the note is about a position rather than a moment, and your team can reply in a thread and @mention whoever needs to see it, all on every plan. There is a fuller breakdown on the time coded annotations page.

New versions stack on the same card, so MV1, MV2 and MV3 sit together and nobody asks which link is current. On Agency and up you also get side by side version compare plus AI transcription with a clickable transcript and an SRT export, which ties into how I get captions approved fast, and on Creator and up there is who watched analytics, so you can see whether the person holding up sign off has actually opened the cut before you chase them.

Seeing client comments inside Premiere Pro

The piece that closes the loop for Premiere editors is the panel. PlayPause has a Premiere Pro panel that brings the client comments into Premiere itself, right, so the notes sit next to your program monitor instead of in a browser tab on the other screen, and when you click a comment the playhead jumps to that frame without the timecode ever passing through anybody's memory.

You can also upload straight from the timeline, and pairing works with a code you type once rather than an IT ticket. There is more detail on the Premiere Pro panel page and the wider PlayPause for Premiere Pro overview, and I wrote a walkthrough of the frame matching itself in syncing client comments to the exact Premiere frame.

To be straight about the limits, Premiere Pro is the only editor with a PlayPause panel of its own, so in DaVinci Resolve, Final Cut Pro and After Effects you export, upload, review and then work from the notes in your editor, which still beats reading digits off an overlay, right, though it is not the same one click jump.

When burned in timecode is still the right call

I am not going to pretend the overlay is dead, and trust me on any level, there are jobs where I burn it in without thinking twice, right.

The way I decide is pretty plain. If a machine or a specialist downstream needs the number, I burn it in, and if a client needs the number only so they can describe a moment to me, I give them a player that already knows the frame. A rough cut going to a non technical stakeholder is the clearest case, because a link and a place to type serves that person far better than digits in the corner, you see what I mean here.

And when the feedback itself is the problem, for instance a stakeholder who rewrites the brief in round three, no overlay fixes that, and I put the honest version of it in six types of difficult video clients.

Frequently asked questions

Where is the Timecode effect in Premiere Pro?

Open the Effects panel, go to Video Effects and then Video, and Timecode sits in that folder. Drag it onto an adjustment layer above your whole sequence rather than onto a single clip, because on a clip it only appears while that clip plays. Then open Effect Controls and set Timecode Source, Format and Time Display before you trust the numbers, right.

Why does my burned in timecode not match the sequence timecode?

In my experience it is almost always one of three settings. The adjustment layer does not start on the first frame while Source is set to Clip, or the sequence starts at 01:00:00:00 and nobody switched to Generate, or Time Display is on a different frame rate than the sequence. Check Start Time in the Timeline panel menu, line the layer up with frame one and match the frame rate.

How do I burn timecode into an export without changing my sequence?

Use the Timecode Overlay in the Effects section of the export settings, or the Effects tab in Media Encoder. That overlay exists only in that one render, so the sequence stays clean. Save it as a review preset and keep a separate clean preset for delivery, which is the safest habit when both files come from the same sequence.

Can clients comment on the exact frame without burned in timecode?

In PlayPause the client opens the link in a browser with no account, pauses where the problem is and types, and the comment stores the frame for them, and they can also draw on the frame or mark out a range. Nobody reads the number off the screen, so nobody can type it back wrong, which is basically the point of a review link.

If you are tired of rendering everything twice, set up a workspace, send a client one link and watch the notes land on the exact frame instead of in your inbox. Every plan on the PlayPause pricing page comes with a 7-day free trial, so you can run one real round through it before you decide anything, right.

So yeah. That's my way of saying it.