Quick Shot vs. Projects: which one should you start with?

Use Quick Shot for a single, disposable clip with no setup; use a Project the moment you need more than one shot to hold together — a recurring character, a consistent look, or an edit you'll actually assemble in the Timeline. Both generate through the same models and the same credit wallet — the difference is entirely about structure, not capability.

What Quick Shot is for

Quick Shot (/dashboard/create) is a freeform composer: write a prompt, pick a model, generate. Behind the scenes it still creates a scratch project so the take has somewhere to live, but you never see or manage that structure. It's the right tool when:

• You're testing what a model does with a prompt before committing to a real project
• You need one clip for something outside a film — a quick social post, a one-off reference image
• You don't need the shot to relate to any other shot

What a Project is for

A Project is the full Script → Board → Shot → Timeline structure — scenes, shots, takes and an editable timeline that all belong to one film or campaign. Reach for a Project as soon as any of these are true:

• You have more than one shot that needs to end up in the same edit
• A character, product or location needs to look the same across shots — that only works through the Library, which is project-scoped
• You want to reorder, trim or assemble what you generate, not just look at it

The line between them isn't permanent

Nothing about Quick Shot output is locked out of a real project later — a good take is a good take regardless of where it started. But building the habit of starting in the right place saves a rebuild later: a character generated inside Quick Shot has no Library asset backing it, so shot two won't automatically look like shot one.

If you're unsure which one you need, ask: will there be a shot two? If yes, start with a Project.