You change a motion word, try another prompt and save a preview. Later, you cannot remember whether the second file used the revised prompt or the earlier one. The useful observation—what you actually wanted to change—gets lost among filenames.
When using a free AI video generator with no signup required, keep a small note outside the generation page. It should connect an input version to an observed preview and one next decision. It does not need to become a production database.
This guide develops a fictional brass-key shot. All prompts and diagrams are planning materials. The sample note begins before generation; any later observations described below are hypothetical, not results from an AI VideoWeb test.
Write the specific input note before trying it. The preview and observation remain empty because this example has not been generated.
## Give the shot a stable name
Start with a name that will still make sense after the first revision: `key-turn`. Then write the goal in ordinary language:
> A hanging brass key makes a gentle half-turn while staying inside a fixed close view. The viewer should recognize the same key throughout.
The goal is not the same thing as the prompt. It is the reason you will accept or reject a preview. You can rewrite a prompt while keeping this question unchanged.
Use a note with these fields:
| Field | What belongs there |
| --- | --- |
| Goal | The visible question the shot should answer. |
| Input ID | A short label for the exact prompt and any image pair. |
| Settings | The frame shape and other settings you actually selected. |
| Preview file | The file you saved, once one exists. |
| Observation | What you can point to in that particular preview. |
| Next decision | What to keep, change or check next. |
An input ID can be as simple as `key-turn-v01`. If you use image inputs, keep their filenames in the same row in start-then-end order. A label such as “new images” will stop being useful as soon as you make another pair.
## Write the first note before the first attempt
Here is a planning entry, with unfinished fields left unfinished:
```text
Shot: key-turn
Input: key-turn-v01
Goal: recognizable key; gentle half-turn; fixed close view
Prompt: One brass key hangs from a plain cord above a dark felt pad.
The key turns gently through about half a turn.
Keep the cord attachment and background in place.
One continuous shot with a fixed camera.
Frame shape: 16:9 planned
Preview file: none — not generated
Observation: none — not generated
Next decision: inspect motion and key identity in the first preview
```
Do not fill an observation field with the intended result. “Key turns gently” is the request. It becomes an observation only if a particular preview actually shows it.
This distinction matters even when the first result looks promising. A request, an expectation and an observation can all use similar words while describing different things.
A hypothetical framing problem motivates one changed sentence. Neither sketch is an observed output or a tested fix.
## Describe the preview without diagnosing the model
After obtaining a preview, use visible statements. A useful hypothetical observation would be: “The key leaves the right edge before the end.” It identifies something another person could check in the saved file.
A weaker note would be: “The model cannot do rotation.” One preview would not establish that. The problem might concern the framing, the requested motion, the inputs or something you have not isolated. Keep the note at the level of the evidence you possess.
Here is how the same hypothetical issue could lead to a manageable revision:
```text
Observation, if seen: the key moves beyond the right edge.
Keep: one key, cord, felt pad and fixed view.
Change for v02: request a wider view with space around the key.
Next question: does the whole key remain visible?
```
This is a revision plan, not a claim that widening a prompt will fix every clip. Its advantage is traceability: you will know what you changed and why you changed it.
If you alter the motion, the framing and both endpoint images together, record all three changes. That can be a reasonable creative choice, but it is a new candidate rather than a clean comparison of one instruction.
## Keep input versions even when you reject a preview
Do not overwrite `v01` with the revised text and then attach the old result to it. Save `v02` as a new entry. Mark an unwanted clip “rejected for framing” or another concrete reason, and keep whatever material is still needed to understand the decision.
You can keep the note in a plain text file, a document or a page you update over time. The important connection is between the exact input and its result. The method does not depend on WeWrite or AI VideoWeb automatically saving a generation history for you.
If you later change from text to paired images, note that as a change of input route. On the current free form, the image route needs both a start image and an end image. Keep their order explicit; reversing them changes the intended direction of the shot.
Keep the versions and their actual future preview filenames connected. Only the camera-framing sentence changes; the next question is whether the whole key stays visible.
## End each entry with a decision, not an empty “try again”
A useful entry ends in one of three ways:
- **Keep this candidate:** it answers the stated question; list any work still needed for its intended use.
- **Revise this input:** name the visible issue and the next change you plan to make.
- **Change the goal:** the shot is trying to communicate something better handled by a different view, a still image or a separate editing step.
The [AI VideoWeb free AI video generator](https://aivideoweb.com/free-ai-video-generator/) can supply the short trial that you attach to this note. Its current free form is a five-second, 480p route with no signup and unlimited total attempts, as documented on 22 October 2026. Verification and queue waits can still be part of an attempt.
Unlimited attempts do not remove the need to keep the versions straight. Before leaving the page, follow its preview and download controls, confirm what you saved and add the actual filename to your note. This article does not establish automatic recovery of an unsaved result.
For the key shot, the next entry should tell you something specific about recognizability, framing or movement. Once the chosen preview answers the question, stop rewriting that question into another prompt. Carry the selected clip and its note into the next stage of your project.
Disclosure: This article is provided by the AI VideoWeb team at FLAQ TECH PTE. LTD.