Netlify Drop Now Builds Framework Projects, Not Just Static Files

Netlify gave Drop, its drag-and-drop deploy tool, the biggest update since it launched in 2018: the tool can now detect a project’s framework and run the build for you, instead of only accepting files that are already built (Netlify Changelog, July 2026).

What changed

Drop has worked the same way since Netlify’s Phil Hawksworth introduced it in August 2018 as “the natural evolution of BitBalloon”: drag a folder of static HTML, CSS and JS onto the browser, get a live URL back (Netlify Blog, 2026). A React app, or any static site generator output that still needed a build step, was out of scope. You built it yourself, then dropped the result.

That limitation is gone. Drop the source folder for a project that needs a build, and if you’re signed in, Netlify now detects the framework and runs the build before publishing (Netlify Changelog). The refresh also makes a dropped site behave like any other Netlify project afterward: drag a new folder onto the Production deploys view to redeploy it, connect a custom domain, and keep building on it the normal way rather than treating it as a disposable demo (Netlify Changelog).

Why Netlify is investing in the onramp

The company’s own numbers explain the bet: among users who signed up in June 2026, more than 60% made their first deploy through Drop rather than a Git-connected project (Netlify Blog, “The 13-year story of Netlify Drop”). Drop opened to AI agents in 2023, and became the fastest way for a coding agent to publish a scaffolded project without walking through repository setup (Netlify Blog).

Both trends run into the same wall without a build step: a first-time user’s local project is rarely already-built static output, and neither is what most agents scaffold today. Framework detection turns Drop from a demo for finished HTML into a real first deploy for the kind of project people and agents actually start with.

Netlify is playing catch-up here, not leading

Vercel launched its own drag-and-drop deploy tool, Vercel Drop, on June 12, 2026, and it could already detect a framework and run the build from day one (Vercel Changelog). Netlify’s refresh lands six weeks later with the same capability, plus features Vercel Drop still lacks: a dropped Vercel project can’t be redeployed into the same project or connected to a custom domain, each new drop starts a fresh project (Vercel Docs). So the two tools solve the build-step gap at roughly the same time but diverge on what happens after: Netlify treats a dropped site as the start of a normal project, Vercel still treats it as disposable.

Our take

A prospective user who drags a Next.js or Astro project onto the old Drop and gets an error about a missing dist folder doesn’t blame the build step, they blame Netlify. Fixing that at the moment of first contact, before a signup form or a CLI, is a small change with an outsized effect on who sticks around. Netlify was behind Vercel on this specific feature, but shipping the redeploy and custom-domain path around it turns a one-off demo into a real onramp. Given that 60% of June’s new signups already chose drag-and-drop over Git, that’s the more valuable half of the update.