Export and Delivery

Web vs Desktop Export

View as Markdown

For manual video and audio exports from the Web editor, ChatCut automatically selects browser or cloud rendering. Agent Plugin video and audio exports use browser rendering by default; cloud video or audio requires your explicit request or agreement. ChatCut Desktop renders locally when the project and required media are available on your computer. Rendering on your own device is free; cloud export may use credits after a free allowance (see Credits and output limits).

Where you workWhere rendering runsHow the file arrivesKeep available
Manual Web video/audio, browser rendering selectedIn the open browserDownloaded or saved by that browserOpen project tab and required media
Manual Web video/audio, cloud rendering selectedIn the cloudDownloaded through the browserRequired media uploaded and accessible to the render
Agent Plugin, default browser video/audio exportIn the selected signed-in browserDownloaded by that browserSupported browser kept open; explicit project/Timeline target
Agent Plugin, explicitly requested cloud video/audioIn the cloudRetrieved from the completed jobAuthorized saved Timeline and remotely readable media
ChatCut Desktop local video exportOn your computerSaved directly to the selected folderProject and required media available on that computer

Export manually from the web app

  1. Select Export in the editor header, then choose the output type and settings.
  2. ChatCut checks the browser, output settings, Timeline media, motion graphics and audio requirements. It selects browser rendering when supported, or cloud rendering when the compatibility checks or current service settings require it. There is no manual renderer switch. When cloud rendering is selected, the button reads Cloud export and Why cloud export? explains the reason.
  3. When the export runs in the cloud, the button shows the estimated credits (for example, Cloud export · N credits). If the export needs credits, ChatCut asks you to confirm that charge with the export button before it starts.
  4. After starting the job, follow progress under the header Export button. Keep the tab open while a browser export is running.
  5. Use Download again or View afterward when that action appears.

Browser rendering uses browser storage or asks where to save a large output, depending on projected size and browser support. A compatible device can also offer 4K browser video export; depending on the project owner’s plan, 4K export may require an upgrade, and ChatCut shows an upgrade prompt if it does.

Cloud rendering needs access to the required media. A job can wait at Preparing media… while uploads finish. Follow that same job in the export queue. Renderer selection happens before rendering starts; if a started job fails, inspect its message before retrying.

Export with the Agent Plugin

For video or audio, ask the agent to export the intended project and Timeline. The export call must name the full timelineId; external Agent Plugin callers must also supply the full projectId. Browser rendering is the default. A signed-in supported browser can render that target while Home or another page is visible. Keep the selected browser open until delivery; navigating does not change the export’s target.

If browser rendering is blocked, have the agent explain the specific blocker. Cloud video or audio is available only when you explicitly request it or agree to it after that explanation. Agent exports do not automatically fall back to cloud after a local failure. See Agent Plugin Setup and Missing Tools if the required tools are unavailable.

Request cloud video or audio explicitly

Through the hosted connection, you can explicitly request cloud video or audio with renderMode="cloud". This differs from manual Web export’s automatic renderer selection. The agent must not switch a failed browser export to cloud without your request or agreement.

  1. Identify the intended project and Timeline using their full IDs. Confirm that the saved Timeline is available to your authorized ChatCut account.
  2. Check that every referenced media asset is readable by the cloud render. A file available only on your computer is not ready for cloud export. Google Drive or Dropbox connection media is not automatically cloud-renderable; follow any requirement to use browser export or upload the required media through the connected browser.
  3. Request cloud video at 1080p or lower, or request cloud audio. Cloud video does not offer 4K; 4K requires compatible browser rendering or Desktop local video export.
  4. Decide on credits before you ask. A cloud export that the agent submits starts right away, without a separate price confirmation. Any duration beyond the project owner’s free allowance is charged to the project owner’s credits. If you don’t want to spend credits, ask the agent to use browser export instead, or export locally in ChatCut Desktop.
  5. Resolve any media, permission, font or quota message. If fonts are unavailable in the cloud renderer, accept a proposed substitution only if it suits the result, or change the fonts before retrying. Cloud selection does not bypass these requirements.
  6. Keep the returned renderId. When checking progress, use track_export for that same job and follow its returned polling interval. Do not submit another export merely to check progress.
  7. Retrieve the completed file and open it to check picture and sound. Keep your own copy of the delivered output.

For example, replace both bracketed values with the actual full IDs before sending:

Prompt

Use my authorized ChatCut project [full project ID] and its saved timeline [full timeline ID]. Export that timeline as 1080p H.264 video using cloud rendering; I am explicitly requesting cloud. Check that all referenced media is remotely readable and report any blocker. Do not substitute unavailable fonts without my agreement. Before submitting, remind me that cloud export may use credits after the free allowance and wait for my go-ahead. Return the export ID and use that same job for progress checks.

When the authorized saved Timeline and all required media are already remotely readable, this cloud route does not require a browser to execute the render or an inbound callback to your computer. A browser can still be required to upload missing media. If the route reports a blocker, keep the project and existing job information and resolve that blocker rather than assuming cloud export will succeed.

If local export is unavailable

Keep the project and original media, then inspect the same job’s message. For a manual Web export routed to cloud, let required uploads finish and resolve any media-access or quota message. For a browser compatibility issue, try the suggested browser, codec or resolution. Resolve a reported Timeline graphic or audio issue before retrying. For Agent exports, follow the explicit cloud-request rule above rather than assuming a failed local job will move to cloud.

Before trying Desktop local video export, confirm that the project and required media are available there. See Export Queue, Downloads, and Retries for progress and retry actions.

Export video locally in ChatCut Desktop

ChatCut Desktop renders video on your computer and saves it directly to the folder you choose, with presets up to 4K, HDR on macOS, and adjustable bitrate. It does not use the cloud export allowance. Before switching to Desktop, confirm that the project and original media you need are available there. For the steps, see Desktop Local Export and 4K.

Credits and output limits

Exports rendered on your own device—in ChatCut Desktop or in your browser—are free. Cloud export may use credits after a free allowance. This applies to cloud video and audio and to motion graphics rendered in the cloud for Graphics or XML exports on the web. In the web editor, the export button shows the estimated credits, and ChatCut asks you to confirm any charge before the export starts. A cloud video or audio export that an agent submits starts without a separate confirmation, so decide on credits before you ask (see Request cloud video or audio explicitly). If the account does not have enough credits, the export does not start and ChatCut tells you why.

The free allowance and any credits come from the project owner’s account. Successfully completed render duration and the duration reserved by active jobs count toward the allowance, and a failed job releases what it reserved. A collaborator’s plan or credits do not replace the project owner’s allowance.

Browser and device compatibility, supported formats, and plan permissions still apply. Individual outputs can still require a paid plan—for example transparent ProRes 4444 motion graphics. Depending on your plan, 4K export may require an upgrade; ChatCut shows an upgrade prompt if it does. See Free and Paid Plans for plan guidance.

See Free and Paid Plans, Desktop Local Export and 4K, and Export Queue, Downloads, and Retries.