Product
Images stay in storage you own.
ZevContent holds the connection and signs the upload. The files never touch us.
Start free
How it works.
-
Connect a bucket you own
ZevCloud, Amazon S3, Cloudflare R2, MinIO, or anything S3 compatible. On ZevCloud it is two clicks and no key to copy.
-
Upload straight from the browser
ZevContent signs the request; the bytes go to your bucket without passing through us.
-
Read the URL back
A public bucket returns a permanent URL. A private one returns a signed URL and the moment it expires.
- Any S3 compatible store
- ZevCloud, Amazon S3, Cloudflare R2, MinIO, or your own.
- Two clicks on ZevCloud
- Pick a bucket. No key to copy, no CORS rule to write.
- Straight from the browser
- Uploads go direct to your bucket with a signed request.
- Alt text and dimensions
- Measured on upload, returned with every image.
- 5
- storage providers, including your own
- 0
- bytes of yours pass through us
- 0
- bandwidth we can ever bill you for
Frequently asked questions
What people ask about media before they commit to it.
Do my images go through ZevContent?
No. We hold the connection and sign the upload; the bytes travel from the browser straight to your bucket. We never store or serve your files.
What happens to my images if I leave?
Nothing. They are already in a bucket you own, under keys you can list. Leaving means changing a key, not exporting anything.
Do I need to write a CORS rule?
On ZevCloud, no: connecting a bucket sets it up. On another provider you add one rule allowing PUT from your dashboard origin, and the connection test tells you if it is wrong.
Start with a project and a key.
Free while we are in beta. Paid plans when we ship them, and never a surprise bill.