My render failed or is taking too long

Exporting a clip doesn't happen on the click: it joins a render queue and is processed on the server. Understanding that solves half the cases.

The states a render goes through

On the Renders page each item shows where it stands:

• Queued — waiting for a free worker.
• Processing — being rendered, with a progress percentage.
• Finished — file ready to download.
• Failed — it errored; you can try again.
• Expired — it did finish, but the file has already been removed by the download window.

It's slow. Is that normal?

The time depends on three things: the length of the clip, how many elements it has, and the size of the queue at that moment. A 4K clip takes far longer than Full HD — the difference is large, not subtle.

Two rules that help calibrate expectations:

• Higher plans get queue priority. At peak hours, someone on a bigger plan renders first.
• Batch exports are deprioritized on purpose. A big batch never holds up someone who exported a single clip — the batch moves, but behind.

You can close the page: the render continues on the server, and there's a notification when it's ready.

If a render sits in "Processing" for more than half an hour, it's shut down on its own and marked as failed — it doesn't hang forever.

It failed: what to do

First, the relief: re-rendering costs no credits. You pay at clipping; rendering and re-rendering are free. Retry as much as you like.

The Try again button is on the render's card, and you can select several failed ones and resubmit them all at once.

Before you repeat it a third time, it's worth checking the likely cause:

Symptom	Common cause	What to do
Fails right at the start, always on the same clip	The source video is gone or downloaded incomplete	Re-import the video or redo the clipping from the source
Fails on a clip from a live stream	The stream recording is incomplete	Wait for the stream to end before exporting that section
Fails on a long or heavy clip	The clip blew past the worker's memory	Export in Full HD instead of 4K, or shorten the clip
"Nothing to render"	The edit ended up with no visible content	Open the editor and check the clip's start, end and elements
Several clips failing at the same time	Momentary fleet capacity	Wait a few minutes and try again

Failures that fix themselves

Not every failure reaches you. Infrastructure interruptions are automatically requeued without ever becoming an error on your screen. And in automatic publishing, render failures considered temporary trigger a new render on their own.

Which means: if a render failed and you saw it, it has probably already been through earlier attempts — making the content a more likely cause than the infrastructure.

If the video came from WhatsApp

Video that has passed through a messaging app sometimes arrives with non-standard color metadata that breaks rendering. CutPro corrects that automatically on import — but if one specific file always fails and came in over WhatsApp, try getting the original video from the source instead of the forwarded copy.

The file disappeared before I downloaded it

That isn't a failure: it's the download window. The rendered file stays available for a period — which varies by plan — and is then removed to free up storage. The render starts showing as Expired.

The fix is to export again, which costs no credits. More detail in downloading your clips.

When to contact support

If the same clip has failed three times in a row, in Full HD, and the source video opens normally, then it's worth investigating. Send the clip's link and the rough time of the last attempt.