What you’ll take away
- Use a stable naming pattern with only useful fields.
- Do not invent names or take numbers that the source cannot establish.
- Treat disk renaming separately from project-bin organization.
Choose names that help the next lookup
A useful name gives the editor enough information to recognize the source without pretending to summarize everything. Project, subject, shot type, and a stable original identifier may be enough. Long strings of speculative tags become difficult to scan and unreliable to search.
In an illustrative product shoot, several files named by the camera show opening the package, a close view of a control, and a wide demonstration. Adding a concise action description makes the intake readable. Keep a distinguishing identifier so two similar takes do not collapse into the same name.
Decide where each field comes from
The scene or visible action may come from content analysis. A take number may come from a slate. A production date may need the shoot record rather than an assumed filesystem timestamp. Tell the assistant which sources are authoritative for the fields you care about.
Leave unknown values uncertain. A person visible in a clip should not acquire a real name merely because another recording used that name. Similarly, “take three” should not mean the third file encountered unless that is your explicit convention. Readable names are useful only when the information is dependable.
Use Wideframe’s naming recipe
The rename-clips workflow describes composing names from a confirmed pattern and keeping a before-and-after mapping. Its default copy-based approach is relevant for intake because it retains a clear relationship to the source files. Add and save the recipe using the page’s instructions.
Give the assistant the folder, field order, casing, and handling of missing information. Start with the naming decisions your team already understands. A new scheme that nobody else recognizes can create more translation work than the original camera names.
Do not confuse renaming with organizing a project
Renaming a disk file changes the source path that other work may refer to. Organizing Premiere bins changes how the project presents clips. They are related but separate tasks. If the footage already supports an active edit, choose the appropriate project organization work rather than casually altering its files.
Keep the naming map with the intake. It helps an editor reconcile production notes that still use the camera names and communicate with someone who has the originals. The map is not busywork; it is the connection between readable editorial names and the recording’s existing identity.
Reuse the convention across shoots
Once the pattern is useful, apply it consistently to later intakes with the new project values. Update the convention when the work changes, but avoid adding a field just because an assistant can describe it. The name should remain easy to recognize during an edit.
Read AI logging and labeling for the broader preparation process and Premiere assistant choices for product fit. Meaningful names are one practical way to make the next footage task easier.
Try this request with your own footage
Create a renamed copy of this new product-shoot intake using project, action, shot type, and original camera identifier. Keep unknown fields unfilled rather than guessing, and give me the original-to-new name mapping for the editor.
Sources
Published by Wideframe. Product details are based on the documentation below; examples are not customer results or benchmarks.
- Wideframe rename-clips workflow · consulted 2026-09-18
- Wideframe pricing and requirements · consulted 2026-09-18
Give the intake readable source names
Use a copied footage intake to build readable names that follow your team’s conventions.
Frequently asked questions
No. Disk filenames and project-bin organization are different operations with different effects on references.
Use confirmed production information for identity fields. A visible person is not enough to establish a name.
Intake is a natural point, before renamed files become established dependencies in an active edit.