Panorama File-Naming Workflow
Create a reliable panorama file-naming workflow for projects, viewpoints, source sequences, edits, and exports.
Choose stable name fields
Use fields that will remain true after the project is delivered: project code, date, property or location code, viewpoint, sequence number, and processing stage. Keep names short enough to read in a file browser and avoid characters that behave differently across operating systems.
Write the convention down before the first capture. For example, a project code followed by location, viewpoint, sequence, and stage is easier to sort than a name based on who was standing nearby.
- Use a consistent date order such as year-month-day.
- Use leading zeroes for numbered viewpoints and sequences.
- Use plain letters, numbers, hyphens, or underscores.
Separate source, working, and delivery
Keep original camera files read-only or in a clearly marked source folder. Create working files for selections and stitched masters, then create delivery exports with an explicit output suffix and dimensions when useful.
Do not rename a source frame only because a processing application displays a friendlier label. Preserve the camera filename in metadata or a project note so a retouch, reshoot, or client question can be traced.
Handle versions and revisions
Use deliberate version numbers for meaningful changes, such as a corrected stitch or client revision. Avoid names like final, final2, or newest because they become ambiguous as soon as another export exists.
Record what changed when a version is created: control-point correction, color adjustment, privacy retouch, projection change, or output resize. Keep the approved delivery distinct from experimental renders.
- Use v001, v002, and similar ordered versions.
- Use a status such as review or approved only when it reflects a real decision.
- Never overwrite the approved master during experimentation.
Run the naming checklist
Before delivery, sort the folder by name and verify that related files group together and that no two viewpoints share an accidental name. Complete these actions: 1. Confirm project and location fields. 2. Check sequence and viewpoint numbers. 3. Replace ambiguous version labels. 4. Remove temporary exports. 5. Open a sample file and confirm its name matches its contents.
A consistent naming workflow reduces accidental uploads and makes a later re-export possible even when the original operator is unavailable.
- Names sort predictably
- Source files remain traceable
- Delivery versions are unambiguous