Storing and sharing files
Put a file on Zaryn and get a link anyone can open. How much space you have, what "public" means here, and how to remove a file.
Search for a command to run…
Put a file on Zaryn and get a link anyone can open. How much space you have, what "public" means here, and how to remove a file.
The Storage page (in the top menu, or zaryn.xyz/storage) is where everything you keep on Zaryn comes together: your repositories, the files you share by link, and your packages, each with how much of your plan it uses.
That's all. The person you send it to doesn't need an account. The link looks like this:
https://ipfs.io/ipfs/bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi?filename=report.pdfYour files stay under My files, newest first, with Copy link and Open next to each one.
Files here are public. Anyone who has the link can open the file, and anyone who has opened it may keep a copy. Don't upload passwords, private photos, contracts or anything else you wouldn't post publicly. For private work, use a private repository.
Files are kept on IPFS, a public network of computers that find files by what they contain instead of where they are. Each file gets an ID made from its contents (a CID, shown under the ▾ button next to the file).
Need one link that always shows your latest version? That's an address you can update (IPNS), under Advanced on the Storage page.
| Free | Premium | |
|---|---|---|
| Files you share by link | 500 MB, up to 50 files | much more, see plans |
| Repositories | 2 GB, files up to 250 MB | more |
| Packages | 500 MB | more |
The bars at the top of the Storage page show what you've used. When a bar turns amber you're past 75%, and Zaryn sends you a notification when you reach a limit.
Open the ▾ menu next to the file and press Stop hosting, then confirm. The file no longer counts against your space and Zaryn stops keeping it online. Because IPFS is a shared network, a copy someone else made may keep working for a while; that's why private things don't belong here.
The same thing over the API, with a personal access token that has the pin:write scope:
# upload: the response has the cid and a ready linkcurl -X POST "https://api.zaryn.xyz/v1/pins?name=report.pdf" \ -H "Authorization: Bearer $ZARYN_TOKEN" \ --data-binary @report.pdf# list your files and your spacecurl -H "Authorization: Bearer $ZARYN_TOKEN" https://api.zaryn.xyz/v1/pins# stop hosting onecurl -X DELETE -H "Authorization: Bearer $ZARYN_TOKEN" https://api.zaryn.xyz/v1/pins/<cid>Each upload comes with a receipt signed by the server (which file, how big, when) that anyone can check later. The Advanced tools on the Storage page cover the rest: checking a file against public gateways, linking a file to the commit it was built from, manifests for AI agents, releases and datasets, and IPNS addresses. How Zaryn keeps files available across servers is in Pinning and IPFS Cluster.