Manage multiple revisions of the same project
How to organize and track different versions with FileVert Collab: history, comparisons, file replacement and step-by-step validation.
� The challenge of multiple revisions
A creative project often goes through several iterations: revision 1, revision 2, final version... How to keep track without losing the history of previous comments and validations?
FileVert Collab offers an intelligent versioning system that allows file replacement while preserving the complete history of exchanges and comments.
� The FileVert Collab versioning system
Force Update
The system uses force_update: true to replace an existing file without creating a new project.
URL Versioning
Each replacement automatically increments a ?updated=X parameter in the URL.
� File replacement process
Click on "Replace"
In the FileVert Collab interface, a "Replace" button allows you to upload a new version of the file. This action triggers the ReUpload component.
Interface intuitive : Intuitive interface: The replacement button only appears for project creators, preserving control.
Select the new file
The uploader respects the same constraints as the initial upload: accepted file types, maximum size, and format validation.
video/*, image/*, audio/* or project-specific restrictions.
Name, size, MIME type automatically extracted from the new file.
Processing and upload
The system performs a patchTransfer with force_update: true, then uploads the file via S3 with a progress bar.
Technical process:
patchTransfer() - Metadata updategetPresignedPostData() - S3 credentials generationuploadFileToS3() - Upload with progressfinalizeTransfer() - Finalization and versioning
Automatic refresh
The URL is updated with the new version, then the page automatically reloads to display the new file with preserved history.
Perfect continuity: Clients immediately see the new version with all their previous comments.
� Smart history management
Comments preserved
All previous comments remain attached to the project, even after file replacement.
URL Versioning
The ?updated=X parameter allows easy tracking of successive versions.
Validations maintained
Previous validations are preserved, allowing complete approval tracking.
� Best practices for multiple revisions
1Communicate major changes
Before replacing a file, inform your clients about the modifications made through a general comment explaining the changes.
Example: "Version 2 uploaded: logo correction + color adjustment according to your feedback"
2Use consistent naming
Name your files systematically to facilitate tracking: ProjectX_V2.mp4, Client_Logo_Final.png
3Limit the number of revisions
Contractually define a maximum number of revisions (e.g., 3) to avoid infinite revision cycles.
Tip: The ?updated=X parameter helps you automatically track the number of revisions made.
� Typical use cases
🎬Video production
V1: First version of the edit
V2: Timing corrections + transitions
V3: Color + audio adjustments
Final: Client-approved version
Advantage: The client sees the evolution without losing their previous temporal comments.
🎨Graphic design
V1: Initial design concept
V2: Color + typography modifications
V3: Spacing + logo adjustments
Final: Production-approved version
Advantage: Visual annotations remain visible and contextualized at each version.
Master your multiple revisions
Use the FileVert Collab versioning system to efficiently manage the evolution of your creative projects.
Frequently asked questions
Answers to common questions about managing multiple revisions