When processing fails: what each message means and what to do

Updated October 26, 2026 · Peelframe

When something goes wrong, Peelframe tells you at which step it failed, what happened and what to do next. Here are the messages you are most likely to see, grouped by step, with their causes and fixes.

Loading the video

Commands for converting, downscaling and splitting are in supported formats and how to convert.

Preparing the AI models

• The AI model files could not be downloaded. — Check your internet connection. Work or school networks sometimes block large downloads; try another network.
• The downloaded AI model file is damaged. — Reload the page and try again.
• The AI engine could not start in this browser. — Use a recent desktop Chrome or Edge, and close other tabs.

GPU notices: processing continues

These are notices, not failures. Processing carries on, though it may take longer.

• GPU acceleration is not available on this device, so the CPU is used. / This GPU does not support part of the AI model, so processing moved to the CPU. / The GPU returned invalid results, so processing moved to the CPU. — Updating the graphics driver and browser may let the GPU be used next time.
• The GPU ran out of memory. — The work is automatically split into smaller pieces and retried. Closing other tabs and programs helps.
• The GPU connection was lost (driver restart or power saving). — It reconnects automatically or continues on the CPU. If it keeps happening, update the driver and turn off sleep or power saving while processing.

When processing stops

• The device ran out of memory. — Close other tabs and programs, or split the video into shorter parts. This happens most on phones, so a computer is recommended.
• The AI engine did not respond for a long time. / The video engine reported no progress for a long time. — Keep the tab in front, close other tabs and try again. Minimizing the window or switching tabs lets the browser slow the work down.
• The AI engine stopped unexpectedly. — Close other tabs and try again; if it repeats, restart the browser.
• Automatic recovery was tried several times, but processing could not continue on this device. — Restart the browser, or split the video into shorter parts.
• Reading the video frames stopped. — Try again with the tab in front; if it repeats, convert to MP4 (H.264).

Saving the result

• Saving the result video failed. — Try again; if it repeats, split the video into shorter parts.
• Merging picture and sound failed. — If it repeats, convert the original to MP4 (H.264 + AAC) and process it again.
• The result file failed its check, so it is not offered. — Peelframe checks the whole result file after processing and does not hand over a file with problems. Process it again.

Still stuck? Send the error log

After an error, the Save error log button saves a peelframe-error.json file. It holds the step that failed, the kind of error, browser and device details and the input format (extension, size, resolution, codecs); it does not contain the video, its file name or the subtitle text. Sending it to help@peelframe.com helps a great deal in finding the cause. See the contact page.