Yes. Up to 100 MB per file and up to 3 files per request are free. Files expire in 72 hours unless you pay $2 to extend by 30 days, or pay to group them into a 30-day space for $5.

Do I need to sign up?

No. Anonymous use is the default. You can optionally attach your email so you can recover files later if you lose the share link.

How long do files last?

Free files expire in 72 hours. After that there is a 7-day grace period during which a $2 extend will bring the file back for 30 more days. After the grace period the storage is permanently purged.

Can AI agents use quik.space?

Yes. quik.space exposes an MCP (Model Context Protocol) server and accepts the x402 standard for stablecoin micropayments on Base. Agents do not need API keys or signup — their wallet is their identity.

What file types are supported?

Any file up to 5 GB. The recipient page renders inline previews for images, audio, video, PDFs, markdown, HTML (sandboxed), Microsoft Office docs, and plain text or code.

Can I upload from CI?

Yes. quik.space exposes an MCP server at /mcp with upload_file, get_file_info, and extend_file. Paid actions return HTTP 402 with a payment requirement; your agent retries with X-Payment-Proof after sending USDC on Base. There is no API key.

What's the largest artifact I can upload?

5 GB per file. For larger builds, split into per-platform artifacts or run a release archive split.

Will my build artifact be used for AI training?

No. quik.space does not train any model on user files. Proprietary builds, internal docs, unreleased binaries: not training data.

Can I keep an artifact alive for a sprint?

Yes. $2 extends a file by 30 days, renewable. For longer than that, push to your real artifact registry; quik.space is a transmission surface, not artifact storage.

MCP is the supported programmatic surface today (JSON-RPC 2.0). A traditional REST API is on the roadmap. For now, your CI can either drive MCP or upload over the web form via headless browser.

File sharing for developers.

Your CI produces a 600 MB build artifact and the reviewer just wants curl-able bytes. quik.space gives you a public read-by-URL link for $1 to $5, no IAM key, no Drive request. The MCP server at /mcp lets agents pay in USDC on Base via x402 to upload programmatically. No API key, no signup, no AI training on your binaries.

Drop a file.

Free under 100 MB. $1 up to 500 MB. $5 up to 5 GB. No signup, no AI training on your files.

or click anywhere to choose

No email means no recovery. If you lose this link, we can't get you back to this file.

Price scales with file count, up to 25 files. Shown once. 7-day expiry.

Have a code? Open with code →

The developer problem

Your CI produces a 600 MB build artifact and you need a reviewer to download it. S3 needs an IAM key. Google Drive needs a permission request. Slack chokes at 1 GB and shoves it behind a generated URL that expires after a download. The reviewer just wants curl-able bytes.

How quik.space fits in

quik.space hands you a public read-by-URL link the reviewer can curl in one line. The MCP server at /mcp lets your CI pay agents in USDC on Base via x402 to upload artifacts programmatically, no API key, no signup. Anyone with the link downloads, no auth dance.

An example workflow

Drop your build artifact. Manual: drag onto quik.space. CI: call the MCP server with upload_file and x402 if the artifact is over 100 MB.
Copy the share URL into your CI logs or Slack. The URL is the full /u/[id] path, curl-friendly. Paste into the PR description or post in the review channel.
Reviewer downloads, no auth dance. curl -O https://quik.space/u/abc12345. No login, no token, no Drive request.

What you’ll typically send

File types developers usually ship through quik.space:

Build artifacts (tarballs, zips, .ipa, .apk)
Container images and OCI tarballs
Log bundles and core dumps
Source-code archives
Documentation PDFs and exports

Typical delivery size sits around 50 MB to 2 GB per artifact. That maps to the free tier (under 100 MB), the $1 Large upload bracket (under 500 MB), or the $5 XL upload bracket (up to 5 GB). See pricing for the full table.

Private by default

quik.space does not train AI on your files. We do not read them. We do not index them. The file is visible only to whoever holds the share link, and it auto-deletes when the clock runs out. WeTransfer changed its terms in July 2025 to allow AI training on user files. We made the opposite call and put it in writing.

Frequently asked

Can I upload from CI?: Yes. quik.space exposes an MCP server at /mcp with upload_file, get_file_info, and extend_file. Paid actions return HTTP 402 with a payment requirement; your agent retries with X-Payment-Proof after sending USDC on Base. There is no API key.
What's the largest artifact I can upload?: 5 GB per file. For larger builds, split into per-platform artifacts or run a release archive split.
Will my build artifact be used for AI training?: No. quik.space does not train any model on user files. Proprietary builds, internal docs, unreleased binaries: not training data.
Can I keep an artifact alive for a sprint?: Yes. $2 extends a file by 30 days, renewable. For longer than that, push to your real artifact registry; quik.space is a transmission surface, not artifact storage.
Is there a REST API?: MCP is the supported programmatic surface today (JSON-RPC 2.0). A traditional REST API is on the roadmap. For now, your CI can either drive MCP or upload over the web form via headless browser.