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.

Should I pack external resources before sending?

Yes. In Blender, File > External Data > Pack All Into File. Otherwise the recipient sees pink missing textures.

Will geometry nodes setups survive?

Yes. The .blend is byte-identical.

Will simulation caches be included?

Bake caches live in a separate folder by default. Either bake to file and pack, or zip the project folder.

Add-on data inside the .blend is preserved. The recipient needs the same add-ons installed to interact with that data.

.blend3d

How to send a Blender file.

Blender packs everything into one .blend if you ask it to. The result is often 500 MB or more. quik.space stores the .blend byte-for-byte and gives the recipient a clean download with packed textures intact, ready to open and render.

Drop your Blender file here.

Free up to 100 MB. No signup, no email needed.

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 a Blender file?

Blender file files use the .blend extension with no single standard MIME type. The format sits in the 3d category. Typical files run 10 MB - 2 GB, which is well above what most email services will accept as an attachment.

Why you can’t email a Blender file

Blender .blend files with packed textures, simulation caches, and complex meshes can hit 1 to 2 GB. Email is not in the conversation.Slack, Discord, and most other workplace tools have similar caps, often around 1 GB for free tiers and with aggressive per-channel storage limits. Even when the file fits, it counts against the recipient’s mailbox quota forever.

How quik.space handles Blender file

quik.space stores the .blend byte-for-byte. Packed textures, render settings, geometry nodes, scene state, all preserved. The recipient opens it in Blender with everything in place. The share page does not render 3D scenes inline. The recipient downloads the file and opens it in the matching DCC.

The file lives for 72 hours by default and then enters a 7-day grace period. We do not train AI on your files. We do not share them with third parties. After grace, the bytes are permanently purged from storage. Read the full policy on privacy.

Common use cases

Send a finished Blender scene to a renderer
Hand off a Blender rig to an animator
Share a Blender geometry-nodes setup with a colleague
Backup a Blender project before a major refactor

Frequently asked

Should I pack external resources before sending?: Yes. In Blender, File > External Data > Pack All Into File. Otherwise the recipient sees pink missing textures.
Will geometry nodes setups survive?: Yes. The .blend is byte-identical.
Will simulation caches be included?: Bake caches live in a separate folder by default. Either bake to file and pack, or zip the project folder.
What about add-ons?: Add-on data inside the .blend is preserved. The recipient needs the same add-ons installed to interact with that data.

Related file types

Looking for size-based pages instead? See the pricing table or read the full FAQ.