Lightworks is a non-linear video editor that organizes source clips, subclips, sequences, effects, audio adjustments, and export settings inside a project. Editing changes the sequence instructions rather than cutting the camera files in place. A project can manage tens of thousands of assets, while the final export reads those decisions and renders one continuous file or interchange package.
Projects save themselves
Lightworks records project changes automatically every few seconds, so it has no ordinary Save or Save As command for routine editing. Clips, bins, markers, and sequences remain part of the project state as the editor works.
Automatic saving protects recent decisions, but it also records an unwanted edit quickly. Sequence copies and project backups still matter before a major restructure. Closing the project is not the moment that makes all earlier work safe; the relevant autosaved state may already include the mistake.
Import decides file ownership
Create link references media at its existing path. It avoids another full copy, but disconnecting that drive or moving the folder makes the linked clip unavailable. Copy Local places the media inside Lightworks storage so the original drive can leave.
Those choices also change project deletion. The official project guide warns that deleting a project can remove media imported through Copy Local or Transcode unless another project uses it. Linked originals remain outside the project, while Lightworks removes only their small link records.
Sequences hold the edit
A sequence arranges clips on video and audio tracks. Insert, overwrite, replace, trim, slip, and slide operations change timing in different ways. A ripple-style change can move later material, while another trim can preserve the surrounding timeline length.
Track selection and sync state matter during these operations. A trim aimed at one picture cut can pull linked sound or leave it behind according to the active controls. The sequence needs playback around the edit, not just inspection of the single cut frame.
Proxies reduce playback load
Lightworks can generate lower-resolution proxy files for demanding footage. The timeline then reads lighter media during editing, while final export returns to the original source. This keeps a large project responsive without replacing its master recordings.
Automatic playback quality may choose a higher-quality source than expected. Selecting Lowest available forces the lowest proxy for steadier playback. Export still needs the original media online; a smooth proxy timeline cannot render full quality after the master drive disappears.
Export follows the region
The export menu can target a marked section, a whole sequence, or another defined region. It also controls format, frame rate, size, audio, and destination. Selecting the wrong region can produce a technically successful file that contains only part of the edit or includes leading and trailing black.
Lightworks reports export progress in the Tasks view. Completion confirms that the renderer finished; it does not confirm that the chosen frame rate, colour treatment, audio mix, and region match the delivery request. The finished file still needs playback outside the editor.
Edition limits appear late
Export choices depend on the active Lightworks edition. The official guide states that the Free edition limits YouTube and Vimeo output to 720p, while other editions expose broader targets and resolutions. A project can therefore edit higher-resolution media even when the current licence cannot produce the planned deliverable.
This limit is easy to discover only at the final menu if the delivery format was never tested. A short export at the start of a project confirms that the intended codec, resolution, and destination are available before the timeline accumulates days of work.
