Key Facts
- A playable export is useful but may be insufficient for correction.
- The archive needs a human-readable map.
- Keep accepted and superseded versions distinguishable.
- Test retrieval before the day you urgently need it.
What Future Change Are You Preparing For?
Start with likely corrections. Could a name be mispronounced, a caption need updating, an image licence require investigation or a scene need replacing? These tasks require different materials.
A flattened video may let you inspect the published result, but it may not let you cleanly change a sentence under music. An editable project without its media may open with missing assets. The archive should preserve the combination required by your workflow.
DreamWild's Terms advise keeping your own copies of important source materials and completed outputs and state that the service is not sold as a permanent archival or disaster-recovery service.
Source: DreamWild Terms. Accessed 2026-10-03. https://dreamwild.ai/terms
Treat the creative workspace as one storage location, not a permanent archive.
What Does A Restore-Ready Folder Look Like?
This author-created structure belongs to a fictional Short about arranging a small exhibition shelf. The project identifier is E042.
Scroll this table sideways to see every column.
| Folder Or File | Contents | Why Keep It? |
|---|---|---|
| E042_manifest.txt | Project summary, accepted version and restore notes | Gives a future editor a starting point |
| exports/ | Accepted vertical video and clearly marked earlier export | Shows what was actually delivered |
| edit/ | Editable project and any required project settings notes | Supports a targeted correction |
| media/ | Original images, audio and footage used by the project | Prevents missing-file surprises |
| text/ | Accepted script, captions and metadata | Makes wording changes traceable |
| evidence/ | Source references, permission records and attribution requirements | Preserves the basis for important decisions |
| release/ | Approval and destination identifier | Connects the local work to the uploaded item |
The names are suggestions. Adapt them to your tools, but keep the distinction between reusable source material, final delivery and evidence.
If your tool does not provide an exportable editable project, mark that part of the archive unavailable. Retain the separate components you can obtain and document which edits would require rebuilding the video. This folder plan does not promise that any service supplies a downloadable project file.
Identify revisions with a consistent naming convention: https://dreamwild.ai/guides/video-file-naming/
What Should The Manifest Say?
Write enough that someone can understand the project without asking its original editor:
“E042 demonstrates a shelf arrangement using our own miniature objects. Accepted export: v05. Editable project references files in media. Caption correction belongs to v05. Music permission is entry M12. Public release record identifies the destination video. To revise narration, use the separate voice file, then rebuild the mix.”
This fictional manifest focuses on the locations and dependencies a future editor might otherwise have to reconstruct.
Include any tool or format requirement that affects reopening, without storing account passwords or access secrets in the archive. If a source file is unavailable, say so now. “Original voice file missing” is more useful than discovering the gap during an urgent correction.
How Do You Test The Archive?
Choose a small restore exercise before removing anything from the working environment. Copy the archive to a separate working location, open the project and check whether the necessary assets resolve.
Test recovery with one representative edit, such as changing a caption and producing a short export. Compare it with the accepted reference and note any missing fonts, assets or instructions.
If you need an unavailable external asset to reopen the project, decide whether to store an authorised local copy, simplify the dependency or document the limit. A folder that merely contains filenames is not a successful restore.
How Much Should You Keep?
Retain what supports correction, rights verification and the published record. Temporary renders and abandoned variations may not all justify permanent storage, but deleting them should be a considered decision rather than an automatic cleanup habit.
Review sensitive material separately. Keep only what you need, restrict access appropriately and avoid duplicating personal information into every project folder.
For permissions that need a longer history: https://dreamwild.ai/guides/video-asset-licence-log/
When Should You Update The Archive?
Update it after an accepted correction or replacement upload. Preserve the earlier release relationship while making the current accepted version obvious.
Schedule a retrieval check when changing editing tools or storage locations. The test is simple: can you find the correct project, explain its dependencies and make the kind of correction you planned for? If not, fix the archive while the original working materials are still available.
Frequently Asked Questions
Is The Finished MP4 Enough?
It preserves the delivered result, but targeted corrections may require editable files, separate audio, captions and original media.
Do I Need To Keep Every Failed Variation?
Choose based on correction and evidence needs. Keep useful history without assuming all temporary output requires permanent retention.
What If A Required Source File Is Missing?
Mark the limitation explicitly and investigate while the project is still fresh. Do not label the archive restore-ready without testing.
Should I Put Passwords In The Manifest?
No. Describe required access without storing passwords or other secrets in the project archive.
Your next step
Put the idea to work.
Pair DreamWild's creative studio with your own tested archive for important projects
Explore the creative studio https://dreamwild.ai/creative-studio/