Step 1: prepare the files you want to deploy
Before opening the dashboard, decide whether you are uploading source code for SiteDropper to build or already-built static output. This choice affects what should go inside the ZIP file.
- For static HTML, include index.html and assets at the ZIP root.
- For built front-end output, ZIP the build directory such as dist, build, or out.
- For Node source projects, include package.json, the lockfile, source files, public assets, and config files.
- Do not include node_modules, local caches, .env files, or unrelated large folders.
Step 2: build Node projects before uploading
If your project uses Node, run the build locally before you package the ZIP. SiteDropper can build supported Node projects after upload, but a local build catches most dependency, TypeScript, and bundler problems before you wait on a remote build.
- Run npm install, pnpm install, or yarn install depending on your lockfile.
- Run npm run build, pnpm build, or yarn build.
- Fix build errors before creating the ZIP.
- If the app needs environment variables, write down the variable names so you can add them in SiteDropper instead of bundling secrets into the archive.
Step 3: create a project in the dashboard
Sign in to SiteDropper, open the dashboard, and create a new project. Give it a clear name and keep visibility as draft while you test the first deployment.
- Use a project name that matches the app or demo you are sharing.
- Add a short description if you expect to have multiple previews.
- Start with draft visibility so the first live URL is not public before you inspect it.
Step 4: upload the ZIP and wait for analysis
Drag the ZIP into the upload area or choose it with the file picker. SiteDropper creates a version for the archive and analyzes it to detect the runtime, framework, commands, root directory, and port.
- If analysis detects the wrong root directory, update the configuration before building.
- If the project needs environment variables, add them before deployment.
- For server apps, confirm the start command and port look correct.
Step 5: build, deploy, and open the live URL
Start the build after analysis looks right. When the build succeeds, deploy it and open the generated SiteDropper URL. If the build fails, check the build logs for missing dependencies, incorrect scripts, or files that were left out of the ZIP.
- Smoke test the home page and any critical route after deployment.
- Keep the project private or draft until the link is ready to share.
- Delete temporary test projects when you no longer need them.