# Export Queue, Downloads, and Retries

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

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

Last updated: 2026-10-11

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 local exports running or waiting at once. Start another after one finishes. Cloud renders use the server queue instead; see [Web vs Desktop Export](https://pr-500-preview.chatcut.dev/docs/web-export-limits) for the rendering and quota differences.

## 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 running row and select X to cancel. On a completed row, X only dismisses the queue entry; it does not delete the saved file.
-   If the job fails, select **Retry**.
-   A completed cloud job downloads automatically once per browser. Use **Download again** or **View** afterward.
-   A completed Desktop local render offers **Show in Finder** and **Open**.

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 dialog exposes only the project’s most recent render jobs. 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.