
Kdenlive sequences within one project share the project's profile. Creating another sequence does not create an independently sized canvas. If two deliverables require independent project profiles, plan separate projects rather than treating sequence tabs as separate resolution settings.
Key Takeaways
- Sequences are timelines stored inside their project.
- They can be rendered separately while sharing project settings.
- A new tab is useful for an edit version, not proof of a new canvas profile.
Separate editorial versions from format versions
Start with a delivery matrix: intended edit, canvas dimensions, frame rate and output purpose. Two cuts with the same underlying profile can be sensible sequences in one project. A landscape master and a vertical deliverable may require independent layout decisions; do not assume that a second tab has acquired its own project profile.
The Kdenlive Sequence manual explicitly says individual sequence settings cannot be changed independently and all sequences use the same project profile. It also distinguishes independent rendering from saving a sequence separately as a project.
Choose the project structure before reframing
- Read the current project profile and record the required profiles for all deliverables.
- Group edits that intentionally share that profile.
- Use named sequences for appropriate alternate cuts or episodes within that group.
- Prepare separate projects when their profile must be independent.
- Revisit composition, captions and graphic positions in every actual delivery canvas.
Do not alter the main project's profile simply to make one sequence appear vertical without reviewing the other sequences. The shared setting means this is a project-level decision, even if only one tab is currently visible.
A hypothetical commercial handoff
Imagine a studio producing three landscape interview edits and one portrait social cut. The three landscape edits could use separate sequences in the landscape project. The portrait deliverable belongs in a separately planned project when it requires its own profile.
The distinction is architectural: it identifies where settings are owned. It does not prescribe a crop or guarantee a particular export quality. Record the project filename beside each deliverable so the next editor knows which setting controls it.
The render-queue version guide helps distinguish submitted outputs after these projects are prepared. Queueing multiple outputs does not make their source sequences independent in profile.
Accept both project scope and final layout
Open each deliverable's project, verify its profile, then inspect the rendered dimensions and composition. Check faces, product labels and captions near the edges, including animated positions rather than one opening frame.
Accept when the required profiles are explicitly owned by the intended projects and the outputs match their briefs. If the wrong canvas appears, resolve project ownership before repeatedly rescaling clips. Independent rendering is not evidence of independently configured sequence settings.
Related tasks
- Will Editing a Kdenlive Project Change a Render Job Already in the Queue?
- How to Set a Picture-in-Picture Frame Without Losing the Subject
- Editing One Nested Intro Changes Every Copy: Is the Source Sequence Shared?
Sources and scope
- Kdenlive Sequence: Sequences share project settings; individual sequence profile changes and separate sequence saves are not supported.
Documentation-based guidance. All scenarios and acceptance worksheets are proposed or hypothetical; no hands-on test, search-volume measurement or AI-citation ranking is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.