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.

Is the Teams attachment cap really 250 MB?

For direct file attachments, yes. OneDrive-backed shares inside Teams can carry much larger files, but those go through SharePoint permissions and may not work cleanly for external guests.

Why does the file work for one teammate and not another?

External guests, federated tenants, and recipients on different mail domains may hit additional tenant policies. A plain HTTPS link sidesteps every one of those checks.

Will a quik.space link be blocked by my IT policy?

Some tenants block unfamiliar domains. quik.space is not on common blocklists. If your tenant filters unfamiliar links, ask IT to allow quik.space.

Does the recipient need a Microsoft account?

No. The link opens in any browser, no Microsoft account required.

What about a 1 GB file?

$5 one-shot for any single file between 500 MB and 5 GB. No subscription.

teams attachment limit

Teams attachment limit.

Microsoft Teams caps direct attachments at 250 MB per file. OneDrive-backed shares can carry more, but they pull the recipient into a SharePoint permissions flow, which is painful for external guests and federated tenants. The fix is to skip both paths and send a plain HTTPS link instead. Drop the file on quik.space, paste the link in the Teams chat, recipient clicks and downloads in their browser. No tenant permissions, no signup. The upload widget below is ready.

Drop a file.

Free up to 100 MB. We will give you a link in seconds.

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 →

What is happening

Microsoft Teams caps direct attachments at 250 MB per file. OneDrive-backed shares inside Teams can carry up to 250 GB.

Teams treats direct file attachments and OneDrive-backed shares as two different things. Drag a file into a chat and Teams uploads it into the linked SharePoint or OneDrive site and shares a link. The per-file cap on that path is the OneDrive cap, which is higher. But for direct attachments on consumer Teams or some federation paths, you may hit a 250 MB ceiling and get a clear error.

Common workarounds

Here is what most people try first, and where each option falls short.

Upload to OneDrive and share inside Teams: Drag into OneDrive first, share the link inside the Teams chat.; Downside. Recipient needs access to your OneDrive site, which may require IT to grant permissions. External users hit extra friction.
Compress to fit under 250 MB: Pack the file into a zip before attaching.; Downside. Video, photos, and PDFs barely shrink. Recipient still has to unpack.
Ask IT to raise the limit: Open a ticket to bump the tenant attachment cap.; Downside. Slow. Some IT teams will not raise the cap for an occasional send. Recipient's tenant may impose its own lower cap.
Email the file instead: Send by email as an attachment.; Downside. Email caps at 20 to 25 MB, much lower than Teams. Hits a worse wall.

The cleaner fix

Drop the file on quik.space, copy the link, paste it into the Teams chat. Recipient clicks the link, downloads in their browser. No tenant permissions, no SharePoint dance, no external-guest pop-ups. Free up to 100 MB. Supports single files up to 5 GB.

The upload widget at the top of this page is the same one on the homepage. Drop the file, copy the link, paste it where you wanted to attach. See pricing for the full table or how it works for the three-step explainer.

What we will not do

We do not read your file. We do not train AI on your file. We do not sell your file. Every upload is encrypted in transit over HTTPS and at rest. The share ID is an 8-character random string with roughly 218 trillion combinations, so the link is practically unguessable. After 72 hours plus a 7-day grace period, the bytes are permanently purged from storage and cannot be recovered.

Frequently asked

Is the Teams attachment cap really 250 MB?: For direct file attachments, yes. OneDrive-backed shares inside Teams can carry much larger files, but those go through SharePoint permissions and may not work cleanly for external guests.
Why does the file work for one teammate and not another?: External guests, federated tenants, and recipients on different mail domains may hit additional tenant policies. A plain HTTPS link sidesteps every one of those checks.
Will a quik.space link be blocked by my IT policy?: Some tenants block unfamiliar domains. quik.space is not on common blocklists. If your tenant filters unfamiliar links, ask IT to allow quik.space.
Does the recipient need a Microsoft account?: No. The link opens in any browser, no Microsoft account required.
What about a 1 GB file?: $5 one-shot for any single file between 500 MB and 5 GB. No subscription.

Hitting a different size cap? Here are nearby problem-state guides.

What is happening

Common workarounds

The cleaner fix

What we will not do

Frequently asked

Related