Walrus Console FAQ
Common questions about Walrus Console. For the concepts behind the answers, read What is Walrus Console?, and for a hands-on walkthrough, follow the Quick Start.
Walrus Console is available on Mainnet through a closed, invite-only beta. Answers below mark the capabilities that arrive at general availability (GA) or later.
Getting started
What Console is, how you get in, and what the free tier covers.
What is Walrus Console?
A place to store files on Walrus and manage them from a browser or from code. You sign in with a Google or Apple account, mint an API key, and upload. Console handles the parts you would otherwise do by hand: account and wallet provisioning, storage payment, and metadata.
How do you sign in?
With a Google account or an Apple account. Console uses Sui zkLogin to derive a Sui address from your identity and provisions a wallet for you, so you never handle private keys to get started. Identities from different providers map to separate accounts. See Authentication and Accounts.
How much can you store for free?
Console keeps a perpetual free tier, capped at 5 GB of total storage. See Billing and the free tier.
What happens when you hit the limit?
Uploads stop at the cap. Usage-based billing and a paid top-up path arrive after GA.
Your files
How long files last, how large they get, and which ones Console shows you.
Do your files expire?
Files you upload through Console renew automatically, as long as your wallet stays active. Active means the wallet made at least one Walrus transaction within a recent activity window. Files you put on Walrus outside Console, through the CLI or an SDK, need manual renewal instead. See Storage epochs.
What is the largest file you can upload?
The per-upload cap is 100 MiB. An upload above the cap fails with a payload_too_large error. See Errors.
Can Console see files you already uploaded with the CLI or an SDK?
Not yet. Console shows what you uploaded through Console, and adds discovery of your existing blobs after GA.
Can you delete a file?
You can delete any file you uploaded through Console, from the web app or through the API. Files you stored outside Console do not appear in Console yet, so delete those with the CLI or an SDK.
Building on Console
Programmatic access, agent clients, and what a team shares today.
What is the API key for?
Everything programmatic. The API, the MCP server, and uploads from your own code all authenticate with it. You mint keys under Integrations in Console, choose a read_write or read_only role for each, and revoke a key whenever you want. Pick a plain API key for the API, the MCP server, and your own code; a Management API key mints further keys programmatically but cannot upload, download, or manage assets. Console shows the full key once, at creation, so store it like a cloud secret access key. See API keys and roles.
How do you use Console with Claude Code or Cursor?
Through the Walrus Console MCP server, the npm package @mysten-incubation/walrus-console-mcp, which publishes with the Console beta. It exposes file and bucket operations as tools your agent calls. Run npx -y @mysten-incubation/walrus-console-mcp install and give it the two values Console showed you when you minted the key: the hbr_ API key and the suiprivkey1 service private key. The installer stores them outside your client configuration, so no key goes in the MCP config file. See Connect AI clients with the MCP server.
Can your team share one account?
Not yet. Through beta and at GA, an account belongs to one person. Team Spaces, which give a group a shared API key and roles that an admin manages, arrive after GA.
What is Walrus Memory, and is it in Console?
Walrus Memory is a separate Walrus product: a portable memory layer for AI agents. Console adds Memory as an asset type at GA, where you browse, search, and manage your agent memory without touching the SDK. Console plans memory storage renewal in a later release. See Asset types.
Does Console work on mobile?
Not yet. Console supports desktop browsers.