# Export Queue, Downloads, and Retries

Source: [Export Queue, Downloads, and Retries](<https://pr-995-preview.chatcut.dev/docs/export-history>)

Documentation index: [llms.txt](<https://pr-995-preview.chatcut.dev/docs/llms.txt>)

Last updated: 2026-11-19

Starting a file export opens a queue under the header **Export** button. It shows the export jobs this editor session has started or observed.

## Why is the export queue icon missing?

On the web, the **Export queue** icon beside **Export** is visible only when the current browser tab has an export to show. Desktop’s queue also includes link imports and is called **Task queue** while a link import is present, including when there are no exports. The entry is hidden when that tab or window has no queue tasks to show; its absence alone does not mean an export has failed. Check the editor tab or window that started the task.

## Browser export queue limits

Each browser tab can have up to three browser exports running or waiting at once; start another after one finishes. The browser also keeps only the three most recent browser-rendered results on this device. Cloud renders use the server queue instead; see [Web vs Desktop Export](https://pr-995-preview.chatcut.dev/docs/web-export-limits) for the rendering differences and when cloud export may use credits.

## Read and manage an export job

-   A running row shows its type, name, status, and staged progress. Cloud progress remains below completion until the render actually finishes.
-   Hover a row and select X. On a running row this is **Cancel task**. On a finished row it is **Delete task**, which only removes the queue entry; it does not delete the saved file.
-   If the job fails, select **Retry**.
-   On the web, a completed cloud job downloads automatically once per browser. Use **Download again** or **View** afterward.
-   In ChatCut Desktop, a completed local render offers **Show in Finder** (**Find In Folder** on Windows) and **Open**.

In the web editor, a cloud export shows its estimated credits on the export button, and ChatCut asks you to confirm any charge before it starts. A cloud export that an agent submits starts without a separate confirmation; see [Web vs Desktop Export](https://pr-995-preview.chatcut.dev/docs/web-export-limits#credits-and-output-limits). When media is still uploading, a cloud export can remain at **Preparing media…** and begin automatically after uploads finish. A long render can change to **Taking longer than usual** without meaning it failed.

The queue is not a permanent account archive. Refreshing can remove session-only rows, and the web queue shows only the project’s render jobs from about the last 24 hours. Save delivered files in your own storage instead of relying on the queue as long-term history. The direct Jianying/CapCut handoff uses its own completion dialog.
