Ask three editors where post-production starts and you’ll get three answers, all wrong in interesting ways. It doesn’t start in the NLE. By the time a timeline exists, half the decisions that determine whether the project finishes smoothly have already been made: how the cards were offloaded, whether anything got verified, what codec the proxies are, where the audio lives. Post is a pipeline, the pipeline has seven stages, and every stage’s mistakes get more expensive to fix one stage later. This page is the map. Each stage below gets the plain-language version of what happens there, the handoff that matters, and the deep guides we’ve built for it.
Last updated: August 2026. This is a reference page and the spine of our gear-guide library; it carries no product pitches of its own. The linked guides do the recommending.
TLDR
If you just want the answer: the pipeline is Ingest → Edit → Color → VFX → Audio → Deliver → Archive, the handoffs between stages matter more than the tools inside them, and the two stages amateurs skip (ingest discipline at the front, real archiving at the back) are the two that decide whether you ever lose work. Everything else is craft; those two are insurance.
Stage 1: Ingest and data management
Everything downstream inherits this stage. Ingest is the unglamorous sequence of getting camera media onto real storage without lying to yourself about whether it copied: offload with checksum verification (not drag-and-drop; software that mathematically proves the copy matches), a folder structure you’ll still understand in February, and a backup that exists before anyone formats a card. On bigger sets this is a whole job (the DIT), and our DIT kit guide is the working version of that cart. For solo shooters it’s twenty disciplined minutes, covered end to end in the travel offload workflow and the media management guide. The card-and-reader side (CFexpress vs SD, what readers don’t bottleneck) has its own guide too.
The handoff that matters: media verified, named, structured, and backed up twice before the edit ever sees it. An editor opening a project should never be the person who discovers a corrupt clip.
Stage 2: Edit
The stage everyone pictures, and the one with the deepest gear rabbit hole. The real hierarchy of what makes editing fast: storage speed and proxies first (a smooth timeline is a storage problem before it’s a CPU problem), then the machine, then the room around it. Our editing-hardware guides cover the whole stack: the Mac guide and GPU guide for the machine, the laptop guide for mobile cutting, the keyboard, mouse, and dock guides for the desk, and the proxy workflow guide for making any machine feel faster than it is. If your media lives on shared storage (it should, once projects overlap), the editing server build is the infrastructure piece, and the whole room is covered in the edit suite guide.
The handoff that matters: a locked cut, exported as a reference, with timelines cleaned of dead clips and disabled tracks. Every downstream stage (color, VFX, audio) works against picture lock; every “small change after lock” ripples through all three.
Stage 3: Color
Color is two different jobs wearing one name: correction (making shots technically right and matched) and grading (making them feel like something). Both depend on seeing the image truthfully, which makes this the most display-dependent stage in the pipeline: the grading monitor guide is the buying decision, calibration is the maintenance discipline, and the budget path of using an OLED TV as your grading and client display is the best money trick in modern color. The conceptual side (what Rec.709 means, log footage, color management vs LUTs) lives in our color spaces reference, and the control surface guide covers when knobs beat a mouse.
The handoff that matters: graded picture rendered against the locked cut, in the delivery color space, with the VFX shots round-tripped (which is why color and VFX coordinate more than any other pair of stages).
Stage 4: VFX
Visual effects in real-world post is mostly not monsters; it’s cleanup, screen replacements, sky swaps, stabilization, and the invisible fixes nobody is supposed to notice. What makes VFX its own stage is the round-trip: shots leave the edit, get worked in other software, and come back matching frame counts, color, and naming exactly. On the infrastructure side it’s the hungriest stage (the VFX workstation guide and cloud rendering guide cover the compute), the on-set data kit covers gathering the reference material that makes shots cheaper, and the small-studio pipeline stack is the software map.
The handoff that matters: versioned shots with predictable names dropped back into the conform. If you’ve ever hunted for “comp_v7_FINAL_final2.mov,” you already know why the naming convention is the whole game.
Stage 5: Audio
Audiences forgive soft focus; they do not forgive dialogue they can’t hear. Audio post is dialogue editing and cleanup (the modern AI tools for which we compared head-to-head), music and effects against the picture, and a mix that hits the delivery loudness spec rather than whatever felt right on the couch. The monitoring chain is its own small stack: studio monitors that can tell the truth in your room, headphones for the detail passes, and enough acoustic treatment that the room stops lying to both. For capture-side problems arriving in your timeline, the audio rescue guide covers what’s fixable.
The handoff that matters: a mix delivered as both a stereo master and stems (dialogue, music, effects separately), because the first revision request after “the mix is done” is always a version you can only make from stems.
Stage 6: Deliver
Delivery is where finished work goes to get technically rejected. Every destination has a spec (resolution, codec, bitrate, loudness, captions) and the spec, not your taste, is the assignment. Our export settings guide covers the social platforms, the encoder presets explainer decodes what the settings mean, the frame rate cheat sheet and aspect ratio cheat sheet handle the two eternal conform questions, and the review-and-approval tools guide covers getting the client’s yes before anything uploads. The delivery specs sheet (companion to this page) is the one-table version for broadcast, streamers, and platforms.
The handoff that matters: the master file plus a QC pass on the actual deliverable (watch YOUR export, not your timeline) plus the paper trail of what was sent where. Future-you will ask.
Stage 7: Archive
The stage everyone plans to do later, where “later” means “after the drive fails.” A real archive is boring and specific: the project consolidated to only what’s needed to reopen it, verified copies on at least two different media, one of them off-site or offline, and a note that tells 2029-you what’s where. The archiving guide is the full workflow (including when LTO tape starts beating hard drives on price), the NAS hub covers the live-storage tier archives graduate from, and the storage calculator does the capacity math. Archive properly and every past project is an asset; don’t, and it’s a liability with your name on it.
The handoff that matters: this one hands off to you, later. The test of an archive is whether a stranger could restore the project from your notes. Write the notes.
The map in one table
| Stage | The job | The expensive mistake | Start here |
|---|---|---|---|
| Ingest | Verified media, structured, backed up | Formatting a card on faith | DIT kit · offload workflow |
| Edit | The cut | Cutting on unverified media, no proxies | Editing hardware guides · proxy guide |
| Color | Truthful, matched, graded picture | Grading on a lying display | Monitor guide · calibration |
| VFX | Invisible fixes, round-tripped | Un-versioned shot chaos | VFX workstation · pipeline stack |
| Audio | Dialogue first, mixed to spec | Mixing in an untreated room to no target | Studio monitors · dialogue tools |
| Deliver | The spec, exactly | QC’ing the timeline instead of the file | Export settings · delivery specs |
| Archive | Restorable, verified, noted | “It’s on that drive somewhere” | Archiving guide |
FAQ
Do small projects really need all seven stages?
They need all seven jobs; they don’t need seven people or seven weeks. A solo YouTube video compresses the pipeline into an afternoon: verified offload, cut, a color pass, a cleanup pass on the dialogue, export to the platform spec, project archived. Same order, same handoffs, smaller everything. The order is the part that scales down intact.
Why is color before audio?
Convention and practicality rather than law: both work from picture lock, and facilities often run them in parallel. Color sits earlier in the map because VFX round-trips through it. If you’re one person doing everything, do them in whichever order keeps you sane; just do both after lock, because redoing a mix against a re-cut is the most demoralizing rework in post.
Where does AI change this map?
Inside stages, not between them. Transcription accelerates the edit, neural tools accelerate dialogue cleanup and roto, generators add a new kind of source media with its own ingest quirks. The stages and handoffs have survived every tool transition since film, and they’re surviving this one; our AI tools hub tracks the inside-the-stages story.
In conclusion
Post-production is a relay, and the baton matters more than the runners. Verify at ingest, lock before you polish, round-trip cleanly, mix to spec, deliver to spec, archive like the drive dies tomorrow. Every guide on this site hangs off one of these seven stages, and this page is the index; it gets updated as new guides ship. If a stage in your workflow keeps hurting, that’s the guide to read next… and if we haven’t written it yet, tell me in the comments, because that’s how half this library got built.
