A reliable video post-production workflow turns camera originals into files that meet a real delivery brief, with enough organisation to make review and later revisions manageable. The steps below give you a practical sequence, but the order can change when a project needs specialist audio, colour or visual effects work.
Before you open an editing application, agree what you are making, who must approve it and where the finished files need to go. Those decisions determine which footage to keep, what each handoff needs to contain and how you will check the final export.
1. Agree the brief and delivery target
Write down the intended audience, purpose and destination first. A short social edit, a client master and an upload to YouTube may use the same footage but need different runtimes, aspect ratios, caption files and review versions. Do not assume that the export suitable for one destination is also the right archive master or broadcast delivery.
Ask the recipient for a current specification when one exists. Confirm frame size and rate, codec or container, audio layout and any loudness target, colour space, caption language and format, file naming, delivery method and deadline. There is no single codec, loudness value or archive format that suits every project. Where a detail is not specified, record the assumption and get agreement before finishing.
Also settle the review process. Name the person who gives consolidated notes, how they will mark timecodes, and whether they are approving the edit, the picture finish or the final master. Agree which project files, media or supporting documents must be handed over. If the work is for a YouTube channel, check its current upload requirements rather than treating a client or broadcast specification as interchangeable with platform guidance.
2. Ingest and protect the footage
Copy the camera originals, production audio and other source material into a project structure that you can understand later. A simple starting point might separate camera media, sound, graphics, music, project files, review exports and final deliveries. Preserve the original card structure when practical; camera metadata or folder relationships can matter to relinking and later troubleshooting.
Use consistent names for the project, sequences and versions. For example, a sequence might be BrandFilm_Assembly_v01, while a review file includes the date or review round. Avoid names such as final-final-new, which do not say which version was approved. Keep names readable and avoid changing original camera filenames unless your workflow has a reliable mapping back to the source.
A copy is not automatically a backup. Verify that copied files open and that the media count or expected folders are present before formatting cards or deleting anything. Keep a separate verified copy appropriate to the project's risk, storage and production needs. Small personal projects and commercial shoots may need different safeguards, but neither should rely on an unverified transfer as its only surviving source.
If several people will work on the project, define where the authoritative media and current project file live, and who is allowed to rename or move them. A handoff that contains footage but no folder map, project version or note about missing media can cost more time than it saves.
3. Review, select and assemble the edit
Organise clips into bins or folders that suit the shoot: by scene, camera, date or media type. Review the footage and mark useful takes, continuity issues, technical problems and moments that might support the story. A spreadsheet, paper log or editing application's markers can all work; choose a method the next person can read.
For longer shoots, make selects before building the sequence. Keep a record of why a shot was chosen or excluded if that choice may be questioned later. If a clip has a problem, note whether it is unusable, needs a workaround or simply needs a second look. These labels help distinguish an editorial decision from a technical limitation.
Build an assembly around the brief rather than polishing individual shots too early. Establish the main order, necessary coverage and approximate runtime, then refine pacing and continuity. Keep the timeline clear enough that another editor can understand its tracks and sequence purpose. A clean assembly is more useful to reviewers than a visually polished cut whose structure is still changing.
Use review exports with unambiguous version names, and ensure notes refer to that version. If you are making a recurring channel video, this is also where you can check that the rendered file is suitable for its later use; for example, the practical considerations in replaying the same video file all day on a YouTube live stream differ from those for a one-off upload.
4. Refine the picture and structure
Once the assembly communicates the intended story, refine shot choice, pacing, continuity and transitions. Check that each cut has a reason, that the action and eyelines make sense, and that the opening and ending do the job promised by the brief. If runtime is fixed, make the necessary decisions before adding detailed finishing work that could be discarded.
Add titles, graphics and captions when the structure is stable enough to judge their timing. Check spelling, names, contrast, legibility and placement against the intended display. Keep text clear of important picture details and allow enough screen time for a viewer to read it. A title that fits a wide frame may be clipped or awkward in a vertical version, so inspect each required aspect ratio rather than relying on a single master as proof.
Decide whether captions should be embedded in the picture, delivered as a separate timed-text file or supplied in both forms. The destination and accessibility brief determine the choice. Confirm the required language and format with the recipient. Blackmagic Design's DaVinci Resolve Edit documentation describes subtitle tracks that can be moved and trimmed like other timeline media, along with supported import and export options. That is one application's documented capability, not a requirement to use that application.
This is a flexible point in the sequence. A project with simple graphics may be ready for sound and colour work. A project with complex compositing, titles that depend on final timing or multiple delivery shapes may need another picture review after effects are incorporated.
5. Finish sound, colour and effects as needed
Treat audio, colour and visual effects as workstreams that need clear inputs and outputs, not mandatory stages with one fixed order. You can finish them yourself, send selected material to a specialist or omit work the brief does not call for. The key is to state which edit version the specialist receives and how changes are to be returned.
For sound, balance dialogue, music, effects and ambience. Listen for noise, distortion, abrupt edits, missing channels and sync problems, both on headphones and on a practical playback system if available. Ask the recipient for any loudness, peak or channel-layout target rather than guessing a universal value. If a specialist receives stems or consolidated tracks, label them and explain their start point, sample rate and intended use where relevant.
For colour, first make shots coherent in exposure and white balance, then apply a creative look if the project calls for one. Confirm whether the delivery is SDR or HDR and what colour space is expected. A monitor or export preset cannot guarantee identical appearance on every screen, so check the rendered file and, where possible, view it on a suitable display. Adobe's Premiere encoding settings reference explains that export colour-space choices vary; its defaults should not be mistaken for a universal target.
Visual effects may be easier to start before the final picture lock if they affect the edit, or to complete after timing is approved when shots are settled. Give the effects artist exact shot references, handles or source media as agreed, frame rate, colour context and the expected return format. On return, check that the shot duration, framing and version match the timeline. If the project also involves a continuous live music or ambience channel, audio continuity deserves its own check; our guide to fixing audio drift in a 24/7 rain sounds stream covers a different but related playback problem.
6. Review versions and collect notes
A review is useful only when everyone is looking at the same cut. Give each review file a clear version identifier and include it in the file name or review message. Keep an approval copy separate from the working project, and do not overwrite a version that is still being discussed.
Ask reviewers to consolidate feedback where possible and identify notes by timecode or a clear description of the moment. Separate required corrections from preferences, and flag any note that changes the agreed brief, runtime or delivery target. If two reviewers disagree, ask the person responsible for approval to resolve the conflict rather than silently choosing one direction.
After making changes, compare the new version with the previous one and check that accepted notes were addressed without creating new problems. Maintain a short version log: what changed, who requested it and whether it is ready for another review or approved for finishing. A client, editor and sound specialist might each use a different tool, but the handoff still needs the same basics: version, notes, assets and the next action.
If the project is intended for a YouTube channel that also runs a pre-recorded live stream, keep the post-production master distinct from the stream setup and confirm how the finished file will be used. The guide to keeping a YouTube stream running while your computer is off addresses that separate operational question; it does not replace checking the video deliverable itself.
7. Export, verify and deliver
Export from the approved sequence using the destination's current specification. Select the required format, frame size, frame rate, codec, audio settings, colour space, captions and destination deliberately. Check that there is enough disk space and that the selected sequence is the intended one. Adobe's Premiere export guidance describes choosing export settings and a destination; the same practical checks apply whichever editor you use.
For YouTube delivery, its recommended upload encoding settings currently advise MP4, H.264 progressive video, AAC-LC or Opus audio at 48 kHz, and matching the recorded frame rate. The page gives resolution-specific bitrate recommendations, including 10 Mbps for 1080p at standard frame rates and 15 Mbps at high frame rates, and recommends BT.709 for SDR uploads. These are YouTube's recommendations, accessed 3 October 2026, not a universal client, broadcast or archive preset. Check the page again when exporting because platform guidance can change.
Do not treat a completed render as a verified deliverable. Open the exported file and watch it from beginning to end when practical; at minimum, inspect the opening, ending, transitions and any sections where notes were applied. Check picture and sound sync, captions, graphics, colour, playback, duration and file properties against the brief. A fast spot-check can find obvious issues, but it is not equivalent to watching the complete master.
Deliver the right set of files: perhaps a master, a smaller review copy, caption files, audio stems or a project and media package. Include a delivery note that identifies each file and its intended use. Keep the approved project and source assets organised for future revisions. If maintaining a recurring YouTube stream is part of your plan, StreamNeo can remove the separate need to keep a computer running to broadcast an uploaded file continuously, leaving this post-production handoff focused on a verified, ready-to-use video.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
What are the steps after filming?
Confirm the brief and delivery target, copy and protect the media, review and select footage, assemble and refine the edit, then complete any needed sound, colour or effects work. Review the right version, export to the destination specification and verify the finished files before delivery. Some projects change the order when specialists or approvals are involved.
Do I need a particular editing application or controller?
No. Choose tools based on the work, team handoffs, caption needs, finishing requirements, export controls, existing skills and budget. A dedicated controller can suit someone who prefers physical edit controls, but it is optional and does not replace a clear project structure or review process.
Is one export preset right for every video?
No. A YouTube upload, client master, broadcast file and archive copy can have different technical requirements. Get the current specification from the recipient, and use platform guidance only for that platform's delivery.
How should I avoid losing track of revisions?
Give each review file and sequence a readable version name, keep a short change log and ask reviewers to identify notes against the version they watched. Preserve approved copies rather than overwriting them, and record which version is cleared for export.