A clear place to begin.
Explore LIMINA Video Studio for timeline editing with visuals, audio, and captions. Understand cloud and local projects, exports, and Agent availability.
One decision at a time.
- 01
Choose your project mode
Open a cloud project from MV Flow or create a local project. Check local project requirements if you need a local workspace or Agent.
- 02
Place assets on tracks
Select or import assets, then place them on tracks. Adding an asset to the library and placing it on the timeline are separate actions.
- 03
Arrange picture and sound
Adjust order, duration, composition, and captions. Check how sound meets each shot and pay attention to save feedback.
- 04
Preview and export
Check that assets are complete and the result matches your intention, then export through your project mode. Keep a project copy if you want to edit again.
Bring separate assets into one piece
The timeline works with generated or imported assets. Arrange shots around the music, work with visuals, audio, and captions, and use preview to review the composition.
Preview resolution and export quality are different settings. Check the actual exported file when evaluating the final result.
Choose between cloud and local projects
Cloud projects open from MV Flow, remain associated with a script branch, save to the cloud, and export on the server.
Local projects can be created directly or converted from a cloud project. The project and required assets are stored on your machine and export locally. A successful conversion does not delete the original cloud project.
- A cloud project continues work on the current MV branch.
- A local project provides a local workspace, supported Agent connections, and project package operations.
- Conversion downloads and validates the assets actually referenced by the project.
Agents work within local projects
A local project can use a supported, configured Agent connection. Your LIMINA account does not replace the account, sign-in, or configuration required by your selected model service.
A connection does not prove that every model and creative workflow has been validated. Generation still follows current account permissions and cost confirmation rules.
Assets, finished videos, and projects have different purposes
New cloud uploads accept images and audio. Images require safety review and audio requires media validation; this is not unrestricted video upload. Existing cloud videos and generated clips remain usable according to their permissions.
An MP4 is for playback, while a project package is for continued editing. Convert a cloud project to a local project before exporting its package, and check the destination client and asset integrity when restoring it.
Check the supported release
Desktop capabilities require a client that matches your system. Platform releases and available features must be checked separately; a feature description does not mean every installer supports it.
This page explains the workflow, not universal compatibility with every device, Agent, or model combination. Review the current release information before downloading.
Before your next step.
Can I use an Agent directly in a cloud project?
Not currently. Follow the conversion flow to create a local project, then configure a supported Agent connection.
Are imported assets automatically placed on the timeline?
Collecting an asset is not the same as arranging it. Once an asset is in the library, use the appropriate track operation to choose its position and duration.
Does conversion delete my cloud project?
No. Conversion prepares and validates the required assets and opens the local project after success. The original cloud project and source assets are retained.
How is video export different from project export?
A video is for viewing and distribution. A project preserves the structure and assets needed for further editing. Keep both separately when you need both uses.