DaVinci Resolve is a post-production workspace for editing video, correcting color, building visual effects, mixing sound, and rendering finished media. A project stores timelines, edits, grades, effects, audio decisions, and links to source files. DaVinci Resolve does not turn imported camera footage into one self-contained movie at the beginning. The project continues to depend on organized source media until the editor creates a final render or a managed archive.
Media comes first
The Media page is where footage enters the working project. Bins hold clips chosen by the editor, while smart bins collect material that matches metadata rules. Camera cards can be cloned before editing so the working copy does not become the only copy. This stage also exposes frame rate, timecode, audio channels, and other details that affect later decisions.
External sound can sync to picture by matching timecode or recorded waveforms. Manual alignment remains available when neither method produces a reliable match. A scratch microphone and a separate recorder may have different clocks, so a good match at the first clap can drift during a long take. Checking another point near the end catches that problem before the timeline fills with edits based on bad synchronization.
Projects live in libraries
DaVinci Resolve keeps projects inside a project library. A DRP file is a transportable project export. Importing it copies the project into the selected library; DaVinci Resolve does not edit the DRP file in place. Later changes belong to the imported copy, which means the original export does not automatically become a current backup.
The distinction matters when two people exchange revisions. Sending the same old DRP again does not collect edits made after import. A fresh export or shared project-library workflow is needed. Source clips are another dependency. If their folders move or a drive letter changes, timelines can show offline media until the editor relinks the files to their new location.
Nodes shape color
The Color page arranges corrections as nodes. One node can balance exposure, another can isolate a face, and a later node can apply a look. Their order matters because each node receives the result of the previous one. Moving a noise-reduction or keying step can therefore change the final image even when every control keeps the same numeric value.
Color management defines how DaVinci Resolve interprets camera material and transforms it for the display and final output. A wrong input color space can create flat or overly contrasted images. Applying a display transform twice causes another mismatch. The viewer alone is not proof that the render will match a broadcast file, web upload, or cinema package; project settings and delivery tags need deliberate choices.
Audio has layers
Fairlight distinguishes clip adjustments, track processing, and bus processing. Changing one clip repairs a local problem. A track effect changes every clip routed through that track, while a bus affects several tracks together. Channel mapping decides which recorded channel reaches which timeline channel.
This routing can solve complex dialogue and music mixes, but it can also hide sound. A muted bus, incorrect patch, or clip placed on an unexpected channel may produce a silent render even though meters moved elsewhere in the project. A short test render and a listen outside DaVinci Resolve reveal routing mistakes before the complete export runs.
Delivery is separate
The Deliver page turns a timeline into files or queues it for rendering. Container, codec, resolution, frame rate, audio layout, and filename are independent choices. A preset is a starting point tied to a destination, not evidence that every source and timeline setting matches that destination.
Render caching and proxy media can make a heavy timeline easier to edit, but both consume storage and can become stale after changes. Final delivery should use the intended source quality and inspect the completed file. That check should cover picture duration, audio channels, subtitles, and the first and last frames rather than relying only on a successful render message.
