Upload from your computer
Drag, drop, pick a strategy, click upload. This page covers every variation of "I have a local file and I want it on Walrus."
Three ways to add files
Drag any file from Finder / Explorer onto the wizard's drop zone. Multiple files at once are fine.
Click "Pick files" and use your OS file picker. Hold Shift / Cmd to select multiple.
Copy a file in your OS (Finder, screenshot tool) and Cmd+V in the wizard. Useful for quick screenshot uploads.
Step-by-step
1. Click "+ New Data Stream"
From any page, click Upload in the sidebar or the + New Data Stream
button. The wizard opens on Step 1: Source with a drag-and-drop zone.
2. Add your file(s)
Drop the file(s). The zone shows a green outline; you'll see a list of what
was picked up. Click any row's ✕ to remove it. Click the empty area to add
more.
3. Pick a strategy (only if you have >1 file)
For a single file, the wizard skips this and goes straight to Config.
For multi-file uploads, pick an Upload Strategy:
N files = N independent blobs, N on-chain register transactions. Recommended for most uses.
Packs all files into one tar archive. One blob, one transaction. Cheaper, but you can only fetch the whole archive.
Auto-picked when all files fit under 10 MiB. One blob, N retrievable patches. Best of both — cheap upload, granular fetch.
Multi-file uploads goes deeper into when to pick each strategy.
4. Configure (Step 2)
Three fields matter here:
How long Walrus keeps your bytes. 1 epoch = ~24h testnet / ~14 days mainnet. Slider goes from 1 up to your plan's cap.
Each file gets its own input with the OS filename pre-filled. Edit any to override what's recorded on-chain. Empty input falls back to the OS name.
Comma-separated Sui addresses to grant decrypt access at upload time. You can add or remove viewers later from the Sharing page.
5. Transform & Store (Step 3)
The wizard auto-detects file type. Tabular files (CSV, JSON, Parquet, Excel) get the Transform Pipeline — drag steps to filter, mask, aggregate, etc. Binary files (images, video, PDFs, archives) skip transforms entirely and upload byte-for-byte.
Click Upload to Walrus to start.
What you see during upload
The progress bar at the bottom of Step 3 reads:
The MB count is real — those are bytes the browser has handed to the network, not a fake timer. Bar transitions:
| 0% | starts when you click Upload | | 10% | reading file from disk | | 50% | done reading; encrypting (if SEAL is on) | | 60-80% | publisher PUT — fills linearly with bytes uploaded | | 80% | publisher returned the blob id | | 80-95% | wallet popup for on-chain register transaction | | 95-100% | transaction landed; refetching state |
A wallet popup appears around 80% asking you to sign register_blob.
Approve. The bar finishes, the wizard shows a success card, and you can
either close (Done — View History) or upload another file.
Where your file ends up
After upload:
Your inventory. Click any blob to see its id, size, epochs left, and open it in the Walrus Explorer.
Chronological log of every blob registered, with the Sui transaction digest for each upload.
Limits & defaults
| Value | |
|---|---|
| Max single-file size | 500 MiB (publisher path) |
| Files larger than 500 MiB | Auto-route through "direct-to-node" path (different progress UI) |
| Quilt auto-strategy | All selected files ≤ 10 MiB each |
| Default epochs | 1 (cheapest) |
| Max epochs | Set by your plan |
Common gotchas
You connected via Google OAuth but the dapp lost the Sui address. Refresh the page; if it persists, sign out and back in.
Session expired. Click the auth badge in the top-right ("Try Again") and re-sign.
Fixed in the latest release. If you still see this, hard-refresh (Cmd+Shift+R) to pick up the new code.
Publisher returned but the wallet popup may have been blocked. Check your wallet extension for a pending signature request.