Early preview · API key required

Made something?
Make it a link.

A website. A demo. That file you need to share. Give your work a home on the web, with a link that’s ready to go.

For people who make things. And the agents helping them.

A little less “how do I send this?”Example
my-project3 files
  • HTMLindex.html
  • CSSstyle.css
  • JSapp.js
Drop files. Share a link.
Your work, on the webmy-project.dropzoom.link

An example URL. Your publication gets its own name.

Put a link to it.

From local to linked

Less setup.
More sharing.

Bring your finished files. DropZoom takes care of putting them online.

  1. Bring your work

    Choose files or a website folder in the dashboard. For a web app, use its built output.

  2. Give it a home

    Connect your publishing key, choose a name and publish. Add a visitor password when you need one.

  3. Send the link

    Open the HTTPS link and share it. Visitors need no publishing key; protected links ask for a password.

A browser for you. An API for your agent.

Your agent makes it.
DropZoom shares it.

Give your agent a built folder and let it publish through the CLI or HTTP API. Get a URL back, update the same link, and roll back to a retained version when you need to.

Read the agent instructions
Publish from the CLI
dropzoom publish ./dist --title "My project"

After installing the CLI, set EDGE_PUBLISH_API to https://publish.dropzoom.link and supply EDGE_PUBLISH_KEY through your secret store.

JSON results. A shareable URL. Your workflow.

Small details. Useful possibilities.

A link you can keep
working with.

New version. Same URL.

Use the CLI or API to replace a publication’s files while keeping the link you already shared.

A password, if you need it.

Add a shared visitor password to a publication. Without one, anyone with the link can open it.

Sites and everyday files.

HTML opens as a website. File collections get a simple listing for viewing or downloading.

Before you drop in

Good to know.

Can I start publishing right away?

DropZoom is currently an early preview for people with an operator-issued publishing key. If you already have a key, open the dashboard. Otherwise, ask the person who invited you for access. Self-service signup is not available yet.

What can I put on DropZoom?

Static websites, built front-end apps, demos, HTML reports, PDFs and other files. Build your app before publishing. DropZoom hosts the result; it does not generate a site or run your server code.

Are my links private?

Publications are public by default. You can set a visitor password, but this early preview is intended for non-sensitive content. Never upload credentials, secrets or files you do not have permission to share.

Can I update something I’ve already shared?

Yes. The CLI and HTTP API can update the files at an existing URL and roll back to retained versions. The browser dashboard currently creates publications, lists them, manages passwords and deletes them.

Does my agent need my Cloudflare credentials?

No. Once the service is installed, publishing uses a DropZoom application key. Your agent can use the CLI or HTTP API without your Cloudflare account token.

The next thing you share

Drop it. Link it. Send it.

Open dashboard