Window Peeper Video Not Working: 8 Fixes by Symptom

Nine out of ten "the window peeper AI is not working" messages we get are one of eight symptoms, and seven of the eight are fixed by a different photo rather than a different tool.

Find your symptom in the table, then read the section below it.

Symptom table

1. The face drifts

What you see: the window has a person in it, chewing, staring — but it is not quite you. The features are averaged.

Why: the model has to reconstruct a face from one angle, at a small size, from a distance. A head turned past about a quarter gives it too little information, and it fills the gap with an average face.

Fix: re-upload with both pupils visible and the nose pointing roughly at the lens. If you only have three-quarter photos, pick the one closest to straight-on.

2. It invented clothes

What you see: the face is right, the outfit is not — a generic shirt, a colour you have never worn.

Why: the outfit comes from the photo. A tight headshot contains no shirt, so the model supplies one.

Fix: use a photo framed from mid-chest up. If the joke depends on the outfit — a work tie, a football shirt, a dressing gown — the outfit has to be visible in the source.

3. Waxy skin, flat face

What you see: the render looks plastic. Detail is gone, the face reads like a mask.

Why: the source was dark, or lit from behind, and the model brightened it into something synthetic.

Fix: daylight, facing a window, no filter. If you must use a night photo, look for one where a screen or a lamp lit your face from the front.

4. A second person appears

What you see: someone else is in the room, blurred and uninvited.

Why: the reference contained two faces and the scene has one seat.

Fix: crop to one person before uploading. Crop tight enough to remove the other person's shoulder.

5. Everything is soft

What you see: the whole clip is slightly smeared, worst during the push-in.

Why: the source was a screenshot, a forwarded image, or a compressed copy. Generators upscale; they do not invent detail.

Fix: use the original file. Check the short edge is at least 1000 px. A 1200 px scan of an old print beats a 400 px WhatsApp forward every time.

6. Hands melt into the burger

What you see: fingers blur into the food, or the hand becomes a suggestion of a hand.

Why: this is the classic 480p failure. Small, fast, occluded detail is the first thing a low-resolution render loses.

Fix: two options. Spend a credit on 720p, or use a photo where the hands are out of frame so the scene can hide them behind the table.

7. The render failed

What you see: an error, or an email saying the job did not complete.

Why: usually the input — an unsupported format, a corrupt file, or an image the model could not detect a face in. Occasionally it is a transient job error.

Fix: re-upload as JPG or PNG. If it fails twice on the same photo, try a different photo before contacting support. Failed renders refund their credits automatically — you do not need to open a ticket.

8. No video in the library

What you see: the render "finished" but there is nothing to download.

Why: most often you are signed in on a different account than the one that started the render (email vs Google sign-in is the usual culprit). Less often, the job is still queued and the page was closed.

Fix: check the email address on the receipt, sign in with that method, then open the library. If the email says it is ready and the library is empty, contact support with the order ID.

When it is not your photo's fault

Four cases where changing the photo will not help:

• You want a different room or meal. The scene is fixed. That is a different product, not a bug.
• You want a specific real location. Generated scenes do not reproduce real buildings.
• You want the person to move like themselves. A still photo gives the model a face, not a performance.
• You want 1080p. Our ceiling is 720p.

If one of those is the blocker, a prompt-based tool is the right move — see window peeper prompt.

The five-minute retry protocol

Before you burn a second credit, do this:

1. Open the source photo at 100% zoom. If the face is soft at full size, it is soft in the render.
2. Check the eyes. Both visible? Any hair or glasses across them?
3. Check the crop. Is there a shirt in the frame?
4. Check the light. Is the face the brightest thing in the photo?
5. Only then re-upload. One well-chosen photo beats five hopeful retries.

If you have retried three times and the face still drifts, the photo is the problem — not the tool. Find a different photo.

What to send support

If you do contact us, include:

• The order ID from the receipt
• The email used at checkout
• Which symptom from the table above
• The source photo, if you are comfortable sharing it

That last one is optional, but it turns "it doesn't work" into a diagnosis in one reply instead of four.

Frequently asked questions

Do failed renders cost me credits? No. They return automatically.

Can I get a refund if the video completed but I do not like it? Unused credits are refundable within 14 days. A completed render is not refunded for taste.

Why did the first render look better than the second? Different photos, or a different model seed. The scene is fixed but the reconstruction is not deterministic.

Can I re-render from the same photo later? Only within seven days — source photos are deleted after that.

Is there a way to preview before spending a credit? No free render. The cheapest test is a 480p render on the single pack.

Does the tool work on Android? Yes, it runs in the browser on any modern phone.

---

If your symptom is not on the list, send us the order ID and we will look at the actual job. If you want to prevent the problem next time, the photo guide is the checklist that keeps retries at one.