Key Facts

  • A filename identifies a file; it does not prove approval.
  • Use a new revision when the exported content changes.
  • Keep the published video identifier beside the local export record.
  • Avoid names whose meaning depends on remembering a conversation.

Start With A Name You Can Read At A Glance

P024_paper-lantern_v03_vertical.mp4

This sample convention uses a project identifier, short subject, revision and delivery shape. P024 finds the project, paper-lantern makes it recognisable, v03 identifies the export, and vertical separates it from other shapes if they exist.

Choose the fields your team needs and keep their order stable. A date may help, but it cannot distinguish three exports made on the same afternoon by itself.

Put revision reasons in a change note. “final_new_fixed_use_this_really_final” records uncertainty rather than telling an unfamiliar uploader which version is current.

Give A Changed Export A Changed Revision

This fictional lantern project shows the sequence of events. The repeated v02 row records its later status change; it is not a second export with the same name.

File Change Review State Next Action
P024_paper-lantern_v01_vertical.mp4 First complete export Review requested Check folded seam
P024_paper-lantern_v02_vertical.mp4 Replaced unclear close-up Approved on review Ready for the agreed upload route
P024_paper-lantern_v03_vertical.mp4 Caption wording changed after approval Approval reopened Review captions and full export
P024_paper-lantern_v02_vertical.mp4 No change to this older file Superseded by project decision Keep outside the active upload folder

Version three contains different captions and needs a new approval decision. Acceptance of version two cannot transfer simply because the newer file looks nearly identical.

Bind the decision to the actual export: https://dreamwild.ai/guides/final-video-approval/

Keep Approval Beside The File

Use a short release record with the exact filename and extension, reviewer, review time, metadata version and any conditions. That record should identify what was accepted without relying on a remembered conversation.

If the file moves, update its location. If its contents change, create a new revision. Overwriting an approved filename makes the old decision ambiguous because two different videos have now carried the same label.

A small team can use one clearly marked delivery folder containing only the accepted export and release record. Keep source material and rejected variations elsewhere so the uploader is given a decision already made, rather than another set of files to choose between.

Keep Captions And Alternate Deliverables Matched

Use the same project and revision identifiers for files that belong together. A v03 caption track should not sit beside a v02 export as if they were an approved pair.

When captions change independently, state which video they accompany and check the combined result. Matching numbers do not prove timing still matches the audio.

Add a clear field for language or aspect ratio when needed. Each delivery should reveal its intended use without requiring the uploader to guess from a thumbnail.

Keep The Archive Useful For Recovery

Save the accepted export, release record, relevant source assets and enough project information to reproduce the work. Retain superseded files where they explain a correction, with their status clearly marked.

DreamWild's Terms tell users to keep their important source materials and outputs. The service is not sold as permanent archival or disaster recovery, so the naming and backup system should not depend on a workspace staying available indefinitely.

Source: DreamWild Terms. Accessed 2026-10-03. https://dreamwild.ai/terms

Plan the archive around what you would need to recover: https://dreamwild.ai/guides/archive-video-projects/

After publication, keep the destination video identifier beside the local export record. The file and its published result can then be traced together.

Test The Folder Without Explaining It

Ask someone unfamiliar with the project to find the approved export using only the folder and release record. If they choose incorrectly, simplify the delivery location or clarify the record.

Repeat after a correction, when two versions look plausible. The system is useful when the next person can still choose the right file without asking what “final” meant last week.

Frequently Asked Questions

Can I Put Approved In The Filename?

You can, but keep the separate record tied to the exact file. A name alone cannot show who checked which content.

Does A Tiny Caption Change Need A New Revision?

Yes, when the delivered file changes. Recheck the affected caption and complete export before accepting the new version.

Can I Overwrite An Older Export?

Avoid overwriting a file referenced by approval. A new revision keeps the earlier decision understandable.

Is This Useful When I Work Alone?

Your future self still needs to distinguish draft, accepted and superseded work. Use the same clear separation without unnecessary administration.

Put the idea to work.

Use this convention for the assets and exports you prepare in DreamWild, so the next upload starts with the right file.

Explore the creative studio https://dreamwild.ai/creative-studio/
← Explore more DreamWild guides