Rendering failed: every message and what to do

Where the message appears

A failed render shows up in three places, always in plain words and never as a raw error code:

• On the Videos page, the card gets a Failed badge and its meta line shows the first sentence of the message.
• In the in-app notifications panel, the full message.
• On the oven screen, if you were still watching: “Render failed.” followed by the reason.

The video page itself shows the Failed badge and the Resume & Re-render → button. Every message below names its fix. Apply it, then resume the video.

Rendering failed. Try again, and contact support if it keeps happening.

The general message. Something stopped mid-render and there is no specific cause you can act on.

1. Open the video and click Resume & Re-render →.
2. On the Shots step, click Generate · N cr again.
3. If it fails a second time, write to Support@AvatarFactory.IO with the video ID (it is in the page address, after /videos/) and the time you started the render. We check the job on our side and reply within one business day.

Rendering stopped: you ran out of credits. Top up, then run it again.

The render needed more credits than your balance held. Your credits are the monthly allotment of your plan; they refresh every billing period.

1. Open your account menu at the top of the app, click Billing, and check your balance and your renewal date.
2. To render now, upgrade to the next plan tier, which adds credits right away. Otherwise wait for the refresh.
3. Shorten the cut if you want it to fit the credits you have: on the Shots step, cinematic shots cost 2 credits per second and talking-head shots 1 credit per second.
4. Click Resume & Re-render → and generate again.

Rendering failed: this avatar has no voice yet. Add a voice, then try again.

The avatar on this video has no voice, so there is nothing to speak the script.

1. Open Avatars, open the avatar, and add or design a voice. Voices walks through it.
2. Return to the video and click Resume & Re-render →.

Rendering failed: one of the images was rejected. Swap it out, then try again.

A scene image or a reference image was refused by the video service.

1. Click Resume & Re-render →.
2. On the shot that uses the rejected image, pick a different saved scene or generate a new one from the scene drawer.
3. Generate again. If you cannot tell which image it was, swap the scene on the first cinematic shot first; those are the shots that start from an image.

Rendering stopped: the script or a shot tripped the content filter. Edit it, then try again.

The words or the direction of a shot hit the service’s content filter.

1. Click Resume & Re-render →, then go back to the Script step.
2. Rewrite the passage that could read as violent, sexual, hateful, or as a real person’s likeness. Direction text on the shot cards counts too.
3. Return to Shots and generate again.

Content rules, likeness and copyright lists the rules that apply to every video.

Rendering failed: the video service did not respond. Try again in a minute.

A temporary outage or timeout on the rendering side. Nothing is wrong with your draft.

1. Wait a few minutes.
2. Click Resume & Re-render → and generate again.
3. If it happens three times in a row, write to us with the video ID; we watch for service problems and can tell you when they clear.

HeyGen did not finish this shot within 15 minutes; credits returned, please render again.

The talking-head service accepted the shot and had not finished it inside the window we wait. The same message appears with Kling or TopView in place of HeyGen when one of those rendered the shot. Nothing is wrong with your draft, and the credits are already back in your balance.

1. Click Resume & Re-render → and generate again. A second run usually clears it.
2. If it happens twice on the same video, try the shot on a different model on the Shots step, then render again.
3. Three times in a row means a service problem on our side: write to us with the video ID and we will tell you when it clears.

Sarah’s voice is no longer available. Open the avatar and pick or regenerate its voice, then render again.

Shown on Render before anything is charged, when the avatar’s voice is no longer in the voice library. It happens after a voice is replaced or removed. No credits were taken: the render never started, so there is nothing to come back.

1. Open that avatar and go to its Voice tab.
2. Pick a voice or generate a new one, and save.
3. Return to the video and render again.

This reel was copied before we measured its word timings, so an edited script cannot be placed on it.

Shown on a Copy a reel render, before anything is charged, when you edited the script and the copy was made before we started measuring where each word is spoken. An edited script is placed on the reel’s own words, so without those measurements the timing would drift. No credits were taken. Two ways on:

• Copy the reel again. The new copy measures the timings and the edited script works.
• Render the original script. The unedited script does not need the measurements.

Render failed. (on the oven screen)

The oven screen adds the reason after “Render failed.” When it reads “Render failed for an unknown reason” or “Failed to start render”, the render did not get far enough to store a cause. Treat it as the general message above: resume, retry once, then write to us.

The render did not start. Try again.

Shown on the Studio step (podcast) and the talking-window step (split-window) when the render request itself was refused. If the line starts with “Fix before rendering:”, the template found script rules that block the render. Click Edit the script → or use the co-writer’s fix option, then click Animate → again.

This take didn’t render. The credits were returned, fix and try again anytime.

This is a single shot, not the whole video. The rest of the video is intact.

1. On the video page, find the shot card with the warning.
2. Click ↻ Try Again on that card, or Fix This Shot to change the transcript, the direction or the scene first.
3. When the new take is ready, click Review Takes, keep the one you want, then click Rebuild Final Video in the bar at the bottom.

The copy stopped while preparing the avatar’s reference pack

Shown on a Copy a reel video. A copy draws each person from their avatar’s Reference Pack, so when a cast avatar has no pack yet, the copy generates one first and waits for it (the card reads “Preparing the Avatar’s Reference Pack”). The copy stops only when the pack cannot be made:

• ”…‘s reference pack could not be generated.” Open that avatar, go to its Reference Pack tab and generate the pack there, then start the copy again.
• ”…‘s reference pack was not ready after 20 minutes.” The pack took too long. Open the avatar’s Reference Pack tab: when the pack shows as ready, start the copy again.
• “You’re out of credits. Upgrade your plan to get more.” The pack costs the same credits as the one made when an avatar is saved, and there were not enough for it. Nothing was spent on the video. Top up or upgrade, then start the copy again.

Resume a failed video

Every failed video keeps its draft. Resume & Re-render → on the video page reopens the wizard with the same avatar, script, shots, scene picks and caption settings, and lands on the last build step. Fix what failed, then generate again. Nothing is redone from scratch.

If the button is missing, the video was created outside the wizard or the draft was deleted; use Generate Similar in the ⋯ More menu instead, which rebuilds the shot list from the video.

What happens to your credits

Every render that fails returns its credits, automatically, in full, without you asking. It happens the moment the render is marked failed, whatever failed it: a service that ran long, a voice that went missing mid-render, a configuration problem on our side, or an error nobody has seen before. A shot that fails on its own says “The credits were returned” on its card.

Some problems are caught before the render starts, so nothing is charged in the first place: a voice that is gone, or an edited script on a reel with no word timings. Those messages appear on the Render button itself and say what to change.

The confirmation before every render shows what the render costs and what stays in your balance, so you can compare before and after. Credits and failed renders covers the details.

When to write to us

Write to Support@AvatarFactory.IO when the same message comes back after one retry, when the credits did not come back within a few minutes, or when a render sits on a stage far past the 10 to 20 minute range. Include the video ID, the time you started, and a screenshot of the card. We reply within one business day.