# Vercel Drop vs Cloudflare Direct Upload **Author:** Ben Sabic --- [Vercel Drop](https://vercel.com/drop) and [Cloudflare Direct Upload](https://developers.cloudflare.com/pages/get-started/direct-upload/) both let you deploy a project without connecting a Git repository. Upload your files, and you get a live URL on the platform's network. The main differences are whether the platform builds your project for you, whether you can move to Git-based deployments later, and how much of the workflow happens in the browser. Vercel Drop is a browser-only flow: drag a file, folder, or `.zip` onto [vercel.com/drop](https://vercel.com/drop) and Vercel handles the rest. It deploys both framework projects and static sites. When you drop a framework project such as Next.js, Vercel detects the framework, builds it, and publishes the result straight to production. No CLI is involved at any point, and you can connect a Git repository to the project afterwards for automatic deployments. Cloudflare Direct Upload publishes prebuilt assets to Cloudflare Pages via two methods: drag-and-drop in the Cloudflare dashboard or the Wrangler CLI. There is no build step on the platform, so you run your project's build command locally and upload the output directory. Direct Upload projects can receive new deployments to production or preview environments, but they can't be switched to Git integration later; moving to automatic deployments means creating a new project. The right choice usually comes down to whether your project needs a build, whether you want a CLI in the loop, and what you plan to do with the project after the first deploy. This guide compares the two across project types, workflow, limits, and the paths each one leaves open. * * * ## Comparing Vercel Drop and Cloudflare Direct Upload Both tools deploy a project without Git. The differences lie in build support, upload methods, limits, and where each project can go next. | Feature | Vercel Drop | Cloudflare Direct Upload | | ---------------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | Upload method | Drag and drop in the browser | Drag and drop in the dashboard, or the Wrangler CLI | | What you can upload | A file, folder, or `.zip` | Drag and drop: a folder or `.zip`; Wrangler: a folder only (no zips) | | Build step | Yes, Vercel detects your framework and builds it | No, you run the build command locally and upload the output | | Framework projects (e.g., Next.js) | Deploy the source directly | Build locally first, upload the output directory | | Deploy target | Straight to production with a live URL | Production or preview at `.pages.dev` | | Updating a project | Each drop creates a new project | Create new deployments into the same project | | Homepage handling | If there's no root `index.html`, you pick which page loads at `/` | Serves the uploaded output as-is | | Server-side code | Framework server features build as part of the drop | Drag and drop doesn't compile a `functions` folder; use Wrangler, or a `_worker.js` file | | Git afterward | Connect a Git repository to the project for automatic deployments | Not available; Direct Upload projects can't switch to Git integration | ### How each upload works With Vercel Drop, you go to [vercel.com/drop](https://vercel.com/drop), drag in a file, folder, or `.zip`, choose the Vercel team and a project name, and select **Deploy**. Vercel creates a new project, uploads your files, detects and builds your framework if there is one, and publishes straight to production. You get a live URL when it finishes. With Cloudflare Direct Upload, you first run your project's build command locally to produce the output directory. From the dashboard, you go to **Workers & Pages**, create a new Pages application with **Drag and drop your files**, name the project, and upload the folder or `.zip`. From the CLI, you run `npx wrangler pages project create` and then `npx wrangler pages deploy `. Either way, the site serves from `.pages.dev`. In practice, reach for Vercel Drop when you have source code (framework or static) and want a browser-only path to production. Reach for Cloudflare Direct Upload when you've already built your assets and want to keep deploying new versions into the same Cloudflare Pages project, especially from a CI pipeline via Wrangler. * * * ## Where Vercel Drop goes deeper Vercel Drop's strengths come from treating a drop like any other Vercel deployment: framework builds, zero tooling, and a project with room to grow. ### Framework projects build automatically Vercel detects your framework and runs its build for you, so you can drop a Next.js project's source code and get a working application, server features included. This covers exports from AI builders like [Bolt.new](https://vercel.com/kb/guide/bolt-vercel-drop), which produce framework projects rather than static output. Cloudflare Direct Upload has no build pipeline; its prerequisites direct you to run the appropriate build command before uploading, which reintroduces the local setup that no-Git deployment is meant to avoid. ### No CLI at any point The entire Vercel Drop flow happens in the browser: drag, name, deploy. Cloudflare's drag-and-drop covers the basic case, but parts of Direct Upload are implemented in the Wrangler CLI. Deploying a `functions` folder requires Wrangler, zip uploads aren't supported through Wrangler while folder limits are higher there, and changing a Direct Upload project's production branch requires a call to the Cloudflare API. With Vercel Drop, nothing about the deploy depends on installed tooling. ### Connect Git when you're ready A dropped project is a standard Vercel project, so you can [connect a Git repository](https://vercel.com/docs/git) to it afterwards and get automatic deployments on every push, with the project and its URL unchanged. Cloudflare states this path is closed for Direct Upload projects: you cannot switch to Git integration later, and moving to automatic deployments means creating a new project. With Vercel Drop, the first deploy doesn't lock in the workflow. ### Choose your homepage when there's no index.html For a static site with no `index.html` at the top of the folder, Vercel asks which page people should see first and lets you pick from a **Root (/)** menu, or choose **No root page**. Every file is still served at its own path either way. Cloudflare Direct Upload serves the uploaded directory as-is, so the structure of your output determines what loads at the root. ### No published file count or size caps Vercel Drop doesn't publish per-file or file-count limits; files upload from your browser, so larger folders take longer on slower connections. Cloudflare's drag-and-drop cap is 1,000 files with a 25 MiB maximum per file, and an oversized file can't be replaced individually: you delete it or reupload the entire project. Wrangler raises the count to 20,000 files but keeps the 25 MiB per-file cap. * * * ## Where Cloudflare Direct Upload goes deeper Cloudflare Direct Upload's strengths come from being a repeatable pipeline for a single project: redeploys, preview environments, and a CLI for automation. ### New deployments into the same project After creating a Direct Upload project, you select **Create a new deployment** to publish a new version of the same site to production or preview. Vercel Drop creates a new project for each drop and doesn't redeploy to an existing one, so iterating on a Vercel Drop project requires connecting to Git or using the [Vercel CLI](https://vercel.com/docs/cli) for subsequent deployments. ### Preview environments with branch aliases Direct Upload deployments can target a preview environment, and Wrangler deploys with `--branch` get an alias at `..pages.dev`. This gives you a production/preview split without Git. Vercel Drop publishes to production; preview deployments on Vercel include [Git integration](https://vercel.com/docs/git) or CLI support. ### A CLI path for CI pipelines Wrangler makes Direct Upload scriptable: `wrangler pages deploy` works with CI providers like GitHub Actions, which suits teams that build on their own platform and use Cloudflare only for hosting. The closest Vercel equivalent is the [Vercel CLI](https://vercel.com/docs/cli), not Vercel Drop itself, which is deliberately a browser-only tool. * * * ## When to choose Vercel Drop or Cloudflare Direct Upload The decision comes down to what you're uploading, what tooling you accept, and where the project should go after the first deploy. | If your workload looks like... | Choose | Why | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------ | --------------------------------------------------------------------------------------------------- | | Deploying a framework project (e.g., Next.js) without building it yourself | Vercel Drop | Vercel detects the framework and builds it for you | | Shipping an export from an AI builder like [Bolt.new](https://vercel.com/kb/guide/bolt-vercel-drop), [Claude Design](https://vercel.com/kb/guide/claude-design), or [Google Stitch](https://vercel.com/kb/guide/google-stitch-vercel-drop) | Vercel Drop | Zips deploy directly, and framework exports build automatically | | A browser-only deploy with no CLI or local build | Vercel Drop | Drag, name, and deploy; nothing depends on installed tooling | | A prototype you may later grow into a Git-connected project | Vercel Drop | Connect a repository afterwards; Direct Upload projects can't switch to Git | | Re-publishing prebuilt assets into the same project repeatedly | Cloudflare Direct Upload | New deployments target the existing project, production or preview | | Uploading build output from your own CI pipeline | Cloudflare Direct Upload | Wrangler scripts the deploy from GitHub Actions and similar tools | | Very large prebuilt sites | Vercel Drop | No published file count or per-file size caps, vs 1,000 files and 25 MiB per file via drag and drop | Teams shipping framework projects, AI tool exports, or anything that needs a build get the most from Vercel Drop, since the build happens on the platform, no CLI is required, and the project can graduate to Git-based deployments without being recreated. Teams uploading prebuilt assets who want to keep deploying new versions to a single Cloudflare Pages project, particularly from CI via Wrangler, will find Cloudflare Direct Upload a natural fit. * * * ## Resources and next steps - Try it at [vercel.com/drop](https://vercel.com/drop), or read the [Vercel Drop documentation](https://vercel.com/docs/drop) for how uploads, framework detection, and homepage selection work. - [Connect a Git repository](https://vercel.com/docs/git) to a dropped project to get automatic deployments on every push. - Use the [Vercel CLI](https://vercel.com/docs/cli) for scripted deployments from your terminal or CI/CD pipeline. - For the Cloudflare side, see the [Direct Upload documentation](https://developers.cloudflare.com/pages/get-started/direct-upload/) for the Wrangler and drag-and-drop flows, limits, and troubleshooting. - Learn how [Cloudflare on Vercel compares against Netlify](https://vercel.com/kb/guide/next-js-on-vercel-vs-cloudflare). --- [View full KB sitemap](/kb/sitemap.md)