Skip to content

Same link, new version

Upload a fresh cut without sending a new link. The recipient always gets the current version, and you keep a history of what came before.

Start a Transfer

One link, many versions

Replace the files behind a transfer and the link stays the same. No more 'final_v3_REALLY_final' chains in your client's inbox.

Version history

Every version is kept as its own entry, up to ten per transfer. Activate any one to make it the live version recipients see.

Extend the expiry

Uploading a new version is the moment to push the expiry out, so a review round that runs long doesn't kill the link.

How it works

1

Send the first version

Share a transfer as normal. That becomes version one automatically.

2

Make your changes

Re-export, fix the notes, do another pass. Whatever the next cut needs.

3

Upload a new version

Add it to the same transfer through the version manager, and optionally extend the expiry.

4

Activate it

The new version goes live on the same link. The recipient always sees the current one.

Review rounds

Send v2 and v3 of an edit on the same link, so the client never has to dig out a new URL each time.

Fixing a mistake

Caught a typo after sending? Upload a corrected version and the old one quietly steps aside.

Iterating with a team

Keep one canonical link for a deliverable while the actual files behind it evolve.

Common questions

Uploading new versions is a Pro and Squad feature. Pro keeps links live up to 30 days and Squad up to 60, and you can extend the expiry when you add a version.

See plans

Explore more

One link that keeps up

Send the next cut on the same link and skip the 'final final' email chain.

Start a Transfer
Beta