Manual video and audio export in the web app automatically chooses browser or cloud rendering. Agent Plugin video and audio export defaults to the open editor’s browser renderer; cloud rendering requires an explicit choice. ChatCut Desktop renders video on your computer. The destination and Free-account quota depend on where rendering runs.
| Where you work | Where rendering runs | How the file arrives | Free-account limit |
|---|---|---|---|
| Manual web export, compatible timeline and browser | In the open browser | Downloaded or saved by that browser | Does not count toward the 60-minute cloud quota |
| Manual web export, automatic cloud fallback | In ChatCut’s cloud | Download after rendering | 60 minutes total across all projects |
| Agent Plugin, default local export | In the open browser | Downloaded by that browser | Does not count toward the 60-minute cloud quota |
| Agent Plugin, explicitly requested cloud export | In ChatCut’s cloud | Download after rendering | 60 minutes total across all projects |
| ChatCut Desktop local video export | On your computer | Saved directly to the selected folder | Does not count toward the 60-minute quota |
Export manually from the web app
- Select Export in the editor header, then choose the output type and settings.
- ChatCut checks the current browser, output settings, timeline media, motion graphics, and audio requirements. There is no renderer switch to choose manually.
- After starting the job, follow progress under the header Export button. Keep the tab open while a browser export is running.
- Use Download again or View afterward when that action appears.
Compatible video and audio exports run in the open browser. Depending on projected size and browser support, ChatCut either uses browser storage or asks where to save a large output. A compatible device can also offer 4K browser video export.
Manual web export falls back to cloud rendering when the browser cannot encode the requested output, a timeline includes unsupported motion graphics, or the browser cannot safely process the required audio. Cloud export must upload the required media and finish on the server before the file downloads. Actual duration depends on upload, network, queue time, output length, and format; do not estimate it only from timeline duration.
Export with the Agent Plugin
Ask the agent to export video or audio. By default, it renders in the browser tab with the project open. Keep the requested timeline active and that tab open until the file downloads.
If no connected editor can render the output, the agent reports an error instead of switching to cloud. Open the project in a supported browser, activate the requested timeline, resolve any reported compatibility issue, and retry. To use cloud rendering, explicitly ask the agent for a cloud export; it must request renderMode="cloud" in submit_export. The default is renderMode="local", with no automatic cloud retry.
Cloud export quota
Free accounts have a cumulative 60-minute web/cloud export quota across all projects. It is not 60 minutes per file or project and does not reset each month. An active paid plan removes this quota.
To check live usage, open Export in the web editor. The quota panel appears when the current output needs cloud rendering and shows Web free export quota and Used … / 60:00. If the next cloud-rendered job would exceed the total, ChatCut blocks it and shows Upgrade and continue export. Browser-rendered video or audio does not increase that total.
Export video locally in ChatCut Desktop
- In ChatCut Desktop, select Export → Video.
- Choose dynamic range, resolution, frame rate, and export range.
- Choose a destination folder and start the export. Keep Desktop open while it renders.
- When it finishes, select Show in Finder or Open.
Desktop local video export saves directly to the selected folder, does not require a separate cloud download, and does not count toward the Free 60-minute web-export quota. It also offers 4K and, on supported hardware, HDR. Actual speed depends on computer performance, codec support, timeline complexity, and output settings.
This distinction applies to Desktop’s local video renderer. Audio, transparent graphics, and some bundled exports started from Desktop can still use cloud rendering and remain subject to the corresponding limits.
What counts
- Video and audio only when ChatCut routes them to cloud rendering.
- Graphics export.
- Motion graphics rendered as part of an XML bundle.
Subtitle and XML files themselves do not add rendered duration. Video or audio rendered in the browser and video rendered locally in ChatCut Desktop do not count, but a cloud-rendered job started from either surface can count.
This duration quota is separate from credits: export does not spend credits. Buying a one-time credit pack does not remove the Free web-export quota; an active paid plan does. Individual outputs can still require Pro—for example transparent ProRes 4444 motion graphics.
See Free and Pro, Desktop Local Export and 4K, and Export Queue, Downloads, and Retries.