Predictable names make derivatives auditable and prevent the familiar final-final-v2 problem. Answering this privacy & workflows question well means looking at evidence from the source file, the properties covered below, and what the final destination actually requires.
A safe workflow considers who may process the file, what hidden data it contains, how long copies persist, and who can retrieve the result. Before anything else in “How to name and organize converted files,” weigh this observation: Keep the source identifier and add purpose, dimensions, or format.
Three findings that guide this choice
The core distinction
Keep the source identifier and add purpose, dimensions, or format.
The practical trade-off
Use ISO dates where chronology matters.
The verification test
Record the transformation when reproducibility matters more than a short filename.
A practical decision for this workflow
Adopt a pattern such as project_asset_purpose_width.format and document it beside the archive.
Use record the transformation when reproducibility matters more than a short filename. as the acceptance test on a representative source before committing an entire archive, publication, or delivery batch.
The privacy & workflows mistake to avoid here
Using ambiguous suffixes like new, latest, final2, and fixed without retaining provenance.
That failure conflicts directly with the recommendation for “How to name and organize converted files”: Adopt a pattern such as project_asset_purpose_width.format and document it beside the archive.
Review checklist before delivery
- ✓The file is approved for the selected processing environment.
- ✓Personal, location, revision, and author metadata were reviewed.
- ✓Temporary and saved-copy retention is understood.
- ✓The result is shared only through an authorized destination.
Judge “How to name and organize converted files” by whether the result passes these specific checks, not by whether a new file merely opens.