You manage a link by asking your agent. There is no list of your links on the website, so keep each link, and the conversation that made it, for later updates and deletes. Your agent must be connected first.
Share
Ask your agent to share a file or a folder. On Free, don’t mention an expiry. Free links expire on their own after seven days. For a built site:
On Paid, a new link needs an explicit expiry, so name one:
Expect a justshare.sh link in the reply. Open it to check the result before you send it on. Just Share creates the link only when every file is stored. If a file is missing, incomplete or expired, no link is created, and nobody sees a half-sent share. See What you can share for how to prepare a folder, and Agents for how an agent sends large files.
A Free request that sets an expiry or turns on version history is refused. On Paid, version history is off for a new link unless you ask for it. This prompt sets a 30-day expiry and turns it on:
You can ask for any expiry from one hour to 365 days, such as “expire in 24 hours”, or for a link that never expires.
On Free, each file can be up to 50 MB and everything you share up to 500 MB. On Paid, the limits are 100 MB and 20 GB. These are decimal units: 1 MB is 1,000,000 bytes. Every plan also has technical limits: 256 files, 8 MiB for files sent inside the call, and a total size for each share. See Limits.
People opening a link can skip ahead in a video or resume a large download, because Just Share serves byte ranges. That stops when the link expires or is deleted.
Update
To change what a link shows, ask your agent to update that link, and name the link or its conversation:
The address stays the same, so you don’t send it again. An update replaces the whole bundle: the agent sends every file the link should keep, and any file it leaves out is gone from the new version. People see the earlier version until the new one is ready. When it is, the link opens the new version.
If the update fails, the current publication stays up unchanged, and your agent should tell you the update didn’t happen. If the link changed since your agent last read it, for example through another agent, the update is refused so it can’t overwrite that change. Ask your agent to read the link’s current version, then try the update again.
| Free | Paid | |
|---|---|---|
| Link after an update | Shows the latest update only | Shows the latest update, plus earlier versions while version history is on |
| Expiry after an update | Restarts at 7 days from the update | Stays as it was, unless you give a new expiry |
Version history
Version history is a Paid choice for each link, and it starts off. Ask your agent to turn it on when it shares or updates the link, or later:
While it is on, each update keeps the version before it for up to 90 days. Saved versions count toward your storage. The person viewing the link can switch between saved versions from the bar at the top of the page, and go back to the latest one. Saved versions are not private backups. They open for anyone who has the link, and they stop opening when the link expires or is deleted, even if their 90 days aren’t up.
Turning history off permanently deletes the link’s saved earlier versions. Turning it on again doesn’t bring them back.
Link to an exact version
The usual /s/SHARE_ID link opens the latest version. A link with
?revision=REVISION_ID selects a saved version, but if that version is gone,
it opens the latest one with a notice.
To prevent that substitution, add pin=strict to the recipient link:
/s/11111111-1111-4111-8111-111111111111?revision=aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa&pin=strictUse the share’s ID and the selected version’s revision ID returned by the API.
Only the literal pin=strict opts in. Both IDs must be UUIDs; letter case is
ignored. In strict mode, a missing or malformed revision ID shows the existing
unavailable page. If the API rejects the revision as unavailable, the page
doesn’t try the latest version. A service failure still shows the existing
temporary failure result.
A strict link selects an exact version; it doesn’t keep that version forever. Anyone with the link can open it while it is available. Deletion, expiry, history being turned off, the 90-day retention limit and losing Paid access still apply. Strict links don’t restore removed versions or add private access.
Delete
Ask your agent to delete a link:
It stops opening right away, and so do all its saved versions. Deleting stops the link from opening. It doesn’t promise when stored copies of the files are erased, and it can’t recall copies someone already downloaded.
Expiry
A link stops opening when it expires.
Free. Each link expires 7 days after its latest successful publication or update. You can’t set a different expiry. A failed update doesn’t restart the 7 days.
Paid. Every new link needs an expiry from one hour to 365 days, or never. An update that doesn’t mention expiry keeps the link’s current one. To change the expiry without sending new files, ask your agent:
A new expiry counts from the moment it is set.
When you reach a limit
A share or update that goes over your plan’s file size, your storage or a technical limit is refused, and your agent tells you why. Nothing is shared, and an existing link keeps showing its current version.
Your agent can send you to the Plan and billing page, where you choose Paid and pay on the account site. See Account. You can also ask your agent to delete links you no longer need. Deleted links stop counting toward your storage.
When Paid ends
If your account goes from Paid back to Free:
- Saved earlier versions stop opening right away. They stay private for 30 days, so they can come back if you choose Paid again in that time.
- A new share or update is refused if it would take your account’s stored files above 500 MB.
- Links that are already up keep working for at most 7 days after Paid ended.
Troubleshooting
413, too large. A file is over your plan’s file size, the share is over your account’s storage, or it is over a technical limit. Share smaller files, delete links you don’t need, or see Limits.
409, the link changed. Another change got there first. Ask your agent to read the link’s current version, then repeat the update.
Upload expired, used or incomplete. A prepared upload accepts one PUT and
lasts one hour. If the upload failed, was used, timed out or never finished,
the agent has to prepare a fresh upload and send the file again.
The entry file is missing from the paths. The file that opens first, such as
index.html, must be one of the files sent. Check the folder, and the path the
agent used.
A path is refused. Rename the file or build with simpler names. The rules are in What you can share.
404, not found, or the link has expired. An update can’t revive a link that expired or was deleted. Share the files again to get a new link.