Know which revision the feedback belongs to

New version. Clear context.

Keep successive uploads under the same file without pretending yesterday’s feedback was made on today’s work.

Start with a Free workspace · see pricing for limits

Illustrative product example · fictional files and names

The history stays attached to the right version.

An uploaded version is immutable. When the work changes, add a new version and keep earlier annotations with their source. A version picker lets you return to the review you need.

Preserved source files

New uploads create new versions rather than rewriting the bytes of an existing version.

Version-specific conversations

Annotations and threads reference the exact version reviewed, including its document page.

Office originals and renders

Each converted Office version has its own separate PDF artifact. Reopening that version uses its existing render.

The workflow

How file versions works.

1
Review the first upload
Leave feedback against a specific version of the file.
2
Add the revision
Upload the changed work as a new version, subject to file permissions and storage capacity.
3
Return to earlier context
Select an earlier version to inspect its original file and saved feedback.

Before you start

Annotations do not automatically move onto a new version. Automatic change detection and annotation transfer are not provided.
Original uploads and retained file versions count toward workspace storage. Rendered PDFs are tracked separately and excluded from customer storage usage.

Plans and limits File access and privacy